All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew McClintock <msm@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix possible uninitialized variable	compiler warning.
Date: Wed, 11 Oct 2006 13:22:19 -0500	[thread overview]
Message-ID: <1160590939.5466.14.camel@localhost> (raw)
In-Reply-To: <20061010085845.433C6353A15@atlas.denx.de>

On Tue, 2006-10-10 at 10:58 +0200, Wolfgang Denk wrote:
> But on the other hand, I think it makes no sense if we start posting
> patches here that are against N private repositories somewhere else. 

The set of patches which this applies to has been submitted several
months ago, I think a follow up patch regarding a problem should be
submitted to the list for all to see.

Is that not acceptable?

-Matthew

  parent reply	other threads:[~2006-10-11 18:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  6:23 [U-Boot-Users] [PATCH] Fix possible uninitialized variable compiler warning Grant Likely
2006-10-10  7:05 ` Wolfgang Denk
2006-10-10  7:13   ` Grant Likely
2006-10-10  8:58     ` Wolfgang Denk
2006-10-11  6:09       ` Grant Likely
2006-10-11  7:44         ` Wolfgang Denk
2006-10-11 15:30           ` Grant Likely
2006-10-11 17:14             ` Haavard Skinnemoen
2006-10-11 20:10             ` Wolfgang Denk
2006-10-12 19:08               ` Grant Likely
2006-10-12 20:26                 ` Wolfgang Denk
2006-10-12 20:51                   ` Grant Likely
2006-10-13  0:13                     ` Wolfgang Denk
2006-10-11 18:22       ` Matthew McClintock [this message]
2006-10-11 18:29         ` Grant Likely
2006-10-11 20:34         ` Wolfgang Denk
2006-10-11 21:02 ` Matthew McClintock
2006-10-11 21:55   ` Wolfgang Denk
2006-10-11 22:04   ` Wolfgang Denk
2006-10-12  6:27     ` Matthew McClintock
2006-10-12  9:16       ` Markus Klotzbücher

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=1160590939.5466.14.camel@localhost \
    --to=msm@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 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.