From: "Bjørn Mork" <bjorn@mork.no>
To: netdev@vger.kernel.org
Subject: Patches depending on changes in usb-next
Date: Tue, 19 Jun 2012 12:52:24 +0200 [thread overview]
Message-ID: <877gv3po9j.fsf@nemi.mork.no> (raw)
Hello,
I have a couple of 3.6 patches for the qmi_wwan driver which depend on
81df2d5 USB: allow match on bInterfaceNumber
fec1868 USB: properly pad out usb_device_id.driver_info
only available in usb-next. Do you prefer that I hold on to these until
after the 3.6 merge window? They only affect module aliases and
probing so the risk isn't too high, although they do represent quite
major changes in that particular area.
Bjørn
reply other threads:[~2012-06-19 10:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=877gv3po9j.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--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