All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jacek Luczak <difrost.kernel@gmail.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for April 9
Date: Wed, 9 Apr 2008 17:03:33 +0200	[thread overview]
Message-ID: <20080409150333.GA24451@elte.hu> (raw)
In-Reply-To: <20080409145058.GA7648@cvg>


* Cyrill Gorcunov <gorcunov@gmail.com> wrote:

> | > It seems that commit 883a9fc4e5d9b0701f15d4e5a23608f942104721 
> | > ("x86: cleanup - rename VM_MASK to X86_VM_MASK") from the x86 tree 
> | > seems to have missed some places.
> | 
> | i think what happened is that some changes came in from other trees 
> | that reintroduced the old symbols?
> 
> actually, that is the only explanation I could find. The last time I 
> sent you patches to fixup *all* VM_MASK (wich were grep'ed on *latest 
> branch over *all* sources inside x86). So this all were settled down 
> by a few of my patches and /for shame on me/ yours fixups. So these 
> fixups were missed on merging.

no, the problem turned out to be that i kept those fixes too spread out, 
and part of them went into the x86/for-akpm portion of the tree, part of 
it went into x86/testing. Since all x86 developers work against 
x86/testing this was never a problem - only now did it become one when i 
shuffled patches and branch boundaries around. Such problems will go 
away once linux-next starts using x86/testing as well. In any case i 
moved your fixes together and fixed up the patch ordering as well.

	Ingo

  reply	other threads:[~2008-04-09 15:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  8:53 linux-next: Tree for April 9 Stephen Rothwell
     [not found] ` <d711229d0804090400p1c92a158j381b86e207a6f38a@mail.gmail.com>
2008-04-09 11:09   ` Stephen Rothwell
2008-04-09 11:27     ` Stephen Rothwell
2008-04-09 11:26       ` Jacek Luczak
2008-04-09 11:34         ` Ingo Molnar
2008-04-09 11:55           ` Jacek Luczak
2008-04-09 12:01           ` Ingo Molnar
2008-04-09 11:31       ` Ingo Molnar
2008-04-09 14:50         ` Cyrill Gorcunov
2008-04-09 15:03           ` Ingo Molnar [this message]
2008-04-09 15:18             ` Cyrill Gorcunov
2008-04-09 16:55 ` Stefan Richter
2008-04-10  0:45   ` Stephen Rothwell
2008-04-10  6:52   ` Ingo Molnar
2008-04-10  7:44     ` Stephen Rothwell
2008-04-10  7:52       ` debug Kconfig option (was Re: linux-next: Tree for April 9) Stefan Richter
2008-04-10  9:51         ` Ingo Molnar
2008-04-10 19:05           ` [PATCH linux1394-2.6.git] firewire: fw-ohci: add option for remote debugging - amendment Stefan Richter
2008-04-10 22:08             ` Stefan Richter
2008-04-10 15:01         ` debug Kconfig option (was Re: linux-next: Tree for April 9) Randy Dunlap
2008-04-10  9:48       ` linux-next: Tree for April 9 Ingo Molnar
2008-04-10 19:02         ` Stefan Richter
2008-04-10  9:39 ` [BUG] linux-next: Tree for April 9 warning on CC_STACKPROTECTOR, followed by kernel panic Kamalesh Babulal
2008-04-10 10:14   ` Jacek Luczak
2008-04-10 10:51     ` Kamalesh Babulal
2008-04-10 10:58       ` Jacek Luczak
2008-04-10 11:47   ` Stephen Rothwell
2008-04-11  9:45     ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2009-04-09  6:33 linux-next: Tree for April 9 Stephen Rothwell
2009-04-11  6:11 ` Andrew Morton
2009-04-11 11:09   ` Mauro Carvalho Chehab
2009-04-11 12:05     ` Stephen Rothwell
2010-04-09  3:34 Stephen Rothwell

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=20080409150333.GA24451@elte.hu \
    --to=mingo@elte.hu \
    --cc=difrost.kernel@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.