[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110308053226.7300e65d@debxo>
Date: Tue, 8 Mar 2011 05:32:26 +0000
From: Andres Salomon <dilinger@...ued.net>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Sergei Shtylyov <sshtylyov@...sta.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Amit Kucheria <amit.kucheria@...onical.com>,
Russell King <linux@....linux.org.uk>,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
Sascha Hauer <kernel@...gutronix.de>,
Uwe Kleine-K?nig <u.kleine-koenig@...gutronix.de>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: mx51_efika: update platform data for new mfd
changes
On Mon, 7 Mar 2011 14:47:00 +0000
Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:
> On Fri, Mar 04, 2011 at 09:58:56PM +0300, Sergei Shtylyov wrote:
> > Andres Salomon wrote:
>
> >>>> MFD changes in c738892f cause the mc13xxx_platform_data struct
>
> >>> Linus asks to also specify the commit summary in parens.
>
> >> Also, what? If there are changes to how patches should be
> >> submitted, please provide a reference
> >> (Documentation/SubmittingPatches should be updated, as well).
>
> > I have no time to rummage in the mail archives, sorry.
>
> There's been multiple discussions of this. The issue is that commit
> IDs only mean something in specific trees and go bad if someone
> rebases, and they aren't legibile by humans (so even if the commit is
> in something like Linus' tree the reader still needs a git repository
> to figure out what changes are being talked about).
Ah, thanks, that makes sense. Sergei's original statement was unclear
("...instead of just the commit ID" would've helped).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists