From: Jeff Garzik <jeff@garzik.org>
To: Greg KH <greg@kroah.com>
Cc: Dan Williams <dcbw@redhat.com>,
Petko Manolov <petkan@nucleusys.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] usb-net/pegasus: fix pegasus carrier detection
Date: Tue, 24 Apr 2007 13:41:47 -0400 [thread overview]
Message-ID: <462E415B.3020707@garzik.org> (raw)
In-Reply-To: <20070424170429.GA13668@kroah.com>
Greg KH wrote:
> On Tue, Apr 24, 2007 at 12:49:12PM -0400, Jeff Garzik wrote:
>> Long term, Greg seemed OK with moving the net drivers from drivers/usb/net
>> to drivers/usb/net, in line with the current policy of placing net drivers
>> in drivers/net/*, bus agnostic. After that move, sending to netdev and me
>> (as you did here) would be the preferred avenue.
>
> Speaking of which, do you want me to do this in the 2.6.22-rc1
> timeframe? Usually big code moves like this are good to do right after
> rc1 comes out as the major churn is usually completed then.
Whatever works best for you. There are few if any interlocking
dependencies.
Or I could wait for you to do your 2.6.22 merge window USB push (sans
this move), and then I can do the rename-across-directories in git in my
normal netdev-2.6.git stream.
Jeff
next prev parent reply other threads:[~2007-04-24 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 14:20 [PATCH] usb-net/pegasus: fix pegasus carrier detection Dan Williams
2007-04-24 16:49 ` Jeff Garzik
2007-04-24 17:04 ` Greg KH
2007-04-24 17:41 ` Jeff Garzik [this message]
2007-04-24 17:48 ` petkan
2007-04-24 20:24 ` Dan Williams
2007-04-25 14:58 ` Petko Manolov
2007-04-25 15:08 ` Dan Williams
2007-04-25 15:09 ` Petko Manolov
2007-04-25 16:03 ` Dan Williams
2007-04-25 16:02 ` Jeff Garzik
2007-04-26 1:30 ` [PATCH] usb-net/pegasus: simplify " Dan Williams
2007-04-26 9:12 ` Petko Manolov
2007-04-28 0:17 ` Jeff Garzik
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=462E415B.3020707@garzik.org \
--to=jeff@garzik.org \
--cc=dcbw@redhat.com \
--cc=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.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).