From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Patch series for package per project?
Date: Thu, 3 Mar 2022 14:40:28 +0100 [thread overview]
Message-ID: <20220303134028.GN12709@pengutronix.de> (raw)
In-Reply-To: <dae3d3de-92b8-6c47-57ea-8aa9506a8ac6@t2data.com>
Hi,
On Thu, Mar 03, 2022 at 10:17:07AM +0100, Christian Melki wrote:
> I want to use the same bootloader (barebox) for various projects.
> But patches are slightly different. series.<project> doesn't seem to work.
> Have I missed something? I just assumed that per project patch series for
> packages would be possible.
> I can see that kernel can steer the use of series file name, but how does
> that work for other packages?
>
> I can also see that there is search for various directory paths, but nothing
> regarding series.<project>?
>
> It would be nice if I could use the same steering analogy as _alternative.
I'm not sure what you mean. Do you have multiple barebox packages in the
same BSP? Or something else?
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2022-03-03 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 9:17 Christian Melki
2022-03-03 13:40 ` Michael Olbrich [this message]
2022-03-03 14:22 ` Christian Melki
2022-03-03 17:07 ` Felix Mellmann
2022-03-03 19:37 ` Christian Melki
2022-03-03 20:11 ` Alexander Dahl
2022-03-03 20:35 ` Alexander Dahl
2022-03-04 8:10 ` Michael Olbrich
2022-03-04 8:24 ` Christian Melki
2022-03-04 15:16 ` Christian Melki
2022-03-04 15:34 ` Michael Olbrich
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=20220303134028.GN12709@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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