From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] rauc: Make rauc bundle version configurable
Date: Mon, 10 Sep 2018 13:45:14 +0200 [thread overview]
Message-ID: <20180910114514.22s35ibmjoysjgpx@pengutronix.de> (raw)
In-Reply-To: <b486deaa0b9d8ed5be0ff1ddf159d88014e9925a.camel@eckelmann.de>
On Mon, Sep 10, 2018 at 11:32:04AM +0000, Schenk, Gavin wrote:
> Hi,
>
> > In my usecase I need PTXCONF_PROJECT_VERSION in the rauc bundle instead
> > of PTXDIST_BSP_AUTOVERSION that is hard coded in rules/image-rauc.make.
> >
> > Introduce a new switch RAUC_BUNDLE_VERSION to menuconfig that defaults
> > to "${PTXDIST_BSP_AUTOVERSION}".
> >
> > Signed-off-by: Gavin Schenk <g.schenk@eckelmann.de>
> > ---
> > Hi,
> >
> > Some time ago we discussed to hardcode PTXCONF_PROJECT_VERSION instead of
> > PTXDIST_BSP_AUTOVERSION in the makefile. There was a reason not to change
> > this, but I do not remember exactly ( Something with a "-" that is mandatory ).
> > Now this patch is my new approach. It is full compatible and solves my usecase.
> >
> > Would you agree to put it into rules/rauc.in, or is
> > platforms/image-rauc.in the better place?
> >
> > Please suggest!
> >
> Ping
Sorry, this got lost here.
The option should be in platforms/image-rauc.in. Can you send a new version?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-09-10 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 12:31 Gavin Schenk
2018-09-10 11:32 ` Schenk, Gavin
2018-09-10 11:45 ` Michael Olbrich [this message]
2018-09-13 5:43 ` Schenk, Gavin
2018-09-17 7:40 ` Michael Olbrich
2018-09-17 10:35 ` <Gavin Schenk>
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=20180910114514.22s35ibmjoysjgpx@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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