From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Andres Salomon <dilinger@queued.net>
Cc: "Sergei Shtylyov" <sshtylyov@mvista.com>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Amit Kucheria" <amit.kucheria@canonical.com>,
"Russell King" <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
"Sascha Hauer" <kernel@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: mx51_efika: update platform data for new mfd changes
Date: Fri, 04 Mar 2011 21:58:56 +0300 [thread overview]
Message-ID: <4D713670.70506@ru.mvista.com> (raw)
In-Reply-To: <20110304083822.0f40d120@debxo>
Hello.
Andres Salomon wrote:
>>> Note that this relies on stuff currently in mfd's next tree, but
>>> this is also a newer driver. I'm not sure which tree it should go
>>> through, as it's a problem that shows up in next.
>> This passage should be under --- tear line.
> What?
See Documentation/SubmittingPatches, section 15, "The canonical patch format".
>>> From: Andres Salomon <dilinger@queued.net>
>>> 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.
>>> to change. This changes one more (new) user of it, fixing a build
>>> error.
>>> Signed-off-by: Andres Salomon <dilinger@queued.net>
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx51_efika: update platform data for new mfd changes
Date: Fri, 04 Mar 2011 21:58:56 +0300 [thread overview]
Message-ID: <4D713670.70506@ru.mvista.com> (raw)
In-Reply-To: <20110304083822.0f40d120@debxo>
Hello.
Andres Salomon wrote:
>>> Note that this relies on stuff currently in mfd's next tree, but
>>> this is also a newer driver. I'm not sure which tree it should go
>>> through, as it's a problem that shows up in next.
>> This passage should be under --- tear line.
> What?
See Documentation/SubmittingPatches, section 15, "The canonical patch format".
>>> From: Andres Salomon <dilinger@queued.net>
>>> 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.
>>> to change. This changes one more (new) user of it, fixing a build
>>> error.
>>> Signed-off-by: Andres Salomon <dilinger@queued.net>
WBR, Sergei
next prev parent reply other threads:[~2011-03-04 19:00 UTC|newest]
Thread overview: 22+ 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:06 ` Andres Salomon
2011-03-04 16:14 ` Sergei Shtylyov
2011-03-04 16:14 ` Sergei Shtylyov
2011-03-04 16:38 ` Andres Salomon
2011-03-04 16:38 ` Andres Salomon
2011-03-04 18:58 ` Sergei Shtylyov [this message]
2011-03-04 18:58 ` Sergei Shtylyov
2011-03-07 14:47 ` Mark Brown
2011-03-07 14:47 ` Mark Brown
2011-03-08 5:32 ` Andres Salomon
2011-03-08 5:32 ` Andres Salomon
2011-03-04 19:46 ` Uwe Kleine-König
2011-03-04 19:46 ` Uwe Kleine-König
2011-03-07 8:53 ` Sascha Hauer
2011-03-07 8:53 ` Sascha Hauer
2011-03-11 20:44 ` Samuel Ortiz
2011-03-11 20:44 ` Samuel Ortiz
2011-03-15 8:33 ` Sascha Hauer
2011-03-15 8:33 ` Sascha Hauer
2011-03-24 20:27 ` Andres Salomon
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=4D713670.70506@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=amit.kucheria@canonical.com \
--cc=dilinger@queued.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.