From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: fenghua.yu@intel.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] kernel: cpu: resctrl: Minor typo fix in the file pseudo_lock.c
Date: Thu, 18 Mar 2021 03:51:08 +0530 [thread overview]
Message-ID: <YFKA1E27BoCC+uNc@ArchLinux> (raw)
In-Reply-To: <d2d6f71a-851d-efc0-df17-bb5dcc8e776e@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On 13:31 Wed 17 Mar 2021, Reinette Chatre wrote:
>Hi Bhaskar,
>
>On 3/17/2021 12:33 PM, Bhaskar Chowdhury wrote:
>> On 10:54 Wed 17 Mar 2021, Reinette Chatre wrote:
>>> Thank you very much for catching this typo.
>>>
>>> My feedback [1] to a previous patch from you applies here also. The
>>> prefix should be "x86/resctrl:" for contributions to this area.
>>>
>> Thanks for the heads up!
>
>This was the third time I mention this to you.
>
Meh ...heck..that means something more important than your words occupied my
mind ...anyway...
>> Do you want another revision of it, or will you
>> take it as it is???
>
>If accepted I am not the one who will merge this patch so having a
>version that is ready for merge (all feedback addressed) would be best.
>
Thanks for the explanations.
>> I am noting down your point ,so ,I might pull out next
>> time I intend to sent out something to this specific area.
>
>Please do note that my comment was not specific to resctrl. This prefix
>style is used by x86 area.
>
I do understand.
>Reinette
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-17 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 8:40 [PATCH] kernel: cpu: resctrl: Minor typo fix in the file pseudo_lock.c Bhaskar Chowdhury
2021-03-17 17:54 ` Reinette Chatre
2021-03-17 18:01 ` Randy Dunlap
2021-03-17 19:29 ` Bhaskar Chowdhury
2021-03-17 19:33 ` Bhaskar Chowdhury
2021-03-17 20:31 ` Reinette Chatre
2021-03-17 22:21 ` Bhaskar Chowdhury [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=YFKA1E27BoCC+uNc@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=reinette.chatre@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.