From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: davinci: mark spi_board_info arg to da8xx_register_spi as const
Date: Wed, 18 Apr 2012 23:57:20 +0530 [thread overview]
Message-ID: <4F8F0788.50600@ti.com> (raw)
In-Reply-To: <20120418173345.GA20039@pengutronix.de>
On 4/18/2012 11:03 PM, Uwe Kleine-K?nig wrote:
> Hi Sekhar,
>
> On Wed, Apr 18, 2012 at 09:55:03PM +0530, Sekhar Nori wrote:
>> On 3/31/2012 1:43 AM, Uwe Kleine-K?nig wrote:
>>> No further changes necessary
>>>
>>> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix•de>
>>
>> Thanks for the patch. I extended this to include some other spi
>> registration routines being used for DM355 and DM365. Here is the
>> updated patch. Can you see if this is OK.
> apart from being exchange-or-outlook-scrambled it looks ok. But actually
> checking that the compiler doesn't yield any new warnings would be a
> better check ...
Hmm, I actually used Thunderbird; but sorry about the scrambling. Yes, I
did check for new warnings.
>
>> Also, please also Cc davinci-linux-open-source at linux.davincidsp.com on
>> davinci patches.
> I asked get_maintainer.pl who to Cc (and cut the list down a bit). Maybe
> get_maintainer.pl doesn't include
> davinci-linux-open-source at linux.davincidsp.com because it's
> subscribers-only?
This should be fixed with the v3.4 kernel as the list is now marked as
"moderated". Can you try with the latest kernel?
Thanks,
Sekhar
prev parent reply other threads:[~2012-04-18 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 20:13 [PATCH] ARM: davinci: mark spi_board_info arg to da8xx_register_spi as const Uwe Kleine-König
2012-04-18 16:25 ` Sekhar Nori
2012-04-18 17:33 ` Uwe Kleine-König
2012-04-18 18:27 ` Sekhar Nori [this message]
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=4F8F0788.50600@ti.com \
--to=nsekhar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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