From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH RFC OSSTEST v1 07/12] ts-debian-di-install: Allow Di Version to come from runvars
Date: Fri, 15 Jan 2016 16:33:13 +0000 [thread overview]
Message-ID: <1452875593.6020.72.camel@citrix.com> (raw)
In-Reply-To: <22165.4153.654237.414038@mariner.uk.xensource.com>
On Tue, 2016-01-12 at 14:39 +0000, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH RFC OSSTEST v1 07/12] ts-debian-di-install:
> Allow Di Version to come from runvars"):
> > and following the lead of the suite arrange for a version selected
> > from the defaults to be written back to the runvars.
> ...
> > - debian_guest_suite
> > + debian_guest_suite debian_guest_diversion
>
> Can we please call this function, ..._di_version ? Otherwise it sounds
> very much like something is being diverted.
>
> > +sub debian_guest_diversion ($) {
> > + my ($gho) = @_;
> > +
> > + $gho->{DiVersion} //= guest_var($gho,'diversion',undef);
> > +
> > + if (!$gho->{DiVersion}) {
> > + $gho->{DiVersion} = $c{TftpDiVersion};
> > + store_runvar("$gho->{Guest}_diversion", $gho->{DiVersion});
>
> I'm not sure what we should do about the runvar. `diversion' is a bad
> name but there is a risk with `..._di_version' getting confused with
> all the `..._revision' fields.
>
> OTOH
>
> osstestdb=> select distinct name from runvars where name like '%version';
> name
> ----------------------
> device_model_version
> (1 row)
>
> osstestdb=>
>
> So maybe guest_di_version would be the right answer.
Yes, I think so too, I'll go with that.
> Aside from the questions about this name, this patch LGTM.
>
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-15 16:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 14:29 [PATCH RFC OSSTEST v1 00/12] Specify host and guest os version in runvars Ian Campbell
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 01/12] Debian: Abolish $suite and $xopts{Suite} from preseed_* interfaces Ian Campbell
2016-01-08 15:08 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 02/12] target_var: Support fallback to all_(guest|host)_$vn Ian Campbell
2016-01-08 15:10 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 03/12] mfi-common: Rename $suite_runvars as $hostos_runvars Ian Campbell
2016-01-08 15:10 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 04/12] mfi-common: always add host suite to hostos_runvars Ian Campbell
2016-01-12 11:27 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 05/12] make-*flight: Abolish $defsuite and $guestdefsuite Ian Campbell
2016-01-12 14:18 ` Ian Jackson
2016-01-15 17:15 ` Ian Campbell
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 06/12] ts-host-install: Support DiVersion coming from runvars Ian Campbell
2016-01-12 14:19 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 07/12] ts-debian-di-install: Allow Di Version to come " Ian Campbell
2016-01-12 14:39 ` Ian Jackson
2016-01-15 16:33 ` Ian Campbell [this message]
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 08/12] make-flight: Set diversion runvar on d-i based test jobs Ian Campbell
2016-01-12 14:42 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 09/12] mfi-common: Set diversion for build & test host install Ian Campbell
2016-01-12 14:41 ` Ian Jackson
2016-01-15 17:36 ` Ian Campbell
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 10/12] Qualify TftpDiVersion with the suite Ian Campbell
2016-01-12 15:19 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 11/12] mfi-common: usual_debianhvm_image: derive version from $guestsuite Ian Campbell
2016-01-12 15:21 ` Ian Jackson
2016-01-08 14:29 ` [PATCH RFC OSSTEST v1 12/12] make-flight: Use older Debian for host and guest OS with older Xen Ian Campbell
2016-01-12 15:22 ` Ian Jackson
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=1452875593.6020.72.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).