From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Prodyut Hazarika" <phazarika@amcc.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Question on 4xx GIT tree
Date: Mon, 8 Sep 2008 17:35:09 -0400 [thread overview]
Message-ID: <20080908173509.7cccdbc7@zod.rchland.ibm.com> (raw)
In-Reply-To: <0CA0A16855646F4FA96D25A158E299D604F7F1A4@SDCEXCHANGE01.ad.amcc.com>
On Mon, 8 Sep 2008 13:55:26 -0700
"Prodyut Hazarika" <phazarika@amcc.com> wrote:
> Hi Josh,
> I am planning to submit a patch to support 4K/16K and 64K page size for 4xx processors.
> I see that your git tree still has the include/asm-powerpc/* header files, while in Linus's git tree, the powerpc specific header file has been moved to arch/powerpc/include/asm.
I assume you're looking at my master branch. That was a bit old and
I've updated it now to match the overall powerpc.git tree master
branch. Sorry about that, I'll be a bit more diligent in keeping it
updated from now on.
> Should I base my patch from your git tree or Linus's git tree? Please advice how to proceed since I want your efforts in merging as painless as possible.
Generally, if you track my 'next' branch that is what will be most
current for 4xx. It contains patches that aren't anywhere else at the
moment.
josh
next prev parent reply other threads:[~2008-09-08 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 20:55 Question on 4xx GIT tree Prodyut Hazarika
2008-09-08 21:35 ` Josh Boyer [this message]
2008-09-08 21:42 ` Prodyut Hazarika
2008-09-08 23:38 ` Josh Boyer
2008-09-10 23:47 ` Prodyut Hazarika
2008-09-11 0:31 ` Josh Boyer
2008-09-11 0:34 ` Prodyut Hazarika
2008-09-11 4:48 ` Stefan Roese
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=20080908173509.7cccdbc7@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=phazarika@amcc.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;
as well as URLs for NNTP newsgroup(s).