From: Xi Wang <xi.wang@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Joe Perches <joe@perches.com>
Subject: Re: [PATCH net-next] filter: fix va_list build error
Date: Wed, 1 May 2013 18:29:40 -0400 [thread overview]
Message-ID: <CAKU6vyaEtNC5ZNvF7_vx8gD+rMh1Jo6Wb_=BarLeG9h_VqkYDw@mail.gmail.com> (raw)
In-Reply-To: <51818350.6040600@redhat.com>
On Wed, May 1, 2013 at 5:04 PM, Daniel Borkmann <dborkman@redhat.com> wrote:
> That's a bit weird. Xi, maybe in a follow-up some time later, could
> you move the GCC-internal stdarg.h rather into linux/printk.h, since
> that's where the problem is coming from? Imho, it might be better off
> there, no?
There was some discussion a while ago on whether to make printk.h self
contained or to disallow including it directly. Joe Perches [CCed]
had patches for that.
https://lkml.org/lkml/2011/5/25/263
- xi
prev parent reply other threads:[~2013-05-01 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 20:24 [PATCH net-next] filter: fix va_list build error Xi Wang
2013-05-01 20:29 ` David Miller
2013-05-01 21:04 ` Daniel Borkmann
2013-05-01 22:29 ` Xi Wang [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='CAKU6vyaEtNC5ZNvF7_vx8gD+rMh1Jo6Wb_=BarLeG9h_VqkYDw@mail.gmail.com' \
--to=xi.wang@gmail.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=joe@perches.com \
--cc=netdev@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).