netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms+renesas@verge.net.au>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-sh@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH repost net-next] net: compile renesas directory if NET_VENDOR_RENESAS is configured
Date: Wed, 26 Aug 2015 00:15:57 +0300	[thread overview]
Message-ID: <55DCDB0D.8060201@cogentembedded.com> (raw)
In-Reply-To: <55DC2899.2050205@cogentembedded.com>

On 08/25/2015 11:34 AM, Sergei Shtylyov wrote:

>> From: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>>
>> Currently the renesas ethernet driver directory is compiled if SH_ETH is
>> configured rather than NET_VENDOR_RENESAS. Although incorrect that was
>> quite harmless as until recently as SH_ETH configured the only driver in
>> the renesas directory. However, as of c156633f1353 ("Renesas Ethernet AVB
>> driver proper") the renesas directory includes another driver, configured
>> by RAVB, and it makes little sense for it to have a hidden dependency on
>> SH_ETH.
>>
>> Signed-off-by: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>> [horms: rewrote changelog]
>> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
>     Sorry about missing that when submitting the AVB driver.

    BTW, why against net-next? I consider this a fix.

MBR, Sergei


  reply	other threads:[~2015-08-25 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  8:03 [PATCH repost net-next] net: compile renesas directory if NET_VENDOR_RENESAS is configured Simon Horman
2015-08-25  8:34 ` Sergei Shtylyov
2015-08-25 21:15   ` Sergei Shtylyov [this message]
2015-08-25 22:55     ` Simon Horman
2015-08-25 23:04       ` David Miller

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=55DCDB0D.8060201@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=netdev@vger.kernel.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).