From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Doug Anderson <dianders@chromium.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Evan Green <evgreen@chromium.org>,
vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
stanislav.nijnikov@wdc.com, linux-scsi@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Bart.VanAssche@wdc.com, Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH v4] scsi: ufs: Make sysfs attributes writable
Date: Tue, 25 Sep 2018 21:08:09 -0400 [thread overview]
Message-ID: <yq1h8idgj5y.fsf@oracle.com> (raw)
In-Reply-To: <CAD=FV=W7h_3LwV-P5_E58-3qOo7Y-yQDTDfSLoU1+3c_6ZF0cg@mail.gmail.com> (Doug Anderson's message of "Tue, 25 Sep 2018 11:40:54 -0700")
Doug,
> I came across this patch and Evan's other one and noticed that they
> haven't been applied though a batch of other SCSI patches for 4.20
> were applied about a week ago. Martin: is there something about these
> patches that needs to change before they can land?
I have simply been awaiting some sort of consensus on the various
competing approaches. Lots of patches posted with tiny incremental fixes
but very little discussion about the merits of one over the other.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-09-26 1:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 22:44 [PATCH v4] scsi: ufs: Make sysfs attributes writable Evan Green
2018-08-09 8:14 ` Stanislav Nijnikov
2018-08-22 11:00 ` Adrian Hunter
2018-09-04 10:27 ` Adrian Hunter
2018-09-25 18:40 ` Doug Anderson
2018-09-26 1:08 ` Martin K. Petersen [this message]
2018-09-26 1:46 ` Doug Anderson
2018-09-26 17:41 ` Evan Green
2018-09-27 6:32 ` Avri Altman
2018-09-27 14:01 ` Christoph Hellwig
2018-09-27 23:16 ` Evan Green
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=yq1h8idgj5y.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stanislav.nijnikov@wdc.com \
--cc=vinholikatti@gmail.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