From: Greg KH <gregkh@linuxfoundation.org>
To: JeffleXu <jefflexu@linux.alibaba.com>
Cc: sashal@kernel.org, stable@vger.kernel.org,
joseph.qi@linux.alibaba.com, caspar@linux.alibaba.com,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH 1/3] virtio-blk: close udev startup race condition as default groups
Date: Wed, 17 Feb 2021 14:26:37 +0100 [thread overview]
Message-ID: <YC0ZjUYhSCawoJ7N@kroah.com> (raw)
In-Reply-To: <6046ceef-061c-d93f-b6a1-2ce2483bec3c@linux.alibaba.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Feb 17, 2021 at 09:12:38PM +0800, JeffleXu wrote:
> Hi all,
>
> Would you please evaluate if these should be fixed in stable tree, at
> least for the virtio-blk scenario [1] ?
What is "these"?
> [1] commit e982c4d0a29b1d61fbe7716a8dcf8984936d6730 ("virtio-blk:
> modernize sysfs attribute creation")
Do you want this backported? To where? Why? If so, where is the
working backport that you have properly tested?
totally confused,
greg k-h
next prev parent reply other threads:[~2021-02-17 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 11:46 [PATCH 0/3] close udev startup race condition for several devices Jeffle Xu
2021-02-07 11:46 ` [PATCH 1/3] virtio-blk: close udev startup race condition as default groups Jeffle Xu
2021-02-07 11:56 ` Greg KH
2021-02-07 22:46 ` Sasha Levin
2021-02-08 1:40 ` JeffleXu
2021-02-17 13:12 ` JeffleXu
2021-02-17 13:26 ` Greg KH [this message]
2021-02-18 2:23 ` JeffleXu
2021-02-07 11:46 ` [PATCH 2/3] aoe: " Jeffle Xu
2021-02-07 11:46 ` [PATCH 3/3] nvme: " Jeffle Xu
2021-02-07 11:52 ` [PATCH 0/3] close udev startup race condition for several devices JeffleXu
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=YC0ZjUYhSCawoJ7N@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=caspar@linux.alibaba.com \
--cc=hare@suse.de \
--cc=jefflexu@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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