From: Petr Mladek <pmladek@suse.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, linux-pci@vger.kernel.org,
linux-mm@kvack.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] sched/autogroup: move sched.h include
Date: Fri, 8 Dec 2017 09:57:55 +0100 [thread overview]
Message-ID: <20171208085755.GA3148@linux.suse> (raw)
In-Reply-To: <20171208082422.5021-1-sergey.senozhatsky@gmail.com>
On Fri 2017-12-08 17:24:22, Sergey Senozhatsky wrote:
> Move local "sched.h" include to the bottom. sched.h defines
> several macros that are getting redefined in ARCH-specific
> code, for instance, finish_arch_post_lock_switch() and
> prepare_arch_switch(), so we need ARCH-specific definitions
> to come in first.
This patch is needed to fix compilation error [1] caused by a patchset
that deprecates %pf/%pF printk modifiers[2].
IMHO, we should make sure that this fix goes into Linus' tree
before the printk-related patchset. What is the best practice,
please?
I see two reasonable possibilities. Either sched people could
push this for-4.15-rcX. Or I could put it into printk.git for-4.16
in the right order.
What do you think?
Referece:
[0] http://lkml.kernel.org/r/201712080259.tvO64XfA%fengguang.wu@intel.com
[1] https://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk.git/commit/?h=for-next&id=98fff2c57b7e88d643cb42ffd910fe9905b33176
Best Regards,
Petr
next prev parent reply other threads:[~2017-12-08 8:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 2:56 [PATCH 0/9] remove some of unneeded kallsyms includes Sergey Senozhatsky
2017-12-08 2:56 ` [PATCH 1/9] sched/autogroup: remove unneeded kallsyms include Sergey Senozhatsky
2017-12-08 8:24 ` [PATCH] sched/autogroup: move sched.h include Sergey Senozhatsky
2017-12-08 8:57 ` Petr Mladek [this message]
2017-12-08 10:39 ` Sergey Senozhatsky
2017-12-08 10:56 ` Peter Zijlstra
2017-12-08 10:56 ` [PATCH 1/9] sched/autogroup: remove unneeded kallsyms include Peter Zijlstra
2017-12-08 11:20 ` Sergey Senozhatsky
2017-12-08 13:43 ` Petr Mladek
2017-12-08 2:56 ` [PATCH 2/9] mm: " Sergey Senozhatsky
2017-12-08 2:56 ` [PATCH 3/9] power: " Sergey Senozhatsky
2017-12-08 14:01 ` Rafael J. Wysocki
2017-12-08 14:48 ` Sergey Senozhatsky
2017-12-17 18:04 ` Rafael J. Wysocki
2017-12-18 14:37 ` Sergey Senozhatsky
2017-12-08 2:56 ` [PATCH 4/9] pci: " Sergey Senozhatsky
2017-12-08 17:53 ` Bjorn Helgaas
2017-12-08 23:55 ` Sergey Senozhatsky
2017-12-08 2:56 ` [PATCH 5/9] pnp: " Sergey Senozhatsky
2017-12-08 14:02 ` Rafael J. Wysocki
2017-12-08 14:49 ` Sergey Senozhatsky
2017-12-17 18:04 ` Rafael J. Wysocki
2017-12-08 2:56 ` [PATCH 6/9] mm: " Sergey Senozhatsky
2017-12-08 2:56 ` [PATCH 7/9] workqueue: " Sergey Senozhatsky
2017-12-11 15:16 ` Tejun Heo
2017-12-12 2:51 ` Sergey Senozhatsky
2017-12-08 2:56 ` [PATCH 8/9] hrtimer: " Sergey Senozhatsky
2017-12-08 2:56 ` [PATCH 9/9] genirq: " Sergey Senozhatsky
2017-12-08 22:24 ` [PATCH 0/9] remove some of unneeded kallsyms includes Andrew Morton
2017-12-09 0:00 ` Sergey Senozhatsky
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=20171208085755.GA3148@linux.suse \
--to=pmladek@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
/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).