linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saravana Kannan <saravanak@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	John Stultz <john.stultz@linaro.org>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Saravana Kannan <saravanak@google.com>
Cc: kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Fix issues with deferred_probe_timeout being non-zero
Date: Wed, 25 May 2022 20:46:07 -0700	[thread overview]
Message-ID: <20220526034609.480766-1-saravanak@google.com> (raw)

Setting deferred_probe_timeout to a non-zero default used to cause
issues with NFS rootfs. But the fix for that is causing other problem.
So revert the fix and set the default deferred_probe_timeout back to
zero.

Most of the Cc list if from commit 35a672363ab3. Please let me know if
you want to be removed from future patches related to
deferred_probe_timeout and NFS rootfs issues.

-Saravana

Saravana Kannan (2):
  driver core: Fix wait_for_device_probe() & deferred_probe_timeout
    interaction
  driver core: Set default deferred_probe_timeout back to 0.

 drivers/base/dd.c | 10 ----------
 1 file changed, 10 deletions(-)

-- 
2.36.1.124.g0e6072fb45-goog


             reply	other threads:[~2022-05-26  3:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  3:46 Saravana Kannan [this message]
2022-05-26  3:46 ` [PATCH v1 1/2] driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction Saravana Kannan
2022-05-26  4:04   ` John Stultz
2022-05-26  3:46 ` [PATCH v1 2/2] driver core: Set default deferred_probe_timeout back to 0 Saravana Kannan
2022-05-30  9:44 ` [PATCH v1 0/2] Fix issues with deferred_probe_timeout being non-zero Geert Uytterhoeven

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=20220526034609.480766-1-saravanak@google.com \
    --to=saravanak@google.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@android.com \
    --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;
as well as URLs for NNTP newsgroup(s).