From: Ingo Molnar <mingo@kernel.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] refcount: trim headers
Date: Sat, 31 Mar 2018 20:46:17 +0200 [thread overview]
Message-ID: <20180331184617.b7lmphk2jsipghii@gmail.com> (raw)
In-Reply-To: <20180331133918.GA9535@avx2>
* Alexey Dobriyan <adobriyan@gmail.com> wrote:
> On Sat, Mar 31, 2018 at 10:36:32AM +0200, Ingo Molnar wrote:
> > > --- a/include/linux/refcount.h
> > > +++ b/include/linux/refcount.h
> > > #include <linux/atomic.h>
> > > -#include <linux/mutex.h>
> > > -#include <linux/spinlock.h>
> > > -#include <linux/kernel.h>
> > > +#include <linux/compiler.h>
> > > +#include <linux/spinlock_types.h>
> > > +
> > > +struct mutex;
>
> > Doesn't build on x86-64 defconfig...
>
> Yeah, it doesn't :-(
> Is this going to go through -tip?
> Or I'll build test over both trees.
Yeah, refcount changes go through the locking tree, so testing it against -tip
would be useful.
Thanks,
Ingo
prev parent reply other threads:[~2018-03-31 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 19:34 [PATCH] refcount: trim headers Alexey Dobriyan
2018-03-31 8:36 ` Ingo Molnar
2018-03-31 13:39 ` Alexey Dobriyan
2018-03-31 18:46 ` Ingo Molnar [this message]
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=20180331184617.b7lmphk2jsipghii@gmail.com \
--to=mingo@kernel.org \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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