From: Christoph Hellwig <hch@infradead.org>
To: Nathan Scott <nathans@sgi.com>
Cc: Chris Mason <mason@suse.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] buffer_insert_list should use list_add_tail
Date: Sat, 21 Jun 2003 09:48:46 +0100 [thread overview]
Message-ID: <20030621094846.A4080@infradead.org> (raw)
In-Reply-To: <20030619231117.GB722@frodo>; from nathans@sgi.com on Fri, Jun 20, 2003 at 09:11:17AM +1000
On Fri, Jun 20, 2003 at 09:11:17AM +1000, Nathan Scott wrote:
> hi Chris,
>
> We noticed this too and Christoph made this change in the
> 2.4 XFS tree a little while ago - let me check dates - ah,
> 9th May. So, fair bit of testing here and we've not seen
> any issues from this change either (we'd also like to see
> it merged).
It's already in 2.5 for a long time and -ac since the XFS merge, too/
prev parent reply other threads:[~2003-06-21 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 13:15 [PATCH] buffer_insert_list should use list_add_tail Chris Mason
2003-06-19 23:11 ` Nathan Scott
2003-06-21 8:48 ` Christoph Hellwig [this message]
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=20030621094846.A4080@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mason@suse.com \
--cc=nathans@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox