LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Kumar Gala <galak@somerset.sps.mot.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH][PPC32] Added MPC8555/8541 security block infrastructure
Date: Mon, 8 Nov 2004 21:34:28 -0800	[thread overview]
Message-ID: <20041108213428.16dfb1f7.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0411082319080.13565@blarg.somerset.sps.mot.com>

Kumar Gala <galak@somerset.sps.mot.com> wrote:
>
> This patch adds OCP, interrupt, and memory offset details for the security 
>  block on MPC8555/8541 to support drivers.

Your email client did space-stuffing on the message, so the patch gets 100%
rejects.  I fixed it up by hand and applied the patch locally, thanks.

I think there's a way of telling Pine to stop doing this.

  reply	other threads:[~2004-11-09  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09  5:25 [PATCH][PPC32] Added MPC8555/8541 security block infrastructure Kumar Gala
2004-11-09  5:34 ` Andrew Morton [this message]
2004-11-09  5:48   ` Kumar Gala
2004-11-09  5:54     ` Andrew Morton
2004-11-09  9:12     ` Geert Uytterhoeven
2004-11-09  6:01 ` Eugene Surovegin
2004-11-09  6:15   ` Kumar Gala

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=20041108213428.16dfb1f7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=galak@somerset.sps.mot.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /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