From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH 1/2] mm: Fix task_nommu build regression in linux-next Date: Tue, 6 Mar 2012 12:39:59 -0800 Message-ID: <20120306123959.1921bcca.akpm@linux-foundation.org> References: <1331045377.17099.2.camel@deneb.redhat.com> <1331064994-6693-1-git-send-email-siddhesh.poyarekar@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from mail.linuxfoundation.org ([140.211.169.12]:42340 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031036Ab2CFUkA (ORCPT ); Tue, 6 Mar 2012 15:40:00 -0500 In-Reply-To: <1331064994-6693-1-git-send-email-siddhesh.poyarekar@gmail.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Siddhesh Poyarekar Cc: Mark Salter , linux-next , linux-kernel , Paul Gortmaker , Oleg Nesterov On Wed, 7 Mar 2012 01:46:33 +0530 Siddhesh Poyarekar 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//maps").