From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-custom: Allow for config fragments in subdirs
Date: Wed, 25 Oct 2023 09:42:40 +0300 [thread overview]
Message-ID: <6e6668ab9849dac171587086399ac6769581181e.camel@ilbers.de> (raw)
In-Reply-To: <56795cac-eab1-4bba-93c2-2dd404a59638@siemens.com>
On Wed, 2023-10-18 at 15:47 +0200, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Might be useful in same cases, and while fetching and processing
> already
> worked, copying didn't take subdirs into account.
>
> Adjust the linux-mainline recipe to have a test case for this.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> .../linux/files/{ => subdir}/no-ubifs-fs.cfg | 0
> meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb | 2 +-
> meta/recipes-kernel/linux/linux-custom.inc | 9 +++++--
> --
> 3 files changed, 6 insertions(+), 5 deletions(-)
> rename meta-isar/recipes-kernel/linux/files/{ => subdir}/no-ubifs-
> fs.cfg (100%)
>
Applied to next, thanks.
prev parent reply other threads:[~2023-10-25 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 13:47 Jan Kiszka
2023-10-25 6:42 ` Uladzimir Bely [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=6e6668ab9849dac171587086399ac6769581181e.camel@ilbers.de \
--to=ubely@ilbers.de \
--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