From: Catalin Marinas <catalin.marinas@arm.com>
To: Steve.Glendinning@smsc.com
Cc: Bill Gatliff <bgat@billgatliff.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-arm-kernel@lists.arm.linux.org.uk, Ian.Saturley@smsc.com,
netdev@vger.kernel.org
Subject: Re: [PATCH 14/16] RealView: Use the in-kernel smc911x.c driver on RealView
Date: Tue, 21 Oct 2008 11:42:06 +0100 [thread overview]
Message-ID: <1224585726.9330.22.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <OF6B543A5F.032D7BBC-ON802574E9.00340E58-802574E9.00396C6E@smsc.com>
On Tue, 2008-10-21 at 11:26 +0100, Steve.Glendinning@smsc.com wrote:
> The smsc911x driver is still maintained (out of tree), and is used by many
> of our customers. Mainline inclusion is still very much the intention!
>
> Almost all the feedback I've had has been positive, but I've had a few
> "can't you just fix the in-tree driver?" responses. The trouble is it's
> not a *small* piece of work!
Can we not have both drivers in the kernel until the transition to the
new one has finished? We seem to still have both eepro100.c and e100.c
in the kernel targeting similar chips.
--
Catalin
next prev parent reply other threads:[~2008-10-21 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1224578293.9330.9.camel@pc1117.cambridge.arm.com>
2008-10-21 10:26 ` [PATCH 14/16] RealView: Use the in-kernel smc911x.c driver on RealView Steve.Glendinning
2008-10-21 10:42 ` Catalin Marinas [this message]
2008-10-21 13:25 ` Bill Gatliff
2008-10-21 18:48 ` Russell King - ARM Linux
2008-10-21 13:27 ` Bill Gatliff
2008-10-21 18:46 ` Russell King - ARM Linux
2008-10-21 19:32 ` Steve.Glendinning
2008-11-04 16:12 Steve.Glendinning
2008-11-04 20:25 ` Bill Gatliff
2008-11-04 22:16 ` Steve.Glendinning
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=1224585726.9330.22.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=Ian.Saturley@smsc.com \
--cc=Steve.Glendinning@smsc.com \
--cc=bgat@billgatliff.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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).