linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] [v2] powerpc/fsl: add PAMUBYPENR register definition to fsl_guts.h
Date: Fri, 16 Mar 2012 14:08:39 -0500	[thread overview]
Message-ID: <4F638FB7.1030509@freescale.com> (raw)
In-Reply-To: <431FD642-F157-4B73-8954-C294A5C107C2@kernel.crashing.org>

Kumar Gala wrote:
> Sticking with my original point of not applying this til PAMU driver is ready as well.

Ok.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2012-03-16 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 17:21 [PATCH 1/2] powerpc/8xxx: remove 85xx/86xx restrictions from fsl_guts.h Timur Tabi
2012-02-16 17:21 ` [PATCH 2/2] [v2] powerpc/fsl: add PAMUBYPENR register definition to fsl_guts.h Timur Tabi
2012-03-16 19:07   ` Kumar Gala
2012-03-16 19:08     ` Timur Tabi [this message]
2012-03-16 19:06 ` [PATCH 1/2] powerpc/8xxx: remove 85xx/86xx restrictions from fsl_guts.h Kumar Gala
2012-03-16 19:09   ` Timur Tabi

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=4F638FB7.1030509@freescale.com \
    --to=timur@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@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).