public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauricio Lin <mauriciolin@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc3-mm2: fs/proc/task_mmu.c warnings
Date: Mon, 2 May 2005 19:56:51 -0400	[thread overview]
Message-ID: <3f250c71050502165655f12110@mail.gmail.com> (raw)
In-Reply-To: <20050502164501.50187481.akpm@osdl.org>

Hi Andrew,

On 5/2/05, Andrew Morton <akpm@osdl.org> wrote:
> Mauricio Lin <mauriciolin@gmail.com> wrote:
> >
> > I managed to replicate the warning. This happens with the vanilla
> > kernel 2.6.11.8. Before this version this warning does not exist. The
> > last patch I posted was based on 2.6.11.7. I am going to post the new
> > patch asap.
> 
> Please don't generate patches for the mainline kernel against the -stable
> tree.  2.6.11.7 is ancient - we've added 22MB of diff since then.
> 
> I think I've fixed all the /proc/pid/smaps problems anwyay.

So you have fixed the warning message, right?

Do you mean that I do not have to create the patch for 2.6.11.8?

BR,

Mauricio Lin.

  reply	other threads:[~2005-05-02 23:56 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 23:43 2.6.12-rc3-mm2 Andrew Morton
2005-05-01  0:27 ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01  0:37   ` 2.6.12-rc3-mm2 Andrew Morton
     [not found]     ` <40f323d00504301753140a7ef4@mail.gmail.com>
2005-05-01  1:12       ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01  2:32 ` 2.6.12-rc3-mm2 - /proc/ide/sr0/model: No such file or directory Jesper Juhl
2005-05-03  3:11   ` Greg KH
2005-05-03  3:18     ` Andrew Morton
2005-05-03  4:48       ` Greg KH
2005-05-03  7:11         ` Bartlomiej Zolnierkiewicz
2005-05-03 18:27           ` Greg KH
2005-05-01  3:30 ` [patch] alternative fix for VFS race (was Re: 2.6.12-rc3-mm2) Nick Piggin
2005-05-01 12:56 ` 2.6.12-rc3-mm2: ACPI problems Rafael J. Wysocki
2005-05-01 13:41   ` Brice Goglin
2005-05-01 15:07 ` 2.6.12-rc3-mm2 - kswapd0 keeps running Damir Perisa
2005-05-01 22:06   ` Andrew Morton
2005-05-02  6:01     ` Damir Perisa
2005-05-02 15:31       ` Damir Perisa
2005-05-02 18:14         ` Andrew Morton
2005-05-02 21:30           ` Damir Perisa
2005-05-06 18:07           ` Damir Perisa
2005-05-04 19:12   ` Cameron Harris
2005-05-04 21:47     ` Damir Perisa
2005-05-01 15:08 ` 2.6.12-rc3-mm2: ppc pte_offset_map() Sean Neakums
2005-05-01 15:50   ` Jesper Juhl
2005-05-01 22:46     ` Andrew Morton
2005-05-01 23:01       ` Jesper Juhl
2005-05-03 22:04         ` cliff white
2005-05-02 10:14       ` Hugh Dickins
2005-05-01 22:29 ` 2.6.12-rc3-mm2: fs/proc/task_mmu.c warnings Adrian Bunk
2005-05-02 22:30   ` Mauricio Lin
2005-05-02 23:35     ` Mauricio Lin
2005-05-02 23:45       ` Andrew Morton
2005-05-02 23:56         ` Mauricio Lin [this message]
2005-05-03 20:16           ` cliff white
2005-05-03 22:12             ` Mauricio Lin
2005-05-03 18:02         ` Cliff White
2005-05-02  5:07 ` 2.6.12-rc3-mm2 James Cloos
2005-05-02  5:26   ` 2.6.12-rc3-mm2 Andrew Morton
2005-04-30 21:34     ` 2.6.12-rc3-mm2 Diego Calleja
2005-05-03 16:08     ` 2.6.12-rc3-mm2 Bill Davidsen
2005-05-03 13:37 ` 2.6.12-rc3-mm2 Barry K. Nathan
2005-05-04 15:12   ` 2.6.12-rc3-mm2 Christoph Hellwig

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=3f250c71050502165655f12110@mail.gmail.com \
    --to=mauriciolin@gmail.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox