public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Peng Tao <tao.peng@emc.com>, Peng Tao <bergwolf@gmail.com>
Subject: Re: [PATCH] staging: Disable lustre file system for MIPS, SH, and XTENSA
Date: Mon, 9 Sep 2013 10:22:32 -0700	[thread overview]
Message-ID: <20130909172232.GA10029@kroah.com> (raw)
In-Reply-To: <20130909170819.GA22764@roeck-us.net>

On Mon, Sep 09, 2013 at 10:08:19AM -0700, Guenter Roeck wrote:
> On Mon, Sep 09, 2013 at 09:39:02AM -0700, Greg Kroah-Hartman wrote:
> > On Mon, Sep 09, 2013 at 06:40:12AM -0700, Christoph Hellwig wrote:
> > > On Sun, Sep 08, 2013 at 06:59:45PM -0700, Greg Kroah-Hartman wrote:
> > > > Can't we just export the functions for those arches?  Surely lutre
> > > > isn't the first/only driver that needs this?
> > > 
> > > Lustre is.  These are core mm helpers, and lustre uses them to
> > > reimplement another core VM function.  It then uses it to access
> > > userspace environment variable.
> > > 
> > > In short all this code should be nuked, and no new symbols should be
> > > exported.
> > 
> > Ugh, you are right, the lustre code needs to be fixed here.
> > 
> Given that, should I send another patch marking it as BROKEN again ?

Well, on those arches it's "broken", so I'll dig up your original patch
on this thread.  It's just "normal" for staging drivers to duplicate
core code, it needs to be fixed up before it can be merged into the
kernel tree, so no need to do anything special.

thanks,

greg k-h

  reply	other threads:[~2013-09-09 17:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09  1:03 [PATCH] staging: Disable lustre file system for MIPS, SH, and XTENSA Guenter Roeck
2013-09-09  1:59 ` Greg Kroah-Hartman
2013-09-09  2:18   ` Ramkumar Ramachandra
2013-09-09  2:33     ` Greg Kroah-Hartman
2013-09-09  2:38       ` Ramkumar Ramachandra
2013-09-09  2:50         ` Greg Kroah-Hartman
2013-09-09  2:55           ` Ramkumar Ramachandra
2013-09-09  3:21             ` Guenter Roeck
2013-09-09  3:38               ` Ramkumar Ramachandra
2013-09-09  2:24   ` Guenter Roeck
2013-09-09  2:31     ` Greg Kroah-Hartman
2013-09-09  2:31       ` Guenter Roeck
2013-09-09  5:01         ` Heiko Carstens
2013-09-10 17:14           ` Peng Tao
2013-09-11  1:44             ` Christoph Hellwig
2013-09-11  2:25               ` Peng Tao
2013-09-11  2:30                 ` Guenter Roeck
2013-09-11  2:51                   ` Peng Tao
2013-09-11 16:29                     ` Christoph Hellwig
2013-09-11 21:23                       ` Dilger, Andreas
2013-09-11 20:48                 ` Dilger, Andreas
2013-09-12  8:01                   ` Peng Tao
2013-09-09 13:40   ` Christoph Hellwig
2013-09-09 16:39     ` Greg Kroah-Hartman
2013-09-09 17:08       ` Guenter Roeck
2013-09-09 17:22         ` Greg Kroah-Hartman [this message]
2013-09-09 19:11           ` Geert Uytterhoeven
2013-09-09 20:06             ` Guenter Roeck
2013-09-10  8:49               ` Geert Uytterhoeven
2013-09-10 16:44                 ` Guenter Roeck
2013-09-10 16:51                   ` Geert Uytterhoeven
2013-09-10 17:15                 ` Peng Tao

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=20130909172232.GA10029@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bergwolf@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=tao.peng@emc.com \
    /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