From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/3] board: Add Vyasa RK388 board support
Date: Wed, 29 Nov 2017 09:20:47 +0100 [thread overview]
Message-ID: <20171129092047.33e30f9c@windsurf.home> (raw)
In-Reply-To: <CAMty3ZBNPnaDxCN+0fmB_VLbNXxovXSyE618LB_5KA7kXt74Lw@mail.gmail.com>
Hello,
On Wed, 29 Nov 2017 12:37:05 +0530, Jagan Teki wrote:
> > Using linux-next doesn't work, as it gets rebased constantly. The
> > commit 7e8a1fd62911a59f1f95d4620e89603230fdd6f9 no longer exists. You
> > have to wait for the support for this board to land into the mainline
> > kernel, or point to a vendor-specific Git tree.
>
> Can't we use linux-next at all? you are with head commits which were
> always changes during rebase, but I've used the board specific commit
> in v5 and that will always unchanged.
No, you can't use linux-next, as commits are not stable.
Please try yourself: wait a few days, delete your Buildroot download
folder entirely, and try to build your defconfig: it will fail, because
the git commit no longer exists on the linux-next Git repository.
If the commit still exists, then it means that it's a commit that is
part of Linus tree, in which case there is no point in using linux-next.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-29 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 9:28 [Buildroot] [PATCH v4 1/3] uboot: Use BR2_TARGET_UBOOT_SPL_NAME for TPL name Jagan Teki
2017-11-18 9:28 ` [Buildroot] [PATCH v4 2/3] board: Add Vyasa RK388 board support Jagan Teki
2017-11-22 18:02 ` Jagan Teki
2017-11-23 21:43 ` Thomas Petazzoni
2017-11-29 7:07 ` Jagan Teki
2017-11-29 8:20 ` Thomas Petazzoni [this message]
2017-11-18 9:28 ` [Buildroot] [PATCH v4 3/3] board: Add Tinker " Jagan Teki
2017-11-23 21:45 ` Thomas Petazzoni
2017-11-23 21:40 ` [Buildroot] [PATCH v4 1/3] uboot: Use BR2_TARGET_UBOOT_SPL_NAME for TPL name Thomas Petazzoni
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=20171129092047.33e30f9c@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.