From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <fengguang.wu@intel.com>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, tglx@linutronix.de,
Ingo Molnar <mingo@elte.hu>,
lkp@01.org
Subject: Re: [kernel/sofirq] ffce8e6f93: BUG:using_smp_processor_id()in_preemptible
Date: Wed, 21 Feb 2018 11:50:08 +0100 [thread overview]
Message-ID: <20180221105008.o4ooqw6hoe5hh4m7@linutronix.de> (raw)
In-Reply-To: <20180220174801.n6qexw4adb5hcd4m@inn>
On 2018-02-21 01:48:01 [+0800], kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: ffce8e6f936e3d879910a76cf8ce6293d78a51e6 ("kernel/sofirq: consolidate common code in __tasklet_schedule() + _hi_")
> url: https://github.com/0day-ci/linux/commits/Sebastian-Andrzej-Siewior/kernel-sofirq-consolidate-common-code-in-__tasklet_schedule-_hi_/20180218-010957
yes, and this patch was superseded by
https://lkml.kernel.org/r/20180216170836.ex2uxcgkk7gniwqi@linutronix.de
Sebastian
next prev parent reply other threads:[~2018-02-21 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 17:20 Consolidate tasklet + tasklet-hi code Sebastian Andrzej Siewior
2018-02-15 17:20 ` [PATCH 1/2] kernel/sofirq: consolidate common code in __tasklet_schedule() + _hi_ Sebastian Andrzej Siewior
2018-02-15 20:07 ` Steven Rostedt
2018-02-15 22:31 ` Julia Cartwright
2018-02-16 8:53 ` Sebastian Andrzej Siewior
2018-02-16 17:31 ` Steven Rostedt
2018-02-16 17:55 ` Sebastian Andrzej Siewior
2018-02-16 18:02 ` Steven Rostedt
2018-02-16 17:08 ` [PATCH 1/2 v2] " Sebastian Andrzej Siewior
2018-02-20 17:48 ` [kernel/sofirq] ffce8e6f93: BUG:using_smp_processor_id()in_preemptible kernel test robot
2018-02-21 10:50 ` Sebastian Andrzej Siewior [this message]
2018-02-15 17:20 ` [PATCH 2/2] kernel/sofirq: consolidate common code in tasklet_action() + tasklet_hi_action() Sebastian Andrzej Siewior
2018-02-15 20:08 ` Steven Rostedt
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=20180221105008.o4ooqw6hoe5hh4m7@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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 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®