From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: Dhaval Vasa <dhaval.vasa@einfochips.com>
Cc: nico@cam.org, linux-kernel@vger.kernel.org, rabeeh@marvell.com,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH v2] [ARM] Kirkwood: Marvell OpenRD-Base board support added to v2.6.31-rc5
Date: Wed, 19 Aug 2009 16:18:59 +0200 [thread overview]
Message-ID: <20090819161859.5546c627@marrow.netinsight.se> (raw)
In-Reply-To: <4A8C02E9.2090701@einfochips.com>
On Wed, 19 Aug 2009 19:19:29 +0530
Dhaval Vasa <dhaval.vasa@einfochips.com> wrote:
> >> +static unsigned int openrd_base_mpp_config[] __initdata = {
> >> + MPP29_GPIO,
> > ^^^^^
> > There is trailing whitespace on this line
> >
> Nicolas has already applied this patch on his orion tree; it would be
> worth generating separate one for whitespace ? Suggest.
Maybe not, I'm not sure what the procedure is. I didn't realise it was
already there - I was looking at another git tree :-)
> > Also, I'd suggest merging "[PATCH v2] Kirkwood: Initialise SATA for
> > OpenRD-Base" into this one and resubmit it.
>
> Nicolas has already applied this patch on his orion tree. Should I
> re-submit now ?
Well, if it's already there I think it's fine as it is. I thought the
patch was still under consideration.
> Can you point me to your patch ?
I posted it about a month ago on this list, see:
http://www.spinics.net/lists/arm-kernel/msg70680.html
I guess you can apply the patch I sent in the last mail to the Orion
tree if it's acceptable - that's basically the diff between my old
patch and the new one you sent.
// Simon
next prev parent reply other threads:[~2009-08-19 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 12:07 [PATCH v2] [ARM] Kirkwood: Marvell OpenRD-Base board support added to v2.6.31-rc5 Dhaval Vasa
2009-08-19 13:18 ` Simon Kagstrom
2009-08-19 13:45 ` Simon Kagstrom
2009-08-19 13:49 ` Dhaval Vasa
2009-08-19 14:18 ` Simon Kagstrom [this message]
2009-08-19 14:58 ` Nicolas Pitre
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=20090819161859.5546c627@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=dhaval.vasa@einfochips.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=rabeeh@marvell.com \
/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