From: Christopher Li <sparse@chrisli.org>
To: Kamil Dudka <kdudka@redhat.com>
Cc: Hannes Eder <hannes@hanneseder.net>,
sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] make sparse headers self-compilable...
Date: Tue, 11 Aug 2009 14:08:59 -0700 [thread overview]
Message-ID: <70318cbf0908111408y609dd2cex42c6b78d3e35d709@mail.gmail.com> (raw)
In-Reply-To: <200908111459.23341.kdudka@redhat.com>
On Tue, Aug 11, 2009 at 5:59 AM, Kamil Dudka<kdudka@redhat.com> wrote:
> Thanks for the hint! It's definitely better, though not sufficient in all
> cases. The amended patch is attached.
Will apply.
Thanks
Chris
prev parent reply other threads:[~2009-08-11 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 20:27 [PATCH] make sparse headers self-compilable Kamil Dudka
2009-08-08 11:10 ` Kamil Dudka
2009-08-11 9:40 ` Christopher Li
2009-08-11 9:55 ` Kamil Dudka
2009-08-11 10:40 ` Kamil Dudka
2009-08-11 21:08 ` Christopher Li
2009-08-11 21:25 ` Kamil Dudka
2009-08-11 12:48 ` Hannes Eder
2009-08-11 12:59 ` Kamil Dudka
2009-08-11 21:08 ` Christopher Li [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=70318cbf0908111408y609dd2cex42c6b78d3e35d709@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=hannes@hanneseder.net \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).