From: Stephen Hemminger <shemminger@vyatta.com>
To: "Ha, Tristram" <Tristram.Ha@Micrel.Com>
Cc: "Dave Miller" <davem@davemloft.net>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.33 1/4] net: Micrel KSZ8841/2 PCI Ethernet driver
Date: Thu, 4 Feb 2010 15:38:07 -0800 [thread overview]
Message-ID: <20100204153807.69d9037a@nehalam> (raw)
In-Reply-To: <14385191E87B904DBD836449AA30269D021A51@MORGANITE.micrel.com>
On Thu, 4 Feb 2010 15:18:54 -0800
"Ha, Tristram" <Tristram.Ha@Micrel.Com> wrote:
> Dave Miller wrote:
> >> This is a resubmission of the Micrel KSZ8841/2 PCI Ethernet driver.
> >
> > The procfs stuff is a non-starter.
> >
> > There will undoubtedly be other devices that have switch-like
> > facilities that we'd like to export configuration support for.
> >
> > The last thing we want is a bunch of procfs files that each
> > driver decides the layout and behavior of.
> >
> > We need a centralized way to config such things, and probably
> > the best is to have a rtnl_link_ops facility to get at the
> > ports and configure them with attribute blobs or similar.
> >
> > We also said in your first submission that the way you're
> > getting at the bridge STP stuff with things like:
> >
> > +/* Needed for STP support. */
> > +#ifdef CONFIG_KSZ8842_STP
> > +#include <../net/bridge/br_private.h>
> > +#endif
> > Yet you left all of this stuff in there.
>
> In my discussions with Alan Cox and Stephen Hemminger, I thought they kind of agree to the code's inclusion in the driver. Sorry for my misunderstanding. I will submit another one with those code removed.
>
> P.S. I did not actually receive your response from my company's e-mail server. I copied it from LKML.
I would rather move any defines needed by driver to
new file: include/net/bridge.h
and include it in br_private.h
Don't want device dumpster diving into bridge control structures.
--
next prev parent reply other threads:[~2010-02-04 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 23:18 [PATCH 2.6.33 1/4] net: Micrel KSZ8841/2 PCI Ethernet driver Ha, Tristram
2010-02-04 23:38 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 23:22 Ha, Tristram
2010-01-29 22:37 Ha, Tristram
2010-02-04 2:00 ` 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=20100204153807.69d9037a@nehalam \
--to=shemminger@vyatta.com \
--cc=Tristram.Ha@Micrel.Com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).