All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Einon <mark.einon@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: davem@davemloft.net, sfr@canb.auug.org.au,
	devel@driverdev.osuosl.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [RFC PATCH v3 linux-next] et131x: Promote staging et131x driver to drivers/net
Date: Wed, 23 Jan 2013 14:51:39 +0000	[thread overview]
Message-ID: <CANK3SE1W5O5Df95MpCCWHaQO_tN7OaA1jJ60zrH5Zx66ZGdNiw@mail.gmail.com> (raw)
In-Reply-To: <20130123143216.GA2050@kroah.com>

On 23 January 2013 14:32, Greg KH <gregkh@linuxfoundation.org> wrote:
> I usually recommend just creating a new patch, that adds the driver to
> the proper place in the kernel, and sending that in.  If the subsystem
> maintainers accept it, then I can just delete the staging driver.
>
> Yes, this looses the history of the code, but usually no one cares about
> that for staging drivers.
>
> If that's not ok, I have no problem accepting this, if I get an ack from
> the subsystem maintainers that it's ok, but again, this patch makes it
> pretty hard for them to know that or not.

I can see how that works - I'll send a v4 update shorty.

Cheers,

Mark

  reply	other threads:[~2013-01-23 14:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 20:40 [RFC PATCH linux-next] et131x: Promote staging et131x driver to drivers/net Mark Einon
2013-01-18 22:57 ` Greg KH
2013-01-19 11:03   ` Dan Carpenter
2013-01-19 11:48     ` [PATCH] staging: et131x: Fix all sparse warnings Mark Einon
2013-01-21 23:44     ` [RFC PATCH linux-next] et131x: Promote staging et131x driver to drivers/net Mark Einon
2013-01-22  6:20       ` Dan Carpenter
2013-01-23 10:10 ` [RFC PATCH v2 " Mark Einon
2013-01-23 10:31   ` Dan Carpenter
2013-01-23 11:31     ` Mark Einon
2013-01-23 12:45   ` [RFC PATCH v3 " Mark Einon
2013-01-23 14:32     ` Greg KH
2013-01-23 14:51       ` Mark Einon [this message]
2013-01-23 16:24     ` [RFC PATCH v4 " Mark Einon
2013-01-29  4:10       ` David Miller
2013-01-29 12:47         ` Mark Einon

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=CANK3SE1W5O5Df95MpCCWHaQO_tN7OaA1jJ60zrH5Zx66ZGdNiw@mail.gmail.com \
    --to=mark.einon@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.