All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: Marek Vasut <marex@denx.de>,
	OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>,
	Otavio Salvador <otavio@ossystems.com.br>,
	Otavio Salvador <otavio.salvador@ossystems.com.br>
Subject: Re: [PATCH] u-boot: Upgrade to 2017.07 release (WIP)
Date: Tue, 11 Jul 2017 22:55:45 -0400	[thread overview]
Message-ID: <20170712025545.GE14320@bill-the-cat> (raw)
In-Reply-To: <20170712010947.GH26405@denix.org>

[-- Attachment #1: Type: text/plain, Size: 4435 bytes --]

On Tue, Jul 11, 2017 at 09:09:47PM -0400, Denys Dmytriyenko wrote:
> On Mon, Jul 10, 2017 at 03:12:19PM -0400, Tom Rini wrote:
> > On Mon, Jul 10, 2017 at 12:08:41PM -0700, Khem Raj wrote:
> > > On 7/10/17 12:06 PM, Tom Rini wrote:
> > > > On Mon, Jul 10, 2017 at 09:02:39PM +0200, Marek Vasut wrote:
> > > >> On 07/10/2017 09:01 PM, Tom Rini wrote:
> > > >>> On Mon, Jul 10, 2017 at 08:57:19PM +0200, Marek Vasut wrote:
> > > >>>> On 07/10/2017 08:51 PM, Otavio Salvador wrote:
> > > >>>>> On Mon, Jul 10, 2017 at 3:47 PM, Marek Vasut <marex@denx.de> wrote:
> > > >>>>>> On 07/10/2017 08:36 PM, Otavio Salvador wrote:
> > > >>>>>>> This patch upgrades the U-Boot to the 2017.07 release.
> > > >>>>>>>
> > > >>>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> > > >>>>>>> ---
> > > >>>>>>>
> > > >>>>>>>  .../u-boot/{u-boot-common_2017.05.inc => u-boot-common_2017.07.inc}     | 2 +-
> > > >>>>>>>  .../u-boot/{u-boot-fw-utils_2017.05.bb => u-boot-fw-utils_2017.07.bb}   | 0
> > > >>>>>>>  .../u-boot/{u-boot-mkimage_2017.05.bb => u-boot-mkimage_2017.07.bb}     | 0
> > > >>>>>>>  meta/recipes-bsp/u-boot/{u-boot_2017.05.bb => u-boot_2017.07.bb}        | 0
> > > >>>>>>>  4 files changed, 1 insertion(+), 1 deletion(-)
> > > >>>>>>>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.05.inc => u-boot-common_2017.07.inc} (88%)
> > > >>>>>>>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.05.bb => u-boot-fw-utils_2017.07.bb} (100%)
> > > >>>>>>>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.05.bb => u-boot-mkimage_2017.07.bb} (100%)
> > > >>>>>>>  rename meta/recipes-bsp/u-boot/{u-boot_2017.05.bb => u-boot_2017.07.bb} (100%)
> > > >>>>>>>
> > > >>>>>>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.05.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc
> > > >>>>>>> similarity index 88%
> > > >>>>>>> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.05.inc
> > > >>>>>>> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc
> > > >>>>>>> index 0e52f27df8..f27989daa1 100644
> > > >>>>>>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.05.inc
> > > >>>>>>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc
> > > >>>>>>> @@ -7,7 +7,7 @@ PE = "1"
> > > >>>>>>>
> > > >>>>>>>  # We use the revision in order to avoid having to fetch it from the
> > > >>>>>>>  # repo during parse
> > > >>>>>>> -SRCREV = "64c4ffa9fa223f7ae8640f9c8f3044bfa0e3bfda"
> > > >>>>>>> +SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943"
> > > >>>>>>
> > > >>>>>> Where did you get this hash from, it's not in the U-Boot repo ...
> > > >>>>>
> > > >>>>> From the tag used by Tom. You can check it on his github repository.
> > > >>>>
> > > >>>> I cannot, that is NOT where the U-Boot recipe points to nor is it in any
> > > >>>> way an official U-Boot source git tree .
> > > >>>
> > > >>> It's also on the official github mirror.  I'll go see why the DENX git
> > > >>> is lagging behind.
> > > >>
> > > >> Hm that's weird. How can it be a mirror if it contains objects not in
> > > >> the mirrored repo ? ;-)
> > > > 
> > > > git supports multiple push URIs.  So I update all 3 locations with a
> > > > single push.  However, git.denx.de works differently than github.com
> > > > does.
> > > 
> > > may be pushing to upstream and then pulling before populating the
> > > mirrors could solve such issues. but I think we should use github.com
> > > in OE src_uri's for speed reasons.
> > 
> > On the back end, things are a bit more complex than that, but I'm
> > working to resolve the current error now.  FWIW, changing the OE recipe
> > to fetch from https://github.com/u-boot/u-boot.git would be fine with
> > me, it's owned by myself, Wolfgang and the person that helped us out and
> > got that project created to start with, so it will only have official
> > changes in it.
> 
> FWIW, I'd be against such change, as long as denx.de remains the official 
> home of U-boot. We don't pull kernel from https://github.com/torvalds/linux

No, but you do pull it from ${KERNELORG_MIRROR}.  At the end of the day,
I don't have a preference either way.  git.denx.de is the official home,
github has an official mirror.  We've actually put in some time making
sure that git.denx.de is in-sync and up to date (this recent issue was
that incrond has an inode leak).  It should be considered a reliable
source.

-- 
Tom

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2017-07-12  2:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 18:36 [PATCH] u-boot: Upgrade to 2017.07 release (WIP) Otavio Salvador
2017-07-10 18:47 ` Marek Vasut
2017-07-10 18:51   ` Otavio Salvador
2017-07-10 18:57     ` Marek Vasut
2017-07-10 19:01       ` Tom Rini
2017-07-10 19:02         ` Marek Vasut
2017-07-10 19:04           ` Marek Vasut
2017-07-10 19:06           ` Tom Rini
2017-07-10 19:07             ` Marek Vasut
2017-07-10 19:08             ` Khem Raj
2017-07-10 19:11               ` Marek Vasut
2017-07-10 19:14                 ` Otavio Salvador
2017-07-10 19:12               ` Tom Rini
2017-07-12  1:09                 ` Denys Dmytriyenko
2017-07-12  2:55                   ` Tom Rini [this message]
2017-07-10 19:14   ` Denys Dmytriyenko
2017-07-10 19:51 ` Tom Rini

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=20170712025545.GE14320@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=denis@denix.org \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    /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.