linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: "Paul Mackerras" <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [RESEND][PATCH 1/2][POWERPC] PIKA Warp: Update platform code tosupportRev B boards
Date: Tue, 29 Apr 2008 01:42:08 -0400	[thread overview]
Message-ID: <20080429014208.79755860@lappy.seanm.ca> (raw)
In-Reply-To: <18454.44365.719572.654726@cargo.ozlabs.ibm.com>

On Tue, 29 Apr 2008 15:08:29 +1000
"Paul Mackerras" <paulus@samba.org> wrote:

> It doesn't help that both of these patches have the same subject line,
> nor that it starts with "Re:". :(

Sorry about that. I just split up the two patches, but the same subject
does apply to both. The code currently in the mainline kernel is for a
Rev A. Since there are no Rev As outside of PIKA, that is not very
useful. These patches bring the platform code up to Rev B standards
(while still maintaining Rev A support).

So the subject is correct for both.

> Also, I find the statement "A change to the dts to get gpios correct
> broke the led code" a bit opaque.  It doesn't tell me in what way it
> was broken or what this patch does to correct, or even what the change
> was in enough detail that I could find the change in the git
> repository.

You won't find it. One of the problems is that I am basically adding
patches to patches to patches, but since none of them are in a
mainline git, they all just keep showing up as one big patch. 

That comment was meant as a quick note to explain why the platform patch
changed from the previous platform patch. Short of diffing the
patches, you can't easily see how they changed.

After the Warp is released (sometime in May), the hardware churn should
end and I can submit patches one at a time rather than one massive
patch.

Cheers,
   Sean

  reply	other threads:[~2008-04-29  5:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 19:22 [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to support Rev B boards Sean MacLennan
2008-04-27 19:25 ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to supportRev " Sean MacLennan
2008-04-28  0:58   ` Stephen Rothwell
2008-04-28  1:51     ` Grant Likely
2008-04-28  2:25       ` Sean MacLennan
2008-04-28  4:47         ` Grant Likely
2008-04-28 17:10           ` Sean MacLennan
2008-04-28 17:44             ` Grant Likely
2008-04-28 17:59               ` Sean MacLennan
2008-04-28 20:44                 ` Richard Purdie
2008-04-28 21:24                   ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code tosupportRev " Sean MacLennan
2008-04-28 21:36                     ` Richard Purdie
2008-04-28  2:31     ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to supportRev " Sean MacLennan
2008-04-28 18:53 ` Sean MacLennan
2008-04-28 19:56   ` Grant Likely
2008-04-28 21:37     ` Sean MacLennan
2008-04-28 21:54       ` Scott Wood
2008-04-28 22:07         ` Sean MacLennan
2008-04-30  0:48           ` Josh Boyer
2008-04-28 22:07       ` Grant Likely
2008-04-29  1:47 ` [RESEND][PATCH 1/2][POWERPC] " Sean MacLennan
2008-04-29  1:50   ` [RESEND][PATCH 2/2][POWERPC] " Sean MacLennan
2008-04-29  1:58     ` Grant Likely
2008-04-29  3:27       ` Sean MacLennan
2008-04-29  3:28   ` [RESEND][PATCH 1/2][POWERPC] " Sean MacLennan
2008-04-29  5:08     ` Paul Mackerras
2008-04-29  5:42       ` Sean MacLennan [this message]
2008-05-06 15:27     ` [RESEND][PATCH 1/2][POWERPC] PIKA Warp: Update platform code tosupportRev " Sean MacLennan

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=20080429014208.79755860@lappy.seanm.ca \
    --to=smaclennan@pikatech.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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).