netdev - Re: [PATCH net] net: qmi_wwan: fix Gobi device probing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 23 Jun 2012 12:05:46 +0200
From:	Bjørn Mork <bjorn@...k.no>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, linux-usb@...r.kernel.org,
	H.Siebmanns@...nline.de
Subject: Re: [PATCH net] net: qmi_wwan: fix Gobi device probing

David Miller <davem@...emloft.net> writes:

> From: Bjørn Mork <bjorn@...k.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.

fair enough

> The USB tree, on the other hand, could pull the net-next tree
> in so you can continue your dependent work there.

OK, that will be up to Greg then.

But failing that, would it be OK to let the 3.6 version of the fix wait
for -rc2?  It's not a crash or any other kind of data loss bug, just a
usability regression with a workaround.


Bjørn
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html