From: Greg KH <greg@kroah.com>
To: Aleksa Sarai <cyphar@cyphar.com>
Cc: Aleksa Sarai <asarai@suse.de>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org,
Valentin Rothberg <vrothberg@suse.com>,
stable@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH v3] scsi: require CAP_SYS_ADMIN to write to procfs interface
Date: Sun, 5 Nov 2017 11:29:42 +0100 [thread overview]
Message-ID: <20171105102942.GA31503@kroah.com> (raw)
In-Reply-To: <CAOviyagXOJE3JqYwd3hUNA+qL0cRVafDgma8FTvq9To9iBaYmQ@mail.gmail.com>
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 Sun, Nov 05, 2017 at 08:11:20PM +1100, Aleksa Sarai wrote:
> I've booted it on a few of my laptops, and nothing seemed to break. Is
> there a particular test-suite you'd recommend that I run?
Workloads/tools that normally interact with this file would be the best
ones, right? Odds are, your normal "laptop booting/running" mode does
not do anything with this file.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-05 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 2:56 [PATCH v3] scsi: require CAP_SYS_ADMIN to write to procfs interface Aleksa Sarai
[not found] ` <20171105025635.10843-1-asarai-l3A5Bk7waGM@public.gmane.org>
2017-11-05 4:02 ` Aleksa Sarai
2017-11-05 4:02 ` Aleksa Sarai
[not found] ` <b3bcff37-d77d-4dc6-ba83-7dddcb51a703-l3A5Bk7waGM@public.gmane.org>
2017-11-09 21:40 ` Eric W. Biederman
2017-11-09 21:40 ` Eric W. Biederman
2017-11-09 21:40 ` Eric W. Biederman
2017-11-05 7:31 ` Greg KH
[not found] ` <20171105073121.GB1431-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-11-05 9:11 ` Aleksa Sarai
2017-11-05 9:11 ` Aleksa Sarai
2017-11-05 10:29 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-05 2:56 Aleksa Sarai
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=20171105102942.GA31503@kroah.com \
--to=greg@kroah.com \
--cc=asarai@suse.de \
--cc=containers@lists.linux-foundation.org \
--cc=cyphar@cyphar.com \
--cc=ebiederm@xmission.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--cc=vrothberg@suse.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 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.