From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] micrel: add support for KSZ8041RNLI
Date: Wed, 11 Dec 2013 17:10:05 -0500 (EST) [thread overview]
Message-ID: <20131211.171005.1026686921972557583.davem@davemloft.net> (raw)
In-Reply-To: <52A8EEF8.3090503@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Thu, 12 Dec 2013 02:02:16 +0300
> Well, the R8A7791 Ether platform support should appear only in 3.14,
> so don't bother. I just wanted to understand the principle you
> follow...
Generally speaking, if the change to support a new device is simply
a matter of adding a new device ID I tend to queue it up for 'net'.
prev parent reply other threads:[~2013-12-11 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 23:20 [PATCH] micrel: add support for KSZ8041RNLI Sergei Shtylyov
2013-12-10 13:19 ` Geert Uytterhoeven
2013-12-10 17:21 ` Sergei Shtylyov
2013-12-10 19:05 ` Geert Uytterhoeven
2013-12-11 3:26 ` David Miller
2013-12-11 15:39 ` Sergei Shtylyov
2013-12-11 18:58 ` David Miller
2013-12-11 21:28 ` Sergei Shtylyov
2013-12-11 21:11 ` David Miller
2013-12-11 23:02 ` Sergei Shtylyov
2013-12-11 22:10 ` David Miller [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=20131211.171005.1026686921972557583.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@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).