From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] markers: Add missing stdargs.h include, needed due to va_list usage
Date: Wed, 12 Nov 2008 16:01:39 -0200 [thread overview]
Message-ID: <20081112180139.GH13263@ghostprotocols.net> (raw)
In-Reply-To: <20081112172147.GD24126@Krystal>
Em Wed, Nov 12, 2008 at 12:21:47PM -0500, Mathieu Desnoyers escreveu:
> * Arnaldo Carvalho de Melo (acme@redhat.com) wrote:
> > diff --git a/include/linux/marker.h b/include/linux/marker.h
> > index 889196c..6213b5e 100644
> > --- a/include/linux/marker.h
> > +++ b/include/linux/marker.h
> > @@ -12,6 +12,7 @@
> > * See the file COPYING for more details.
> > */
> >
> > +#include <stdarg.h>
>
> Hrm given it's already included in kernel.h for printk, I am not sure
> it's required here ? Although it cannot hurt to add it explicitly.
Well, its just that while writing code I noticed that if I included
marker.h as the first include the compilation would fail.
My impression was that if you use something, you should include its
definition, not relying on the includes hell.
> Mathieu
>
> > #include <linux/types.h>
> >
> > struct module;
next prev parent reply other threads:[~2008-11-12 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 12:52 [PATCH] markers: Add missing stdargs.h include, needed due to va_list usage Arnaldo Carvalho de Melo
2008-11-12 17:21 ` Mathieu Desnoyers
2008-11-12 18:01 ` Arnaldo Carvalho de Melo [this message]
2008-11-12 18:49 ` Mathieu Desnoyers
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=20081112180139.GH13263@ghostprotocols.net \
--to=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.