From: Andrew Morton <akpm@linux-foundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] non-MM commits for 6.2-rc1
Date: Mon, 12 Dec 2022 14:27:54 -0800 [thread overview]
Message-ID: <20221212142754.5f699c4ff515fd9d42768fb2@linux-foundation.org> (raw)
In-Reply-To: <Y5eoS/UfBhovR70j@zx2c4.com>
On Mon, 12 Dec 2022 15:16:43 -0700 "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> On Mon, Dec 12, 2022 at 01:44:25PM -0800, Andrew Morton wrote:
> > wifi: rt2x00: use explicitly signed or unsigned types
>
> Why is this part of your PULL? This was a netdev/wireless tree fix which
> was in 6.1-rc5. Kalle wrote that he took it on 21 Oct 2022 in:
> https://lore.kernel.org/all/166633563389.6242.13987912613257140089.kvalo@kernel.org/
>
Huh. I guess git quietly accepts the identical commit, so Stephen
never told me and my test-merge-with-Linus-latest also came up clean.
Which leaves it to me to manually handle these things, and that's
unreliable.
Is there some way of telling git to complain about identical changes
when doing a trial merge?
next prev parent reply other threads:[~2022-12-12 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 21:44 Andrew Morton
2022-12-12 22:16 ` Jason A. Donenfeld
2022-12-12 22:27 ` Andrew Morton [this message]
2022-12-12 23:16 ` Vlastimil Babka
2022-12-13 2:35 ` Andrew Morton
2022-12-13 2:44 ` Linus Torvalds
2022-12-13 2:58 ` Stephen Rothwell
2022-12-12 23:33 ` Linus Torvalds
2022-12-13 1:32 ` Linus Torvalds
2022-12-13 1:39 ` 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=20221212142754.5f699c4ff515fd9d42768fb2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@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