From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
devicetree-discuss@lists.ozlabs.org,
vladimir.barinov@cogentembedded.com
Subject: Re: [PATCH v2 0/4] R-Car SATA driver and platform data
Date: Mon, 25 Feb 2013 17:08:19 +0400 [thread overview]
Message-ID: <512B6243.9060808@cogentembedded.com> (raw)
In-Reply-To: <20130219034210.GA7701@verge.net.au>
Hello.
On 19-02-2013 7:42, Simon Horman wrote:
>> Here's the v2 of the set of 4 patches against the Simon Horman's renesas.git
>> repo, 'next' branch:
>> [1/4] libata: add R-Car SATA driver
>> [2/4] ARM: mach-shmobile: r8a7779: SATA DT configuration
>> [3/4] ARM: mach-shmobile: r8a7779: add SATA support
>> [4/4] ARM: mach-shmobile: marzen: add SATA support
>> Patch 1 also applies to the 'upstream' branch of Jeff Garzik's libata-dev.git
>> repo.
>> Patch changes since the initial posting are reported in the individual patches.
> Thanks, I have updated topic/r-car-sata and verified
> that the SATA driver is successfully initialised for both
> non-DT and DT boot.
The SATA driver have been already merged by Linus:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=163cf81d266f017d718ef786fbbb6b2513ce7ec3
Can we merge the rest of the patches in this merge window?
WBR, Sergei
next prev parent reply other threads:[~2013-02-25 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 20:27 [PATCH v2 0/4] R-Car SATA driver and platform data Sergei Shtylyov
2013-02-19 3:42 ` Simon Horman
2013-02-25 13:08 ` Sergei Shtylyov [this message]
2013-02-26 0:07 ` Simon Horman
2013-02-26 3:10 ` Kuninori Morimoto
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=512B6243.9060808@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=horms@verge.net.au \
--cc=jgarzik@pobox.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=rob.herring@calxeda.com \
--cc=vladimir.barinov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).