Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: dm-devel@redhat.com
Subject: Re: dm: impose configurable deadline for dm_request_fn's merge heuristic
Date: Mon, 2 Mar 2015 18:26:42 -0500	[thread overview]
Message-ID: <20150302232642.GC26740@redhat.com> (raw)
In-Reply-To: <20150302163143.GA27120@mwanda>

On Mon, Mar 02 2015 at 11:31am -0500,
Dan Carpenter <dan.carpenter@oracle.com> wrote:

> Hello Mike Snitzer,
> 
> The patch 6ee47d96b97d: "dm: impose configurable deadline for
> dm_request_fn's merge heuristic" from Feb 26, 2015, leads to the
> following static checker warning:
> 
> 	drivers/md/dm.c:1968 dm_attr_rq_based_queue_deadline_store()
> 	warn: impossible condition '(deadline > ((~0 >> 1))) => (s32min-s32max > s32max)'

Fixed up with latest code, see:
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=f975bc0d522d1e57b108bf9e2e0293ee3f78f821

      reply	other threads:[~2015-03-02 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 16:31 dm: impose configurable deadline for dm_request_fn's merge heuristic Dan Carpenter
2015-03-02 23:26 ` 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=20150302232642.GC26740@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dm-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox