From: Ard Biesheuvel <ardb@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avi Fishman <avifishman70@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
Tali Perry <tali.perry1@gmail.com>,
Patrick Venture <venture@google.com>,
Nancy Yuen <yuenn@google.com>,
Benjamin Fair <benjaminfair@google.com>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Vladimir Zapolskiy <vz@mleia.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-omap@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v2] usb: reduce kernel log spam on driver registration
Date: Mon, 5 Sep 2022 13:17:55 +0200 [thread overview]
Message-ID: <CAMj1kXFuzXPmah+bO+tORQSWnBn_YktDA716FJA=_Psez0OTmg@mail.gmail.com> (raw)
In-Reply-To: <YxXYgNsug4BIWsoF@kroah.com>
On Mon, 5 Sept 2022 at 13:07, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Mon, Sep 05, 2022 at 12:52:52PM +0200, Ard Biesheuvel wrote:
> > Drivers are typically supposed to be quiet unless they are actually
> > probed, but for some reason, USB host controllers seem to be exempt from
> > this rule, and happily broadcast their existence into the kernel log at
> > boot even if the hardware in question is nowhere to be found.
> >
> > Let's fix that, and remove these pr_info() calls.
> >
> > Cc: Alan Stern <stern@rowland.harvard.edu>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Nicolas Ferre <nicolas.ferre@microchip.com>
> > Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
> > Cc: Claudiu Beznea <claudiu.beznea@microchip.com>
> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Cc: Alim Akhtar <alim.akhtar@samsung.com>
> > Cc: Avi Fishman <avifishman70@gmail.com>
> > Cc: Tomer Maimon <tmaimon77@gmail.com>
> > Cc: Tali Perry <tali.perry1@gmail.com>
> > Cc: Patrick Venture <venture@google.com>
> > Cc: Nancy Yuen <yuenn@google.com>
> > Cc: Benjamin Fair <benjaminfair@google.com>
> > Cc: Patrice Chotard <patrice.chotard@foss.st.com>
> > Cc: Vladimir Zapolskiy <vz@mleia.com>
> > Cc: linux-usb@vger.kernel.org
> > Cc: linux-arm-kernel@lists.infradead.org
> > Cc: linux-kernel@vger.kernel.org
> > Cc: linux-samsung-soc@vger.kernel.org
> > Cc: linux-omap@vger.kernel.org
> > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Acked-by: Alan Stern <stern@rowland.harvard.edu>
> > Reviewed-by: Rob Herring <robh@kernel.org>
> > Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
> > ---
> > v2: - drop another couple of occurrences pointed out by Robert
> > - drop hcd_name variables as well if the only reference to them is
> > being dropped
> > - pick up acks
>
> I've already applied your first version, so can you rebase this against
> linux-next and send just the fixups?
>
OK
prev parent reply other threads:[~2022-09-05 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 10:52 [PATCH v2] usb: reduce kernel log spam on driver registration Ard Biesheuvel
2022-09-05 11:07 ` Greg Kroah-Hartman
2022-09-05 11:17 ` Ard Biesheuvel [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='CAMj1kXFuzXPmah+bO+tORQSWnBn_YktDA716FJA=_Psez0OTmg@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alim.akhtar@samsung.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=claudiu.beznea@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=patrice.chotard@foss.st.com \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=vz@mleia.com \
--cc=yuenn@google.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).