All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: mm.h: Fix noMMU breakage
Date: Fri, 21 Jan 2011 08:49:55 +0100	[thread overview]
Message-ID: <1295596196-8233-1-git-send-email-monstr@monstr.eu> (raw)

Hi,

all noMMU systems are broken that's why I would like to add
this patch (or any similar/better) to mainline ASAP. 
For more information please look at patch description.

Can you give me some ACKs?

Who is responsible for this mm patch? Andrew?

Thanks,
Michal



WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <monstr@monstr.eu>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: mm.h: Fix noMMU breakage
Date: Fri, 21 Jan 2011 08:49:55 +0100	[thread overview]
Message-ID: <1295596196-8233-1-git-send-email-monstr@monstr.eu> (raw)

Hi,

all noMMU systems are broken that's why I would like to add
this patch (or any similar/better) to mainline ASAP. 
For more information please look at patch description.

Can you give me some ACKs?

Who is responsible for this mm patch? Andrew?

Thanks,
Michal


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2011-01-21  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  7:49 Michal Simek [this message]
2011-01-21  7:49 ` mm.h: Fix noMMU breakage Michal Simek
2011-01-21  7:49 ` [PATCH] mm: System without MMU do not need pte_mkwrite Michal Simek
2011-01-21  7:49   ` Michal Simek
2011-01-21 14:35   ` Rik van Riel
2011-01-21 14:35     ` Rik van Riel

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=1295596196-8233-1-git-send-email-monstr@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.