public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Moessbauer, Felix" <felix.moessbauer@siemens.com>,
	Baurzhan Ismagulov <ibr@radix50.net>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "henning.schild@siemens.com" <henning.schild@siemens.com>
Subject: Re: [PATCH 1/2] feat: package linux-perf-<version> in kernel recipe
Date: Thu, 18 Feb 2021 09:28:18 +0100	[thread overview]
Message-ID: <d131d63e-d626-34a8-64cc-1461c45d8cf2@siemens.com> (raw)
In-Reply-To: <DB7PR10MB1948E29D30D91C4A5F8649F589859@DB7PR10MB1948.EURPRD10.PROD.OUTLOOK.COM>

On 18.02.21 09:01, [ext] Moessbauer, Felix wrote:
> Hi Baurzhan,
> 
> Thanks for the review.
> I'll change that in the next version.
> 
> In the meantime, I discovered that there are still a couple of things missing for Debian bullseye.
> They added version bindings between linux-perf and linux-perf-<version>, so we have to build the linux-perf package as well.
> I'll do that in v2 as well.
> 
> Apart from that: IMO doing the debianization of the kernel tools (also kselftest) in the kernel recipe is way better than having it in a dedicated recipe.
> Using this approach, it is also possible to use an upstream kernel, but our perf package.
> Technically, we then have to fetch and build the whole kernel manually, but only the perf packages are installed.
> That's a bit of extra work (which could be avoided if we check inside the kernel recipe which target is attracted. Don't know if that's possible).

I don't thing you can explore that during the build. But you could add
some control variables to the kernel recipe that will decide which
packages are going to be built out of it.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-02-18  8:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 12:41 [PATCH 0/1] RFC: Package perf from linux kernel tools Felix Moessbauer
2021-01-19 12:41 ` [PATCH 1/1] " Felix Moessbauer
2021-01-19 16:31   ` Baurzhan Ismagulov
2021-01-20 15:23     ` Moessbauer, Felix
2021-01-20 15:26       ` Henning Schild
2021-01-21 10:52       ` [PATCH v2 0/2] " Felix Moessbauer
2021-01-21 11:56         ` Jan Kiszka
2021-01-21 15:00           ` Moessbauer, Felix
2021-01-21 16:35             ` Jan Kiszka
2021-02-09  8:58         ` Anton Mikanovich
2021-02-17 10:18         ` Baurzhan Ismagulov
2021-01-21 10:52       ` [PATCH 1/2] feat: package linux-perf-<version> in kernel recipe Felix Moessbauer
2021-02-17 10:28         ` Baurzhan Ismagulov
2021-02-18  8:01           ` Moessbauer, Felix
2021-02-18  8:28             ` Jan Kiszka [this message]
2021-04-22  9:52             ` Anton Mikanovich
2021-04-27  9:24               ` [RFC v2 0/2] " Felix Moessbauer
2021-04-27  9:24               ` [PATCH v2 1/2] RFC: Package perf from linux kernel tools Felix Moessbauer
2021-04-27  9:24               ` [PATCH v2 2/2] Add wrapper to load correct python perf module based on kernel Felix Moessbauer
2021-01-21 10:52       ` [PATCH 2/2] feat: add and package python bindings for perf Felix Moessbauer
2021-01-20 11:12 ` [PATCH 0/1] RFC: Package perf from linux kernel tools Henning Schild
2021-01-20 11:21 ` Henning Schild

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=d131d63e-d626-34a8-64cc-1461c45d8cf2@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=ibr@radix50.net \
    --cc=isar-users@googlegroups.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