All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	Avri Altman <avri.altman@wdc.com>,
	linux-scsi@vger.kernel.org,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	Bean Huo <beanhuo@micron.com>,
	Stanley Chu <stanley.chu@mediatek.com>,
	Asutosh Das <quic_asutoshd@quicinc.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: ufs: Increase the START STOP UNIT timeout from 1 s to 10 s
Date: Wed, 12 Apr 2023 09:34:17 -0700	[thread overview]
Message-ID: <ce0794e1-45d5-c76a-9835-7285353e786c@acm.org> (raw)
In-Reply-To: <a71dc651-a306-eebe-968e-0d9e56f44a76@intel.com>

On 4/11/23 11:31, Adrian Hunter wrote:
> It would be better not to assume current stable trees are the only
> consumers of fixes.  Presumably adding the extra Fixes tag does no
> harm.

Hi Adrian,

The convention is to add a reference to the most recent patch that got 
fixed in the patch description. Anyone who backports fixes is assumed to 
follow the chain of patches transitively that is created by Fixes: tags.

Thanks,

Bart.



  reply	other threads:[~2023-04-12 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  0:11 [PATCH] scsi: ufs: Increase the START STOP UNIT timeout from 1 s to 10 s Bart Van Assche
2023-04-11  8:39 ` Adrian Hunter
2023-04-11 17:31   ` Bart Van Assche
2023-04-11 18:31     ` Adrian Hunter
2023-04-12 16:34       ` Bart Van Assche [this message]
2023-04-12 17:24         ` Adrian Hunter
2023-04-12 17:31           ` Bart Van Assche

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=ce0794e1-45d5-c76a-9835-7285353e786c@acm.org \
    --to=bvanassche@acm.org \
    --cc=adrian.hunter@intel.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=jaegeuk@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_asutoshd@quicinc.com \
    --cc=stanley.chu@mediatek.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.