public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: Don't match device with NULL of_node/fwnode
Date: Tue, 10 Dec 2024 11:17:42 -0800	[thread overview]
Message-ID: <Z1iT1tK-kHyNIoNL@google.com> (raw)
In-Reply-To: <CAL_Jsq+5cQHqoJ9wAgt0moU94Bddgsw+Q3TEWDqQ+-rryJPS1Q@mail.gmail.com>

On Tue, Dec 10, 2024 at 06:33:05AM -0600, Rob Herring wrote:
> On Mon, Dec 9, 2024 at 5:47 PM Brian Norris <briannorris@chromium.org> wrote:
> > FWIW, last week, I also cooked this change locally (+ the ACPI change;
> > and a kunit test for added fun), before I noticed Rob submitted this
> > one. If you'd rather, I can submit my patch series. Or I can submit my
> > patch series on top of this. Whichever you'd prefer.
> 
> If you have a kunit test, you win. :)

Ha, OK:

https://lore.kernel.org/linux-kselftest/20241210191353.533801-1-briannorris@chromium.org/
Subject: [PATCH 0/4] drivers: base: Don't match device with NULL of_node/fwnode/etc + tests

(Side note: I just noticed my mail script managed to skip LKML, although
it got the acpi, kunit, and kselftest lists. I can resend if that's a
problem.)

Brian

      reply	other threads:[~2024-12-10 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  0:02 [PATCH] driver core: Don't match device with NULL of_node/fwnode Rob Herring (Arm)
2024-12-04  9:37 ` Greg Kroah-Hartman
2024-12-09 23:47   ` Brian Norris
2024-12-10 12:33     ` Rob Herring
2024-12-10 19:17       ` Brian Norris [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=Z1iT1tK-kHyNIoNL@google.com \
    --to=briannorris@chromium.org \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.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