From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>
Cc: "Anvin, H Peter" <h.peter.anvin@intel.com>,
"Dutt, Sudeep" <sudeep.dutt@intel.com>,
"Yokoyama, Caz" <caz.yokoyama@intel.com>,
"Chandramouli,
Dasaratharaman" <dasaratharaman.chandramouli@intel.com>,
"Rao, Nikhil" <nikhil.rao@intel.com>,
"Kharche, Harshavardhan R" <harshavardhan.r.kharche@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] checkpatch: Don't require kernel style __attribute__ shortcuts in uapi paths
Date: Mon, 11 Nov 2013 22:01:10 +0000 [thread overview]
Message-ID: <6DC2528F945B4149AB6566DFB5F22ED38AAA1DC8@ORSMSX109.amr.corp.intel.com> (raw)
In-Reply-To: <1384120524.3081.18.camel@joe-AO722>
> -----Original Message-----
> From: Joe Perches [mailto:joe@perches.com]
> Sent: Sunday, November 10, 2013 1:55 PM
> Subject: [PATCH] checkpatch: Don't require kernel style __attribute__ shortcuts
> in uapi paths
>
> Avoid proscribing kernel styled shortcuts for
> gcc extensions of __attribute__((foo)) in the
> uapi include paths.
Thanks Joe. This works for us nicely.
prev parent reply other threads:[~2013-11-11 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <527D5646.9010005@intel.com>
[not found] ` <6DC2528F945B4149AB6566DFB5F22ED38AAA18B7@ORSMSX109.amr.corp.intel.com>
2013-11-10 21:56 ` Joe Perches
[not found] ` <1384120524.3081.18.camel@joe-AO722>
2013-11-11 22:01 ` Dixit, Ashutosh [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=6DC2528F945B4149AB6566DFB5F22ED38AAA1DC8@ORSMSX109.amr.corp.intel.com \
--to=ashutosh.dixit@intel.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=caz.yokoyama@intel.com \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=eddie.dong@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=harshavardhan.r.kharche@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=sudeep.dutt@intel.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
all inboxes | Powered by JetHome®