From: viresh.linux@gmail.com (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: QUERY: Inclusion of header files in kernel header files.
Date: Wed, 24 Feb 2010 09:50:59 +0530 [thread overview]
Message-ID: <22dbbef21002232020k76d0f737tf24c8cba29679a21@mail.gmail.com> (raw)
In-Reply-To: <f17812d71002231852l1e47add7pc17764c67d26ae2b@mail.gmail.com>
> My understanding is that if you are going to include every dependency
> into the header files, they are going to explode very soon. E.g. like bus.h,
> as long as you declared something like:
>
> struct device;
> struct resource;
>
If these two structure prototypes are already present in latest kernel
then its okay.
Actually i have seen 2.6.32 and these prototypes are not present
there, so we may need to add
header file or add prototypes of these structures.
rgds,
viresh.
next prev parent reply other threads:[~2010-02-24 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 6:30 QUERY: Inclusion of header files in kernel header files viresh kumar
2010-02-24 2:52 ` Eric Miao
2010-02-24 4:20 ` viresh kumar [this message]
2010-02-24 12:59 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2010-02-23 6:36 viresh kumar
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=22dbbef21002232020k76d0f737tf24c8cba29679a21@mail.gmail.com \
--to=viresh.linux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).