From: Jani Nikula <jani.nikula@linux.intel.com>
To: Christoph Hellwig <hch@infradead.org>, Dave Airlie <airlied@linux.ie>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] check headers fix.
Date: Tue, 24 May 2016 12:52:05 +0300 [thread overview]
Message-ID: <87bn3vdbqy.fsf@intel.com> (raw)
In-Reply-To: <20160524091005.GB13166@infradead.org>
On Tue, 24 May 2016, Christoph Hellwig <hch@infradead.org> wrote:
> On Tue, May 24, 2016 at 07:29:25AM +0100, Dave Airlie wrote:
>>
>> Hi Linus,
>>
>> here is the C++ guards warning fix from Arnd.
>
> So why the hell do we have C++ guards in kernel headers?
uapi headers. See [1] for the cover letter to the patches with
rationale.
BR,
Jani.
[1] http://mid.gmane.org/1461269857-12813-1-git-send-email-emil.l.velikov@gmail.com
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-05-24 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 6:29 [git pull] check headers fix Dave Airlie
2016-05-24 9:10 ` Christoph Hellwig
2016-05-24 9:52 ` Jani Nikula [this message]
2016-05-24 10:12 ` Daniel Vetter
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=87bn3vdbqy.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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