From: Javier Martinez Canillas <javierm@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 10:06:08 +0100 [thread overview]
Message-ID: <83ec1332-7e08-208e-31aa-d326af67337f@redhat.com> (raw)
In-Reply-To: <Y5bthMXYH1MuD9VY@kroah.com>
On 12/12/22 09:59, Greg Kroah-Hartman wrote:
> On Mon, Dec 12, 2022 at 09:50:16AM +0100, Javier Martinez Canillas wrote:
[...]
>> 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.
>
Sure, I will. Thanks!
> thanks,
>
> greg k-h
>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2022-12-12 9:07 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
2022-12-12 9:06 ` Javier Martinez Canillas [this message]
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=83ec1332-7e08-208e-31aa-d326af67337f@redhat.com \
--to=javierm@redhat.com \
--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=gregkh@linuxfoundation.org \
--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 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.