LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Roland Dreier <rdreier@cisco.com>,
	LKML <linux-kernel@vger.kernel.org>,
	general@lists.openfabrics.org, ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH v2] powerpc: move include files to arch/powerpc/include/asm
Date: Sun, 3 Aug 2008 09:58:14 -0500	[thread overview]
Message-ID: <A5259752-468C-4CBA-BEF3-4E088ED1A5B9@kernel.crashing.org> (raw)
In-Reply-To: <20080801152030.ff10b6b2.sfr@canb.auug.org.au>


On Aug 1, 2008, at 12:20 AM, Stephen Rothwell wrote:

> from include/asm-powerpc.  This is the result of a
>
> mkdir arch/powerpc/include/asm
> git mv include/asm-powerpc/* arch/powerpc/include/asm
>
> Followed by a few documentation/comment fixups and a couple of places
> where <asm-powepc/...> was being used explicitly.  Of the latter only
> one was outside the arch code and it is a driver only built for  
> powerpc.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>
> v2 don't change other arch files - the fixups are only in comments  
> anyway.
>
> This patch can be applied with "git am" - the full patch is way to bug
> for our mailing lists.
>
> This has been built for all the powerpc defconfigs including
> all{no,mod,yes}config.  There was only one failure, but that is
> expected anyway (I had to apply patches for the iommu and hfcmulti
> breakages).

Paul, what's the plan for this change?  If this is something that will  
go in so can we get a tree with it so we can base other patches on it  
(like the PPC_MERGE cleanup)?

- k

  reply	other threads:[~2008-08-03 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01  5:20 [PATCH v2] powerpc: move include files to arch/powerpc/include/asm Stephen Rothwell
2008-08-03 14:58 ` Kumar Gala [this message]
2008-08-03 15:02   ` Stephen Rothwell
2008-08-03 15:00 ` 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=A5259752-468C-4CBA-BEF3-4E088ED1A5B9@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=rdreier@cisco.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox