From: patchwork-bot+linux-soc@kernel.org
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: soc@kernel.org
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Make NOP_USB_XCEIV driver built-in
Date: Fri, 16 Jul 2021 21:22:06 +0000 [thread overview]
Message-ID: <162647052602.25202.10091257368755064642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1625915095-23077-1-git-send-email-stefan.wahren@i2se.com>
Hello:
This patch was applied to soc/soc.git (refs/heads/arm/fixes):
On Sat, 10 Jul 2021 13:04:55 +0200 you wrote:
> The usage of usb-nop-xceiv PHY on Raspberry Pi boards with BCM283x has
> been a "regression source" a lot of times. The last case is breakage of
> USB mass storage boot has been commit e590474768f1 ("driver core: Set
> fw_devlink=on by default") for multi_v7_defconfig. As long as
> NOP_USB_XCEIV is configured as module, the dwc2 USB driver defer probing
> endlessly and prevent booting from USB mass storage device. So make
> the driver built-in as in bcm2835_defconfig and arm64/defconfig.
>
> [...]
Here is the summary with links:
- ARM: multi_v7_defconfig: Make NOP_USB_XCEIV driver built-in
https://git.kernel.org/soc/soc/c/ab37a7a890c1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-07-16 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 11:04 [PATCH] ARM: multi_v7_defconfig: Make NOP_USB_XCEIV driver built-in Stefan Wahren
2021-07-10 11:04 ` Stefan Wahren
2021-07-11 21:27 ` Florian Fainelli
2021-07-11 21:27 ` Florian Fainelli
2021-07-12 5:04 ` Stefan Wahren
2021-07-12 5:04 ` Stefan Wahren
2021-07-16 21:22 ` patchwork-bot+linux-soc [this message]
2021-07-16 21:24 ` Arnd Bergmann
2021-07-16 21:24 ` Arnd Bergmann
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=162647052602.25202.10091257368755064642.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
--cc=stefan.wahren@i2se.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).