netdev - Re: [PATCH] bgmac: add helper checking for BCM4707 / BCM53018 chip id

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] [day] [month] [year] [list]

Message-ID: <CACna6ry1FwQuqQ-jzB0DQN+uXpH7XZid5bc-pOp=JkJbt2JOMw@mail.gmail.com>
Date:	Sat, 30 Jan 2016 10:49:50 +0100
From:	Rafał Miłecki <zajec5@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	Network Development <netdev@...r.kernel.org>,
	Hauke Mehrtens <hauke@...ke-m.de>,
	Felix Fietkau <nbd@...nwrt.org>
Subject: Re: [PATCH] bgmac: add helper checking for BCM4707 / BCM53018 chip id

On 30 January 2016 at 08:03, David Miller <davem@...emloft.net> wrote:
> From: Rafał Miłecki <zajec5@...il.com>
> Date: Sat, 30 Jan 2016 00:41:07 +0100
>
>> Chipsets with BCM4707 / BCM53018 ID require special handling at a few
>> places in the code. It's likely there will be more IDs to check in the
>> future. To simplify it add this trivial helper.
>>
>> Signed-off-by: Rafał Miłecki <zajec5@...il.com>
>
> The net-next tree is not open, therefore submitting this kind of cleanup
> is not appropriate.

Oops, I got experience from other trees where patches are just queued
(usually with patchwork). I just read about netdev not playing this
way in netdev-FAQ.txt, I didn't expect that. I'll resubmit it later.

-- 
Rafał