Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] linux/linux.mk: ensure custom kernel version is set
Date: Mon, 11 Apr 2022 07:08:53 +0300	[thread overview]
Message-ID: <87pmlodzw4.fsf@tarshish> (raw)
In-Reply-To: <877d7wogm1.fsf@dell.be.48ers.dk>

Hi Peter,

On Sun, Apr 10 2022, Peter Korsgaard wrote:
>>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
>
>  > Validate that BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE is set when
>  > required.
>
>  > Fixes:
>  > http://autobuild.buildroot.net/results/117/117c08e414776202446a9fdb96d084aa3c16af48
>
>  > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
>
> Committed to 2022.02.x, thanks.

Not in 2022.02.x as of commit 989c7c8f7b6e ("package/vim: security bump
to version 8.2.4732").

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-11  4:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05  1:20 [Buildroot] [PATCH 1/1] linux/linux.mk: ensure custom kernel version is set James Hilliard
2022-04-10 14:50 ` Arnout Vandecappelle
2022-04-10 19:58 ` Peter Korsgaard
2022-04-11  4:08   ` Baruch Siach via buildroot [this message]
2022-04-11  6:30     ` Peter Korsgaard

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=87pmlodzw4.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=james.hilliard1@gmail.com \
    --cc=peter@korsgaard.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox