From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: 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 13:49:06 -0500 [thread overview]
Message-ID: <20081112184905.GA28208@Krystal> (raw)
In-Reply-To: <20081112180139.GH13263@ghostprotocols.net>
* Arnaldo Carvalho de Melo (acme@redhat.com) wrote:
> 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.
>
Ok,
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Thanks,
Mathieu
> > Mathieu
> >
> > > #include <linux/types.h>
> > >
> > > struct module;
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2008-11-12 18:49 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
2008-11-12 18:49 ` Mathieu Desnoyers [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=20081112184905.GA28208@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=acme@redhat.com \
--cc=linux-kernel@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