From: Steven Rostedt <rostedt@goodmis.org>
To: John Kacur <jkacur@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/3] sysctl-include-fix.patch
Date: Mon, 21 Nov 2011 11:06:22 -0500 [thread overview]
Message-ID: <1321891582.20742.9.camel@frodo> (raw)
In-Reply-To: <1321707028-12487-3-git-send-email-jkacur@redhat.com>
On Sat, 2011-11-19 at 13:50 +0100, John Kacur wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cherry-picked for v3.0-rt and fixed minor merge conflict
> Signed-off-by: John Kacur <jkacur@redhat.com>
> ---
> include/linux/sysctl.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Why is this needed? Did something break without it?
And if so, what?
-- Steve
>
> diff --git a/include/linux/sysctl.h b/include/linux/sysctl.h
> index 11684d9..92b99dd 100644
> --- a/include/linux/sysctl.h
> +++ b/include/linux/sysctl.h
> @@ -931,6 +931,7 @@ enum
> #ifdef __KERNEL__
> #include <linux/list.h>
> #include <linux/rcupdate.h>
> +#include <linux/atomic.h>
>
> /* For the /proc/sys support */
> struct ctl_table;
next prev parent reply other threads:[~2011-11-21 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 12:50 [PATCH 0/3] Suggested patches for v3.0.9-rt26 John Kacur
2011-11-19 12:50 ` [PATCH 1/3] rcu-more-fallout.patch John Kacur
2011-11-21 16:04 ` Steven Rostedt
2011-11-19 12:50 ` [PATCH 2/3] sysctl-include-fix.patch John Kacur
2011-11-21 16:06 ` Steven Rostedt [this message]
2011-11-19 12:50 ` [PATCH 3/3] rcu: Drive configuration directly from SMP and PREEMPT John Kacur
2011-11-21 16:10 ` Steven Rostedt
2011-11-21 23:18 ` John Kacur
2011-11-21 23:18 ` John Kacur
2011-11-21 23:46 ` Steven Rostedt
2011-11-21 23:51 ` John Kacur
2011-11-21 23:51 ` John Kacur
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=1321891582.20742.9.camel@frodo \
--to=rostedt@goodmis.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.