public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	schwidefsky@de.ibm.com, mingo@elte.hu, davem@davemloft.net,
	tony.luck@intel.com, paulus@samba.org, tglx@linutronix.de,
	lethal@linux-sh.org
Subject: Re: [PATCH 0/3] hugetlbfs: cleanup and new primitives for s390
Date: Tue, 1 Apr 2008 15:31:02 -0700	[thread overview]
Message-ID: <20080401153102.09af4aca.akpm@linux-foundation.org> (raw)
In-Reply-To: <1207058485.5063.36.camel@localhost.localdomain>

On Tue, 01 Apr 2008 16:01:25 +0200
Gerald Schaefer <gerald.schaefer@de.ibm.com> wrote:

> this patchset cleans up hugetlbfs architecture headers and adds new
> primitives as preparation for the s390 large page support. Most notably
> we found that we need to add a new tlb flush for the copy-on-write of
> a large page (patch #2). We think that this is a bug, but obviously one
> that hasn't shown up so far on any of the other large page architectures.
> 
> As there were no objections so far, which would be the right tree for
> this to get it upstream?

-mm, I suppose.

But all the patcehs had the same title and I'd prefer to not have to
invent your patch titles for you.

  parent reply	other threads:[~2008-04-01 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 14:01 [PATCH 0/3] hugetlbfs: cleanup and new primitives for s390 Gerald Schaefer
2008-04-01 14:06 ` [PATCH 1/3] " Gerald Schaefer
2008-04-01 14:08 ` [PATCH 2/3] " Gerald Schaefer
2008-04-01 14:10 ` [PATCH 3/3] " Gerald Schaefer
2008-04-01 22:31 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-02 14:17 [PATCH 0/3] " Gerald Schaefer

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=20080401153102.09af4aca.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.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