From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] ARM: shmobile: r8a7778: fix Ether device name
Date: Tue, 11 Jun 2013 19:49:40 +0000 [thread overview]
Message-ID: <51B77F54.8030001@cogentembedded.com> (raw)
In-Reply-To: <20130611074850.GE10440@verge.net.au>
Hello.
On 06/11/2013 11:48 AM, Simon Horman wrote:
>> While recasting commit 524219146a89aee5366326c225ccd71231419d89 (ARM: shmobile:
>> R8A7778: add Ether support), I made a typo in the platform device's name: used
>> underscore instead of hyphen.
>> However, there's now patch merged to net-next.git renaming the platform device
>> from "sh-eth" to "r8a777x-ehter", so it makes the most sense to change the name
>> straight to that one.
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> ---
>> The patch is atop of the 'renesas-next-20130607' tag of the 'renesas.git' tree
>> and the USB patches I have submitted earlier.
>> Changes in version 2:
>> - changed the platform device's name as in the patch merged to 'net-next.git';
>> - lowercased the SoC name in the subject.
> Thanks, I have queued this up in the soc2 branch.
> My current plan is to let that branch sit in next for a few
> days and then send a pull-request for it to be included in v3.11.
Could you then merge the BOCK-W Ether support too? The patch
currently has some offsets applying to 'renesas-next-20130611v2', should
I respin it?
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: shmobile: r8a7778: fix Ether device name
Date: Tue, 11 Jun 2013 23:49:40 +0400 [thread overview]
Message-ID: <51B77F54.8030001@cogentembedded.com> (raw)
In-Reply-To: <20130611074850.GE10440@verge.net.au>
Hello.
On 06/11/2013 11:48 AM, Simon Horman wrote:
>> While recasting commit 524219146a89aee5366326c225ccd71231419d89 (ARM: shmobile:
>> R8A7778: add Ether support), I made a typo in the platform device's name: used
>> underscore instead of hyphen.
>> However, there's now patch merged to net-next.git renaming the platform device
>> from "sh-eth" to "r8a777x-ehter", so it makes the most sense to change the name
>> straight to that one.
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> ---
>> The patch is atop of the 'renesas-next-20130607' tag of the 'renesas.git' tree
>> and the USB patches I have submitted earlier.
>> Changes in version 2:
>> - changed the platform device's name as in the patch merged to 'net-next.git';
>> - lowercased the SoC name in the subject.
> Thanks, I have queued this up in the soc2 branch.
> My current plan is to let that branch sit in next for a few
> days and then send a pull-request for it to be included in v3.11.
Could you then merge the BOCK-W Ether support too? The patch
currently has some offsets applying to 'renesas-next-20130611v2', should
I respin it?
WBR, Sergei
next prev parent reply other threads:[~2013-06-11 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 21:23 [PATCH v2 1/2] ARM: shmobile: r8a7778: fix Ether device name Sergei Shtylyov
2013-06-08 21:23 ` Sergei Shtylyov
2013-06-11 7:48 ` Simon Horman
2013-06-11 7:48 ` Simon Horman
2013-06-11 19:49 ` Sergei Shtylyov [this message]
2013-06-11 19:49 ` Sergei Shtylyov
2013-06-12 1:49 ` Simon Horman
2013-06-12 1:49 ` Simon Horman
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=51B77F54.8030001@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.