From: peterz@infradead.org
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Petr Mladek <pmladek@suse.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Waiman Long <longman@redhat.com>
Subject: Re: [PATCH 0/2] locking/qspinlock: Break qspinlock_types.h header loop
Date: Wed, 29 Jul 2020 16:28:13 +0200 [thread overview]
Message-ID: <20200729142813.GD2638@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200729132849.GA1160@jagdpanzerIV.localdomain>
On Wed, Jul 29, 2020 at 10:28:49PM +0900, Sergey Senozhatsky wrote:
> On (20/07/29 15:00), peterz@infradead.org wrote:
> > On Wed, Jul 29, 2020 at 10:51:44PM +1000, Herbert Xu wrote:
> > > On Wed, Jul 29, 2020 at 02:47:44PM +0200, peterz@infradead.org wrote:
> > > >
> [..]
> > > > Anyway, the patches look sane enough, I'll go stick them in
> > > > tip/locking/core or somesuch.
> > >
> > > Perhaps add them on top of the other two patches in locking/header?
> >
> > Can do,
>
> locking/header would be better
Done.
next prev parent reply other threads:[~2020-07-29 14:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 11:03 linux-next: build failure after merge of the printk tree Stephen Rothwell
2020-07-29 11:47 ` Herbert Xu
2020-07-29 12:28 ` [PATCH 0/2] locking/qspinlock: Break qspinlock_types.h header loop Herbert Xu
2020-07-29 12:31 ` [PATCH 1/2] locking/atomic: Move ATOMIC_INIT into linux/types.h Herbert Xu
2020-07-29 14:33 ` [tip: locking/core] " tip-bot2 for Herbert Xu
2020-07-29 12:33 ` [PATCH 2/2] locking/qspinlock: Do not include atomic.h from qspinlock_types.h Herbert Xu
2020-07-29 14:33 ` [tip: locking/core] " tip-bot2 for Herbert Xu
2020-07-29 12:47 ` [PATCH 0/2] locking/qspinlock: Break qspinlock_types.h header loop peterz
2020-07-29 12:51 ` Herbert Xu
2020-07-29 13:00 ` peterz
2020-07-29 13:28 ` Sergey Senozhatsky
2020-07-29 14:28 ` peterz [this message]
2020-07-29 16:41 ` Sergey Senozhatsky
2020-07-29 13:35 ` Waiman Long
2020-07-29 15:04 ` Andy Shevchenko
2020-07-30 0:59 ` Herbert Xu
2020-07-30 7:47 ` Andy Shevchenko
2020-07-30 7:50 ` Herbert Xu
2020-07-30 7:55 ` Andy Shevchenko
2020-08-06 3:37 ` Vineet Gupta
2020-07-29 17:50 ` Sergey Senozhatsky
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=20200729142813.GD2638@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andy.shevchenko@gmail.com \
--cc=bp@alien8.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=x86@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