linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: avri.altman@wdc.com, adrian.hunter@intel.com, bvanassche@acm.org,
	jpinto@synopsys.com, stanley.chu@mediatek.com, satyat@google.com,
	jejb@linux.ibm.com, Keoseong Park <keosung.park@samsung.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	ALIM AKHTAR <alim.akhtar@samsung.com>,
	asutoshd@codeaurora.org, joe@perches.com, cang@codeaurora.org,
	Kiwoong Kim <kwmad.kim@samsung.com>,
	beanhuo@micron.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2] scsi: ufs: Refactor ufshcd_is_intr_aggr_allowed()
Date: Fri, 23 Jul 2021 22:13:53 -0400	[thread overview]
Message-ID: <162692235522.25137.16055407630853050493.b4-ty@oracle.com> (raw)
In-Reply-To: <1891546521.01624860001810.JavaMail.epsvc@epcpadp3>

On Mon, 28 Jun 2021 14:58:01 +0900, Keoseong Park wrote:

> Simplify if else statement to return statement,
> and remove code related to CONFIG_SCSI_UFS_DWC that is not in use.
> 
> v1 -> v2
> Remove code related to CONFIG_SCSI_UFS_DWC that is not in use.

Applied to 5.15/scsi-queue, thanks!

[1/1] scsi: ufs: Refactor ufshcd_is_intr_aggr_allowed()
      https://git.kernel.org/mkp/scsi/c/1c0810e79cb3

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2021-07-24  2:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210628055801epcms2p449fdffa1a6c801497d7e65bae2896b79@epcms2p4>
2021-06-28  5:58 ` [PATCH v2] scsi: ufs: Refactor ufshcd_is_intr_aggr_allowed() Keoseong Park
2021-06-28  6:32   ` Bean Huo
2021-06-28 16:56   ` Bart Van Assche
2021-07-18 21:52   ` Martin K. Petersen
2021-07-24  2:13   ` Martin K. Petersen [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=162692235522.25137.16055407630853050493.b4-ty@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=jejb@linux.ibm.com \
    --cc=joe@perches.com \
    --cc=jpinto@synopsys.com \
    --cc=keosung.park@samsung.com \
    --cc=kwmad.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=satyat@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).