From: David Brownell <david-b@pacbell.net>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net,
akpm@linux-foundation.org
Subject: Re: [PATCH 6/9] mpc52xx_psc_spi: remove code associated with !CONFIG_PPC_MERGE
Date: Wed, 15 Oct 2008 14:34:33 -0700 [thread overview]
Message-ID: <200810151434.33693.david-b@pacbell.net> (raw)
In-Reply-To: <764B32F3-E12E-4649-A2BB-3F94044D371F@kernel.crashing.org>
On Wednesday 15 October 2008, Kumar Gala wrote:
>
> On Aug 20, 2008, at 11:46 PM, Kumar Gala wrote:
>
> > Now that arch/ppc is gone we don't need CONFIG_PPC_MERGE anymore
> > remove the dead code associated with !CONFIG_PPC_MERGE.
> >
> > Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> > ---
> > drivers/spi/mpc52xx_psc_spi.c | 55
> > -----------------------------------------
> > 1 files changed, 0 insertions(+), 55 deletions(-)
>
> Any update on acceptance of this patch?
Still seems to be in the MM queue ready to merge
a bit later in the window.
- Dave
prev parent reply other threads:[~2008-10-15 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1219294018-12557-1-git-send-email-galak@kernel.crashing.org>
[not found] ` <1219294018-12557-2-git-send-email-galak@kernel.crashing.org>
[not found] ` <1219294018-12557-3-git-send-email-galak@kernel.crashing.org>
[not found] ` <1219294018-12557-4-git-send-email-galak@kernel.crashing.org>
[not found] ` <1219294018-12557-5-git-send-email-galak@kernel.crashing.org>
[not found] ` <1219294018-12557-6-git-send-email-galak@kernel.crashing.org>
2008-08-21 4:46 ` [PATCH 6/9] mpc52xx_psc_spi: remove code associated with !CONFIG_PPC_MERGE Kumar Gala
[not found] ` <1219294018-12557-7-git-send-email-galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2008-10-15 21:23 ` Kumar Gala
2008-10-15 21:34 ` David Brownell [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=200810151434.33693.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).