From: Guenter Roeck <linux@roeck-us.net>
To: Isaac Manjarres <isaacmanjarres@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Saravana Kannan <saravanak@google.com>,
stable@kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] driver core: Fix bus_type.match() error handling
Date: Tue, 16 Aug 2022 04:13:11 -0700 [thread overview]
Message-ID: <20220816111311.GC1108868@roeck-us.net> (raw)
In-Reply-To: <YvsoYzIhOtX9DOi2@google.com>
On Mon, Aug 15, 2022 at 10:17:23PM -0700, Isaac Manjarres wrote:
> On Mon, Aug 15, 2022 at 09:25:07PM -0700, Guenter Roeck wrote:
> > > v1 -> v2:
> > > - Fixed the logic in __driver_attach() to allow a driver to continue
> > > attempting to match and bind with devices in case of any error, not
> > > just probe deferral.
> > >
> > > Guenter,
> > >
> > > Can you please give test this patch to make sure it still works for you?
> > >
> >
> > Not as well as v1. I still see the clk crash with versatileab, and imx25-pdk
> > emulations now stall during boot when trying to boot from usb.
> >
> > Guenter
> Thanks for trying the patch out. This patch isn't meant to fix the clk
> crash that you mentioned on another thread. I had made the following patch for
> that: https://lore.kernel.org/lkml/YvqTvuqSll30Rv2k@google.com/. Have
> you been able to give that a shot yet? If not can you please test with the
> patch in this e-mail and that patch?
>
No, sorry, I missed that one. It does not apply, though - it is whitespace
corrupted. I tried to fix it up, but that failed.
> Please make sure you do not include this patch as it is known to cause
> deadlocks: https://lore.kernel.org/lkml/YvXhJRlHN9OAIA5l@google.com/.
>
No, I did not include that patch.
> Did you test imx25-pdk emulations with just v1 of this patch previously?
>
I am quite sure I did because it is a single setup.
Thanks,
Guenter
next prev parent reply other threads:[~2022-08-16 11:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220815211927eucas1p275ed3f63f1baf76b319a828c214c651f@eucas1p2.samsung.com>
2022-08-15 21:19 ` Isaac J. Manjarres
2022-08-16 4:25 ` Guenter Roeck
2022-08-16 5:17 ` Isaac Manjarres
2022-08-16 11:13 ` Guenter Roeck [this message]
2022-08-16 17:13 ` Isaac Manjarres
2022-08-17 1:05 ` Guenter Roeck
2022-08-17 1:12 ` Isaac Manjarres
2022-08-18 22:59 ` Guenter Roeck
2022-08-19 0:38 ` Isaac Manjarres
2022-08-19 11:28 ` Guenter Roeck
2022-08-19 17:45 ` Isaac Manjarres
2022-08-19 20:01 ` Bart Van Assche
2022-08-19 20:55 ` Guenter Roeck
2022-08-19 22:08 ` Guenter Roeck
2022-08-20 0:07 ` Bart Van Assche
2022-08-20 11:48 ` Guenter Roeck
2022-08-21 21:39 ` Bart Van Assche
2022-08-25 9:22 ` Marek Szyprowski
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=20220816111311.GC1108868@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=isaacmanjarres@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rafael@kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=saravanak@google.com \
--cc=stable@kernel.org \
--cc=tomeu.vizoso@collabora.com \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®