From: Dennis Zhou <dennis@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, Christoph Lameter <cl@linux.com>,
Vlastimil Babka <vbabka@suse.cz>, Baoquan He <bhe@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] percpu changes for v6.2-rc1
Date: Tue, 13 Dec 2022 07:41:07 -0800 [thread overview]
Message-ID: <Y5idE7pw3ZNtXhVT@fedora> (raw)
In-Reply-To: <CAHk-=wifBA8qdHp8kySVq6=iyaYmKXfSON7=5s9aWyfpL=Yy1w@mail.gmail.com>
On Mon, Dec 12, 2022 at 04:11:28PM -0800, Linus Torvalds wrote:
> On Mon, Dec 12, 2022 at 9:13 AM Dennis Zhou <dennis@kernel.org> wrote:
> >
> > Baoquan was nice enough to run some clean ups for percpu. There will be
> > a minor merge conflict with Vlastimil's slab PR [1]. This is due to
> > adjusting the PERCPU_DYNAMIC_EARLY_SIZE up for proper early percpu
> > reservation size on arm64 with 64k pages.
>
> Well, the merge was trivial, but...
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu.git for-6.2
>
> Argh, this is a plain branch. I was really hoping that we had all
> moved on to using signed tags for pulls.
>
> I've pulled this, because I still don't absolutely _require_ signed
> tags for kernel.org accounts, but can you please try to start using
> them in the future?
>
> The plain unsigned branches (and unsigned tags) are getting rare
> enough that I'm slowly starting to consider making them a hard
> requirement. Not this release, probably not the next one, but...
>
Got it. I'll send you signed tags from now on. Thanks for pulling this.
Thanks,
Dennis
> Linus
next prev parent reply other threads:[~2022-12-13 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 17:13 Dennis Zhou
2022-12-13 0:11 ` Linus Torvalds
2022-12-13 15:41 ` Dennis Zhou [this message]
2022-12-13 0:36 ` 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=Y5idE7pw3ZNtXhVT@fedora \
--to=dennis@kernel.org \
--cc=bhe@redhat.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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