public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Dave Airlie <airlied@redhat.com>,
	Keith Packard <keithp@keithp.com>, Eric Anholt <eric@anholt.net>,
	Nick Piggin <npiggin@suse.de>,
	David Howells <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Export tiny shmem_file_setup for DRM-GEM
Date: Mon, 20 Oct 2008 14:38:25 -0500	[thread overview]
Message-ID: <1224531505.4323.33.camel@calx> (raw)
In-Reply-To: <Pine.LNX.4.64.0810201939310.14915@blonde.site>

On Mon, 2008-10-20 at 19:47 +0100, Hugh Dickins wrote:
> On Mon, 20 Oct 2008, Matt Mackall wrote:
> > On Sun, 2008-10-19 at 12:52 +0100, Hugh Dickins wrote:
> > > We're trying to keep the !CONFIG_SHMEM tiny-shmem.c (using ramfs without
> > > swap) in synch with CONFIG_SHMEM shmem.c (and mpm is preparing patches
> > > to combine them).  I was glad to see EXPORT_SYMBOL_GPL(shmem_file_setup)
> > > go into shmem.c, but why not support DRM-GEM when !CONFIG_SHMEM too?
> > > But caution says still depend on MMU, since !CONFIG_MMU is.. different.
> > > 
> > > Signed-off-by: Hugh Dickins <hugh@veritas.com>
> > 
> > Acked-by: Matt Mackall <mpm@selenic.com>
> 
> Thanks.
> 
> > 
> > Hugh, what path do you usually take for upstreaming shmem bits and what
> > path should I take with my unify patch?
> 
> I send them to Andrew (Cc linux-kernel and/or linux-mm, erratic which,
> at best depending on what the area of interest is - there's not much
> of interest to linux-mm in the case of this unification) to get their
> airing in -mm until the next merge window.
> 
> You could do that, or were you expecting me to pick up what you had?
> We can do it that way too if you prefer: as things stood, I think
> you were intending to add a patch to remove that redundant function,
> and another to remove CONFIG_TMPFS - but I can do them if you prefer.

Yeah, I've got a few patches here. I'll send them to Andrew, cc:ed to
you and linux-kernel then.

-- 
Mathematics is the supreme nostalgia of our time.


  reply	other threads:[~2008-10-20 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19 11:52 [PATCH] Export tiny shmem_file_setup for DRM-GEM Hugh Dickins
2008-10-20 18:02 ` Matt Mackall
2008-10-20 18:47   ` Hugh Dickins
2008-10-20 19:38     ` Matt Mackall [this message]
2008-10-20 20:20 ` Dave Airlie
2008-10-20 23:04 ` Hugh Dickins

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=1224531505.4323.33.camel@calx \
    --to=mpm@selenic.com \
    --cc=airlied@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=eric@anholt.net \
    --cc=hugh@veritas.com \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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