linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, linux-hyperv@vger.kernel.org,
	Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH] revert async probing of VMBus scsi device
Date: Wed, 5 Jun 2019 12:10:20 -0700	[thread overview]
Message-ID: <20190605121020.1a41b753@hermes.lan> (raw)
In-Reply-To: <20190605190722.GA19684@infradead.org>

On Wed, 5 Jun 2019 12:07:23 -0700
Christoph Hellwig <hch@infradead.org> wrote:

> On Wed, Jun 05, 2019 at 12:06:40PM -0700, Stephen Hemminger wrote:
> > > Which is true for every device, and why we use UUIDs or label for
> > > mounts that are supposed to be stable.  
> > 
> > Not everyone is smart enough to do that.  
> 
> Sure.  But they should not get a way out for just one specific driver.

There are people running new kernels on 6 year old distributions.
Was every distribution smart enough then? If you think so, then
this not necessary.

  reply	other threads:[~2019-06-05 19:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 18:52 [PATCH] revert async probing of VMBus scsi device Stephen Hemminger
2019-06-05 18:54 ` Haiyang Zhang
2019-06-05 18:56 ` Christoph Hellwig
2019-06-05 19:06   ` Stephen Hemminger
2019-06-05 19:07     ` Christoph Hellwig
2019-06-05 19:10       ` Stephen Hemminger [this message]
2019-06-05 19:26         ` Christoph Hellwig
2019-06-05 20:06           ` Stephen Hemminger
2019-06-05 21:20           ` Stephen Hemminger
2019-06-05 19:27       ` David Miller

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=20190605121020.1a41b753@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=hch@infradead.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sthemmin@microsoft.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).