From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: David Hendel <david@silicom.co.il>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>, Anna Lukin <annal@silicom.co.il>
Subject: Re: Silicom bypass driver promote from staging
Date: Thu, 7 Aug 2014 13:19:47 -0700 [thread overview]
Message-ID: <20140807201947.GA6060@kroah.com> (raw)
In-Reply-To: <3BFAEADE799AF145974162DF00E013AF018F814DAB@exchange2010.silicom.local>
On Thu, Aug 07, 2014 at 09:26:54AM +0000, David Hendel wrote:
> Hello Netdev group,
>
> For the /driver/staging/silicom that we want to promote.
> We have our bypass driver updated and we would like to move forward with integrating it into the kernel mainline We are not sure of what is the best location to have these driver located, as this is not really a network driver.
> The options that we see are:
> driver/misc/silicom/...
> driver/char/silicom/...
> driver/bypass/silicom/....
>
> The description of the functionality of the driver is below per readme of this driver in the /driver/staging/silicom.
>
> Currently in the attached driver we have defined it to be in driver/bypass/silicom/....
> If this is OK with you then we can continue with that. if you thing that it needs to be in another location then we can change the patch.
Making your patch an attachment in base64 mode, makes it impossible to
quote to review it :(
Anyway, I stopped at the first header file. The kernel already has BIT
definitions, no driver should ever have to redefine these and do it on
their own. That leads me to believe that this code really isn't all
that "cleaned up" at all.
Should I just look at what is in drivers/staging/silicom/ right now as
code to review? Or have you changed it any by making this patch?
thanks,
greg k-h
next prev parent reply other threads:[~2014-08-07 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BFAEADE799AF145974162DF00E013AF018F80FFCF@exchange2010.silicom.local>
[not found] ` <20140805150957.GC27303@kroah.com>
2014-08-07 9:26 ` Silicom bypass driver promote from staging David Hendel
2014-08-07 9:46 ` Jeff Kirsher
2014-08-07 16:55 ` Stephen Hemminger
2014-08-07 20:19 ` gregkh [this message]
2014-08-07 21:51 ` Francois Romieu
2014-09-27 6:54 ` David Hendel
2014-09-29 1:10 ` gregkh
2014-09-29 7:18 ` David Hendel
2014-09-29 7:18 ` David Hendel
2014-09-29 17:07 ` gregkh
2014-09-29 21:52 ` Francois Romieu
2014-09-29 7:22 ` David Hendel
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=20140807201947.GA6060@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=annal@silicom.co.il \
--cc=arnd@arndb.de \
--cc=david@silicom.co.il \
--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).