From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Stein <alexander.stein@systec-electronic.com>
Subject: Re: [ptxdist] search path order for patch series
Date: Wed, 10 Feb 2016 09:32:37 +0100 [thread overview]
Message-ID: <201602100932.37276.jbe@pengutronix.de> (raw)
In-Reply-To: <1878376.0s4r4KxYn6@ws-stein>
Hi Alexander,
On Tuesday 09 February 2016 16:29:06 Alexander Stein wrote:
> in a project I have to add a platform which requirs a slightly different
> (kernel) patch set than current one. Up to now my patches are located in
> PTXDIST_WORKSPACE/patches/linux-x.y.z which works great. I tried to use a
> series.PLATFORMSUFFIX which didn't work. After reading
>
http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf
> I noticed that section 4.1.2 and 4.2.4 names different search orders. While I
> prefere the one from 4.1.2 (PTXDIST_PLATFORMCONFIGDIR/patches/linux-x.y.z
> before PTXDIST_WORKSPACE/patches/linux-x.y.z) it seems that ptxdist actually
> uses the one from 4.2.4 PTXDIST_WORKSPACE/patches/linux-x.y.z before
> PTXDIST_PLATFORMCONFIGDIR/patches/linux-x.y.z. Which one was intended?
A single platform can be used in different BSPs, and a BSP describes a specific
application which might need special adaptions to the platform to make it
work.
So, the BSP itself (e.g. "PTXDIST_WORKSPACE") has always the highest priority.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-02-10 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 15:29 Alexander Stein
2016-02-10 8:32 ` Juergen Borleis [this message]
2016-02-10 9:08 ` Alexander Stein
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=201602100932.37276.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=alexander.stein@systec-electronic.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