mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nitin Rawat <quic_nitirawa@quicinc.com>
To: Markus Elfring <Markus.Elfring@web.de>,
	<linux-scsi@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	Bart Van Assche <bvanassche@acm.org>,
	"James Bottomley" <James.Bottomley@HansenPartnership.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ufs: ufs-qcom: Fix ESI null pointer dereference
Date: Mon, 11 Aug 2025 00:45:43 +0530	[thread overview]
Message-ID: <4ce3b453-1941-42ac-ae03-e66c09f40852@quicinc.com> (raw)
In-Reply-To: <f9dfcc92-4591-41bb-973b-86d12ca37e19@web.de>



On 8/10/2025 5:30 PM, Markus Elfring wrote:
> …
>> Fix by restructuring the ESI configuration to try MSI allocation
>> first, before any other resource allocation and …
> 
> How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n145

Sorry, I missed adding the Fixes tag in the commit message. Thanks for 
pointing it out.  I’ll make sure to include in next patchset.

> 
> Regards,
> Markus


      reply	other threads:[~2025-08-10 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-09 13:44 [PATCH V1] " Nitin Rawat
2025-08-10 12:00 ` [PATCH] " Markus Elfring
2025-08-10 19:15   ` Nitin Rawat [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=4ce3b453-1941-42ac-ae03-e66c09f40852@quicinc.com \
    --to=quic_nitirawa@quicinc.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Markus.Elfring@web.de \
    --cc=bvanassche@acm.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=neil.armstrong@linaro.org \
    --cc=tglx@linutronix.de \
    /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®