[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090918191154.GB30063@redhat.com>
Date: Fri, 18 Sep 2009 15:11:54 -0400
From: Mike Snitzer <snitzer@...hat.com>
To: "Jun'ichi Nomura" <j-nomura@...jp.nec.com>
Cc: Jens Axboe <jens.axboe@...cle.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Alasdair G Kergon <agk@...hat.com>,
David Strand <dpstrand@...il.com>,
device-mapper development <dm-devel@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] dm: Use blk_queue_copy_limits()
On Fri, Sep 18 2009 at 12:26pm -0400,
Jun'ichi Nomura <j-nomura@...jp.nec.com> wrote:
> Use new blk_queue_copy_limits() so that invalid limits
> (max_sectors == 0) are fixed up appropriately when copied to the queue.
>
> Signed-off-by: Kiyoshi Ueda <k-ueda@...jp.nec.com>
> Signed-off-by: Jun'ichi Nomura <j-nomura@...jp.nec.com>
> Reported-by: David Strand <dpstrand@...il.com>
> Cc: Mike Snitzer <snitzer@...hat.com>
> Cc: Alasdair G Kergon <agk@...hat.com>
> Cc: Martin K. Petersen <martin.petersen@...cle.com>
> Cc: Jens Axboe <jens.axboe@...cle.com>
> ---
> drivers/md/dm-table.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6.31.work/drivers/md/dm-table.c
> ===================================================================
> --- linux-2.6.31.work.orig/drivers/md/dm-table.c
> +++ linux-2.6.31.work/drivers/md/dm-table.c
> @@ -1090,7 +1090,7 @@ void dm_table_set_restrictions(struct dm
> /*
> * Copy table's limits to the DM device's request_queue
> */
> - q->limits = *limits;
> + blk_queue_copy_limits(q, limits);
>
> if (limits->no_cluster)
> queue_flag_clear_unlocked(QUEUE_FLAG_CLUSTER, q);
How about just having 2 patches in the series and folding the above DM
change into the first patch?
Doesn't _really_ matter I guess...
Anyway, these minor points aside: I like what you've done with this
series.
Acked-by: Mike Snitzer <snitzer@...hat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists