From: Christoph Hellwig <hch@lst.de>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: [PATCH] fix valid but harmless sparse warning in xfs_log_recovery.c
Date: Tue, 18 Sep 2007 16:39:04 +0200 [thread overview]
Message-ID: <20070918143904.GA8488@lst.de> (raw)
In-Reply-To: <46EF6A6A.3080702@sgi.com>
On Tue, Sep 18, 2007 at 04:04:26PM +1000, Lachlan McIlroy wrote:
> Ah thanks for that, my goof.
Can you and Tim make sure this goes to Linus? I saw Tim sent out
your original fix, and I really don't want to regress on sparse warnings
in mainline.
prev parent reply other threads:[~2007-09-19 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 12:04 [PATCH] fix valid but harmless sparse warning in xfs_log_recovery.c Christoph Hellwig
[not found] ` <46EF6A6A.3080702@sgi.com>
2007-09-18 14:39 ` 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=20070918143904.GA8488@lst.de \
--to=hch@lst.de \
--cc=lachlan@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox