From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Patch series for package per project?
Date: Thu, 3 Mar 2022 20:37:45 +0100 [thread overview]
Message-ID: <00ae8995-135e-dc67-737e-4c7d6ec3e08a@t2data.com> (raw)
In-Reply-To: <9e421142-d037-6b62-79c4-2a7a9a09d120@benfm.de>
On 3/3/22 18:07, Felix Mellmann wrote:
> On 03.03.22 15:22, Christian Melki wrote:
>>
>>
>> On 3/3/22 2:40 PM, Michael Olbrich wrote:
>>> 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?
>>>
>>
>> Just one barebox version, but for different archs, with different
>> patchsets. I'd like the patches to live in the same place as they've
>> always done, i.e. under patches/package/...
>> But patches/package/series.$platform or similar does not seem to work?
>>
> Would it be an option to put the patches below each of the platformdirs?
>
> I ran into a similiar situation when starting to migrate to a different
> CPU platform. After a couple of years putting serveral "platformconfig"
> files within the same directory as "ptxconfig" I'm now using separate
> subdirs for each platform where separate sets of platform dependent
> patches are lying.
>
> Felix
>
Hi Felix.
Thanks for the suggestion.
Ideally not. It irks me a bit that patches have to go to a different
place because they belong to another platform than the "default". Or
that they have to go somewhere else altogether because they need to be
split into platforms.
It doesn't make much sense to me.
Regards,
Christian
>> Christian
>>
>>> Michael
>>>
>>
>> _______________________________________________
>> ptxdist mailing list
>> ptxdist@pengutronix.de
>> To unsubscribe, send a mail with subject "unsubscribe" to
>> ptxdist-request@pengutronix.de
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
_______________________________________________
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 19:39 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
2022-03-03 14:22 ` Christian Melki
2022-03-03 17:07 ` Felix Mellmann
2022-03-03 19:37 ` Christian Melki [this message]
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=00ae8995-135e-dc67-737e-4c7d6ec3e08a@t2data.com \
--to=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