public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v2] Remove #undef DEBUG from MPC83xx board header files
Date: Wed, 16 Jan 2008 09:00:48 -0600	[thread overview]
Message-ID: <478E1C20.9080801@freescale.com> (raw)
In-Reply-To: <20080115184351.0ffb9196.kim.phillips@freescale.com>

Kim Phillips wrote:

> ?  Am I missing something?  mpc83xx files aren't special in this area.
> it appears to be a problem for a lot of boards:

I'm a Freescale employee (as are you), and so I'm not going to post a patch that 
makes an untested changed to someone else's boards.  And since 83xx is separate 
from 85xx and 86xx, I have to keep the patches separate, too.


-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-01-16 15:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 23:09 [U-Boot-Users] [PATCH v2] Remove #undef DEBUG from MPC83xx board header files Timur Tabi
2008-01-16  0:43 ` Kim Phillips
2008-01-16 15:00   ` Timur Tabi [this message]
2008-01-16 16:30     ` Kim Phillips
2008-01-16  1:57 ` [U-Boot-Users] [PATCH v2] Remove #undef DEBUG from MPC83xx boardheader files Liu Dave
2008-02-11 23:45 ` [U-Boot-Users] [PATCH v2] Remove #undef DEBUG from MPC83xx board header files 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=478E1C20.9080801@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