mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Larsson <andreas@gaisler.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] sparc updates for v7.4
Date: Thu, 29 Oct 2026 10:50:11 +0100	[thread overview]
Message-ID: <69d7b329-4e67-4948-891b-1138d26db6d2@gaisler.com> (raw)
In-Reply-To: <9d7432f2a82685fe36f807a38f4ebd0a76f1cabf.camel@physik.fu-berlin.de>

On 2026-10-29 09:05, John Paul Adrian Glaubitz wrote:
> Hi Andreas,
> 
> On Thu, 2026-10-29 at 08:03 +0100, Andreas Larsson wrote:
>> I got a late Tested-by for one of the patches, "sparc64: increase kernel
>> thread stack size to 32K" that I picked up already 2026-09-27, that I
>> inserted just before preparing the pull request. Sorry about that. Apart
>> from that added Tested-by, all changes has been on my for-next since
>> 2026-10-23, and most much longer than that, and with that included in
>> linux-next.
> 
> If you really want to modify an old commit without touching the date, you
> can use this git rebase command:
> ...

I'm happy if my sparc-for-7.4-tag2 tag, that points to the actual commit
that has been included by linux-next, is merged as is, without the added
Tested-by. No need to complicate things with additional options at this
point I think.


>> Below follows a pull request for my original for-next before the added
>> Tested-by. I hope you can take either my original pull request with my
>> explanation of the one below if you rather want to have commit dates
>> that better represents when they were picked up.
> 
> Can you push this to your for-linus branch?

My for-next branch is back where it was, i.e. where sparc-for-7.4-tag2
is now pointing.

Cheers,
Andreas


  reply	other threads:[~2026-10-29  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 13:44 Andreas Larsson
2026-10-28 17:03 ` Linus Torvalds
2026-10-28 20:50   ` John Paul Adrian Glaubitz
2026-10-28 20:56     ` John Paul Adrian Glaubitz
2026-10-29  7:03   ` Andreas Larsson
2026-10-29  8:05     ` John Paul Adrian Glaubitz
2026-10-29  9:50       ` Andreas Larsson [this message]
2026-10-29 22:49       ` Linus Torvalds
2026-10-30  6:47         ` John Paul Adrian Glaubitz
2026-10-30  7:25         ` Andreas Larsson

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=69d7b329-4e67-4948-891b-1138d26db6d2@gaisler.com \
    --to=andreas@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®