All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: David Rientjes <rientjes@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Neela Kolli <Neela.Kolli@engenio.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] megaraid: fix CONFIG_PROC_FS compile errors
Date: Mon, 30 Apr 2007 19:25:44 -0700	[thread overview]
Message-ID: <20070430192544.5ee78178.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070430084414.be98e552.randy.dunlap@oracle.com>

On Mon, 30 Apr 2007 08:44:14 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:

> On Mon, 30 Apr 2007 07:35:00 -0700 (PDT) David Rientjes wrote:
> 
> > Only declare mega_proc_dir_entry() in CONFIG_PROC_FS.  We should call
> > mega_create_proc_entry() only in this configuration so make sure it's defined
> > if we call it.
> > 
> > Only define mega_adapinq() in CONFIG_PROC_FS.  mega_internal_dev_inquiry()
> > and mega_print_inquiry() were never declared without CONFIG_PROC_FS so
> > make sure we don't have prototypes for them if we aren't going to define
> > them.
> > 
> > Move the declaration of 'buf' in mega_remove_one() because we only use it
> > in the CONFIG_PROC_FS case.
> 
> Just noting the presence of:
>   http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc7/2.6.21-rc7-mm2/broken-out/megaraid-fix-warnings-when-config_proc_fs=n.patch
> 

That patch has been submitted fourteen times in the past year, and was
completely ignored each time.

> 
> Oh, and that SCSI patches need to go to the linux-scsi mailing list.
> 

There seem to be little point in doing that.

  reply	other threads:[~2007-05-01  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 14:35 [patch] megaraid: fix CONFIG_PROC_FS compile errors David Rientjes
2007-04-30 15:44 ` Randy Dunlap
2007-05-01  2:25   ` Andrew Morton [this message]
2007-05-01  4:25     ` Randy Dunlap

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=20070430192544.5ee78178.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Neela.Kolli@engenio.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rientjes@google.com \
    --cc=torvalds@linux-foundation.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 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.