From: Yann Sionneau <ysionneau@kalray.eu> To: Jeff Xie <xiehuan09@gmail.com> Cc: "Arnd Bergmann" <arnd@arndb.de>, "Albert Ou" <aou@eecs.berkeley.edu>, "Alexander Shishkin" <alexander.shishkin@linux.intel.com>, "Andrew Morton" <akpm@linux-foundation.org>, "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>, "Ard Biesheuvel" <ardb@kernel.org>, "Arnaldo Carvalho de Melo" <acme@kernel.org>, "Boqun Feng" <boqun.feng@gmail.com>, bpf@vger.kernel.org, "Christian Brauner" <brauner@kernel.org>, devicetree@vger.kernel.org, "Eric Biederman" <ebiederm@xmission.com>, "Eric Paris" <eparis@redhat.com>, "Ingo Molnar" <mingo@redhat.com>, "Jan Kiszka" <jan.kiszka@siemens.com>, "Jason Baron" <jbaron@akamai.com>, "Jiri Olsa" <jolsa@kernel.org>, "Jonathan Corbet" <corbet@lwn.net>, "Josh Poimboeuf" <jpoimboe@kernel.org>, "Kees Cook" <keescook@chromium.org>, "Kieran Bingham" <kbingham@kernel.org>, "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>, linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-audit@redhat.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-perf-users@vger.kernel.org, linux-pm@vger.kernel.org, linux-riscv@lists.infradead.org, "Marc Zyngier" <maz@kernel.org>, "Mark Rutland" <mark.rutland@arm.com>, "Masami Hiramatsu" <mhiramat@kernel.org>, "Namhyung Kim" <namhyung@kernel.org>, "Nick Piggin" <npiggin@gmail.com>, "Oleg Nesterov" <oleg@redhat.com>, "Palmer Dabbelt" <palmer@dabbelt.com>, "Paul Moore" <paul@paul-moore.com>, "Paul Walmsley" <paul.walmsley@sifive.com>, "Peter Zijlstra" <peterz@infradead.org>, "Rob Herring" <robh+dt@kernel.org>, "Sebastian Reichel" <sre@kernel.org>, "Steven Rostedt" <rostedt@goodmis.org>, "Thomas Gleixner" <tglx@linutronix.de>, "Waiman Long" <longman@redhat.com>, "Will Deacon" <will@kernel.org>, "Alex Michon" <amichon@kalray.eu>, "Ashley Lesdalons" <alesdalons@kalray.eu>, "Benjamin Mugnier" <mugnier.benjamin@gmail.com>, "Clement Leger" <clement.leger@bootlin.com>, "Guillaume Missonnier" <gmissonnier@kalray.eu>, "Guillaume Thouvenin" <gthouvenin@kalray.eu>, "Jean-Christophe Pince" <jcpince@gmail.com>, "Jonathan Borne" <jborne@kalray.eu>, "Jules Maselbas" <jmaselbas@kalray.eu>, "Julian Vetter" <jvetter@kalray.eu>, "Julien Hascoet" <jhascoet@kalray.eu>, "Julien Villette" <jvillette@kalray.eu>, "Louis Morhet" <lmorhet@kalray.eu>, "Luc Michel" <lmichel@kalray.eu>, "Marc Poulhiès" <dkm@kataplop.net>, "Marius Gligor" <mgligor@kalray.eu>, "Samuel Jones" <sjones@kalray.eu>, "Thomas Costis" <tcostis@kalray.eu>, "Vincent Chardon" <vincent.chardon@elsys-design.com> Subject: Re: [RFC PATCH 00/25] Upstream kvx Linux port Date: Mon, 9 Jan 2023 16:30:50 +0100 [thread overview] Message-ID: <bccad498-3af2-08f1-8264-cf7b438732d3@kalray.eu> (raw) In-Reply-To: <CAEr6+ECPFeokSULpWzYEYLROYHXNA0PtvdUchT37d4_qVA-PKQ@mail.gmail.com> Hi Jeff, On 1/9/23 16:11, Jeff Xie wrote: > On Mon, Jan 9, 2023 at 9:21 PM Yann Sionneau <ysionneau@kalray.eu> wrote: >> Hi Jeff, >> >> On 1/7/23 07:25, Jeff Xie wrote: >>> Hi, >>> >>> On Wed, Jan 4, 2023 at 1:01 AM Yann Sionneau <ysionneau@kalray.eu> wrote: >>>> [snip] >>>> >>>> A kvx toolchain can be built using: >>>> # install dependencies: texinfo bison flex libgmp-dev libmpc-dev libmpfr-dev >>>> $ git clone https://github.com/kalray/build-scripts >>>> $ cd build-scripts >>>> $ source last.refs >>>> $ ./build-kvx-xgcc.sh output >>> I would like to build the kvx-xgcc to compile and test the linux >>> kernel, but it reported a compile error. >>> I wonder what version of gcc you are using. >>> >>> My build environment: >>> VERSION="20.04.2 LTS (Focal Fossa)" >>> gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) >>> >>> >>> Compile error: >>> $ ./build-kvx-xgcc.sh output >>> >>> ../../binutils/libiberty/fibheap.c: In function ‘fibheap_replace_key_data’: >>> ../../binutils/libiberty/fibheap.c:38:24: error: ‘LONG_MIN’ undeclared >>> (first use in this function) >>> 38 | #define FIBHEAPKEY_MIN LONG_MIN >>> | ^~~~~~~~ >>> [snip] >> What SHA1 of https://github.com/kalray/build-scripts are you using? > I have executed the "source last.refs" I was referring to the SHA1 of the repo itself (build-scripts). `last.refs` is a symbolic link which can point to several releases, depending on "when" you did the clone. I am asking this because we recently published new toolchains. I want to make sure which one you are trying to build. >> We are building our toolchain on Ubuntu 18.04 / 20.04 and 22.04 without >> issues, I don't understand why it does not work for you, although indeed >> the error log you are having pops out on my search engine and seems to >> be some well known issue. > Yes, there are many answers on the web, but none of them solve this problem. > >> If the build-script does not work for you, you can still use the >> pre-built toolchains generated by the GitHub automated actions: >> https://github.com/kalray/build-scripts/releases/tag/v4.11.1 ("latest" >> means 22.04) > Thanks, this is the final solution ;-) Good to see it helped :) Regards, -- Yann
WARNING: multiple messages have this Message-ID (diff)
From: Yann Sionneau <ysionneau@kalray.eu> To: Jeff Xie <xiehuan09@gmail.com> Cc: "Arnd Bergmann" <arnd@arndb.de>, "Albert Ou" <aou@eecs.berkeley.edu>, "Alexander Shishkin" <alexander.shishkin@linux.intel.com>, "Andrew Morton" <akpm@linux-foundation.org>, "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>, "Ard Biesheuvel" <ardb@kernel.org>, "Arnaldo Carvalho de Melo" <acme@kernel.org>, "Boqun Feng" <boqun.feng@gmail.com>, bpf@vger.kernel.org, "Christian Brauner" <brauner@kernel.org>, devicetree@vger.kernel.org, "Eric Biederman" <ebiederm@xmission.com>, "Eric Paris" <eparis@redhat.com>, "Ingo Molnar" <mingo@redhat.com>, "Jan Kiszka" <jan.kiszka@siemens.com>, "Jason Baron" <jbaron@akamai.com>, "Jiri Olsa" <jolsa@kernel.org>, "Jonathan Corbet" <corbet@lwn.net>, "Josh Poimboeuf" <jpoimboe@kernel.org>, "Kees Cook" <keescook@chromium.org>, "Kieran Bingham" <kbingham@kernel.org>, "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>, linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-audit@redhat.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-perf-users@vger.kernel.org, linux-pm@vger.kernel.org, linux-riscv@lists.infradead.org, "Marc Zyngier" <maz@kernel.org>, "Mark Rutland" <mark.rutland@arm.com>, "Masami Hiramatsu" <mhiramat@kernel.org>, "Namhyung Kim" <namhyung@kernel.org>, "Nick Piggin" <npiggin@gmail.com>, "Oleg Nesterov" <oleg@redhat.com>, "Palmer Dabbelt" <palmer@dabbelt.com>, "Paul Moore" <paul@paul-moore.com>, "Paul Walmsley" <paul.walmsley@sifive.com>, "Peter Zijlstra" <peterz@infradead.org>, "Rob Herring" <robh+dt@kernel.org>, "Sebastian Reichel" <sre@kernel.org>, "Steven Rostedt" <rostedt@goodmis.org>, "Thomas Gleixner" <tglx@linutronix.de>, "Waiman Long" <longman@redhat.com>, "Will Deacon" <will@kernel.org>, "Alex Michon" <amichon@kalray.eu>, "Ashley Lesdalons" <alesdalons@kalray.eu>, "Benjamin Mugnier" <mugnier.benjamin@gmail.com>, "Clement Leger" <clement.leger@bootlin.com>, "Guillaume Missonnier" <gmissonnier@kalray.eu>, "Guillaume Thouvenin" <gthouvenin@kalray.eu>, "Jean-Christophe Pince" <jcpince@gmail.com>, "Jonathan Borne" <jborne@kalray.eu>, "Jules Maselbas" <jmaselbas@kalray.eu>, "Julian Vetter" <jvetter@kalray.eu>, "Julien Hascoet" <jhascoet@kalray.eu>, "Julien Villette" <jvillette@kalray.eu>, "Louis Morhet" <lmorhet@kalray.eu>, "Luc Michel" <lmichel@kalray.eu>, "Marc Poulhiès" <dkm@kataplop.net>, "Marius Gligor" <mgligor@kalray.eu>, "Samuel Jones" <sjones@kalray.eu>, "Thomas Costis" <tcostis@kalray.eu>, "Vincent Chardon" <vincent.chardon@elsys-design.com> Subject: Re: [RFC PATCH 00/25] Upstream kvx Linux port Date: Mon, 9 Jan 2023 16:30:50 +0100 [thread overview] Message-ID: <bccad498-3af2-08f1-8264-cf7b438732d3@kalray.eu> (raw) In-Reply-To: <CAEr6+ECPFeokSULpWzYEYLROYHXNA0PtvdUchT37d4_qVA-PKQ@mail.gmail.com> Hi Jeff, On 1/9/23 16:11, Jeff Xie wrote: > On Mon, Jan 9, 2023 at 9:21 PM Yann Sionneau <ysionneau@kalray.eu> wrote: >> Hi Jeff, >> >> On 1/7/23 07:25, Jeff Xie wrote: >>> Hi, >>> >>> On Wed, Jan 4, 2023 at 1:01 AM Yann Sionneau <ysionneau@kalray.eu> wrote: >>>> [snip] >>>> >>>> A kvx toolchain can be built using: >>>> # install dependencies: texinfo bison flex libgmp-dev libmpc-dev libmpfr-dev >>>> $ git clone https://github.com/kalray/build-scripts >>>> $ cd build-scripts >>>> $ source last.refs >>>> $ ./build-kvx-xgcc.sh output >>> I would like to build the kvx-xgcc to compile and test the linux >>> kernel, but it reported a compile error. >>> I wonder what version of gcc you are using. >>> >>> My build environment: >>> VERSION="20.04.2 LTS (Focal Fossa)" >>> gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) >>> >>> >>> Compile error: >>> $ ./build-kvx-xgcc.sh output >>> >>> ../../binutils/libiberty/fibheap.c: In function ‘fibheap_replace_key_data’: >>> ../../binutils/libiberty/fibheap.c:38:24: error: ‘LONG_MIN’ undeclared >>> (first use in this function) >>> 38 | #define FIBHEAPKEY_MIN LONG_MIN >>> | ^~~~~~~~ >>> [snip] >> What SHA1 of https://github.com/kalray/build-scripts are you using? > I have executed the "source last.refs" I was referring to the SHA1 of the repo itself (build-scripts). `last.refs` is a symbolic link which can point to several releases, depending on "when" you did the clone. I am asking this because we recently published new toolchains. I want to make sure which one you are trying to build. >> We are building our toolchain on Ubuntu 18.04 / 20.04 and 22.04 without >> issues, I don't understand why it does not work for you, although indeed >> the error log you are having pops out on my search engine and seems to >> be some well known issue. > Yes, there are many answers on the web, but none of them solve this problem. > >> If the build-script does not work for you, you can still use the >> pre-built toolchains generated by the GitHub automated actions: >> https://github.com/kalray/build-scripts/releases/tag/v4.11.1 ("latest" >> means 22.04) > Thanks, this is the final solution ;-) Good to see it helped :) Regards, -- Yann _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-01-09 15:32 UTC|newest] Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-03 16:43 [RFC PATCH 00/25] Upstream kvx Linux port Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 01/25] Documentation: kvx: Add basic documentation Yann Sionneau 2023-01-03 17:50 ` Jonathan Corbet 2023-01-09 9:51 ` [PATCH 0/8] kvx documentation improv (was: Re: [RFC PATCH 01/25] Documentation: kvx: Add basic documentation) Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 1/8] Documentation: kvx: Convert to reST Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 2/8] Documentation: kvx: Wrap diagrams in literal code block Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 3/8] Documentation: kvx: Fix lists Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 4/8] Documentation: kvx: kvx-iommu: Use reST syntax for subsections Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 5/8] Documentation: kvx: kvx-iommu: monospacize kvx iommu device tree path Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 6/8] Documentation: kvx: Promote title headings Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 7/8] Documentation: kvx: Use literal code block for command-line inputs Bagas Sanjaya 2023-01-09 9:51 ` [PATCH 8/8] Documentation: kvx: reword Bagas Sanjaya 2023-01-09 10:59 ` [PATCH 0/8] kvx documentation improv (was: Re: [RFC PATCH 01/25] Documentation: kvx: Add basic documentation) Jules Maselbas 2023-01-10 0:18 ` Randy Dunlap 2023-01-18 8:44 ` [RFC PATCH 01/25] Documentation: kvx: Add basic documentation Yann Sionneau 2023-01-05 18:38 ` kernel test robot 2023-01-18 15:09 ` Jeff Xie 2023-01-03 16:43 ` [RFC PATCH 02/25] kvx: Add ELF-related definitions Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 21:35 ` Eric W. Biederman 2023-01-03 21:35 ` Eric W. Biederman 2023-01-18 8:48 ` Yann Sionneau 2023-01-18 8:48 ` Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 03/25] kvx: Add build infrastructure Yann Sionneau 2023-01-03 17:29 ` Randy Dunlap 2023-01-05 13:12 ` Jules Maselbas 2023-01-06 0:43 ` kernel test robot 2023-01-03 16:43 ` [RFC PATCH 04/25] kvx: Add CPU definition headers Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 05/25] kvx: Add atomic/locking headers Yann Sionneau 2023-01-04 9:53 ` Mark Rutland 2023-01-06 14:11 ` Jules Maselbas 2023-01-10 13:24 ` Mark Rutland 2023-01-18 13:40 ` Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 06/25] kvx: Add other common headers Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 07/25] kvx: Add boot and setup routines Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 08/25] kvx: Add exception/interrupt handling Yann Sionneau 2023-01-09 20:54 ` Thomas Gleixner 2023-01-03 16:43 ` [RFC PATCH 09/25] kvx: irqchip: Add support for irq controllers Yann Sionneau 2023-01-03 21:28 ` Rob Herring 2023-01-03 16:43 ` [RFC PATCH 10/25] kvx: Add process management Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 11/25] kvx: Add memory management Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-04 11:37 ` Mike Rapoport 2023-01-04 11:37 ` Mike Rapoport 2023-01-03 16:43 ` [RFC PATCH 12/25] kvx: Add system call support Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-04 15:07 ` Arnd Bergmann 2023-01-04 15:07 ` Arnd Bergmann 2023-01-09 20:55 ` Thomas Gleixner 2023-01-09 20:55 ` Thomas Gleixner 2023-01-03 16:43 ` [RFC PATCH 13/25] kvx: Add signal handling support Yann Sionneau 2023-01-04 11:28 ` Mark Rutland 2023-01-03 16:43 ` [RFC PATCH 14/25] kvx: Add ELF relocations and module support Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 15/25] kvx: Add misc common routines Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 16/25] kvx: Add some library functions Yann Sionneau 2023-01-05 13:05 ` Clément Léger 2023-01-03 16:43 ` [RFC PATCH 17/25] kvx: Add multi-processor (SMP) support Yann Sionneau 2023-01-03 21:22 ` Rob Herring 2023-01-05 8:12 ` Clément Léger 2023-01-03 16:43 ` [RFC PATCH 18/25] kvx: Add kvx default config file Yann Sionneau 2023-01-04 13:02 ` Bagas Sanjaya 2023-01-06 14:52 ` Jules Maselbas 2023-01-03 16:43 ` [RFC PATCH 19/25] kvx: power: scall poweroff driver Yann Sionneau 2023-01-04 17:08 ` Sebastian Reichel 2023-01-03 16:43 ` [RFC PATCH 20/25] kvx: gdb: add kvx related gdb helpers Yann Sionneau 2023-01-04 7:41 ` Jan Kiszka 2023-01-05 15:19 ` Dmitrii Bundin 2023-01-03 16:43 ` [RFC PATCH 21/25] kvx: Add support for ftrace Yann Sionneau 2023-01-05 12:55 ` Clément Léger 2023-01-05 14:20 ` Steven Rostedt 2023-01-05 14:50 ` Mark Rutland 2023-01-03 16:43 ` [RFC PATCH 22/25] kvx: Add support for jump labels Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 23/25] kvx: Add debugging related support Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 24/25] kvx: Add support for CPU Perf Monitors Yann Sionneau 2023-01-03 16:43 ` Yann Sionneau 2023-01-03 16:43 ` [RFC PATCH 25/25] kvx: Add support for cpuinfo Yann Sionneau 2023-01-03 20:52 ` [RFC PATCH 00/25] Upstream kvx Linux port Rob Herring 2023-01-03 20:52 ` Rob Herring 2023-01-03 20:52 ` Rob Herring 2023-01-04 15:58 ` Arnd Bergmann 2023-01-04 15:58 ` Arnd Bergmann 2023-01-04 15:58 ` Arnd Bergmann 2023-01-05 10:40 ` Jules Maselbas 2023-01-05 10:40 ` Jules Maselbas 2023-01-05 10:40 ` Jules Maselbas 2023-01-05 12:05 ` Arnd Bergmann 2023-01-05 12:05 ` Arnd Bergmann 2023-01-05 12:05 ` Arnd Bergmann 2023-01-05 14:12 ` Steven Rostedt 2023-01-05 14:12 ` Steven Rostedt 2023-01-05 14:12 ` Steven Rostedt 2023-01-07 6:25 ` Jeff Xie 2023-01-07 6:25 ` Jeff Xie 2023-01-07 6:25 ` Jeff Xie 2023-01-09 13:21 ` Yann Sionneau 2023-01-09 13:21 ` Yann Sionneau 2023-01-09 13:21 ` Yann Sionneau 2023-01-09 15:11 ` Jeff Xie 2023-01-09 15:11 ` Jeff Xie 2023-01-09 15:11 ` Jeff Xie 2023-01-09 15:30 ` Yann Sionneau [this message] 2023-01-09 15:30 ` Yann Sionneau 2023-01-09 15:53 ` Jeff Xie 2023-01-09 15:53 ` Jeff Xie 2023-01-16 7:31 ` Jeff Xie 2023-01-16 7:31 ` Jeff Xie 2023-01-16 7:31 ` Jeff Xie
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=bccad498-3af2-08f1-8264-cf7b438732d3@kalray.eu \ --to=ysionneau@kalray.eu \ --cc=acme@kernel.org \ --cc=akpm@linux-foundation.org \ --cc=alesdalons@kalray.eu \ --cc=alexander.shishkin@linux.intel.com \ --cc=amichon@kalray.eu \ --cc=aneesh.kumar@linux.ibm.com \ --cc=aou@eecs.berkeley.edu \ --cc=ardb@kernel.org \ --cc=arnd@arndb.de \ --cc=boqun.feng@gmail.com \ --cc=bpf@vger.kernel.org \ --cc=brauner@kernel.org \ --cc=clement.leger@bootlin.com \ --cc=corbet@lwn.net \ --cc=devicetree@vger.kernel.org \ --cc=dkm@kataplop.net \ --cc=ebiederm@xmission.com \ --cc=eparis@redhat.com \ --cc=gmissonnier@kalray.eu \ --cc=gthouvenin@kalray.eu \ --cc=jan.kiszka@siemens.com \ --cc=jbaron@akamai.com \ --cc=jborne@kalray.eu \ --cc=jcpince@gmail.com \ --cc=jhascoet@kalray.eu \ --cc=jmaselbas@kalray.eu \ --cc=jolsa@kernel.org \ --cc=jpoimboe@kernel.org \ --cc=jvetter@kalray.eu \ --cc=jvillette@kalray.eu \ --cc=kbingham@kernel.org \ --cc=keescook@chromium.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-audit@redhat.com \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-perf-users@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=lmichel@kalray.eu \ --cc=lmorhet@kalray.eu \ --cc=longman@redhat.com \ --cc=mark.rutland@arm.com \ --cc=maz@kernel.org \ --cc=mgligor@kalray.eu \ --cc=mhiramat@kernel.org \ --cc=mingo@redhat.com \ --cc=mugnier.benjamin@gmail.com \ --cc=namhyung@kernel.org \ --cc=npiggin@gmail.com \ --cc=oleg@redhat.com \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=paul@paul-moore.com \ --cc=peterz@infradead.org \ --cc=robh+dt@kernel.org \ --cc=rostedt@goodmis.org \ --cc=sjones@kalray.eu \ --cc=sre@kernel.org \ --cc=tcostis@kalray.eu \ --cc=tglx@linutronix.de \ --cc=vincent.chardon@elsys-design.com \ --cc=will@kernel.org \ --cc=xiehuan09@gmail.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.