Displaying 4 results from an estimated 4 matches for "sd_format_disk_nam".
Did you mean:
sd_format_disk_name
2012 Mar 30
10
[PATCH 0/4] block: move sd_format_disk_name() into block core as disk_name_format()
This patch series renames "sd_format_disk_name()" to
"disk_name_format()" and moves it into block core. So
that who needs formatting disk name can use it, instead
of duplicating these similar help functions.
Ren Mingxin (4):
block: add function disk_name_format() into block core
scsi: replace sd_format_disk_name() to disk...
2012 Mar 30
10
[PATCH 0/4] block: move sd_format_disk_name() into block core as disk_name_format()
This patch series renames "sd_format_disk_name()" to
"disk_name_format()" and moves it into block core. So
that who needs formatting disk name can use it, instead
of duplicating these similar help functions.
Ren Mingxin (4):
block: add function disk_name_format() into block core
scsi: replace sd_format_disk_name() to disk...
2012 Mar 28
2
[PATCH] virtio_blk: add helper function to support mass of disks naming
On Wed, Mar 28, 2012 at 02:54:43PM +0800, Ren Mingxin wrote:
> Hi,
>
> The current virtblk's naming algorithm just supports 26^3
> disks. If there are mass of virtblks(exceeding 26^3), there
> will be disks with the same name.
>
> According to "sd_format_disk_name()", I add function
> "virtblk_name_format()" for virtblk to support mass of
> disks.
>
> Signed-off-by: Ren Mingxin <renmx at cn.fujitsu.com>
Nod. This is basically what 3e1a7ff8a0a7b948f2684930166954f9e8e776fe
did. Except, maybe we should move this function into...
2012 Mar 28
2
[PATCH] virtio_blk: add helper function to support mass of disks naming
On Wed, Mar 28, 2012 at 02:54:43PM +0800, Ren Mingxin wrote:
> Hi,
>
> The current virtblk's naming algorithm just supports 26^3
> disks. If there are mass of virtblks(exceeding 26^3), there
> will be disks with the same name.
>
> According to "sd_format_disk_name()", I add function
> "virtblk_name_format()" for virtblk to support mass of
> disks.
>
> Signed-off-by: Ren Mingxin <renmx at cn.fujitsu.com>
Nod. This is basically what 3e1a7ff8a0a7b948f2684930166954f9e8e776fe
did. Except, maybe we should move this function into...