From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: joel@joelfernandes.org, mathieu.desnoyers@efficios.com,
peterz@infradead.org, tj@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] Make call_srcu() available during very early boot
Date: Tue, 14 Aug 2018 11:41:29 -0700 [thread overview]
Message-ID: <20180814184129.GK24813@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180814143451.0ee99bf8@gandalf.local.home>
On Tue, Aug 14, 2018 at 02:34:51PM -0400, Steven Rostedt wrote:
> On Tue, 14 Aug 2018 10:44:43 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>
> > > > If I recall correctly, this subterfuge suppresses compiler complaints
> > > > about initializing an unsigned long with a negative number. :-/
> > >
> > > Did you try:
> > >
> > > .srcu_gp_seq_needed = -1UL,
> > >
> > > ?
> >
> > Works for my compiler, not sure what set of complaints pushed me in that
> > direction.
>
> I've used -1UL for unsigned long initializations for pretty much my
> entire programming career. I've never had any issues with it.
Fair enough. I have to fix a "void void" that my compilers were happy
with, so might as well do this one also. "I am telling you, don't even
-think- about expecting a return value from -this- function!!!" ;-)
Thanx, Paul
next prev parent reply other threads:[~2018-08-14 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 16:24 [PATCH RFC] Make call_srcu() available during very early boot Paul E. McKenney
2018-08-14 16:49 ` Steven Rostedt
2018-08-14 17:06 ` Paul E. McKenney
2018-08-14 17:24 ` Steven Rostedt
2018-08-14 17:44 ` Paul E. McKenney
2018-08-14 18:34 ` Steven Rostedt
2018-08-14 18:41 ` Paul E. McKenney [this message]
2018-08-14 21:02 ` Paul E. McKenney
2018-08-17 16:08 ` Tejun Heo
2018-08-17 16:31 ` 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=20180814184129.GK24813@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).