From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, tglx@linutronix.de,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: events: intel: A letter change in a word to make it sound right,in the file bts.c
Date: Tue, 16 Mar 2021 11:00:48 +0530 [thread overview]
Message-ID: <YFBCiNzEZJp3CTSv@ArchLinux> (raw)
In-Reply-To: <ecbefd37-1504-a167-760a-96026b9f67b0@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On 22:19 Mon 15 Mar 2021, Randy Dunlap wrote:
>On 3/15/21 9:19 PM, Bhaskar Chowdhury wrote:
>>
>> s/kernal/kernel/
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> arch/x86/events/intel/bts.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/events/intel/bts.c b/arch/x86/events/intel/bts.c
>> index 731dd8d0dbb1..6320d2cfd9d3 100644
>> --- a/arch/x86/events/intel/bts.c
>> +++ b/arch/x86/events/intel/bts.c
>> @@ -594,7 +594,7 @@ static __init int bts_init(void)
>> * we cannot use the user mapping since it will not be available
>> * if we're not running the owning process.
>> *
>> - * With PTI we can't use the kernal map either, because its not
>> + * With PTI we can't use the kernel map either, because its not
>
> it's
>
Heck!
>> * there when we run userspace.
>> *
>> * For now, disable this driver when using PTI.
>> --
>
>
>--
>~Randy
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-16 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 4:19 [PATCH] x86: events: intel: A letter change in a word to make it sound right,in the file bts.c Bhaskar Chowdhury
2021-03-16 5:19 ` Randy Dunlap
2021-03-16 5:30 ` 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=YFBCiNzEZJp3CTSv@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--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