mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andreas Werner <andreas.werner@men.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH 1/2] libata-eh.c: Introduce new ata port flag for controller which lockup on read log page
Date: Sat, 5 Dec 2015 00:19:38 +0800	[thread overview]
Message-ID: <201512050022.mZp5ScP0%fengguang.wu@intel.com> (raw)
In-Reply-To: <1d3460f05e6acf5c296f1b7dec0f9fdaca55c0fc.1449243748.git.andreas.werner@men.de>

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

Hi Andreas,

[auto build test ERROR on tj-libata/for-next]
[also build test ERROR on v4.4-rc3 next-20151203]

url:    https://github.com/0day-ci/linux/commits/Andreas-Werner/libata-introduce-ATA_FLAG_NO_LOG_PAGE/20151204-235659
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata for-next
config: i386-randconfig-x008-12041200 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All error/warnings (new ones prefixed by >>):

   drivers/ata/libata-eh.c: In function 'ata_read_log_page':
>> drivers/ata/libata-eh.c:1520:6: error: 'flags' undeclared (first use in this function)
     if (flags & ATA_FLAG_NO_LOG_PAGE)
         ^
   drivers/ata/libata-eh.c:1520:6: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/ata/libata-eh.c:1508:16: warning: unused variable 'ap_flags' [-Wunused-variable]
     unsigned long ap_flags = dev->link->ap->flags;
                   ^

vim +/flags +1520 drivers/ata/libata-eh.c

  1502	 *	RETURNS:
  1503	 *	0 on success, AC_ERR_* mask otherwise.
  1504	 */
  1505	unsigned int ata_read_log_page(struct ata_device *dev, u8 log,
  1506				       u8 page, void *buf, unsigned int sectors)
  1507	{
> 1508		unsigned long ap_flags = dev->link->ap->flags;
  1509		struct ata_taskfile tf;
  1510		unsigned int err_mask;
  1511		bool dma = false;
  1512	
  1513		DPRINTK("read log page - log 0x%x, page 0x%x\n", log, page);
  1514	
  1515		/*
  1516		 * Return error without actually issuing the
  1517		 * command on controller which e.g. lockup
  1518		 * on a read log page.
  1519		 */
> 1520		if (flags & ATA_FLAG_NO_LOG_PAGE)
  1521			return AC_ERR_DEV;
  1522	
  1523	retry:

---
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: 29818 bytes --]

  parent reply	other threads:[~2015-12-04 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 15:52 [PATCH 0/2] libata: introduce ATA_FLAG_NO_LOG_PAGE Andreas Werner
2015-12-04 15:53 ` [PATCH 1/2] libata-eh.c: Introduce new ata port flag for controller which lockup on read log page Andreas Werner
2015-12-04 16:13   ` kbuild test robot
2015-12-04 16:19   ` kbuild test robot [this message]
2015-12-04 15:53 ` [PATCH 2/2] ata/sata_fsl.c: add ATA_FLAG_NO_LOG_PAGE to blacklist the controller for log page reads Andreas Werner

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=201512050022.mZp5ScP0%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=andreas.werner@men.de \
    --cc=kbuild-all@01.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®