From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: pr-tracker-bot@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [GIT PULL] MM updates for 7.2-rc1
Date: Thu, 18 Jun 2026 16:37:52 -0400 [thread overview]
Message-ID: <20260618-generous-sceptical-jackdaw-3d32db@meerkat> (raw)
In-Reply-To: <CAHk-=whn39dQtoMeJrz++nAnZpgnrooU0dgzOZXdn1LyxQ+f2w@mail.gmail.com>
On Thu, Jun 18, 2026 at 09:02:06AM -0700, Linus Torvalds wrote:
> This is very wrong. That merge (2f9f5887b427) is merging Jens'
> io_uring epoll cleanup. Not Andrew's MM tree, which I haven't gotten
> to yet.
>
> I wonder why pr-tracker-bot got this wrong.
>
> [ Goes off and looks ]
>
> Oh. Andrew's pull request is confused. It says
>
> The following changes since commit e771677...
> ...
> for you to fetch changes up to e771677....
>
> and note how the "since" commit and "up to" commits are the same (and
> is my iommufd merge). So then pr-tracker bot thinks it's merged when
> the "since" commit was merged.
Let me at least handle this situation -- it's clearly an oversight.
> That doesn't explain why pr-tracker-bot thinks it got merged in what
> was me merging Jens' tree, but whatever.
I'll look into this as well.
-K
next prev parent reply other threads:[~2026-06-18 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 22:31 Andrew Morton
2026-06-18 15:22 ` pr-tracker-bot
2026-06-18 16:02 ` Linus Torvalds
2026-06-18 16:29 ` Andrew Morton
2026-06-18 20:37 ` Konstantin Ryabitsev [this message]
2026-06-18 20:58 ` Konstantin Ryabitsev
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=20260618-generous-sceptical-jackdaw-3d32db@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=pr-tracker-bot@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®