Messages in this thread | | | Date | Wed, 7 Mar 2012 09:01:15 +0530 | Subject | Re: [PATCH 1/2] mm: Fix task_nommu build regression in linux-next | From | Siddhesh Poyarekar <> |
| |
On Wed, Mar 7, 2012 at 2:09 AM, Andrew Morton <akpm@linux-foundation.org> wrote: > On Wed, 7 Mar 2012 01:46:33 +0530 > Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com> wrote: > >> Commit b7b2a0afacada237005068294cb0ccc49d32889e resulted in a build >> failure for nommu builds: > > Bare git commit IDs aren't very useful, because the ID of a patch can > be different in different trees. And in linux-next, the ID of a patch > can change over time. This is why we like to refer to commits using the > formulation b7b2a0afacad ("procfs: mark thread stack correctly in > proc/<pid>/maps").
Thanks, I'll keep this in mind.
-- Siddhesh Poyarekar http://siddhesh.in -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |