linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hemant Kumar <hemantk@codeaurora.org>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>, manivannan.sadhasivam@linaro.org
Cc: linux-arm-msm@vger.kernel.org, jhugo@codeaurora.org,
	linux-kernel@vger.kernel.org, carl.yin@quectel.com,
	naveen.kumar@quectel.com, loic.poulain@linaro.org
Subject: Re: [PATCH v1 2/4] bus: mhi: pci_generic: Use enum entry for event ring priority
Date: Thu, 17 Jun 2021 15:21:32 -0700	[thread overview]
Message-ID: <1623968492.10055.7.camel@codeaurora.org> (raw)
In-Reply-To: <1623965435-30224-3-git-send-email-bbhatt@codeaurora.org>

On Thu, 2021-06-17 at 14:30 -0700, Bhaumik Bhatt wrote:
> Instead of using a default event ring priority of 1, use the enum
> provided and set it to default.
> 
> Signed-off-by: Bhaumik Bhatt <bbhatt@codeaurora.org>
> ---
Reviewed-by: Hemant Kumar <hemantk@codeaurora.org>
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project


  reply	other threads:[~2021-06-17 22:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 21:30 [PATCH v1 0/4] MHI event ring priority updates Bhaumik Bhatt
2021-06-17 21:30 ` [PATCH v1 1/4] bus: mhi: core: Add support for processing priority of event ring Bhaumik Bhatt
2021-06-18  7:03   ` Manivannan Sadhasivam
2021-06-18 17:17     ` Bhaumik Bhatt
2021-06-18 17:31       ` Manivannan Sadhasivam
2021-06-18 17:43         ` Bhaumik Bhatt
2021-06-17 21:30 ` [PATCH v1 2/4] bus: mhi: pci_generic: Use enum entry for event ring priority Bhaumik Bhatt
2021-06-17 22:21   ` Hemant Kumar [this message]
2021-06-17 21:30 ` [PATCH v1 3/4] ath11k: " Bhaumik Bhatt
2021-06-17 21:30 ` [PATCH v1 4/4] bus: mhi: core: Enable support for event ring priorities Bhaumik Bhatt
2021-06-17 22:20   ` Hemant Kumar

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=1623968492.10055.7.camel@codeaurora.org \
    --to=hemantk@codeaurora.org \
    --cc=bbhatt@codeaurora.org \
    --cc=carl.yin@quectel.com \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=naveen.kumar@quectel.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).