From: Greg KH <greg@kroah.com>
To: Kumar Gala <galak@freescale.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] ppc32: trivial fix for e500 oprofile build
Date: Wed, 9 Mar 2005 10:59:04 -0800 [thread overview]
Message-ID: <20050309185904.GF27268@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503041303290.18551@blarg.somerset.sps.mot.com>
On Fri, Mar 04, 2005 at 01:09:18PM -0600, Kumar Gala wrote:
> Andrew, Greg
>
> Here is a patch for the new 2.6.11 release tree and for Linus.
>
> Fix for trivial fix for 2.6.11 oprofile compilation on e500 based ppc.
>
> Signed-off-by: Andy Fleming <afleming@freescale.com>
> Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
Added to the -stable queue, thanks.
greg k-h
prev parent reply other threads:[~2005-03-09 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 19:09 [PATCH] ppc32: trivial fix for e500 oprofile build Kumar Gala
2005-03-09 18:59 ` Greg KH [this message]
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=20050309185904.GF27268@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=galak@freescale.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;
as well as URLs for NNTP newsgroup(s).