From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jeremy Linton <jeremy.linton@arm.com>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
dave@stgolabs.net, josh@joshtriplett.org
Subject: Re: [PATCH] locktorture: Fix Oops when reader/writer count is 0
Date: Wed, 8 Nov 2017 06:17:36 -0800 [thread overview]
Message-ID: <20171108141736.GD3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171108082750.GW3165@worktop.lehotels.local>
On Wed, Nov 08, 2017 at 09:27:50AM +0100, Peter Zijlstra wrote:
> On Tue, Nov 07, 2017 at 02:15:55PM -0800, Paul E. McKenney wrote:
> > But Jeremy's list of email addresses is what you would expect from
> > looking at MAINTAINERS, so how about the following patch?
>
> True; I tend to also look at git history (as goes get_maintainers.pl
> IIRC).
Me too, and that certainly is best practice.
> > commit 58322063498c8f5a3cc88f95bee237a0ce81f70a
> > Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > Date: Tue Nov 7 14:10:03 2017 -0800
> >
> > torture: Place all torture-test modules in one MAINTAINERS group
> >
> > There is some confusion about where patches to kernel/torture.c
> > and kernel/locking/locktorture.c should be sent. This commit
> > therefore updates MAINTAINERS appropriately.
> >
> > Reported-by: Peter Zijlstra <peterz@infradead.org>
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> Seems fair;
>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Applied, thank you!
Thanx, Paul
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 2d3d750b19c0..eab868adedc6 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -8091,6 +8091,7 @@ F: arch/*/include/asm/rwsem.h
> > F: include/linux/seqlock.h
> > F: lib/locking*.[ch]
> > F: kernel/locking/
> > +X: kernel/locking/locktorture.c
> >
> > LOGICAL DISK MANAGER SUPPORT (LDM, Windows 2000/XP/Vista Dynamic Disks)
> > M: "Richard Russon (FlatCap)" <ldm@flatcap.org>
> > @@ -11318,15 +11319,6 @@ L: linux-wireless@vger.kernel.org
> > S: Orphan
> > F: drivers/net/wireless/ray*
> >
> > -RCUTORTURE MODULE
> > -M: Josh Triplett <josh@joshtriplett.org>
> > -M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > -L: linux-kernel@vger.kernel.org
> > -S: Supported
> > -T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> > -F: Documentation/RCU/torture.txt
> > -F: kernel/rcu/rcutorture.c
> > -
> > RCUTORTURE TEST FRAMEWORK
> > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > M: Josh Triplett <josh@joshtriplett.org>
> > @@ -13558,6 +13550,18 @@ L: platform-driver-x86@vger.kernel.org
> > S: Maintained
> > F: drivers/platform/x86/topstar-laptop.c
> >
> > +TORTURE-TEST MODULES
> > +M: Davidlohr Bueso <dave@stgolabs.net>
> > +M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > +M: Josh Triplett <josh@joshtriplett.org>
> > +L: linux-kernel@vger.kernel.org
> > +S: Supported
> > +T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> > +F: Documentation/RCU/torture.txt
> > +F: kernel/torture.c
> > +F: kernel/rcu/rcutorture.c
> > +F: kernel/locking/locktorture.c
> > +
> > TOSHIBA ACPI EXTRAS DRIVER
> > M: Azael Avalos <coproscefalo@gmail.com>
> > L: platform-driver-x86@vger.kernel.org
> >
>
next prev parent reply other threads:[~2017-11-08 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 15:52 [PATCH] locktorture: Fix Oops when reader/writer count is 0 Jeremy Linton
2017-11-07 20:01 ` Jeremy Linton
2017-11-07 21:07 ` Peter Zijlstra
2017-11-07 22:15 ` Paul E. McKenney
2017-11-08 8:27 ` Peter Zijlstra
2017-11-08 14:17 ` Paul E. McKenney [this message]
2017-11-08 14:45 ` Davidlohr Bueso
2017-11-08 16:48 ` Paul E. McKenney
2017-11-08 16:57 ` Jeremy Linton
2017-11-08 17:44 ` Paul E. McKenney
2017-11-09 16:15 ` Jeremy Linton
2017-11-09 16:19 ` Davidlohr Bueso
2017-11-09 16:45 ` Paul E. McKenney
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=20171108141736.GD3624@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dave@stgolabs.net \
--cc=jeremy.linton@arm.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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