All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 3/3] dmaengine: sf-pdma: Get number of channel by device tree
Date: Sat, 15 Jan 2022 01:32:34 +0800	[thread overview]
Message-ID: <202201150140.AnHdUdow-lkp@intel.com> (raw)
In-Reply-To: <91a8fb6dff811b36db951ee98d955ad14a2a30eb.1642151791.git.zong.li@sifive.com>

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

Hi Zong,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on vkoul-dmaengine/next]
[also build test WARNING on v5.16]
[cannot apply to robh/for-next next-20220114]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Zong-Li/Determine-the-number-of-DMA-channels-by-dma-channels-property/20220114-172017
base:   https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git next
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20220115/202201150140.AnHdUdow-lkp(a)intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/efa33512fd463fd6e29750992df1d40513eb5a7c
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Zong-Li/Determine-the-number-of-DMA-channels-by-dma-channels-property/20220114-172017
        git checkout efa33512fd463fd6e29750992df1d40513eb5a7c
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   In file included from include/linux/compiler_types.h:85,
                    from <command-line>:
   arch/riscv/include/asm/jump_label.h: In function 'vchan_cookie_complete':
>> include/linux/compiler-gcc.h:86:38: warning: 'asm' operand 0 probably does not match constraints
      86 | #define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0)
         |                                      ^~~
   arch/riscv/include/asm/jump_label.h:20:9: note: in expansion of macro 'asm_volatile_goto'
      20 |         asm_volatile_goto(
         |         ^~~~~~~~~~~~~~~~~
   include/linux/compiler-gcc.h:86:38: error: impossible constraint in 'asm'
      86 | #define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0)
         |                                      ^~~
   arch/riscv/include/asm/jump_label.h:20:9: note: in expansion of macro 'asm_volatile_goto'
      20 |         asm_volatile_goto(
         |         ^~~~~~~~~~~~~~~~~


vim +/asm +86 include/linux/compiler-gcc.h

313dd1b629219d Kees Cook   2017-05-05  76  
cb984d101b30eb Joe Perches 2015-06-25  77  /*
cb984d101b30eb Joe Perches 2015-06-25  78   * GCC 'asm goto' miscompiles certain code sequences:
cb984d101b30eb Joe Perches 2015-06-25  79   *
cb984d101b30eb Joe Perches 2015-06-25  80   *   http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670
cb984d101b30eb Joe Perches 2015-06-25  81   *
cb984d101b30eb Joe Perches 2015-06-25  82   * Work it around via a compiler barrier quirk suggested by Jakub Jelinek.
cb984d101b30eb Joe Perches 2015-06-25  83   *
cb984d101b30eb Joe Perches 2015-06-25  84   * (asm goto is automatically volatile - the naming reflects this.)
cb984d101b30eb Joe Perches 2015-06-25  85   */
cb984d101b30eb Joe Perches 2015-06-25 @86  #define asm_volatile_goto(x...)	do { asm goto(x); asm (""); } while (0)
cb984d101b30eb Joe Perches 2015-06-25  87  

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2022-01-14 17:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14  9:17 [PATCH v3 0/3] Determine the number of DMA channels by 'dma-channels' property Zong Li
2022-01-14  9:17 ` Zong Li
2022-01-14  9:17 ` [PATCH v3 1/3] riscv: dts: Add dma-channels property in dma node Zong Li
2022-01-14  9:17   ` Zong Li
2022-01-14  9:17 ` [PATCH v3 2/3] dt-bindings: Add dma-channels for pdma device node Zong Li
2022-01-14  9:17   ` Zong Li
2022-01-14  9:17 ` [PATCH v3 3/3] dmaengine: sf-pdma: Get number of channel by device tree Zong Li
2022-01-14  9:17   ` Zong Li
2022-01-14 17:32   ` kernel test robot [this message]
2022-01-14 19:16   ` kernel test robot
2022-01-17  1:29     ` Zong Li
  -- strict thread matches above, loose matches on Subject: below --
2022-01-14 17:22 kernel test robot
2022-01-14 17:22 ` kernel 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=202201150140.AnHdUdow-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.