From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: John Stultz <jstultz@google.com>,
linux-kernel@vger.kernel.org, Brian Masney <bmasney@redhat.com>,
Bjorn Andersson <andersson@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Peter Robinson <pbrobinson@redhat.com>,
Enric Balletbo i Serra <eballetbo@redhat.com>,
Steev Klimaszewski <steev@kali.org>,
Rob Herring <robh@kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-arm-msm@vger.kernel.org,
Saravana Kannan <saravanak@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v2 1/4] driver core: Make driver_deferred_probe_timeout a static variable
Date: Mon, 12 Dec 2022 09:59:48 +0100 [thread overview]
Message-ID: <Y5bthMXYH1MuD9VY@kroah.com> (raw)
In-Reply-To: <549800ec-6da2-64ad-62a6-c8e4a35dc212@redhat.com>
On Mon, Dec 12, 2022 at 09:50:16AM +0100, Javier Martinez Canillas wrote:
> Hello Greg,
>
> On 11/17/22 20:14, John Stultz wrote:
> > On Wed, Nov 16, 2022 at 3:54 AM Javier Martinez Canillas
> > <javierm@redhat.com> wrote:
> >>
> >> It is not used outside of its compilation unit, so there's no need to
> >> export this variable.
> >>
> >> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> >> ---
> >>
> >> (no changes since v1)
> >>
> >> drivers/base/dd.c | 6 ++----
> >> include/linux/device/driver.h | 1 -
> >> 2 files changed, 2 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/drivers/base/dd.c b/drivers/base/dd.c
> >> index 3dda62503102..040b4060f903 100644
> >> --- a/drivers/base/dd.c
> >> +++ b/drivers/base/dd.c
> >> @@ -257,13 +257,11 @@ static int deferred_devs_show(struct seq_file *s, void *data)
> >> DEFINE_SHOW_ATTRIBUTE(deferred_devs);
> >>
> >> #ifdef CONFIG_MODULES
> >> -int driver_deferred_probe_timeout = 10;
> >> +static int driver_deferred_probe_timeout = 10;
> >> #else
> >> -int driver_deferred_probe_timeout;
> >> +static int driver_deferred_probe_timeout;
> >> #endif
> >>
> >> -EXPORT_SYMBOL_GPL(driver_deferred_probe_timeout);
> >> -
> >
> > Yeah, I added the EXPORT for the regulator code to use it in
> > dca0b44957e5 but that got backed out when setting
> > driver_deferred_probe_timeout to 30s was reverted, and this bit was
> > forgotten.
> >
> > Thanks for catching this!
> >
> > Acked-by: John Stultz <jstultz@google.com>
> >
>
> Could you please pick this patch? Is a fix independent of the other
> patches in the series and it has already been acked by John.
It is the middle of the merge window and I can't take anything now until
after 6.2-rc1 is out. I also really can't take individual patches out
of a patch series easily, so please just resend it as a single patch
when 6.2-rc1 is out.
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-12 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:53 [PATCH v2 0/4] driver core: Decouple device links enforcing and probe deferral timeouts Javier Martinez Canillas
2022-11-16 11:53 ` [PATCH v2 1/4] driver core: Make driver_deferred_probe_timeout a static variable Javier Martinez Canillas
2022-11-16 12:57 ` Andrew Halaney
2022-11-17 19:14 ` John Stultz
2022-12-12 8:50 ` Javier Martinez Canillas
2022-12-12 8:59 ` Greg Kroah-Hartman [this message]
2022-12-12 9:06 ` Javier Martinez Canillas
2022-11-16 12:00 ` [PATCH v2 2/4] driver core: Set deferred probe timeout to 0 if modules are disabled Javier Martinez Canillas
2022-11-16 16:39 ` Andrew Halaney
2022-11-16 16:51 ` Javier Martinez Canillas
2022-11-16 12:01 ` [PATCH v2 3/4] driver core: Add fw_devlink.timeout param to stop waiting for devlinks Javier Martinez Canillas
2022-11-16 16:09 ` Randy Dunlap
2022-11-16 19:05 ` Andrew Halaney
2022-11-17 15:19 ` Andrew Halaney
2022-11-17 18:55 ` Javier Martinez Canillas
2022-11-17 19:07 ` John Stultz
2022-11-17 19:16 ` Javier Martinez Canillas
2022-11-16 12:02 ` [PATCH v2 4/4] driver core: Disable driver deferred probe timeout by default Javier Martinez Canillas
2022-11-16 19:15 ` Andrew Halaney
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=Y5bthMXYH1MuD9VY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andersson@kernel.org \
--cc=ast@kernel.org \
--cc=bmasney@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dianders@chromium.org \
--cc=eballetbo@redhat.com \
--cc=javierm@redhat.com \
--cc=jstultz@google.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbrobinson@redhat.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=steev@kali.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