From: dilinger@queued.net (Andres Salomon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx51_efika: update platform data for new mfd changes
Date: Tue, 8 Mar 2011 05:32:26 +0000 [thread overview]
Message-ID: <20110308053226.7300e65d@debxo> (raw)
In-Reply-To: <20110307144700.GF1829@sirena.org.uk>
On Mon, 7 Mar 2011 14:47:00 +0000
Mark Brown <broonie@opensource.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).
next prev parent reply other threads:[~2011-03-08 5:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:06 [PATCH] ARM: mx51_efika: update platform data for new mfd changes Andres Salomon
2011-03-04 16:14 ` Sergei Shtylyov
2011-03-04 16:38 ` Andres Salomon
2011-03-04 18:58 ` Sergei Shtylyov
2011-03-07 14:47 ` Mark Brown
2011-03-08 5:32 ` Andres Salomon [this message]
2011-03-04 19:46 ` Uwe Kleine-König
2011-03-07 8:53 ` Sascha Hauer
2011-03-11 20:44 ` Samuel Ortiz
2011-03-15 8:33 ` Sascha Hauer
2011-03-24 20:27 ` Andres Salomon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110308053226.7300e65d@debxo \
--to=dilinger@queued.net \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).