From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add support for the MPC8349E-mITX-GP
Date: Mon, 29 Jan 2007 13:32:16 -0600 [thread overview]
Message-ID: <45BE4BC0.5050402@freescale.com> (raw)
In-Reply-To: <2B16AB83-7726-4C84-B48E-254E8FEF734C@kernel.crashing.org>
Kumar Gala wrote:
> Well, I'd suggest trying it again based on the latest ITX defconfing
> and see what happens. If you need to update both defconfigs to make
> them consistent I'm fine with that. Just figured they should be
> insync (except the removed functionality for ITX-GP).
Ok, I'll make new patch that updates the ITX config file and makes an ITX-GP
config file and keeps the diffs to a minimum. I'll submit it when the window
for 2.6.21 opens.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-01-29 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 21:33 [PATCH] Add support for the MPC8349E-mITX-GP Timur Tabi
2007-01-26 6:19 ` Kumar Gala
2007-01-26 15:08 ` Timur Tabi
2007-01-26 15:22 ` Kumar Gala
2007-01-29 16:36 ` Timur Tabi
2007-01-29 16:37 ` Kumar Gala
2007-01-29 19:32 ` Timur Tabi [this message]
2007-01-29 19:55 ` Kumar Gala
2007-01-29 23:15 ` Paul Mackerras
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=45BE4BC0.5050402@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.