public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] build-kernel.sh: handle kernel configs with CONFIG_LOCALVERSION
Date: Fri, 11 May 2018 18:33:38 +0300	[thread overview]
Message-ID: <aaf5e0c5-33ff-b9b0-d66c-3d2ecdfc0188@ilbers.de> (raw)
In-Reply-To: <20180420123921.1927-1-henning.schild@siemens.com>

On 04/20/2018 03:39 PM, Henning Schild wrote:
> Setting this option in your kernel config will result in filenames that
> build-kernel.sh does not expect. To not introduce confusion between
> recipe versions and debian package versions simply require the recipe to
> have a PV matching "make kernelrelease".
> 

Applied to next, thanks!

Alex

      reply	other threads:[~2018-05-11 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 12:39 Henning Schild
2018-05-11 15:33 ` Alexander Smirnov [this message]

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=aaf5e0c5-33ff-b9b0-d66c-3d2ecdfc0188@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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