All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] u-boot: Update to v2016.11 release
Date: Fri, 18 Nov 2016 21:30:52 +0100	[thread overview]
Message-ID: <96a66f71-61e3-6386-c463-6f7df9c60d43@denx.de> (raw)
In-Reply-To: <20161118194439.GF26131@denix.org>

On 11/18/2016 08:44 PM, Denys Dmytriyenko wrote:
> On Fri, Nov 18, 2016 at 08:29:55PM +0100, Marek Vasut wrote:
>> Upgrade U-Boot to the latest version.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
>> Cc: Denys Dmytriyenko <denis@denix.org>
> 
> Acked-by: Denys Dmytriyenko <denys@ti.com>
> 
> 
>> Cc: Ross Burton <ross.burton@intel.com>
>> ---
>>
>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc b/meta/recipes-bsp/u-boot/u-boot-common_2016.11.inc
>> similarity index 71%
>> rename from meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc
>> rename to meta/recipes-bsp/u-boot/u-boot-common_2016.11.inc
>> index f706a6b..84adc1c 100644
>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc
>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2016.11.inc
>> @@ -7,8 +7,8 @@ PE = "1"
>>  
>>  # We use the revision in order to avoid having to fetch it from the
>>  # repo during parse
>> -SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9"
>> +SRCREV = "29e0cfb4f77f7aa369136302cee14a91e22dca71"
>>  
>> -SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y"
>> +SRC_URI = "git://git.denx.de/u-boot.git"
> 
> Will it branch off into own branch eventually?Does master ever get 
> re-written? I guess as long as this commit always stays in master, it should 
> be fine.

Master never gets rewritten and the commit is always in master, unless
we screw something up bad and need to make a fixup release (which
happens almost never :-)), in which case that goes into separate branch.

-- 
Best regards,
Marek Vasut


  reply	other threads:[~2016-11-18 20:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 19:29 [PATCH] u-boot: Update to v2016.11 release Marek Vasut
2016-11-18 19:44 ` Denys Dmytriyenko
2016-11-18 20:30   ` Marek Vasut [this message]
2016-11-18 20:24 ` Tom Rini
2016-11-28  2:42   ` Marek Vasut
2016-12-05 15:45 ` Bill Randle
2016-12-05 16:19 ` Burton, Ross
2016-12-05 16:24   ` Marek Vasut

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=96a66f71-61e3-6386-c463-6f7df9c60d43@denx.de \
    --to=marex@denx.de \
    --cc=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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.