From: Leo Liang <ycliang@andestech.com>
To: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Cc: Rick Chen <rick@andestech.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH] riscv: Fix build against binutils 2.38
Date: Wed, 13 Apr 2022 01:49:17 +0000 [thread overview]
Message-ID: <YlYsHSyZ+OwPnXGT@ubuntu01> (raw)
In-Reply-To: <CA+zEjCtZg6+=17S_JwoOq7LWBV1PVL-9aq7eXLfSVbQ4Vyqjjw@mail.gmail.com>
Hi Alex,
On Tue, Apr 12, 2022 at 11:14:32AM +0200, Alexandre Ghiti wrote:
> Hi Leo,
> > A gentle ping.
> >
> > Any comments?
> > Or should we spin a patch for updating the toolchain used for 32 bit build?
>
> Sorry for being very slow here, if the patch is too much of a burden,
> maybe you should drop it for now, I will have more time to work on
> this in 2 weeks, sorry again.
>
> Alex
>
Understood! No worries! Take your time to it.
Best regards,
Leo
> >
> > Best regards,
> > Leo
next prev parent reply other threads:[~2022-04-13 1:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 13:47 [PATCH] riscv: Fix build against binutils 2.38 Alexandre Ghiti
2022-01-28 14:15 ` Bin Meng
2022-01-28 18:03 ` Heinrich Schuchardt
2022-01-28 18:19 ` Aurelien Jarno
2022-01-28 18:28 ` Aurelien Jarno
2022-01-28 18:22 ` Heinrich Schuchardt
2022-02-17 9:24 ` Leo Liang
2022-02-17 10:28 ` Alexandre Ghiti
2022-02-19 8:51 ` Leo Liang
2022-02-21 16:42 ` Alexandre Ghiti
2022-03-01 3:21 ` Leo Liang
2022-03-03 11:06 ` Leo Liang
2022-03-09 6:31 ` Leo Liang
2022-03-10 8:03 ` Alexandre Ghiti
2022-04-07 9:12 ` Leo Liang
2022-04-12 9:14 ` Alexandre Ghiti
2022-04-13 1:49 ` Leo Liang [this message]
2022-10-01 23:24 ` Heinrich Schuchardt
2022-10-01 23:57 ` Tom Rini
2022-10-02 1:52 ` Heinrich Schuchardt
2022-10-02 17:16 ` Tom Rini
2022-10-02 17:25 ` Tom Rini
2022-06-23 13:40 ` Heiko Stübner
2022-08-30 20:28 ` Christian Stewart
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=YlYsHSyZ+OwPnXGT@ubuntu01 \
--to=ycliang@andestech.com \
--cc=alexandre.ghiti@canonical.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.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