From: "Bjørn Mork" <bjorn@mork•no>
To: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Cc: David Miller <davem@davemloft•net>,
netdev@vger•kernel.org, linux-usb@vger•kernel.org
Subject: Re: Using interface number probing for usbnet drivers before 3.6-rc1?
Date: Wed, 04 Jul 2012 16:50:53 +0200 [thread overview]
Message-ID: <87ipe3lgvm.fsf@nemi.mork.no> (raw)
In-Reply-To: <20120704144649.GC23020@kroah.com> (Greg Kroah-Hartman's message of "Wed, 4 Jul 2012 07:46:49 -0700")
Greg Kroah-Hartman <gregkh@linuxfoundation•org> writes:
> On Wed, Jul 04, 2012 at 01:19:35PM +0200, Bjørn Mork wrote:
>> David Miller <davem@davemloft•net> writes:
>> > From: Bjørn Mork <bjorn@mork•no>
>> > Date: Sat, 23 Jun 2012 11:26:54 +0200
>> >
>> >> Is waiting for 3.6-rc1 the best alternative, or is cherry-picking them
>> >> an option?
>> >
>> > I'm extremely reluctant to have a dependency on another tree.
>> >
>> > The USB tree, on the other hand, could pull the net-next tree
>> > in so you can continue your dependent work there.
>>
>> Hello Greg,
>>
>> I know I said I would be more careful about cross-tree dependencies, but
>> here I am again...
>>
>> The context is: How should I proceed with interface number based probing
>> for usbnet drivers, in particular qmi_wwan which already has a few
>> patches in net-next?
>>
>> I see two possible remaining options:
>>
>> 1) you pull the net-next changes into usb-next so that I can do the
>> work against usb-next now, or
>> 2) I wait for 3.6-rc1 and do the work against the net tree after
>> 3.6-rc1 is merged there
>>
>> I have decided to go for option #2 unless either of you have other
>> preferences, as I believe that is going to cause the least work and
>> merge trouble for you both.
>
> What about:
> 3) You send the usb interface number matching patches again for them
> to be included in the net-next tree as well, causing duplicates to be
> in linux-next, but allowing you to send your patches into net-next.
>
> That is what we have done at times for other patches, and if David is ok
> with it, so am I. Odds are, the merge will happen automatically, but if
> not, I can handle it when 3.6-rc1 comes around.
>
> Sound good?
I could have misunderstood, but I thought that was out of the question
given that David didn't want to cherry-pick them from usb-next.
Bjørn
next prev parent reply other threads:[~2012-07-04 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:45 [PATCH net] net: qmi_wwan: fix Gobi device probing Bjørn Mork
2012-06-23 0:17 ` David Miller
[not found] ` <20120622.171735.637204872051168180.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-23 9:26 ` Bjørn Mork
[not found] ` <87y5neidk1.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2012-06-23 9:37 ` David Miller
2012-06-23 10:05 ` Bjørn Mork
[not found] ` <87txy2ibr8.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2012-06-23 10:35 ` David Miller
[not found] ` <20120623.033546.563917179592608418.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-06-23 10:44 ` Bjørn Mork
2012-07-04 11:19 ` Using interface number probing for usbnet drivers before 3.6-rc1? (was: Re: [PATCH net] net: qmi_wwan: fix Gobi device probing) Bjørn Mork
[not found] ` <87mx3flqns.fsf_-_-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2012-07-04 14:46 ` Greg Kroah-Hartman
2012-07-04 14:50 ` Bjørn Mork [this message]
[not found] ` <87ipe3lgvm.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2012-07-04 15:11 ` Using interface number probing for usbnet drivers before 3.6-rc1? Greg Kroah-Hartman
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=87ipe3lgvm.fsf@nemi.mork.no \
--to=bjorn@mork$(echo .)no \
--cc=davem@davemloft$(echo .)net \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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