From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-scsi@vger.kernel.org, Mauelshagen@redhat.com,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
dm-devel@redhat.com, jens.axboe@oracle.com
Subject: Re: [PATCHSET] block,scsi,libata: implement alt_size
Date: Fri, 08 May 2009 12:21:45 -0400 [thread overview]
Message-ID: <4A045C19.4060801@garzik.org> (raw)
In-Reply-To: <4A03F7A8.9090204@kernel.org>
Tejun Heo wrote:
> Dan Williams wrote:
>> On Mon, May 4, 2009 at 8:28 PM, Tejun Heo <tj@kernel.org> wrote:
>>> Pushing this in the kernel without updating dm-raid is kind of
>>> pointless. Who should I be poking to get the userland part moving?
>> Dmraid is not the only potential user. Mdadm will also care about
>> this as I have seen a report that points to a user having what looks
>> like an HPA issue with an Intel(R) Matrix array. So, there are two
>> immediate users for this interface. Heinz is the right person to poke
>> for dmraid updates. I'll handle the mdadm update.
>
> Alright, then. With Jeff's reluctant ack and scheduled mdadm update,
> I guess this one can go upstream. I'll refresh the patchset and
> repost. Umm... BTW do I have Heinz's mail address right?
The email addr is correct according to dmraid-current.tar.bz2 (dated Sep
2008), at least. I don't have any better info.
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: Dan Williams <dan.j.williams@gmail.com>,
linux-ide@vger.kernel.org, jens.axboe@oracle.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
James.Bottomley@hansenpartnership.com, Mauelshagen@redhat.com,
dm-devel@redhat.com
Subject: Re: [PATCHSET] block,scsi,libata: implement alt_size
Date: Fri, 08 May 2009 12:21:45 -0400 [thread overview]
Message-ID: <4A045C19.4060801@garzik.org> (raw)
In-Reply-To: <4A03F7A8.9090204@kernel.org>
Tejun Heo wrote:
> Dan Williams wrote:
>> On Mon, May 4, 2009 at 8:28 PM, Tejun Heo <tj@kernel.org> wrote:
>>> Pushing this in the kernel without updating dm-raid is kind of
>>> pointless. Who should I be poking to get the userland part moving?
>> Dmraid is not the only potential user. Mdadm will also care about
>> this as I have seen a report that points to a user having what looks
>> like an HPA issue with an Intel(R) Matrix array. So, there are two
>> immediate users for this interface. Heinz is the right person to poke
>> for dmraid updates. I'll handle the mdadm update.
>
> Alright, then. With Jeff's reluctant ack and scheduled mdadm update,
> I guess this one can go upstream. I'll refresh the patchset and
> repost. Umm... BTW do I have Heinz's mail address right?
The email addr is correct according to dmraid-current.tar.bz2 (dated Sep
2008), at least. I don't have any better info.
Jeff
next prev parent reply other threads:[~2009-05-08 16:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 2:55 [PATCHSET] block,scsi,libata: implement alt_size Tejun Heo
2009-02-01 2:55 ` Tejun Heo
2009-02-01 2:55 ` [PATCH 1/3] block: add alt_size Tejun Heo
2009-02-01 2:55 ` Tejun Heo
2009-02-01 2:55 ` [PATCH 2/3] scsi: add scsi_device->alt_capacity Tejun Heo
2009-02-01 2:55 ` Tejun Heo
2009-02-01 2:55 ` [PATCH 3/3] libata: export HPA size as alt_size Tejun Heo
2009-02-01 2:55 ` Tejun Heo
2009-02-02 17:12 ` [PATCH] libata: change drive ready wait after hard reset to 5s Stuart_Hayes
2009-02-02 17:12 ` Stuart_Hayes
2009-02-02 17:17 ` Mario Limonciello
2009-02-09 21:48 ` Stuart_Hayes
2009-02-09 21:48 ` Stuart_Hayes
2009-02-01 2:59 ` [PATCHSET] dmraid: use alt_size Tejun Heo
2009-02-01 2:59 ` Tejun Heo
2009-02-01 2:59 ` Tejun Heo
2009-02-01 3:00 ` [PATCH 1/3] dmraid: set read_info to @offset by default in read_raid_dev() Tejun Heo
2009-02-01 3:00 ` Tejun Heo
2009-02-01 3:00 ` [PATCH 2/3] dmraid: add alt_size to dev_info Tejun Heo
2009-02-01 3:00 ` Tejun Heo
2009-02-01 3:01 ` [PATCH 3/3] dmraid: make nv use alt_size if available Tejun Heo
2009-02-01 3:01 ` Tejun Heo
2009-02-01 3:20 ` [PATCHSET] block,scsi,libata: implement alt_size Jeff Garzik
2009-02-01 4:14 ` Tejun Heo
2009-02-01 4:14 ` Tejun Heo
2009-04-30 1:13 ` Tejun Heo
2009-04-30 1:13 ` Tejun Heo
2009-04-30 1:13 ` Tejun Heo
2009-04-30 1:45 ` Jeff Garzik
2009-04-30 1:50 ` Tejun Heo
2009-04-30 20:00 ` Jeff Garzik
2009-04-30 21:15 ` Dan Williams
2009-04-30 21:15 ` Dan Williams
2009-05-04 8:02 ` Tejun Heo
2009-05-04 8:02 ` Tejun Heo
2009-05-04 16:48 ` Dan Williams
2009-05-05 3:28 ` Tejun Heo
2009-05-05 15:34 ` Dan Williams
2009-05-08 9:13 ` Tejun Heo
2009-05-08 16:21 ` Jeff Garzik [this message]
2009-05-08 16:21 ` Jeff Garzik
2009-05-08 16:23 ` Dan Williams
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=4A045C19.4060801@garzik.org \
--to=jeff@garzik.org \
--cc=Mauelshagen@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.