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 1/1] Fix 8313ERDB board configuration
Date: Thu, 15 May 2008 18:10:05 -0500	[thread overview]
Message-ID: <482CC2CD.4090607@freescale.com> (raw)
In-Reply-To: <20080515230637.E66552487F@gemini.denx.de>

Wolfgang Denk wrote:
> In message <482CBCA4.2050009@freescale.com> you wrote:
>> Fair enough, but the changes that are in York's patch have been tested.
>> Considering that the fix window for 1.3.3 is closing fast, we don't have the
>> bandwidth for additional testing of the additional and unrelated changes that
>> are being requested.
> 
> What exactly is the risk?

Probably not much, but that isn't my point.  I find it really annoying when
someone posts a patch to fix a specific bug, and the reply is "why don't you fix
this other bug too, while you're at it?"

Right now, the 8313ERDB will generate a machine check if you boot it with the
top-of-tree kernel.  This patch fixes that.  For 1.3.4, if you like, we can
submit a patch that removes all MAC and IP address macros from all 83xx boards.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-05-15 23:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 20:26 [U-Boot-Users] [PATCH 1/1] Fix 8313ERDB board configuration York Sun
2008-05-15 20:50 ` Ben Warren
2008-05-15 21:21   ` York Sun
2008-05-15 22:11     ` Ben Warren
2008-05-15 22:22     ` Wolfgang Denk
2008-05-15 22:26       ` Timur Tabi
2008-05-15 22:41         ` Wolfgang Denk
2008-05-15 22:43           ` Timur Tabi
2008-05-15 23:06             ` Wolfgang Denk
2008-05-15 23:10               ` Timur Tabi [this message]
2008-05-16  0:25                 ` Ben Warren
2008-05-19 21:01                   ` Wolfgang Denk
2008-05-19 21:04 ` 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=482CC2CD.4090607@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