All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
	kbuild-all@01.org
Subject: Re: [dm:for-next 26/26] drivers/md/dm-crypt.c:3068:2: error: 't' undeclared; did you mean 'ti'?
Date: Fri, 10 Aug 2018 16:15:50 -0400	[thread overview]
Message-ID: <20180810201550.GA23525@redhat.com> (raw)
In-Reply-To: <201808110324.UeVLl4oD%fengguang.wu@intel.com>

On Fri, Aug 10 2018 at  3:12pm -0400,
kbuild test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
> head:   08575fd060d7f88f674509461b32d86b272093d9
> commit: 08575fd060d7f88f674509461b32d86b272093d9 [26/26] dm crypt: don't decrease device limits
> config: i386-allmodconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
>         git checkout 08575fd060d7f88f674509461b32d86b272093d9
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> 
> All errors (new ones prefixed by >>):
> 
>    drivers/md/dm-crypt.c: In function 'crypt_io_hints':
> >> drivers/md/dm-crypt.c:3068:2: error: 't' undeclared (first use in this function); did you mean 'ti'?
>      t->io_min = max_t(unsigned, limits->io_min, cc->sector_size);
>      ^
>      ti
>    drivers/md/dm-crypt.c:3068:2: note: each undeclared identifier is reported only once for each function it appears in


Fixed up, needed to be: limits->io_min = max_t(unsigned, limits->io_min, cc->sector_size);

Sorry for the noise...

And thanks,
Mike

      reply	other threads:[~2018-08-10 20:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 19:12 [dm:for-next 26/26] drivers/md/dm-crypt.c:3068:2: error: 't' undeclared; did you mean 'ti'? kbuild test robot
2018-08-10 20:15 ` Mike Snitzer [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=20180810201550.GA23525@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=lkp@intel.com \
    --cc=mpatocka@redhat.com \
    /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.