From: "H. Peter Anvin" <hpa@zytor.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
harvey.harrison@gmail.com, sam@ravnborg.org,
jaswinderrajput@gmail.com
Subject: Re: [patch 0/5] x86 -tip: headers cleanup
Date: Wed, 14 Jan 2009 15:41:34 -0800 [thread overview]
Message-ID: <496E782E.5020900@zytor.com> (raw)
In-Reply-To: <496e4e23.0305560a.4545.ffffaf3c@mx.google.com>
Cyrill Gorcunov wrote:
> Small series of headers cleanup, easy to bisect.
> make headers_check still complains about vars
> being found in comments but this is just a false
> alarm. Please review.
Applied patch 1 to tip:x86/setup-lzma, and patches 2, 4 and 5 to
tip:x86/header-fixes.
I'm holding off on patch 3 until we can get feedback on it.
-hpa
prev parent reply other threads:[~2009-01-14 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 20:37 [patch 0/5] x86 -tip: headers cleanup Cyrill Gorcunov
2009-01-14 20:55 ` Sam Ravnborg
2009-01-14 20:58 ` Cyrill Gorcunov
2009-01-14 23:41 ` H. Peter Anvin [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=496E782E.5020900@zytor.com \
--to=hpa@zytor.com \
--cc=gorcunov@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=jaswinderrajput@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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