From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ronni Holm-Nielsen <theronni@gmail.com>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
Johannes Buchner <buchner.johannes@gmx.at>,
ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Jens Axboe <jens.axboe@oracle.com>,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
xfs@oss.sgi.com
Subject: Re: [patch 0/7] per-bdi flushing model improvements. reiser4
Date: Tue, 02 Feb 2010 23:26:20 +0100 [thread overview]
Message-ID: <4B68A68C.6030001@gmail.com> (raw)
In-Reply-To: <5e2ec5ac1002021345g569c743dtc5ccf77cde6738ae@mail.gmail.com>
Hello everyone.
The patches 1-3 are reverses for the following -mm stuff:
http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-fixed-null-pointer-dereference.patch
http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-generic_sync_sb_inodes-doesnt-exist-anymore.patch
http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-vfs-add-super_operationssync_inodes-2.patch
This is incorrect attempts to adjust reiser4 to the new per-bdi flushing
model.
The authors are cc-ed,
any comments, suggestions are welcome.
Thanks,
Edward.
Ronni Holm-Nielsen wrote:
> To clarify (being a ReiserFS subscriber):
>
> patch 0, 4-6 sent to Andrew, ReiserFS, linux-fsdevel, linux-kernel, xfs,
> jens.axboe
> patch 1-3, 7 sent to Andrew, ReiserFS
>
> - Ronni
>
> On Tue, Feb 2, 2010 at 11:42 PM, Jens Axboe <jens.axboe@oracle.com> wrote:
>
>
>> On Tue, Feb 02 2010, Edward Shishkin wrote:
>>
>>> Christoph Hellwig wrote:
>>>
>>>> I got this introduction twice, but patches 1-3 didn't make it to any of
>>>> the lists.
>>>>
>>>>
>>>>
>>>>
>>> done
>>>
>> Where?
>>
>> --
>> Jens Axboe
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ronni Holm-Nielsen <theronni@gmail.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com, Johannes Buchner <buchner.johannes@gmx.at>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Subject: Re: [patch 0/7] per-bdi flushing model improvements. reiser4
Date: Tue, 02 Feb 2010 23:26:20 +0100 [thread overview]
Message-ID: <4B68A68C.6030001@gmail.com> (raw)
In-Reply-To: <5e2ec5ac1002021345g569c743dtc5ccf77cde6738ae@mail.gmail.com>
Hello everyone.
The patches 1-3 are reverses for the following -mm stuff:
http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-fixed-null-pointer-dereference.patch
http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-generic_sync_sb_inodes-doesnt-exist-anymore.patch
http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-vfs-add-super_operationssync_inodes-2.patch
This is incorrect attempts to adjust reiser4 to the new per-bdi flushing
model.
The authors are cc-ed,
any comments, suggestions are welcome.
Thanks,
Edward.
Ronni Holm-Nielsen wrote:
> To clarify (being a ReiserFS subscriber):
>
> patch 0, 4-6 sent to Andrew, ReiserFS, linux-fsdevel, linux-kernel, xfs,
> jens.axboe
> patch 1-3, 7 sent to Andrew, ReiserFS
>
> - Ronni
>
> On Tue, Feb 2, 2010 at 11:42 PM, Jens Axboe <jens.axboe@oracle.com> wrote:
>
>
>> On Tue, Feb 02 2010, Edward Shishkin wrote:
>>
>>> Christoph Hellwig wrote:
>>>
>>>> I got this introduction twice, but patches 1-3 didn't make it to any of
>>>> the lists.
>>>>
>>>>
>>>>
>>>>
>>> done
>>>
>> Where?
>>
>> --
>> Jens Axboe
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
>
>
next prev parent reply other threads:[~2010-02-02 22:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 1:55 [patch 0/7] per-bdi flushing model improvements. reiser4 Edward Shishkin
2010-02-02 1:55 ` Edward Shishkin
2010-02-02 8:17 ` Christoph Hellwig
2010-02-02 8:17 ` Christoph Hellwig
2010-02-02 15:25 ` Edward Shishkin
2010-02-02 15:25 ` Edward Shishkin
2010-02-02 19:42 ` Jens Axboe
2010-02-02 19:42 ` Jens Axboe
2010-02-02 21:45 ` Ronni Holm-Nielsen
2010-02-02 22:26 ` Edward Shishkin [this message]
2010-02-02 22:26 ` Edward Shishkin
2010-02-21 19:47 ` Johannes Buchner
2010-02-21 19:47 ` Johannes Buchner
2010-02-21 20:30 ` Edward Shishkin
2010-02-21 20:30 ` Edward Shishkin
2010-02-24 7:12 ` Christian Kujau
2010-02-24 7:12 ` Christian Kujau
2010-02-02 21:47 ` Ronni Holm-Nielsen
2010-02-02 21:47 ` Ronni Holm-Nielsen
2010-02-02 21:47 ` Ronni Holm-Nielsen
-- strict thread matches above, loose matches on Subject: below --
2010-02-02 1:39 Edward Shishkin
2010-02-02 1:39 ` Edward Shishkin
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=4B68A68C.6030001@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=buchner.johannes@gmx.at \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=theronni@gmail.com \
--cc=xfs@oss.sgi.com \
/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.