Re: [PATCH] raid1: use an int as the return value of raise_barrier()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Hou Tao <houtao1@xxxxxxxxxx>
Subject: Re: [PATCH] raid1: use an int as the return value of raise_barrier()
From: Song Liu <liu.song.a23@xxxxxxxxx>
Date: Mon, 22 Jul 2019 14:46:04 -0700
Cc: linux-raid <linux-raid@xxxxxxxxxxxxxxx>, Song Liu <songliubraving@xxxxxx>, open list <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20190702143548.133020-1-houtao1@huawei.com>
References: <20190702143548.133020-1-houtao1@huawei.com>

On Tue, Jul 2, 2019 at 7:30 AM Hou Tao <houtao1@xxxxxxxxxx> wrote:
>
> Using a sector_t as the return value is misleading, because
> raise_barrier() only return 0 or -EINTR.
>
> Also add comments for the return values of raise_barrier().
>
> Signed-off-by: Hou Tao <houtao1@xxxxxxxxxx>

Applied. Thanks for the patch.

Song

References:
- [PATCH] raid1: use an int as the return value of raise_barrier()
  - From: Hou Tao

Prev by Date: Re: [RFC PATCH 0/3] md: export internal stats through debugfs
Next by Date: Re: [V2 PATCH] Set R5_ReadError when there is read failure on parity disk of raid6
Previous by thread: [PATCH] raid1: use an int as the return value of raise_barrier()
Next by thread: [PATCH] Set R5_ReadError when there is read failure on parity disk of raid6
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID Wiki] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux Block] [Linux IDE] [Linux SCSI] [Linux Hams] [Device Mapper] [Device Mapper Cryptographics] [Kernel] [Linux Admin] [Linux Net] [GFS] [RPM] [git] [Yosemite Forum]

Powered by Linux