linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Russell King <rmk+kernel@arm.linux.org.uk>
Cc: kbuild-all@01.org, Ulf Hansson <ulf.hansson@linaro.org>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	linux-mmc@vger.kernel.org, Marcin Wojtas <mw@semihalf.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH v3 07/25] mmc: sdhci: command response CRC error handling
Date: Tue, 26 Jan 2016 22:10:50 +0800	[thread overview]
Message-ID: <201601262227.M2FVUU8y%fengguang.wu@intel.com> (raw)
In-Reply-To: <E1aO3qT-0005iB-CJ@rmk-PC.arm.linux.org.uk>

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

Hi Russell,

[auto build test WARNING on ulf.hansson-mmc/next]
[also build test WARNING on v4.5-rc1 next-20160125]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Russell-King/mmc-core-shut-up-voltage-ranges-unspecified-pr_info/20160126-214738
base:   https://git.linaro.org/people/ulf.hansson/mmc next
config: x86_64-randconfig-x018-01260845 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   In file included from include/linux/linkage.h:4:0,
                    from include/linux/kernel.h:6,
                    from include/linux/delay.h:10,
                    from drivers/mmc/host/sdhci.c:16:
   drivers/mmc/host/sdhci.c: In function 'sdhci_cmd_irq':
   drivers/mmc/host/sdhci.c:2344:15: warning: suggest parentheses around comparison in operand of '&' [-Wparentheses]
          intmask & (SDHCI_INT_CRC | SDHCI_INT_TIMEOUT) ==
                  ^
   include/linux/compiler.h:147:28: note: in definition of macro '__trace_if'
     if (__builtin_constant_p((cond)) ? !!(cond) :   \
                               ^
>> drivers/mmc/host/sdhci.c:2343:3: note: in expansion of macro 'if'
      if (host->cmd->data &&
      ^
   drivers/mmc/host/sdhci.c:2344:15: warning: suggest parentheses around comparison in operand of '&' [-Wparentheses]
          intmask & (SDHCI_INT_CRC | SDHCI_INT_TIMEOUT) ==
                  ^
   include/linux/compiler.h:147:40: note: in definition of macro '__trace_if'
     if (__builtin_constant_p((cond)) ? !!(cond) :   \
                                           ^
>> drivers/mmc/host/sdhci.c:2343:3: note: in expansion of macro 'if'
      if (host->cmd->data &&
      ^
   drivers/mmc/host/sdhci.c:2344:15: warning: suggest parentheses around comparison in operand of '&' [-Wparentheses]
          intmask & (SDHCI_INT_CRC | SDHCI_INT_TIMEOUT) ==
                  ^
   include/linux/compiler.h:158:16: note: in definition of macro '__trace_if'
      ______r = !!(cond);     \
                   ^
>> drivers/mmc/host/sdhci.c:2343:3: note: in expansion of macro 'if'
      if (host->cmd->data &&
      ^

vim +/if +2343 drivers/mmc/host/sdhci.c

  2327			       SDHCI_INT_END_BIT | SDHCI_INT_INDEX)) {
  2328			if (intmask & SDHCI_INT_TIMEOUT)
  2329				host->cmd->error = -ETIMEDOUT;
  2330			else
  2331				host->cmd->error = -EILSEQ;
  2332	
  2333			/*
  2334			 * If this command initiates a data phase and a response
  2335			 * CRC error is signalled, the card can start transferring
  2336			 * data - the card may have received the command without
  2337			 * error.  We must not terminate the mmc_request early.
  2338			 *
  2339			 * If the card did not receive the command or returned an
  2340			 * error which prevented it sending data, the data phase
  2341			 * will time out.
  2342			 */
> 2343			if (host->cmd->data &&
  2344			    intmask & (SDHCI_INT_CRC | SDHCI_INT_TIMEOUT) ==
  2345			     SDHCI_INT_CRC) {
  2346				host->cmd = NULL;
  2347				return;
  2348			}
  2349	
  2350			tasklet_schedule(&host->finish_tasklet);
  2351			return;

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

  reply	other threads:[~2016-01-26 14:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 13:38 [PATCH v3 00/25] MMC/SDHCI fixes Russell King - ARM Linux
2016-01-26 13:39 ` [PATCH v3 01/25] mmc: core: shut up "voltage-ranges unspecified" pr_info() Russell King
2016-01-26 13:39 ` [PATCH v3 02/25] mmc: core: improve mmc_of_parse_voltage() to return better status Russell King
2016-01-26 13:39 ` [PATCH v3 03/25] mmc: block: shut up "retrying because a re-tune was needed" message Russell King
2016-01-26 13:39 ` [PATCH v3 04/25] mmc: core: report tuning command execution failure reason Russell King
2016-01-26 13:39 ` [PATCH v3 05/25] mmc: sdhci: move initialisation of command error member Russell King
2016-01-26 13:39 ` [PATCH v3 06/25] mmc: sdhci: clean up command error handling Russell King
2016-01-26 13:39 ` [PATCH v3 07/25] mmc: sdhci: command response CRC " Russell King
2016-01-26 14:10   ` kbuild test robot [this message]
2016-01-26 14:11   ` kbuild test robot
2016-01-26 13:39 ` [PATCH v3 08/25] mmc: sdhci: avoid unnecessary mapping/unmapping of align buffer Russell King
2016-01-26 13:39 ` [PATCH v3 09/25] mmc: sdhci: allocate alignment and DMA descriptor buffer together Russell King
2016-01-27  9:14   ` Adrian Hunter
2016-01-27 19:50     ` Russell King - ARM Linux
2016-01-26 13:40 ` [PATCH v3 10/25] mmc: sdhci: clean up coding style in sdhci_adma_table_pre() Russell King
2016-01-26 13:40 ` [PATCH v3 11/25] mmc: sdhci: avoid walking SG list for writes Russell King
2016-01-26 13:40 ` [PATCH v3 12/25] mmc: sdhci: factor out common DMA cleanup in sdhci_finish_data() Russell King
2016-01-26 13:40 ` [PATCH v3 13/25] mmc: sdhci: move sdhci_pre_dma_transfer() Russell King
2016-01-26 13:40 ` [PATCH v3 14/25] mmc: sdhci: factor out sdhci_pre_dma_transfer() from sdhci_adma_table_pre() Russell King
2016-01-26 13:40 ` [PATCH v3 15/25] mmc: sdhci: pass the cookie into sdhci_pre_dma_transfer() Russell King
2016-01-26 13:40 ` [PATCH v3 16/25] mmc: sdhci: always unmap a mapped data transfer in sdhci_post_req() Russell King
2016-01-26 13:40 ` [PATCH v3 17/25] mmc: sdhci: clean up host cookie handling Russell King
2016-01-26 13:40 ` [PATCH v3 18/25] mmc: sdhci: plug DMA mapping leak on error Russell King
2016-01-26 13:40 ` [PATCH v3 19/25] mmc: sdhci-pxav3: fix higher speed mode capabilities Russell King
2016-01-26 13:40 ` [PATCH v3 20/25] mmc: sdhci: further fix for DMA unmapping in sdhci_post_req() Russell King
2016-01-26 13:40 ` [PATCH v3 21/25] mmc: sdhci: fix data timeout (part 1) Russell King
2016-01-26 13:41 ` [PATCH v3 22/25] mmc: sdhci: fix data timeout (part 2) Russell King
2016-01-26 13:41 ` [PATCH v3 23/25] mmc: sdhci: prepare DMA address/size quirk handling consolidation Russell King
2016-01-26 13:41 ` [PATCH v3 24/25] mmc: sdhci: consolidate the DMA/ADMA size/address quicks Russell King
2016-01-26 13:41 ` [PATCH v3 25/25] mmc: sdhci: further code simplication Russell King
2016-01-26 15:33 ` [PATCH v3 00/25] MMC/SDHCI fixes Gregory CLEMENT

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=201601262227.M2FVUU8y%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=kbuild-all@01.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mw@semihalf.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=shawnguo@kernel.org \
    --cc=ulf.hansson@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).