LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vaibhav Jain <vaibhav@linux.ibm.com>
To: Gautam Menghani <gautam@linux.ibm.com>
Cc: Gautam Menghani <Gautam.Menghani@ibm.com>,
	maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	chleroy@kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/64s: Fix the vector number in comments for h_facility_unavailable
Date: Mon, 18 May 2026 08:47:37 +0530	[thread overview]
Message-ID: <87lddh5ru6.fsf@vajain21.in.ibm.com> (raw)
In-Reply-To: <agcaxAANsk5gNzWX@Gautams-MacBook-Pro.local>

Gautam Menghani <gautam@linux.ibm.com> writes:

> On Wed, May 13, 2026 at 02:35:29PM +0530, Vaibhav Jain wrote:
>> Hey Gautam,
>> 
>> Thanks for the patch. Since this patch doesnt have any functional or
>> code change can you please put a 'trivial' suffix to it patch title like
>> [1] or some other suffix indicating its a non-functional change. That
>> way maintainers can easily pull the patch without worrying much about a
>> regression.
>> 
>> [1]
>> https://git.kernel.org/powerpc/c/d2827e5e2e0f0941a651f4b1ca5e9b778c4b5293
>
> Yeah I've mentioned "comments" in the title, so I guess that's fine?
>
> Thanks,
> Gautam

Bike shedding a bit but using the term 'trivial' might be better then
using the term 'comments'

-- 
Cheers
~ Vaibhav


      reply	other threads:[~2026-05-18  3:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  8:04 [PATCH] powerpc/64s: Fix the vector number in comments for h_facility_unavailable Gautam Menghani
2026-05-12 17:48 ` Harsh Prateek Bora
2026-05-12 18:03 ` Amit Machhiwal
2026-05-13  4:00 ` Ritesh Harjani
2026-05-13  9:05 ` Vaibhav Jain
2026-05-15 13:08   ` Gautam Menghani
2026-05-18  3:17     ` Vaibhav Jain [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=87lddh5ru6.fsf@vajain21.in.ibm.com \
    --to=vaibhav@linux.ibm.com \
    --cc=Gautam.Menghani@ibm.com \
    --cc=chleroy@kernel.org \
    --cc=gautam@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.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