public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Pierre Peiffer <pierre.peiffer@bull.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [resend][PATCH] Remove duplicated declarations in procfs
Date: Fri, 28 Sep 2007 00:39:27 -0700	[thread overview]
Message-ID: <20070928003927.6d08c050.akpm@linux-foundation.org> (raw)
In-Reply-To: <46FCACFC.3010103@bull.net>

On Fri, 28 Sep 2007 09:27:56 +0200 Pierre Peiffer <pierre.peiffer@bull.net> wrote:

> From: Pierre Peiffer <pierre.peiffer@bull.net>
> 
> This is a trivial patch that removes some duplicated declarations of
> extern variables.
> 
> Signed-off-by: Pierre Peiffer <pierre.peiffer@bull.net>
> ---
> 
>  fs/proc/internal.h |    4 ----
>  1 files changed, 0 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/proc/internal.h b/fs/proc/internal.h
> index b215c35..d812816 100644
> --- a/fs/proc/internal.h
> +++ b/fs/proc/internal.h
> @@ -50,10 +50,6 @@ extern const struct file_operations proc_maps_operations;
>  extern const struct file_operations proc_numa_maps_operations;
>  extern const struct file_operations proc_smaps_operations;
>  
> -extern const struct file_operations proc_maps_operations;
> -extern const struct file_operations proc_numa_maps_operations;
> -extern const struct file_operations proc_smaps_operations;
> -
>  
>  void free_proc_entry(struct proc_dir_entry *de);

yup, thanks, the maps2 patches in -mm already accidentally fixed this so I haven't
bothered merging it as a standalone thing.


  reply	other threads:[~2007-09-28  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  7:27 [resend][PATCH] Remove duplicated declarations in procfs Pierre Peiffer
2007-09-28  7:39 ` Andrew Morton [this message]
2007-09-28  7:49   ` Pierre Peiffer

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=20070928003927.6d08c050.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.peiffer@bull.net \
    /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