mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yi Jiangshan" <13667453960@163.com>
To: "kernel test robot" <lkp@intel.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, kbuild-all@lists.01.org,
	lczerner@redhat.com, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Jiangshan Yi" <yijiangshan@kylinos.cn>
Subject: Re:Re: [PATCH v3] fs/ext4: replace ternary operator with min()/max() and min_t()
Date: Thu, 8 Sep 2022 10:34:51 +0800 (CST)	[thread overview]
Message-ID: <78e3a115.fe4.1831af33a72.Coremail.13667453960@163.com> (raw)
In-Reply-To: <202208210652.VUSXxffI-lkp@intel.com>


At 2022-08-21 06:50:24, "kernel test robot" <lkp@intel.com> wrote:
>Hi Jiangshan,
>
>Thank you for the patch! Perhaps something to improve:
>
>[auto build test WARNING on tytso-ext4/dev]
>[also build test WARNING on linus/master v6.0-rc1 next-20220819]
>[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#_base_tree_information]
>
>sparse warnings: (new ones prefixed by >>)
>>> fs/ext4/super.c:6907:26: sparse: sparse: incompatible types in comparison expression (different type sizes):
>>> fs/ext4/super.c:6907:26: sparse:    unsigned long *
>>> fs/ext4/super.c:6907:26: sparse:    unsigned int *
>

This bug has been fixed by the latest patch。
[PATCH v4] fs/ext4: replace ternary operator with min()/max() and min_t()
URL： https://lore.kernel.org/all/20220817025928.612851-1-13667453960@163.com/

thanks，

Jiangshan Yi



      reply	other threads:[~2022-09-08  2:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  1:15 Jiangshan Yi
2022-08-16 10:10 ` kernel test robot
2022-08-20 22:50 ` kernel test robot
2022-09-08  2:34   ` Yi Jiangshan [this message]

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=78e3a115.fe4.1831af33a72.Coremail.13667453960@163.com \
    --to=13667453960@163.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=kbuild-all@lists.01.org \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=tytso@mit.edu \
    --cc=yijiangshan@kylinos.cn \
    /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®