All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add support for building toolchains against custom kernel headers.
Date: Tue, 21 Aug 2018 15:36:55 +0200	[thread overview]
Message-ID: <20180821133655.GN15347@scaer> (raw)
In-Reply-To: <da2cf4b2-2fdf-943e-3a7f-2cd6e89f0920@embecosm.com>

Mark, All,

On 2018-08-21 14:28 +0100, Mark Corbin spake thusly:
> On 21/08/18 14:11, Yann E. MORIN wrote:
> > No, I'd prefer if we were to actualyl add a .hash file for linux-headers
> > and for linux as well, btw, with the former being a symlink to the
> > latter.
> >
> > So, when you respin, prepare a series that:
> >
> >  1. adds the help text alone,
> >  2. adds a .hash for linux and a symlink to it from linux-headers
> Does this need populating with just the hashes for the current 'default'
> versions, i.e. 4.17.17, 4.16.18, 4.15.18, 4.14.65,...etc. or all
> possible versions (!!!) from kernel.org?

We indeed only want the ones we explicitly refer to from Config.in.

> I presume that custom versions will remain exempt via
> 'BR_NO_CHECK_HASH_FOR' as originally intended?

Exactly, yes.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-08-21 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 11:06 [Buildroot] [PATCH 1/1] Add support for building toolchains against custom kernel headers Mark Corbin
2018-08-21 12:05 ` Thomas Petazzoni
2018-08-21 12:51   ` Mark Corbin
2018-08-21 13:11     ` Yann E. MORIN
2018-08-21 13:28       ` Mark Corbin
2018-08-21 13:36         ` Yann E. MORIN [this message]
2018-08-21 20:01       ` Arnout Vandecappelle

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=20180821133655.GN15347@scaer \
    --to=yann.morin.1998@free.fr \
    --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.