Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1391588 > unrolled thread

Re: [PATCH] Use MICRO UINT_MAX instead of actual value

Started byMinfei Huang <mnghuan@gmail.com>
First post2016-04-30 12:20 +0200
Last post2016-04-30 12:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] Use MICRO UINT_MAX instead of actual value Minfei Huang <mnghuan@gmail.com> - 2016-04-30 12:20 +0200

#1391588 — Re: [PATCH] Use MICRO UINT_MAX instead of actual value

FromMinfei Huang <mnghuan@gmail.com>
Date2016-04-30 12:20 +0200
SubjectRe: [PATCH] Use MICRO UINT_MAX instead of actual value
Message-ID<rtAae-66I-13@gated-at.bofh.it>
Ping.

Any comment is appreciate.

Thanks
Minfei

On 04/25/16 at 11:13P, Minfei Huang wrote:
> It's more elegant to use MICRO UINT_MAX to represent the max value of
> type unsigned int. So replace the actual value by using this MICRO.
> 
> Signed-off-by: Minfei Huang <mnghuan@gmail.com>
> ---
>  drivers/nvme/host/core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index 643f457..2c0bb13 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -597,7 +597,7 @@ static void nvme_config_discard(struct nvme_ns *ns)
>  
>  	ns->queue->limits.discard_alignment = logical_block_size;
>  	ns->queue->limits.discard_granularity = logical_block_size;
> -	blk_queue_max_discard_sectors(ns->queue, 0xffffffff);
> +	blk_queue_max_discard_sectors(ns->queue, UINT_MAX);
>  	queue_flag_set_unlocked(QUEUE_FLAG_DISCARD, ns->queue);
>  }
>  
> -- 
> 2.6.3
> 

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web