linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Android Kernel Team <kernel-team@android.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] driver core: Avoid pointless deferred probe attempts
Date: Tue, 23 Feb 2021 11:09:58 +0100	[thread overview]
Message-ID: <CAMuHMdUo_2WPxDeckhF3nt2+p5eG=mpP84a_fWFZnXyeohqo0g@mail.gmail.com> (raw)
In-Reply-To: <20210217235130.1744843-1-saravanak@google.com>

Hi Saravana,

On Thu, Feb 18, 2021 at 12:51 AM Saravana Kannan <saravanak@google.com> wrote:
> There's no point in adding a device to the deferred probe list if we
> know for sure that it doesn't have a matching driver. So, check if a
> device can match with a driver before adding it to the deferred probe
> list.
>
> Signed-off-by: Saravana Kannan <saravanak@google.com>

Thanks for your patch!

> ---
> Geert,
>
> Can you give this a shot for your I2C DMA issue with fw_devlink=on?

Yes, this makes I2C use DMA again on Salvator-XS during kernel boot-up.

I haven't run any more elaborate tests on other platforms.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2021-02-23 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17 23:51 [PATCH] driver core: Avoid pointless deferred probe attempts Saravana Kannan
2021-02-18 17:18 ` Rafael J. Wysocki
2021-02-18 17:24   ` Saravana Kannan
2021-02-18 17:58     ` Saravana Kannan
2021-02-25  1:32     ` Saravana Kannan
2021-02-23 10:09 ` Geert Uytterhoeven [this message]
2021-02-23 19:56   ` Saravana Kannan

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='CAMuHMdUo_2WPxDeckhF3nt2+p5eG=mpP84a_fWFZnXyeohqo0g@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=saravanak@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).