mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Jiri Kosina <jkosina@suse.com>, Jan Kara <jack@suse.com>,
	Tejun Heo <tj@kernel.org>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	Byungchul Park <byungchul.park@lge.com>,
	linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH POC 1/4] printk: Prepeparation for fake cont buffers
Date: Sat, 16 Jul 2016 02:26:53 +0800	[thread overview]
Message-ID: <201607160256.HaERvTJR%fengguang.wu@intel.com> (raw)
In-Reply-To: <1468601942-18482-2-git-send-email-pmladek@suse.com>

[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]

Hi,

[auto build test ERROR on v4.7-rc7]
[cannot apply to next-20160715]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Petr-Mladek/printk-Several-fixes-of-cont-buffer-and-console-handling/20160716-012724
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   kernel/printk/printk.c: In function 'console_cont_flush':
>> kernel/printk/printk.c:2177:11: error: 'struct cont' has no member named 'msg'
     if (!cont.msg->text_len)
              ^
>> kernel/printk/printk.c:2185:37: error: 'cont_console_len' undeclared (first use in this function)
     if (console_seq < log_next_seq && !cont_console_len)
                                        ^~~~~~~~~~~~~~~~
   kernel/printk/printk.c:2185:37: note: each undeclared identifier is reported only once for each function it appears in
   kernel/printk/printk.c:2191:27: error: 'struct cont' has no member named 'msg'
     call_console_drivers(cont.msg->level, NULL, 0, text, len);
                              ^

vim +2177 kernel/printk/printk.c

  2171	{
  2172		unsigned long flags;
  2173		size_t len;
  2174	
  2175		raw_spin_lock_irqsave(&logbuf_lock, flags);
  2176	
> 2177		if (!cont.msg->text_len)
  2178			goto out;
  2179	
  2180		/*
  2181		 * We still queue earlier records, likely because the console was
  2182		 * busy. The earlier ones need to be printed before this one, we
  2183		 * did not flush any fragment so far, so just let it queue up.
  2184		 */
> 2185		if (console_seq < log_next_seq && !cont_console_len)
  2186			goto out;
  2187	
  2188		len = cont_print_text(text, size);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6334 bytes --]

  reply	other threads:[~2016-07-15 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 16:58 [PATCH POC 0/4] printk: Several fixes of cont buffer and console handling Petr Mladek
2016-07-15 16:58 ` [PATCH POC 1/4] printk: Prepeparation for fake cont buffers Petr Mladek
2016-07-15 18:26   ` kbuild test robot [this message]
2016-07-15 16:59 ` [PATCH POC 2/4] printk: Do not block cont buffer by partially flushed lines Petr Mladek
2016-07-15 18:31   ` kbuild test robot
2016-07-15 22:08   ` kbuild test robot
2016-07-15 16:59 ` [PATCH POC 3/4] printk: Flush the cont buffer after the other lines Petr Mladek
2016-07-15 16:59 ` [PATCH POC 4/4] printk: Correctly replay buffer log for a new console Petr Mladek
2016-07-15 18:27   ` kbuild test robot

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=201607160256.HaERvTJR%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=byungchul.park@lge.com \
    --cc=jack@suse.com \
    --cc=jkosina@suse.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=tj@kernel.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®