linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: lizhe <sensor1010@163.com>, Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/bus/brcmstb_gisb.c : Remove the suppress_bind_attrs attribute of the driver
Date: Tue, 22 Mar 2022 20:52:32 -0700	[thread overview]
Message-ID: <ef8f8d44-5fc6-5f8e-c33c-c514eb455596@gmail.com> (raw)
In-Reply-To: <531e91bf.3734.17fb4e3150e.Coremail.sensor1010@163.com>



On 3/22/2022 8:47 PM, lizhe wrote:
> HI Andy Shevchenko
> Even if it is loaded as a module, its execution flow is still executed 
> through do_one_initcall(),
> __platform_driver_probe() still invoked.
>       So, this suppress_bind_attrs = true is redundant
> 
> https://github.com/torvalds/linux/commit/707a4cdf86e5d6a2c4fad51fb98a6ff3425f820e 
> <https://github.com/torvalds/linux/commit/707a4cdf86e5d6a2c4fad51fb98a6ff3425f820e> 
> 
> 
>      The author has simply added some descriptions here. Nothing 
> substantial has changed.

No HTML please, and yes I have seen your patch, and yes I plan on 
applying it. No need to fuss about it however.
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-03-23  3:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20  6:45 [PATCH] drivers/bus/brcmstb_gisb.c : Remove the suppress_bind_attrs attribute of the driver lizhe
2022-03-22 14:52 ` Andy Shevchenko
2022-03-22 14:56   ` Andy Shevchenko
     [not found]     ` <531e91bf.3734.17fb4e3150e.Coremail.sensor1010@163.com>
2022-03-23  3:52       ` Florian Fainelli [this message]
2022-04-19 18:49 ` Florian Fainelli

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=ef8f8d44-5fc6-5f8e-c33c-c514eb455596@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensor1010@163.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).