From: Joe Perches <joe@perches.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@osdl.org, torvalds@osdl.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] proc_fs.h redux
Date: Sat, 27 Oct 2007 15:40:04 -0700 [thread overview]
Message-ID: <1193524804.26695.103.camel@localhost> (raw)
In-Reply-To: <20071027194758.GD9816@martell.zuzino.mipt.ru>
On Sat, 2007-10-27 at 23:47 +0400, Alexey Dobriyan wrote:
> Remove proc_fs.h from headers that doesn't really need it.
> --- a/arch/powerpc/kernel/process.c
> +++ b/arch/powerpc/kernel/process.c
> @@ -17,6 +17,7 @@
> #include <linux/errno.h>
> #include <linux/sched.h>
> #include <linux/kernel.h>
> +#include <linux/fs.h>
Your code doesn't match your patch description.
You've got new includes of:
<linux/fs.h>
<linux/proc_fs.h>
<linux/err.h>
<linux/kref.h>
and forward declarations of
struct proc_dir_entry;
struct file_operations;
As a general rule, I think it better to use includes
than use naked forward declarations.
next prev parent reply other threads:[~2007-10-27 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 19:47 [PATCH] proc_fs.h redux Alexey Dobriyan
2007-10-27 22:40 ` Joe Perches [this message]
2007-10-28 7:02 ` Alexey Dobriyan
2007-10-28 8:44 ` Sam Ravnborg
2007-10-29 13:03 ` Arnaldo Carvalho de Melo
2007-10-28 10:34 ` Russell King
2007-10-28 10:43 ` Jan Engelhardt
2007-10-28 11:59 ` Bernhard Walle
2007-10-28 13:04 ` Russell King
2007-10-28 13:04 ` Russell King
2007-10-28 13:25 ` Bernhard Walle
2007-10-28 17:58 ` Roman Zippel
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=1193524804.26695.103.camel@localhost \
--to=joe@perches.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@zeniv.linux.org.uk \
/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.