public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ia64: kernel: Few typos fixed in the file fsys.S
Date: Thu, 11 Mar 2021 06:36:57 +0000	[thread overview]
Message-ID: <YEm3ubX2Jqu49MwF@Gentoo> (raw)
In-Reply-To: <e26a1461-0d05-d79c-7688-de45d285e068@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

On 22:15 Wed 10 Mar 2021, Randy Dunlap wrote:
>On 3/10/21 10:10 PM, Bhaskar Chowdhury wrote:
>>
>> Mundane spelling fixes.
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>
>Acked-by: Randy Dunlap <rdunlap@infradead.org>
>
>but no maintainer Cc:ed to pick it up...
>
I have seen "maintainer less" files and you have pointed out that too in the
past...what do I do Randy??? Should run "git blame" to find out ,who touch the file and
include those mail??? I don't think that would be good idea.

Bemused!! Throw some light.
>> ---
>>  arch/ia64/kernel/fsys.S | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/ia64/kernel/fsys.S b/arch/ia64/kernel/fsys.S
>> index 0750a716adc7..2094f3249019 100644
>> --- a/arch/ia64/kernel/fsys.S
>> +++ b/arch/ia64/kernel/fsys.S
>> @@ -172,7 +172,7 @@ ENTRY(fsys_gettimeofday)
>>  	// r25 = itc_lastcycle value
>>  	// r26 = address clocksource cycle_last
>>  	// r27 = (not used)
>> -	// r28 = sequence number at the beginning of critcal section
>> +	// r28 = sequence number at the beginning of critical section
>>  	// r29 = address of itc_jitter
>>  	// r30 = time processing flags / memory address
>>  	// r31 = pointer to result
>> @@ -432,7 +432,7 @@ GLOBAL_ENTRY(fsys_bubble_down)
>>  	 *	- r29: psr
>>  	 *
>>  	 * We used to clear some PSR bits here but that requires slow
>> -	 * serialization.  Fortuntely, that isn't really necessary.
>> +	 * serialization.  Fortunately, that isn't really necessary.
>>  	 * The rationale is as follows: we used to clear bits
>>  	 * ~PSR_PRESERVED_BITS in PSR.L.  Since
>>  	 * PSR_PRESERVED_BITS==PSR.{UP,MFL,MFH,PK,DT,PP,SP,RT,IC}, we
>> --
>
>
>--
>~Randy
>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-03-11  6:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  6:22 [PATCH] ia64: kernel: Few typos fixed in the file fsys.S Bhaskar Chowdhury
2021-03-11  6:15 ` Randy Dunlap
2021-03-11  6:17   ` John Paul Adrian Glaubitz
2021-03-11  6:21     ` Randy Dunlap
2021-03-11  6:36   ` Bhaskar Chowdhury [this message]
2021-03-11  6:30     ` Randy Dunlap

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=YEm3ubX2Jqu49MwF@Gentoo \
    --to=unixbhaskar@gmail.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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