mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Daniel Gomez <da.gomez@samsung.com>,
	linux-modules@vger.kernel.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Modules fixes for v6.16-rc6
Date: Wed, 9 Jul 2025 21:14:23 +0200	[thread overview]
Message-ID: <64c1b31c-a65f-4eaf-b343-0b5b9b2c1086@kernel.org> (raw)
In-Reply-To: <CAHk-=whHRv28HBL47x-L5okG+fZDJyX432uxG3AQqbqRAgkAYQ@mail.gmail.com>

On 08/07/2025 22.21, Linus Torvalds wrote:
> On Tue, 8 Jul 2025 at 12:38, Daniel Gomez <da.gomez@kernel.org> wrote:
>>
>> Petr and Sebastian went down to the archive history  (before Git) and
>> found the commit that broke it b3b91325f3c7 ("Don't relocate
>> non-allocated regions in modules.").
> 
> When mentioning git commits in other trees, you really do need to
> mention *which* other tree it is.

Makes sense. I thought there was only one history tree to search for this.

> 
> In this case, it seems to be
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux-fullhistory.git/
> 
> that has that commit, but that's actually a kind of odd tree.
> 
> The typical bitkeeper conversion tree (which is where I suspect the
> full-history conversion then got it from, unless somebody did a
> separate conversion) that contains that commit is actually
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/

Thanks for the link.

> 
> and there the commit has commit ID 1a6100caae ("Don't relocate
> non-allocated regions in modules")

That's it.

> 
>                  Linus

  parent reply	other threads:[~2025-07-09 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 19:38 Daniel Gomez
2025-07-08 20:21 ` Linus Torvalds
2025-07-08 20:30   ` pr-tracker-bot
2025-07-09 19:14   ` Daniel Gomez [this message]
2025-07-08 20:40 ` pr-tracker-bot

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=64c1b31c-a65f-4eaf-b343-0b5b9b2c1086@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=da.gomez@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.com \
    --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®