From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: josh@joshtriplett.org, rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: don't include <linux/ktime.h> in rcutiny.h
Date: Thu, 22 Aug 2019 07:00:42 -0700 [thread overview]
Message-ID: <20190822140042.GZ28441@linux.ibm.com> (raw)
In-Reply-To: <20190822034841.GA13668@lst.de>
On Thu, Aug 22, 2019 at 05:48:41AM +0200, Christoph Hellwig wrote:
> On Wed, Aug 21, 2019 at 08:02:00PM -0700, Paul E. McKenney wrote:
> > On Thu, Aug 22, 2019 at 10:53:43AM +0900, Christoph Hellwig wrote:
> > > The kbuild reported a built failure due to a header loop when RCUTINY is
> > > enabled with my pending riscv-nommu port. Switch rcutiny.h to only
> > > include the minimal required header to get HZ instead.
> > >
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> >
> > Queued for review and testing, thank you!
> >
> > Do you need this in v5.4? My normal workflow would put it into v5.5.
>
> I hope the riscv-nommu coe gets merges for 5.4, so if we could queue
> it up for that I'd appreciate it.
OK, it did pass rcutorture's various !SMP scenarios, so this seems
plausible.
I am sending my main pull request today, but will also put this patch
where 0day and -next can see it. If it does OK with that and with
additional review/testing for a few days, I will send a second pull
request with that patch some time next week.
Thanx, Paul
prev parent reply other threads:[~2019-08-22 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 1:53 [PATCH] rcu: don't include <linux/ktime.h> in rcutiny.h Christoph Hellwig
2019-08-22 3:02 ` Paul E. McKenney
2019-08-22 3:48 ` Christoph Hellwig
2019-08-22 14:00 ` Paul E. McKenney [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=20190822140042.GZ28441@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=hch@lst.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rcu@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.