[PATCH-RESEND 20/23] staging/lustre/lprocfs: interpret result of dt_statfs() correctly

[Peng Tao]

On Tue, Jun 4, 2013 at 10:51 AM, Greg Kroah-Hartman
<gregkh at linuxfoundation.org> wrote:
> On Tue, Jun 04, 2013 at 10:35:09AM +0800, Peng Tao wrote:
>> On Tue, Jun 4, 2013 at 2:26 AM, Greg Kroah-Hartman
>> <gregkh at linuxfoundation.org> wrote:
>> > On Mon, Jun 03, 2013 at 09:40:57PM +0800, Peng Tao wrote:
>> >> From: "John L. Hammond" <john.hammond at intel.com>
>> >>
>> >> In a7369bcd860af61a073cb2424139e3acccdcb203, I accidentally reversed
>> >
>> > That commit id means nothing here, in the kernel, so I'll not apply this
>> > patch for now, sorry.  Please fix this and resend it.
>> >
>> Thanks. I'll fix and resend it.
>>
>> And I noticed that somehow I didn't get notifications of bellow two
>> patches being queued:
>>
>> [PATCH-RESEND 15/23] staging/lustre/changelog: fix CL_LAYOUT, accept all types
>> http://driverdev.linuxdriverproject.org/pipermail/devel/2013-June/038763.html
>>
>> [PATCH-RESEND 17/23] staging/lustre/changelog: fix CL_LAYOUT comment, string
>> http://driverdev.linuxdriverproject.org/pipermail/devel/2013-June/038765.html
>>
>> Could you please confirm if they were queued? Do I need to resend them as well?
>
> Both of them are in my tree, you can always confirm this yourself by
> checking out the staging-next branch of the staging.git tree on
> git.kernel.org.  Which is what you will need to be doing anyway, if you
> wish to send me future patches, as I've already accepted one by someone
> other than youself, so you need to ensure that you stay in sync.
>
I see. Thanks for the information. I'll check there in future.

Thanks,
Tao