From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniil Lunev <dlunev@chromium.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Bart Van Assche <bvanassche@acm.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>, Bean Huo <beanhuo@micron.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Keoseong Park <keosung.park@samsung.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Sohaib Mohamed <sohaib.amhmd@gmail.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v7] ufs: core: print UFSHCD capabilities in controller's sysfs node
Date: Mon, 22 Aug 2022 11:28:13 +0200 [thread overview]
Message-ID: <YwNMLRMl6CpEu54/@kroah.com> (raw)
In-Reply-To: <CAONX=-fScRJt-j1USO6gKXm780S=XBGHVc_LUziSZDiStc5P6A@mail.gmail.com>
On Mon, Aug 22, 2022 at 07:03:02PM +1000, Daniil Lunev wrote:
> On Mon, Aug 15, 2022 at 4:42 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > Please provide a lot more information about this in the changelog text.
> > What would you want to see here if you had to review this change?
>
> Hi Greg,
> Sorry for toppost, let me try again.
> Can you clarify what specifically is missing from the changelog?
What changelog? I don't really know anymore as I have no context,
sorry. Remember some of us get 1000+ emails a day to deal with.
thanks,
greg k-h
prev parent reply other threads:[~2022-08-22 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 0:48 [PATCH v7] ufs: core: print UFSHCD capabilities in controller's sysfs node Daniil Lunev
2022-08-15 6:42 ` Greg Kroah-Hartman
2022-08-21 23:59 ` Daniil Lunev
2022-08-22 6:10 ` Greg Kroah-Hartman
2022-08-22 9:03 ` Daniil Lunev
2022-08-22 9:28 ` Greg Kroah-Hartman [this message]
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=YwNMLRMl6CpEu54/@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=dlunev@chromium.org \
--cc=jejb@linux.ibm.com \
--cc=keosung.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchehab+huawei@kernel.org \
--cc=sohaib.amhmd@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