mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xin Li <xin@zytor.com>
To: Harry Fellowes <harryfellowes1@gmail.com>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	hpa@zytor.com
Subject: Re: [PATCH] x86/boot: clean up whitespace in a20.c
Date: Mon, 25 Aug 2025 11:01:32 -0700	[thread overview]
Message-ID: <50f68d28-beb4-4dab-b077-e9e2ba1ae9ee@zytor.com> (raw)
In-Reply-To: <20250825174641.16030-1-harryfellowes1@gmail.com>

On 8/25/2025 10:46 AM, Harry Fellowes wrote:
> Remove trailing whitespace and fix blank lines in arch/x86/boot/a20.c
> reported by checkpatch.pl.
> 
> No functional changes.
> 
> Signed-off-by: Harry Fellowes <harryfellowes1@gmail.com>
> ---
>   arch/x86/boot/a20.c | 18 +++++++++---------
>   1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/arch/x86/boot/a20.c b/arch/x86/boot/a20.c
> index a2b6b428922a..15bbd4ac55cc 100644
> --- a/arch/x86/boot/a20.c
> +++ b/arch/x86/boot/a20.c
> @@ -135,29 +135,29 @@ int enable_a20(void)
>   		  (legacy free, etc.) */
>   	       if (a20_test_short())
>   		       return 0;
> -	
> +

This is good.

>   	       /* Next, try the BIOS (INT 0x15, AX=0x2401) */
>   	       enable_a20_bios();
>   	       if (a20_test_short())
>   		       return 0;
> -	
> -	       /* Try enabling A20 through the keyboard controller */
> +
> +/* Try enabling A20 through the keyboard controller */

Why?  We do tabs at the beginning.

>   	       kbc_err = empty_8042();
>   
>   	       if (a20_test_short())
>   		       return 0; /* BIOS worked, but with delayed reaction */
> -	
> -	       if (!kbc_err) {
> +
> +if (!kbc_err) {

...

>   		       enable_a20_kbc();
>   		       if (a20_test_long())
>   			       return 0;
>   	       }
> -	
> -	       /* Finally, try enabling the "fast A20 gate" */
> +
> +/* Finally, try enabling the "fast A20 gate" */

...

>   	       enable_a20_fast();
>   	       if (a20_test_long())
>   		       return 0;
>          }
> -
> -       return -1;
> +
> +return -1;

Fix one but then add four, not a good deal.


>   }


      reply	other threads:[~2025-08-25 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 17:46 Harry Fellowes
2025-08-25 18:01 ` Xin Li [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=50f68d28-beb4-4dab-b077-e9e2ba1ae9ee@zytor.com \
    --to=xin@zytor.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=harryfellowes1@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®