SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] R-Car SATA platform data
Date: Thu, 07 Mar 2013 03:20:55 +0000	[thread overview]
Message-ID: <20130307032055.GI9499@verge.net.au> (raw)
In-Reply-To: <5137D139.9010304@cogentembedded.com>

On Thu, Mar 07, 2013 at 02:28:57AM +0300, Sergei Shtylyov wrote:
> Hello.
> 
> On 03/01/2013 10:25 AM, Simon Horman wrote:
> 
> >
> >>Hello.
> >>
> >>    Here's the v4 of the set of now 3 patches (the driver itself has been merged
> >>since) against the Simon Horman's renesas.git repo, 'next' branch:
> >>
> >>[1/3] ARM: mach-shmobile: r8a7779: SATA DT configuration
> >>[2/3] ARM: mach-shmobile: r8a7779: add SATA support
> >>[3/3] ARM: mach-shmobile: marzen: add SATA support
> >>
> >>Patch changes since the initial posting are reported in the individual patches.
> >Thanks. I have refreshed the topic/r-car-sata branch of the renesas tree
> >accordingly. That branch still contains a copy of the "Add Renesas R-Car
> >on-chip 3Gbps SATA controller driver." but it should disappear once I rebase
> >(e.g. on v3.9-rc1).
> 
>    I see you have finally merged my patches to your 'next' branch, thanks.
> However, you've also merged Morimoto-san's patch to change from gic_spi()
> to gic_iid(), and I thought I'd recast patch 2/3 to make it use
> gic_iid() too.

Sorry for messing that up.

> How do we do now, do I need to send a new patch to convert to gic_iid()?

Yes, I think it would be best if you sent an incremental patch.

Sorry once again for the mix-up.

      reply	other threads:[~2013-03-07  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 19:32 [PATCH v4 0/3] R-Car SATA platform data Sergei Shtylyov
2013-03-01  7:25 ` Simon Horman
2013-03-06 22:28   ` Sergei Shtylyov
2013-03-07  3:20     ` Simon Horman [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=20130307032055.GI9499@verge.net.au \
    --to=horms@verge.net.au \
    --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