Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Fenghua Yu <fenghua.yu@intel.com>, <x86@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	<linux-kernel@vger.kernel.org>, <llvm@lists.linux.dev>,
	<patches@lists.linux.dev>
Subject: Re: [PATCH v2] x86/resctrl: Annotate get_mem_config functions as __init
Date: Tue, 17 Sep 2024 08:14:17 -0700	[thread overview]
Message-ID: <c4175ca2-6551-4255-ab5c-0840f2b43008@intel.com> (raw)
In-Reply-To: <20240917133520.GA2360164@thelio-3990X>

Hi Nathan,

On 9/17/24 6:35 AM, Nathan Chancellor wrote:
> Hi Reinette,
> 
> On Mon, Sep 16, 2024 at 02:42:09PM -0700, Reinette Chatre wrote:
>> Just one nit in the subject ... this area has the custom to use "()" to
>> highlight that the name refers to a function, so rather:
>>
>> 	x86/resctrl: Annotate get_mem_config() functions as __init
> 
> Thanks, I am aware of this custom since I do it in the commit message
> but since get_mem_config() is a function in this file and it is not
> exactly touched by this change, it did not really feel appropriate to
> add the parentheses there.

hmmm ... I understand that () is used to highlight that the text is
referring to a function independent from how the function is impacted
by the change.

> 
> I can send a v3 with this fixed if so desired or perhaps whoever is
> going to apply this can just do it then?

Could you please send v3? That will make its inclusion smoother (pending
any other feedback from next level maintainers).

Thank you very much.

Reinette


  reply	other threads:[~2024-09-17 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 23:27 [PATCH v2] x86/resctrl: Annotate get_mem_config functions as __init Nathan Chancellor
2024-09-16 21:42 ` Reinette Chatre
2024-09-17 13:35   ` Nathan Chancellor
2024-09-17 15:14     ` Reinette Chatre [this message]
2024-09-17 16:04       ` Nathan Chancellor

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=c4175ca2-6551-4255-ab5c-0840f2b43008@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mingo@redhat.com \
    --cc=nathan@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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