From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/fsl: add PAMUBYPENR register definition to fsl_guts.h
Date: Tue, 7 Feb 2012 13:25:37 -0600 [thread overview]
Message-ID: <4F317AB1.7080208@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1202071221150.22169@gate.crashing.org>
Kumar Gala wrote:
> What code will use this? Once such code exists, have this patch in that
> patch series.
Isn't this patch harmless? I'm not adding any code, and there already are
plenty of fields defined in that struct that aren't used anywhere.
The register is for the PAMU driver, which is nowhere near ready for
upstream anyway. I was hoping to get the this patch in the pipeline ahead
of schedule.
So if you don't mind, I'd like you to consider this patch as-is.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-02-07 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 19:17 [PATCH] powerpc/fsl: add PAMUBYPENR register definition to fsl_guts.h Timur Tabi
2012-02-07 18:21 ` Kumar Gala
2012-02-07 19:25 ` Timur Tabi [this message]
2012-02-08 2:13 ` Question about fsl_pq_mdio_probe and dts file for p1010rdb Bob Cochran
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=4F317AB1.7080208@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).