From: Thomas Gleixner <tglx@linutronix.de>
To: "André Almeida" <andrealmeid@collabora.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org
Cc: mingo@redhat.com, dvhart@infradead.org, kernel@collabora.com,
krisman@collabora.com
Subject: Re: [RESEND PATCH 3/4] futex: Remove unused or redundant includes
Date: Sat, 18 Jul 2020 02:02:34 +0200 [thread overview]
Message-ID: <87pn8tpu5h.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <7b7270f6-636a-0b72-8fae-a181d1dfc3e2@collabora.com>
André Almeida <andrealmeid@collabora.com> writes:
> I just retested compiling tip/locking/core, and it seems something
> changed the last time I wrote the patch. Removing <linux/compat.h> will
> indeed break the compilation now, the patch bellow should fix it. Sorry
> for the noise.
I just folded it back manually and force pushed the result. Manually
because the below:
> =======================================
>
> diff --git a/kernel/futex.c b/kernel/futex.c
> index f483bc52dbac..4616d4ad609d 100644
>
> --- a/kernel/futex.c
>
> +++ b/kernel/futex.c
>
> @@ -31,6 +31,7 @@
>
> 31 * "The futexes are also cursed."
> 32 * "But they come in a choice of three flavours!"
> 33 */
> +34#include <linux/compat.h>
> 35#include <linux/jhash.h>
> 36#include <linux/pagemap.h>
> 37#include <linux/syscalls.h>
does not really qualify as a valid patch.
next prev parent reply other threads:[~2020-07-18 0:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 20:28 [RESEND PATCH 0/4] futex: Minor code improvements André Almeida
2020-07-02 20:28 ` [RESEND PATCH 1/4] futex: Remove put_futex_key() André Almeida
2020-07-17 22:01 ` [tip: locking/core] " tip-bot2 for André Almeida
2020-07-02 20:28 ` [RESEND PATCH 2/4] futex: Remove needless goto's André Almeida
2020-07-17 22:01 ` [tip: locking/core] " tip-bot2 for André Almeida
2020-07-02 20:28 ` [RESEND PATCH 3/4] futex: Remove unused or redundant includes André Almeida
2020-07-17 21:46 ` Thomas Gleixner
2020-07-17 22:39 ` André Almeida
2020-07-18 0:02 ` Thomas Gleixner [this message]
2020-07-17 22:01 ` [tip: locking/core] " tip-bot2 for André Almeida
2020-07-18 0:01 ` tip-bot2 for André Almeida
2020-07-02 20:28 ` [RESEND PATCH 4/4] futex: Consistently use fshared as boolean André Almeida
2020-07-17 22:01 ` [tip: locking/core] " tip-bot2 for André Almeida
2020-07-18 0:01 ` tip-bot2 for André Almeida
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=87pn8tpu5h.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=andrealmeid@collabora.com \
--cc=dvhart@infradead.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®