mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: 高严凯 <gaoyankaigeren@gmail.com>, "Bean Huo" <huobean@gmail.com>
Cc: Avri Altman <Avri.Altman@wdc.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	"James E . J . Bottomley" <jejb@linux.ibm.com>,
	Bean Huo <beanhuo@micron.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ufs: core: Disable auto h8 before ssu
Date: Thu, 20 Oct 2022 10:47:41 -0700	[thread overview]
Message-ID: <828a4157-09c3-3fc5-175e-b4da508a35d0@acm.org> (raw)
In-Reply-To: <CAFN68yVLdwrJBivqjGfGd7qiGp_h8FwucBLvSH97wNiyik4nQw@mail.gmail.com>

On 10/19/22 22:15, 高严凯 wrote:
> Do you agree this patch? I'd like to hear your opinion about this.

Hi,

On Linux kernel mailing lists it is expected that replies are posted 
below the original email instead of above. Please follow this 
convention. More information is available at 
https://en.wikipedia.org/wiki/Posting_style#Bottom-posting.

Please also do the following:
* Fix the issues reported by the kernel test robot.
* Follow the recommendations from Avri and Bean.

Thanks,

Bart.


  reply	other threads:[~2022-10-20 17:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  2:16 Ten Gao
2022-10-11  3:39 ` kernel test robot
2022-10-11  7:07 ` Avri Altman
2022-10-11 11:53   ` 高严凯
2022-10-12  6:28     ` Avri Altman
2022-10-12  8:12       ` Avri Altman
2022-10-12  8:49         ` 高严凯
2022-10-12 14:25     ` Bean Huo
2022-10-14  2:44       ` 高严凯
2022-10-14  5:48         ` Bean Huo
2022-10-14 10:15           ` 高严凯
2022-10-20  5:15             ` 高严凯
2022-10-20 17:47               ` Bart Van Assche [this message]
2022-10-11  9:59 ` kernel test robot

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=828a4157-09c3-3fc5-175e-b4da508a35d0@acm.org \
    --to=bvanassche@acm.org \
    --cc=Avri.Altman@wdc.com \
    --cc=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=beanhuo@micron.com \
    --cc=gaoyankaigeren@gmail.com \
    --cc=huobean@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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
all inboxes | Powered by JetHome®