mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Doug Gilbert <dgilbert@interlog.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH v3 0/3] scsi: ufs: minor cleanups
Date: Wed, 22 Jun 2022 16:50:03 +0200	[thread overview]
Message-ID: <349ba57a-87c4-b49f-aca5-7d62d55068d5@linaro.org> (raw)
In-Reply-To: <20220613100655.105301-1-krzysztof.kozlowski@linaro.org>

On 13/06/2022 12:06, Krzysztof Kozlowski wrote:
> Hi,
> 
> Changes since v2
> ================
> 1. More whitespace cleanups.
> 
> Changes since v1
> ================
> 1. Drop patch 1 (needs further work).
> 2. Rebase on current linux-next (including Bart Van Assche's work).
> 
> v1: https://lore.kernel.org/all/20220408103027.311624-1-krzysztof.kozlowski@linaro.org/
> 

Hi folks,

Any comments? Patches are BTW independent, so the UFS one can be applied
separately.

Best regards,
Krzysztof

      parent reply	other threads:[~2022-06-22 14:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 10:06 Krzysztof Kozlowski
2022-06-13 10:06 ` [PATCH v3 1/3] scsi: core: fix white-spaces Krzysztof Kozlowski
2022-06-13 10:06 ` [PATCH v3 2/3] scsi: ufs: ufshcd-pltfrm: constify pointed data Krzysztof Kozlowski
2022-06-22 16:11   ` Bart Van Assche
2022-06-13 10:06 ` [PATCH v3 3/3] scsi: ufs: ufshcd: " Krzysztof Kozlowski
2022-06-22 16:13   ` Bart Van Assche
2022-06-23  7:16     ` Krzysztof Kozlowski
2022-06-22 14:50 ` Krzysztof Kozlowski [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=349ba57a-87c4-b49f-aca5-7d62d55068d5@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dgilbert@interlog.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®