From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
fenghua.yu@intel.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, reinette.chatre@intel.com
Subject: Re: [PATCH V4] arch: kernel: cpu: x86/resctrl: Takes a letter away and append a colon to match below struct member
Date: Tue, 12 Jan 2021 18:51:44 -0800 [thread overview]
Message-ID: <a6e94a78-9841-96bb-f07f-4bd01d6a6903@infradead.org> (raw)
In-Reply-To: <20210113024838.GA28337@debian>
On 1/12/21 6:48 PM, Bhaskar Chowdhury wrote:
> On 20:24 Tue 12 Jan 2021, Gustavo A. R. Silva wrote:
>>
>>
>> On 1/12/21 20:03, Bhaskar Chowdhury wrote:
>>> s/kernlfs/kernfs/
>>> s/@mon_data_kn/@mon_data_kn:/
>>>
>>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>>> ---
>>> Changes from V3: Fix the subject line typo stuc to struct and mention cpu architecture
>>
>> ...and what changed from v1 to v2 and from v2 to v3?
>>
>
> Gustavo, it seems you are not following up properly ....could you please put
> little more effort for know it????
>
> There were mails....pls scan and read ..
All of these version change logs should be in this patch, under the "---" line.
--
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law
next prev parent reply other threads:[~2021-01-13 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 2:03 [PATCH V4] arch: kernel: cpu: x86/resctrl: Takes a letter away and append a colon to match below struct member Bhaskar Chowdhury
[not found] ` <f20be5e1-a2a6-14d4-5813-1fb716783bb2@embeddedor.com>
2021-01-13 2:48 ` Bhaskar Chowdhury
2021-01-13 2:51 ` Randy Dunlap [this message]
2021-01-13 3:02 ` Bhaskar Chowdhury
[not found] ` <8aafe837-f4e9-1440-890b-f07d83eed30c@embeddedor.com>
2021-01-13 10:41 ` Bhaskar Chowdhury
2021-01-13 17:11 ` Reinette Chatre
2021-01-13 17:42 ` Fenghua Yu
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=a6e94a78-9841-96bb-f07f-4bd01d6a6903@infradead.org \
--to=rdunlap@infradead.org \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=gustavo@embeddedor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=unixbhaskar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).