From: Peter Zijlstra <peterz@infradead.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: mingo@redhat.com, will@kernel.org, longman@redhat.com,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
paulmck@kernel.org, frederic@kernel.org, josh@joshtriplett.org,
neeraj.iitr10@gmail.com, urezki@gmail.com, rcu@vger.kernel.org
Subject: Re: [GIT PULL] LOCKDEP changes for v6.12
Date: Thu, 8 Aug 2024 12:19:39 +0200 [thread overview]
Message-ID: <20240808101939.GG31338@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <ZrQ97Zz27Tzmr0Zi@tardis>
On Wed, Aug 07, 2024 at 08:39:25PM -0700, Boqun Feng wrote:
> Hi Peter & Ingo,
>
> Per discussion:
>
> https://lore.kernel.org/lkml/20240802151619.GN39708@noisy.programming.kicks-ass.net/
>
> I'm sending a PR with some lockdep changes to tip.
>
>
> The following changes since commit d5934e76316e84eced836b6b2bafae1837d1cd58:
>
> cleanup: Add usage and style documentation (2024-08-05 16:54:41 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux tags/lockdep-for-tip.20240806
>
Right, so a few things for next time, could you read
Documentation/process/maintainer-tip.rst and make sure patches more or
less adhere to the things outlined there.
Things I noticed in the few seconds I looked at things:
Subjects don't start with a capital letter after the ':'
The Changelog for the lockdep-vs-rcu thing can be much condensed by not
including full stack dumps but only the relevant information.
If you don't want to edit patches by hand, you're free to push back and
get the submitter to do things before applying them.
Anyway, since I'm about to head out to the beach, I'm pulling this. Also
I need to figure out how git works with remotes and tags... stupid
things :-)
next prev parent reply other threads:[~2024-08-08 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 3:39 Boqun Feng
2024-08-08 10:19 ` Peter Zijlstra [this message]
2024-08-08 16:11 ` Boqun Feng
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=20240808101939.GG31338@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=neeraj.iitr10@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=will@kernel.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®