All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: "Isaac J. Manjarres" <isaacmanjarres@google.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	stable@vger.kernel.org, Saravana Kannan <saravanak@google.com>,
	Guenter Roeck <linux@roeck-us.net>,
	kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] driver core: Don't probe devices after bus_type.match() probe deferral
Date: Thu, 1 Sep 2022 07:28:59 +0200	[thread overview]
Message-ID: <YxBDG9ebNDwEni2j@kroah.com> (raw)
In-Reply-To: <Yw/CyRFr1bYNlNGh@shell.armlinux.org.uk>

On Wed, Aug 31, 2022 at 09:21:29PM +0100, Russell King (Oracle) wrote:
> Greg,
> 
> Are you happy for me to pick up this patch as part of the fixes for the
> AMBA changes? The original patch that it is fixing is a patch that was
> part of a series that was merged through my tree.
> 
> It's fixing a problem that has been noticed by several people and the
> fix is now a few weeks old.

Sorry, I'm behind in driver core stuff.  I'll pick it up later today.

greg k-h

  reply	other threads:[~2022-09-01  5:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 18:40 [PATCH v3] driver core: Don't probe devices after bus_type.match() probe deferral Isaac J. Manjarres
2022-08-25 22:20 ` Saravana Kannan
2022-08-30 11:39 ` Linus Walleij
2022-08-31 20:21 ` Russell King (Oracle)
2022-09-01  5:28   ` Greg Kroah-Hartman [this message]
2022-09-01 13:57     ` Greg Kroah-Hartman

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=YxBDG9ebNDwEni2j@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=isaacmanjarres@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=m.szyprowski@samsung.com \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.com \
    --cc=stable@vger.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 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.