From: Kalle Valo <kvalo@codeaurora.org>
To: "Michael Büsch" <m@bues.ch>
Cc: H Buus <ubuntu@hbuus.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ssb/gpio: Remove unnecessary WARN_ON from driver_gpio
Date: Tue, 25 Jun 2019 08:07:31 +0300 [thread overview]
Message-ID: <87v9wus164.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20190610204927.2de21c9a@wiggum> ("Michael \=\?utf-8\?Q\?B\=C3\=BCs\?\= \=\?utf-8\?Q\?ch\=22's\?\= message of "Mon, 10 Jun 2019 20:49:27 +0200")
Michael Büsch <m@bues.ch> writes:
> The WARN_ON triggers on older BCM4401-B0 100Base-TX ethernet controllers.
> The warning serves no purpose. So let's just remove it.
>
> Reported-by: H Buus <ubuntu@hbuus.com>
> Signed-off-by: Michael Büsch <m@bues.ch>
For some reason patchwork (or pwcli script) didn't like this patch so
manually applied to wireless-drivers-next:
e73e43246da6 ssb/gpio: Remove unnecessary WARN_ON from driver_gpio
I have a faint recollection that I had a similar problem with another
patch from Michael, did we ever conclude what was the issue?
--
Kalle Valo
next prev parent reply other threads:[~2019-06-25 5:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 21:44 Should b44_init lead to WARN_ON in drivers/ssb/driver_gpio.c:464? H Buus
2019-06-09 21:57 ` Michael Büsch
2019-06-10 0:13 ` Larry Finger
2019-06-10 5:40 ` H Buus
2019-06-10 6:51 ` Michael Büsch
2019-06-10 18:49 ` [PATCH] ssb/gpio: Remove unnecessary WARN_ON from driver_gpio Michael Büsch
2019-06-10 19:16 ` Larry Finger
2019-06-11 4:56 ` H Buus
2019-06-25 5:07 ` Kalle Valo [this message]
2019-06-25 12:10 ` Jonas Gorski
2019-06-25 12:24 ` Kalle Valo
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=87v9wus164.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--cc=ubuntu@hbuus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.