From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH for 4.21 v7 1/4] automation: drop debian:11-riscv64 container
Date: Fri, 21 Feb 2025 18:04:06 +0100 [thread overview]
Message-ID: <cb818120-dc01-470d-a9c8-9b3587042405@gmail.com> (raw)
In-Reply-To: <e1215fff-65cf-418b-b13f-6405c38b1787@suse.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On 2/21/25 1:30 PM, Jan Beulich wrote:
> On 21.02.2025 12:57, Oleksii Kurochko wrote:
>> On 2/21/25 9:35 AM, Jan Beulich wrote:
>>> On 20.02.2025 18:44, Oleksii Kurochko wrote:
>>>> There are two reasons for that:
>>>> 1. In the README, GCC baseline is chosen to be 12.2, whereas Debian 11
>>>> uses GCC 10.2.1.
>>> Which README is this? Not the one at the root of the tree, afaics, which
>>> continues to mention only x86 and Arm.
>> I missed to add this patch:https://gitlab.com/xen-project/people/olkur/xen/-/commit/57901e60066e93d986670aa91fb390774c965d3f.
>>
>> Would it be enough just to do a reply for this patch series and send what git format-patch gives?
> Don't know. In particular I have been under the impression that "git format-patch"
> formats things slightly differently than what "git am" would expect. Can't you use
> "git send-email" here as well, making that patch 0.5/4?
Done by using git send-email.
At least, my mail app parsed this case well.
~ Oleksii
[-- Attachment #2: Type: text/html, Size: 1935 bytes --]
next prev parent reply other threads:[~2025-02-21 17:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 17:44 [PATCH for 4.21 v7 0/4] RISC-V runtime detection of extenstions Oleksii Kurochko
2025-02-20 17:44 ` [PATCH for 4.21 v7 1/4] automation: drop debian:11-riscv64 container Oleksii Kurochko
2025-02-21 8:35 ` Jan Beulich
2025-02-21 11:57 ` Oleksii Kurochko
2025-02-21 12:30 ` Jan Beulich
2025-02-21 17:04 ` Oleksii Kurochko [this message]
2025-02-21 12:31 ` Jan Beulich
2025-02-20 17:44 ` [PATCH for 4.21 v7 2/4] xen/riscv: drop CONFIG_RISCV_ISA_RV64G Oleksii Kurochko
2025-02-26 12:55 ` Jan Beulich
2025-02-20 17:44 ` [PATCH for 4.21 v7 3/4] xen/riscv: make zbb as mandatory Oleksii Kurochko
2025-02-26 12:58 ` Jan Beulich
2025-02-26 14:38 ` Oleksii Kurochko
2025-02-26 14:49 ` Jan Beulich
2025-02-26 17:16 ` Oleksii Kurochko
2025-02-20 17:44 ` [PATCH for 4.21 v7 4/4] xen/riscv: identify specific ISA supported by cpu Oleksii Kurochko
2025-02-21 17:02 ` [PATCH for 4.21 v7 0.5/4] xen/README: add compiler and binutils versions for RISCV-64 Oleksii Kurochko
2025-02-24 10:57 ` Jan Beulich
2025-02-24 15:52 ` Oleksii Kurochko
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=cb818120-dc01-470d-a9c8-9b3587042405@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=cardoe@cardoe.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.