From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Hannes Reinecke <hare@suse.de>
Cc: netdev@vger.kernel.org, Michal Kubecek <mkubecek@suse.com>,
Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH] fddi: Fixup potential uninitialized bars
Date: Tue, 26 Jan 2016 08:55:41 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.20.1601260759180.7055@eddie.linux-mips.org> (raw)
In-Reply-To: <1453793251-101247-1-git-send-email-hare@suse.de>
On Tue, 26 Jan 2016, Hannes Reinecke wrote:
> dfx_get_bars() allocates the various bars, depending on the
> bus type. But as the function itself returns void and there
> is no default selection there is a risk of the function
> returning without allocating any bars.
> This patch moves the entries around so that PCI is assumed
> to the the default bus, and adds a WARN_ON check if that
> should no be the case.
> And I've made some minor code reshuffles to keep checkpatch
> happy.
>
> Signed-off-by: Hannes Reinecke <hare@suse.com>
> ---
> drivers/net/fddi/defxx.c | 29 ++++++++++++++++-------------
> 1 file changed, 16 insertions(+), 13 deletions(-)
NAK, this has been fixed already with a much simpler change, commit
62f2aaabcf41 ("defxx: fix build warning"). Exactly one of `dfx_bus_pci',
`dfx_bus_eisa' or `dfx_bus_tc' will always be true or `dfx_register' will
not have been called in the first place, so it's not even worth a BUG_ON
IMHO.
Thanks for looking into this problem though, always welcome!
Maciej
prev parent reply other threads:[~2016-01-26 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 7:27 [PATCH] fddi: Fixup potential uninitialized bars Hannes Reinecke
2016-01-26 8:55 ` Maciej W. Rozycki [this message]
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.20.1601260759180.7055@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=mkubecek@suse.com \
--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).