[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071205123033.GA15394@elte.hu>
Date: Wed, 5 Dec 2007 13:30:33 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Joerg Roedel <joerg.roedel@....com>
Cc: tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] x86_64: define all _PAGE_* in terms of _PAGE_BIT_*
* Joerg Roedel <joerg.roedel@....com> wrote:
> > > > > Sorry, forgot to check the patches before submission. Will
> > > > > cleanup and resubmit soon.
> > > >
> > > > please if possible send a delta against x86.git, not a
> > > > replacement patch. It's easier for the patchflow.
> > >
> > > Not sure I understand you right here. Do you mean a patch on top
> > > of my previous patches?
> >
> > yeah - that's easier to pick up for me (because i've already got
> > your series applied), and it's also easier for you as well. It also
> > makes sense to generally split style fixes from substantial patches.
> > (in the cases where there are pre-existing style problems in the
> > code)
>
> Ok, thanks. Will prepare a patch on top of my first patch series.
it's all in the mm branch of x86.git:
git-clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6.git
cd linux-2.6.git
git-branch x86 # (1)
git-checkout x86
git-pull git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git mm
so the easiest is to do patches just against that tree.
NOTE: the x86.git tree is frequently regenerated, so it can not be
rolling upgraded the usual git way via typing 'git-pull' - you have to
zap your x86 branch and re-pull:
git-checkout master
git-branch -D x86 # this zaps everything!
and repeat from (1) above.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists