linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Ingo Molnar <mingo@kernel.org>,
	Juri Lelli <juri.lelli@redhat.com>
Subject: Re: linux-next: Tree for Oct 22 (sched...)
Date: Fri, 22 Oct 2021 13:25:41 -0700	[thread overview]
Message-ID: <fcb0c32f-efcf-961c-2226-85a5121c7c09@infradead.org> (raw)
In-Reply-To: <20211022201533.6085b17f@canb.auug.org.au>

On 10/22/21 2:15 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20211021:
> 

on i386 or x86_64:

Lots of errors referring to sched->plug when CONFIG_BLOCK
is not set.

E.g.:
../kernel/sched/core.c: In function ‘io_schedule_prepare’:
../kernel/sched/core.c:8331:13: error: ‘struct task_struct’ has no member named ‘plug’
   if (current->plug)
              ^~
../kernel/sched/core.c:8332:25: error: ‘struct task_struct’ has no member named ‘plug’
    blk_flush_plug(current->plug, true);
                          ^~
../fs/fs-writeback.c: In function ‘writeback_sb_inodes’:
../fs/fs-writeback.c:1896:15: error: ‘struct task_struct’ has no member named ‘plug’
     if (current->plug)
                ^~
../fs/fs-writeback.c:1897:27: error: ‘struct task_struct’ has no member named ‘plug’
      blk_flush_plug(current->plug, false);
                            ^~
   CC      arch/x86/kernel/cpu/capflags.o
../fs/fs-writeback.c: In function ‘wakeup_flusher_threads’:
../fs/fs-writeback.c:2295:25: error: ‘struct task_struct’ has no member named ‘plug’
    blk_flush_plug(current->plug, true);
                          ^~


-- 
~Randy

  reply	other threads:[~2021-10-22 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  9:15 linux-next: Tree for Oct 22 Stephen Rothwell
2021-10-22 20:25 ` Randy Dunlap [this message]
2021-10-22 20:32 ` linux-next: Tree for Oct 22 (drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c) Randy Dunlap
2021-10-22 23:16 ` linux-next: Tree for Oct 22 (drivers/net/wireless/mediatek/mt76/mt7615/sdio_mcu.o) Randy Dunlap

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=fcb0c32f-efcf-961c-2226-85a5121c7c09@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vincent.guittot@linaro.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).