|
[meta-selinux][PATCH 02/16] selinux: upgrade inc files to 3.0 (20191204)
Yi Zhao
Signed-off-by: Yi Zhao <yi.zhao@...>
--- .../selinux/{selinux_20190315.inc => selinux_20191204.inc} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename recipes-security/selinux/{selinux_20190315.inc => selinux_20191204.inc} (90%) diff --git a/recipes-security/selinux/selinux_20190315.inc b/recipes-security/selinux/selinux_20191204.inc similarity index 90% rename from recipes-security/selinux/selinux_20190315.inc rename to recipes-security/selinux/selinux_20191204.inc index e79dd54..113fc30 100644 --- a/recipes-security/selinux/selinux_20190315.inc +++ b/recipes-security/selinux/selinux_20191204.inc @@ -1,4 +1,4 @@ -SELINUX_RELEASE = "20190315" +SELINUX_RELEASE = "20191204" SRC_URI = "https://github.com/SELinuxProject/selinux/releases/download/${SELINUX_RELEASE}/${BPN}-${PV}.tar.gz" -- 2.17.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [meta-intel][PATCH] conf:machine: Use weak reference for SERIAL_CONSOLES variable
Anuj Mittal
On Tue, 2020-04-14 at 08:25 +0200, Marek Belisko wrote:
This add possibility to override in custom layer.I think having just this would make this statement not do anything as these machine files includes x86-base.inc which also sets this variable using a ?=. This would probably also need a ??= in x86-base.inc. Thanks, Anuj APPEND += "rootwait console=ttyS0,115200 console=ttyPCH0,115200
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: meta-intel: Override SERIAL_CONSOLES variable
Marek Belisko
On Sat, Apr 11, 2020 at 8:09 AM Anuj Mittal <anuj.mittal@...> wrote:
Done: https://lists.yoctoproject.org/g/yocto/message/49131 BR, marek
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-intel][PATCH] conf:machine: Use weak reference for SERIAL_CONSOLES variable
Marek Belisko
This add possibility to override in custom layer.
Signed-off-by: Marek Belisko <marek.belisko@...> --- conf/machine/intel-core2-32.conf | 2 +- conf/machine/intel-corei7-64.conf | 2 +- conf/machine/intel-skylake-64.conf | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-core2-32.conf index 20c9872..384ad1e 100644 --- a/conf/machine/intel-core2-32.conf +++ b/conf/machine/intel-core2-32.conf @@ -27,7 +27,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \ " SYSLINUX_OPTS = "serial 0 115200" -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyPCH0" +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyPCH0" APPEND += "rootwait console=ttyS0,115200 console=ttyPCH0,115200 console=tty0" IMAGE_FSTYPES += "wic" diff --git a/conf/machine/intel-corei7-64.conf b/conf/machine/intel-corei7-64.conf index 6164bf3..2009537 100644 --- a/conf/machine/intel-corei7-64.conf +++ b/conf/machine/intel-corei7-64.conf @@ -32,7 +32,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \ " SYSLINUX_OPTS = "serial 0 115200" -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2" +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2" APPEND += "rootwait console=ttyS0,115200 console=tty0" IMAGE_FSTYPES += "wic" diff --git a/conf/machine/intel-skylake-64.conf b/conf/machine/intel-skylake-64.conf index e367951..503a982 100644 --- a/conf/machine/intel-skylake-64.conf +++ b/conf/machine/intel-skylake-64.conf @@ -25,7 +25,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \ " SYSLINUX_OPTS = "serial 0 115200" -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2" +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2" APPEND += "rootwait console=ttyS0,115200 console=tty0" IMAGE_FSTYPES += "wic" -- 2.7.4
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: What is the recommended method to patch a recipe?
Philip Balister
On 4/13/20 10:31 AM, Nicolas Dechesne wrote:
On Mon, Apr 13, 2020 at 12:55 PM Alexander Kanavin <alex.kanavin@...>I just ran across a bbappend that change configure options, but looking at the original recipe, there is a PACKAGECONFIG option to do the same thing. So they could have used that mechanism instram of the bbappend. Philip Recipes version upgrades (or downgrade) should be done in a dedicated layer
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Files get sporadically lost for native packages
Alexander Kanavin
Adding Michael (lack of confirmtation email from bugzilla). Alex
On Mon, 13 Apr 2020 at 19:59, Konrad Weihmann <kweihmann@...> wrote: Hi Randy,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Files get sporadically lost for native packages
Konrad Weihmann <kweihmann@...>
Hi Randy,
toggle quoted messageShow quoted text
I'm trying all day to create an account at bugzilla to file the issue, but somehow I don't get any confirmation mail (although I tried several mail accounts today, and no it didn't got stuck in spam;-)) - guess that's not how it is supposed to be, right :-)? - I don't know where to address such a problem, so take this reply as FYI. Best Konrad
On 03.04.20 21:28, Randy MacLeod wrote:
On 2020-04-02 4:44 a.m., Konrad Weihmann wrote:Hi Konrad,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Image size reduction
On 2020-04-04 12:27 p.m., Ajam Ali
wrote:
Ajam,
It would be useful if you could reply either way.
If there's still a problem then perhaps someone can help.
If you are able to resolve the issue, then a brief summary of what you did could help the next person who has a similar issue.
Thanks, ../Randy
-- # Randy MacLeod # Wind River Linux
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
M+ & H bugs with Milestone Movements WW15
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Enhancements/Bugs closed WW15!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Current Top developers on Yocto Project 3.1
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
Stephen Jolley
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.
Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 309 unassigned or newcomer bugs.
We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “3.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then “3.2”.
Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: What is the recommended method to patch a recipe?
On Mon, Apr 13, 2020 at 12:55 PM Alexander Kanavin <alex.kanavin@...> wrote:
Ok.. you're right. Well at least my answer is not complete ;)
This is correct. We should encourage everyone to report, and even better propose a fix, to the relevant layer, when the 'problem' is applicable. I didn't want to discourage that, for sure! When developing against master, it's a no brainer. When developing against a stable branch (like probably many users), it's not as obvious. In that case I think trying to avoid 'touching' somebody else layer remains a good advice, since it makes upgrades and maintenance trickier.
Recipes version upgrades (or downgrade) should be done in a dedicated layer owned by the 'developer', and in that case, I agree that bbappend should be prohibited, and the entire recipe should be copied.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: What is the recommended method to patch a recipe?
Alexander Kanavin
On Mon, 13 Apr 2020 at 12:46, Nicolas Dechesne <nicolas.dechesne@...> wrote:
I beg to differ! Bbappends are making it difficult to reason about what the recipe with all its appends is doing (because they destroy spatial locality and aren't easily visible), and I would actually discourage using them if the modification can go to the original recipe. Is it fixing a problem? Is it adding a build option absent from the original recipe? Then please take the trouble to submit the change to the owners of the recipe. Similarly, if a bbappend is re-setting the component version to something else (yes, people do that despite my best efforts to prohibit the practice), then a much cleaner approach is to actually make a fully copy of the recipe, or go and fix the original. Alex
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: What is the recommended method to patch a recipe?
On Mon, Apr 13, 2020 at 10:20 AM nus1998 <nus1998@...> wrote:
A good rule of thumb is to never modify a metadata that is not yours. That applies to everything: * if you need to modify a bb file from a 3rd party library, create a bbappend file in your layer * if you need to modify a bbappend from a 3rd party, then create another bbappend in your layer And by 3rd party i mean any layer/tree which is not yours (OE-core, or any other layer your are using).
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: What is the recommended method to patch a recipe?
Thomas Goodwin
As with a lot of things, I’m sure it all depends on the scope of the change. Personally, if I ‘own’ the original bbappend, then I consider if it’s worth establishing an override or some other similar mechanism within that bbappend, depending on what I’m developing (an image feature or something machine-specific). If it’s a one-off for a specific build that I can lump together with other changes, then I go with a new layer specific those changes.
One thing to keep in mind is that if you create your own layer with a bbappend ,then layer priority will impact which portions of your bbappend overwrite the others and the original recipe. You can use bitbake -e package-name to get a view of how bitbake is overlaying all changes for it.
Cheers,
Thomas
On Apr 13, 2020, 4:20 AM -0400, nus1998 <nus1998@...>, wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
What is the recommended method to patch a recipe?
nus1998 <nus1998@...>
Hi All, I googled some topics on how to patch a recipe, most of them recommend to generate a corresponding <foo>.bbappend to apply the patch, I wonder if there is already a bbappend file, shall I modify the bbappend file directly, or create another layer to overwrite the bbappend file (and including the patchs in original bbappend file)? Thanks in advance Nus
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: QA notification for completed autobuilder build (yocto-3.1.rc2)
Sangeeta Jain
Hello all,
toggle quoted messageShow quoted text
This is the full report for yocto-3.1.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. No new defects are found in this cycle. Note: Few failures are observed. These are setup issue since running tests remotely, not real yocto issue. Thanks, Sangeeta
-----Original Message-----
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: meta-intel: Override SERIAL_CONSOLES variable
Anuj Mittal
Could you send a patch please?
toggle quoted messageShow quoted text
Thanks, Anuj
-----Original Message-----
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[PATCHv1][ptest-runner 2/2] Add support to specify multiple folder for ptest-runner
Anibal Limon
Enables multiple folders in -d option the current use case is to be able
specify multilib folders in the same run. The -d option allows directories without whitespaces inside, example to run after compile: $ ./ptest-runner -d "test/data tests/data2/" [YOCTO #12604] Signed-off-by: Aníbal Limón <anibal.limon@...> --- main.c | 91 ++++++++++++++++++++++----------- ptest_list.c | 17 ++++++ ptest_list.h | 1 + tests/data2/go/ptest/run-ptest | 3 ++ tests/data2/lua/ptest/run-ptest | 3 ++ utils.h | 4 +- 6 files changed, 87 insertions(+), 32 deletions(-) create mode 100755 tests/data2/go/ptest/run-ptest create mode 100755 tests/data2/lua/ptest/run-ptest diff --git a/main.c b/main.c index 01d60f7..e3a1b69 100644 --- a/main.c +++ b/main.c @@ -47,10 +47,43 @@ static inline void print_usage(FILE *stream, char *progname) { - fprintf(stream, "Usage: %s [-d directory] [-e exclude] [-l list] [-t timeout]" + fprintf(stream, "Usage: %s [-d directory directory2 ...] [-e exclude] [-l list] [-t timeout]" " [-x xml-filename] [-h] [ptest1 ptest2 ...]\n", progname); } +static char ** +str2array(char *str, const char *delim, int *num) +{ + char *c, *tok; + char **array; + int i; + + c = str; + *num = 1; + while (*c) { + if (isspace(*c)) + (*num)++; + c++; + } + + + array = malloc((size_t)*num * sizeof(char**)); + CHECK_ALLOCATION(array, 1, 1); + + i = 0; + tok = strtok_r(str, delim, &c); + array[i] = strdup(tok); + CHECK_ALLOCATION(array[i], 1, 1); + i++; + while ((tok = strtok_r(NULL, " ", &c)) != NULL) { + array[i] = strdup(tok); + CHECK_ALLOCATION(array[i], 1, 1); + i++; + } + + return array; +} + int main(int argc, char *argv[]) { @@ -59,7 +92,6 @@ main(int argc, char *argv[]) int i; int rc; int ptest_exclude_num = 0; - char *c, *tok; #ifdef MEMCHECK mtrace(); @@ -68,7 +100,11 @@ main(int argc, char *argv[]) struct ptest_list *head, *run; struct ptest_options opts; - opts.directory = strdup(DEFAULT_DIRECTORY); + opts.dirs = malloc(sizeof(char **) * 1); + CHECK_ALLOCATION(opts.dirs, 1, 1); + opts.dirs[0] = strdup(DEFAULT_DIRECTORY); + CHECK_ALLOCATION(opts.dirs[0], 1, 1); + opts.dirs_no = 1; opts.exclude = NULL; opts.list = 0; opts.timeout = DEFAULT_TIMEOUT; @@ -78,34 +114,12 @@ main(int argc, char *argv[]) while ((opt = getopt(argc, argv, "d:e:lt:x:h")) != -1) { switch (opt) { case 'd': - free(opts.directory); - opts.directory = realpath(optarg, NULL); - CHECK_ALLOCATION(opts.directory, 1, 1); + free(opts.dirs[0]); + free(opts.dirs); + opts.dirs = str2array(optarg, " ", &(opts.dirs_no)); break; case 'e': - c = optarg; - ptest_exclude_num = 1; - - while (*c) { - if (isspace(*c)) - ptest_exclude_num++; - c++; - } - - - opts.exclude = malloc((size_t)ptest_exclude_num * sizeof(char)); - CHECK_ALLOCATION(opts.exclude, 1, 1); - - i = 0; - tok = strtok_r(optarg, " ", &c); - opts.exclude[i] = strdup(tok); - CHECK_ALLOCATION(opts.exclude[i], 1, 1); - i++; - while ((tok = strtok_r(NULL, " ", &c)) != NULL) { - opts.exclude[i] = strdup(tok); - CHECK_ALLOCATION(opts.exclude[i], 1, 1); - i++; - } + opts.exclude = str2array(optarg, " ", &ptest_exclude_num); break; case 'l': opts.list = 1; @@ -140,10 +154,25 @@ main(int argc, char *argv[]) } } - head = get_available_ptests(opts.directory); + head = NULL; + for (i = 0; i < opts.dirs_no; i ++) { + struct ptest_list *tmp; + + tmp = get_available_ptests(opts.dirs[i]); + if (tmp == NULL) { + fprintf(stderr, PRINT_PTESTS_NOT_FOUND_DIR, opts.dirs[i]); + continue; + } + + + if (head == NULL) + head = tmp; + else + head = ptest_list_extend(head, tmp); + } if (head == NULL || ptest_list_length(head) == 0) { fprintf(stderr, PRINT_PTESTS_NOT_FOUND); - return 1; + return 1; } if (opts.list) { diff --git a/ptest_list.c b/ptest_list.c index a5632f8..917ef4f 100644 --- a/ptest_list.c +++ b/ptest_list.c @@ -216,3 +216,20 @@ ptest_list_remove(struct ptest_list *head, char *ptest, int free) return p; } + +struct ptest_list * +ptest_list_extend(struct ptest_list *head, struct ptest_list *extend) +{ + struct ptest_list *p, *q; + + VALIDATE_PTR_RNULL(head); + VALIDATE_PTR_RNULL(extend); + + for (p = head; p->next != NULL; p = p->next); + q = extend->next; + p->next = q; + + free(extend); + + return head; +} diff --git a/ptest_list.h b/ptest_list.h index e1caffc..02a64bb 100644 --- a/ptest_list.h +++ b/ptest_list.h @@ -64,5 +64,6 @@ extern struct ptest_list *ptest_list_search(struct ptest_list *, char *); extern struct ptest_list *ptest_list_search_by_file(struct ptest_list *, char *, struct stat); extern struct ptest_list *ptest_list_add(struct ptest_list *, char *, char *); extern struct ptest_list *ptest_list_remove(struct ptest_list *, char *, int); +extern struct ptest_list *ptest_list_extend(struct ptest_list *, struct ptest_list *); #endif // PTEST_RUNNER_LIST_H diff --git a/tests/data2/go/ptest/run-ptest b/tests/data2/go/ptest/run-ptest new file mode 100755 index 0000000..d8a9ca2 --- /dev/null +++ b/tests/data2/go/ptest/run-ptest @@ -0,0 +1,3 @@ +#!/bin/sh + +echo "go" diff --git a/tests/data2/lua/ptest/run-ptest b/tests/data2/lua/ptest/run-ptest new file mode 100755 index 0000000..07a7713 --- /dev/null +++ b/tests/data2/lua/ptest/run-ptest @@ -0,0 +1,3 @@ +#!/bin/sh + +echo "lua" diff --git a/utils.h b/utils.h index aa53707..39832e6 100644 --- a/utils.h +++ b/utils.h @@ -27,13 +27,15 @@ #include "ptest_list.h" #define PRINT_PTESTS_NOT_FOUND "No ptests found.\n" +#define PRINT_PTESTS_NOT_FOUND_DIR "Warning: ptests not found in, %s.\n" #define PRINT_PTESTS_AVAILABLE "Available ptests:\n" #define CHECK_ALLOCATION(p, size, exit_on_null) \ check_allocation1(p, size, __FILE__, __LINE__, exit_on_null) struct ptest_options { - char *directory; + char **dirs; + int dirs_no; char **exclude; int list; int timeout; -- 2.26.0
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|