netdev - Re: [PATCH net 0/3] qmi_wwan: simplify device matching and add a few new devices

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]

Message-ID: <87mx1zjctu.fsf@nemi.mork.no>
Date:	Mon, 13 Aug 2012 12:39:09 +0200
From:	Bjørn Mork <bjorn@...k.no>
To:	netdev@...r.kernel.org
Cc:	linux-usb@...r.kernel.org
Subject: Re: [PATCH net 0/3] qmi_wwan: simplify device matching and add a few new devices

Bjørn Mork <bjorn@...k.no> writes:

> The home cooked whitelisting code can be removed now that 
> the USB core supports interface number matching.
>
> The second patch adds a few new devices.
>
> The third patch improves device list readability by using
> existing macros where possible.
>
> I hope this can go in 3.6-rc2/3. The series is based on
> the current net/master (commit 2359a476)

Just an additional afterthought: Please do not apply this as it is to
"net-next" if you decide it is inappropriate for "net".

New devices will be added to the driver during the 3.6 cycle whether or
not the probing changes are accepted.  This will result in unnecessary
merge conflicts. I'll submit a new version of the patch set for
"net-next" when we have a better idea of what the device list looks like
at the beginning of the 3.7 cycle.

But I am still hoping this is accepted for "net", although I obviously
screwed up choosing strategy to avoid net/usb merge conflicts.

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