From: egtvedt@samfundet.no (Hans-Christian Egtvedt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] avr32: fix build failures from mis-naming of atmel_nand.h
Date: Fri, 23 Mar 2012 08:38:50 +0100 [thread overview]
Message-ID: <20120323073850.GB31010@samfundet.no> (raw)
In-Reply-To: <4F6B316F.5080307@atmel.com>
Around Thu 22 Mar 2012 15:04:31 +0100 or thereabout, Nicolas Ferre wrote:
> On 03/22/2012 01:33 PM, Hans-Christian Egtvedt :
>> Around Thu 22 Mar 2012 01:18:40 -0400 or thereabout, Paul Gortmaker wrote:
<snipp Atmel NAND cleanup>
>>>> Yes, we need to fix this. But I would not like to see this
>>>> "platform_data/atmel.h" renamed: I think that this file was designed to
>>>> collect several common platform data (ie: not just NAND related).
>>>>
>>>> So maybe we should just rename the entry that exists in
>>>> mach-at32ap/include/mach/board.h
>>>> and remove all occurrences of platform_data/atmel_nand.h
>>>
>>> Funny, since this is what I did 1st before I re-read the original commit
>>> log in more detail. :) Oh well. Here is the alternate solution. You
>>> guys can pick whichever one you like best. I compile tested this one
>>> as well.
>>
>> I'll leave it to Nicolas to sign-off on this, but the changes look fine for
>> me.
>
> Ok, which way do you want to follow for inclusion in mainline? I take it
> through arm-soc?
I have not gotten my key signed by any kernel developers yet, so typically
I've asked people to take it through Andrew's tree.
<snipp>
--
HcE
prev parent reply other threads:[~2012-03-23 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 2:15 [PATCH] avr32: fix build failures from mis-naming of atmel_nand.h Paul Gortmaker
2012-03-21 7:26 ` Hans-Christian Egtvedt
2012-03-21 8:26 ` Nicolas Ferre
2012-03-22 5:18 ` Paul Gortmaker
2012-03-22 12:33 ` Hans-Christian Egtvedt
2012-03-22 14:04 ` Nicolas Ferre
2012-03-23 7:38 ` Hans-Christian Egtvedt [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=20120323073850.GB31010@samfundet.no \
--to=egtvedt@samfundet.no \
--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).