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,
	Phillips Kim-R1AAHA <Kim.Phillips@freescale.com>
Subject: Re: [PATCH][POWERPC] QE: Make QUICC Engine support a configurableoption
Date: Fri, 16 Mar 2007 15:16:18 -0500	[thread overview]
Message-ID: <45FAFB12.70306@freescale.com> (raw)
In-Reply-To: <03ECE1F6-5048-44FA-86FD-A42C954E4071@kernel.crashing.org>

Kumar Gala wrote:

>> The patch works, but I was wondering if you could move the QE Options 
>> (i.e. fast and/or slow UCC support) to this same menu?  Right now, 
>> that menu appears on the top level. Instead, it should just appear on 
>> the Platform menu under "QUICC Engine Support".
> 
> This will get fixed up as part of my larger arch/powerpc/Kconfig cleanup

Actually, I forgot that my UCC fast/slow Kconfig patch makes the QE Options menu go away 
completely.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-03-16 20:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 18:15 [PATCH][POWERPC] QE: Make QUICC Engine support a configurable option Kumar Gala
2007-03-14 18:37 ` Kim Phillips
2007-03-14 19:36   ` Timur Tabi
2007-03-15  3:02     ` [PATCH][POWERPC] QE: Make QUICC Engine support a configurableoption Li Yang-r58472
2007-03-15  3:49       ` Kumar Gala
2007-03-15  5:39         ` Li Yang-r58472
2007-03-15  5:40           ` Kumar Gala
2007-03-15  6:29             ` Li Yang-r58472
2007-03-15 13:04               ` Timur Tabi
2007-03-15 15:07                 ` Kumar Gala
2007-03-15 16:47                   ` Scott Wood
2007-03-15 16:51                     ` Timur Tabi
2007-03-16 19:21                   ` Timur Tabi
2007-03-16 19:44                     ` Kumar Gala
2007-03-16 20:16                       ` Timur Tabi [this message]
2007-03-16 19:47                   ` 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=45FAFB12.70306@freescale.com \
    --to=timur@freescale.com \
    --cc=Kim.Phillips@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).