All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Merge fixes/clean up outside merge window? was: Re: [PATCH] lib_arm: do_bootm_linux() - correct a small mistake
Date: Thu, 20 Nov 2008 17:52:05 +0100	[thread overview]
Message-ID: <492595B5.3050505@googlemail.com> (raw)
In-Reply-To: <20081114172449.GE9542@game.jcrosoft.org>

Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 15:53 Sun 09 Nov     , Ilko Iliev wrote:
> 
>>This patch corrects a small bug in the "if" condition: 
>>the parameter "flag" is 0 and the "if" condition is always true.
>>The result is - the boom command doesn't start the kernel.
>>Affected targets: all arm based.
>>
>>
>>Signed-off-by: Ilko Iliev <iliev@ronetix.at>
>>---
>> lib_arm/bootm.c |    2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
> 
> Applied to u-boot-arm/master and u-boot-arm/omap3

Is there any special reason why no git pull request for mainline for 
this is sent? Isn't this an important fix which should go into 
mainline even if merge window is not open?

Dirk

And btw: What's about merging clean up patches like

http://lists.denx.de/pipermail/u-boot/2008-November/043220.html

now (outside merge window) into mainline via e.g. u-boot-arm/master? 
Having this merged now, I could rebase OMAP3 patch against this and 
mainline would be ready when merge window opens.

  reply	other threads:[~2008-11-20 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 14:53 [U-Boot] [PATCH] lib_arm: do_bootm_linux() - correct a small mistake Ilko Iliev
2008-11-14 17:24 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-20 16:52   ` Dirk Behme [this message]
2008-11-20 19:08     ` [U-Boot] Merge fixes/clean up outside merge window? was: " 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=492595B5.3050505@googlemail.com \
    --to=dirk.behme@googlemail.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.