From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: netdev@vger.kernel.org
Subject: [PATCH 0/4] FDDI: defza: Fix a bunch of small issues
Date: Wed, 7 Nov 2018 12:06:46 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.1811070323450.20378@eddie.linux-mips.org> (raw)
Hi,
Here is a bunch of small fixes addressing issues that I missed in my
final round of testing. None of these affect run-time behaviour. One was
actually found by the kbuild bot, which turned out to be more pedantic
than my compiler. See individual change descriptions for details.
Please apply.
Maciej
next reply other threads:[~2018-11-07 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 12:06 Maciej W. Rozycki [this message]
2018-11-07 12:06 ` [PATCH 1/4] FDDI: defza: Fix SPDX annotation Maciej W. Rozycki
2018-11-07 12:06 ` [PATCH 2/4] FDDI: defza: Add missing comment closing Maciej W. Rozycki
2018-11-07 12:07 ` [PATCH 3/4] FDDI: defza: Move SMT Tx data buffer declaration next to its skb Maciej W. Rozycki
2018-11-07 12:07 ` [PATCH 4/4] FDDI: defza: Make the driver version string constant Maciej W. Rozycki
2018-11-08 5:53 ` [PATCH 0/4] FDDI: defza: Fix a bunch of small issues 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=alpine.LFD.2.21.1811070323450.20378@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--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;
as well as URLs for NNTP newsgroup(s).