From: David Miller <davem@davemloft.net>
To: zajec5@gmail.com
Cc: netdev@vger.kernel.org, hauke@hauke-m.de, nbd@openwrt.org
Subject: Re: [PATCH] bgmac: add helper checking for BCM4707 / BCM53018 chip id
Date: Fri, 29 Jan 2016 23:03:26 -0800 (PST) [thread overview]
Message-ID: <20160129.230326.2013535528827383323.davem@davemloft.net> (raw)
In-Reply-To: <1454110867-9489-1-git-send-email-zajec5@gmail.com>
From: Rafał Miłecki <zajec5@gmail.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@gmail.com>
The net-next tree is not open, therefore submitting this kind of cleanup
is not appropriate.
next prev parent reply other threads:[~2016-01-30 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 23:41 [PATCH] bgmac: add helper checking for BCM4707 / BCM53018 chip id Rafał Miłecki
2016-01-30 7:03 ` David Miller [this message]
2016-01-30 9:49 ` Rafał Miłecki
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 6:47 Rafał Miłecki
2016-02-06 8:37 ` David Miller
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=20160129.230326.2013535528827383323.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hauke@hauke-m.de \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=zajec5@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).