public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Marco Crivellari <marco.crivellari@suse.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fix whitespace damage in r4k_wait from VS timer fix
Date: Mon, 1 Dec 2025 10:40:47 +0100	[thread overview]
Message-ID: <aS1in-g4pb7J0Xez@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2510191229030.39634@angie.orcam.me.uk>

On Sun, Oct 19, 2025 at 12:49:02PM +0100, Maciej W. Rozycki wrote:
> Remove stray spaces/tabs introduced with commit 56651128e2fb ("MIPS: Fix 
> idle VS timer enqueue") and add missing indentation for a branch delay 
> slot.
> 
> Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk>
> ---
> It would have been caught, for the most issues, with:
> 
> whitespace = indent-with-non-tab,space-before-tab,trailing-space
> 
> in git configuration.  Is there a way to get it propagated with checkouts?
> ---
>  arch/mips/kernel/genex.S |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2025-12-01  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-19 11:49 [PATCH] MIPS: Fix whitespace damage in r4k_wait from VS timer fix Maciej W. Rozycki
2025-12-01  6:50 ` [PING][PATCH] " Maciej W. Rozycki
2025-12-01  9:40 ` Thomas Bogendoerfer [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=aS1in-g4pb7J0Xez@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=marco.crivellari@suse.com \
    /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