All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Christoph Hellwig <hch@infradead.org>,
	Gaudenz Steinlin <gaudenz@debian.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, 486798@bugs.debian.org,
	josejx@gentoo.org
Subject: Re: [PATCH] restore export of handle_mm_fault for Mac on Linux
Date: Thu, 19 Jun 2008 04:01:45 -0700	[thread overview]
Message-ID: <20080619110145.GA27196@kroah.com> (raw)
In-Reply-To: <84144f020806190346t6c27fa02w77de08a14bd5cb89@mail.gmail.com>

On Thu, Jun 19, 2008 at 01:46:57PM +0300, Pekka Enberg wrote:
> On Thu, Jun 19, 2008 at 11:58:05AM +0200, Gaudenz Steinlin wrote:
> >> There is an effort underway to bring the MOL kernel modules into
> >> a mergeable form. But it's not there yet. Joseph Jezak, the MOl main
> >> developer nowdays is working on it. So MOL no longer want's to hide out
> >> of tree. It just needs some more time.
> 
> On Thu, Jun 19, 2008 at 1:38 PM, Christoph Hellwig <hch@infradead.org> wrote:
> > It would be useful if you could send some status-updates to lkml and
> > the kvm list.
> 
> And why not submit MOL to the new linux-staging tree?

That sounds good to me, send them over when you have something that
builds and looks semi-sane :)

thanks,

greg k-h

      reply	other threads:[~2008-06-19 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 10:14 [PATCH] restore export of handle_mm_fault for Mac on Linux Gaudenz Steinlin
2008-06-18 11:49 ` Christoph Hellwig
2008-06-18 12:45   ` Paul Mackerras
2008-06-18 12:51     ` Christoph Hellwig
2008-06-19  9:59       ` Gaudenz Steinlin
2008-06-18 17:18 ` Alan Cox
2008-06-19  9:58   ` Gaudenz Steinlin
2008-06-19 10:38     ` Christoph Hellwig
2008-06-19 10:46       ` Pekka Enberg
2008-06-19 11:01         ` Greg KH [this message]

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=20080619110145.GA27196@kroah.com \
    --to=greg@kroah.com \
    --cc=486798@bugs.debian.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gaudenz@debian.org \
    --cc=hch@infradead.org \
    --cc=josejx@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /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.