From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Define upmconfig() for 834x systems
Date: Fri, 08 Sep 2006 17:50:12 -0500 [thread overview]
Message-ID: <4501F3A4.3060108@freescale.com> (raw)
In-Reply-To: <20060908223226.79375353AD0@atlas.denx.de>
Wolfgang Denk wrote:
> If you intend to use this with any future patches, then please submit
> your patches in an order that makes some sense.
Well, I have a dilemma then.
This upmconfig() patch is generic for all 834x systems. It may not be currently used by the 8349EMDS, but it will be used by the upcoming 8349EMITX patch I'm working on. Without the new upmconfig(), the ITX code won't compile. And yet, the patch is not specific to the ITX.
That's why I sent it out today.
So you're saying I should send it out as part of my ITX patch, even though it's not ITX-specific?
> Also, please follow the Coding Style requirements (trailing white
> space).
Sorry, I keep thinking I've covered everything in the coding style, but something always slips through.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2006-09-08 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 21:47 [U-Boot-Users] [PATCH] Define upmconfig() for 834x systems timur at freescale.com
2006-09-08 22:32 ` Wolfgang Denk
2006-09-08 22:50 ` Timur Tabi [this message]
2006-09-08 23:05 ` Wolfgang Denk
2006-09-11 17:37 ` Ben Warren
2006-09-11 17:53 ` Timur Tabi
2006-09-11 18:52 ` Wolfgang Denk
2006-09-11 18:52 ` [U-Boot-Users] 86xx patches? (was [PATCH] Define upmconfig() for 834x systems) Jon Loeliger
2006-09-11 18:46 ` [U-Boot-Users] [PATCH] Define upmconfig() for 834x systems Wolfgang Denk
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=4501F3A4.3060108@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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