From: Tristan Gingold <gingold@adacore.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org, Andrew Waterman <andrew@sifive.com>
Subject: Re: binutils-2_28-branch: Various RISC-V Fixes
Date: Mon, 27 Feb 2017 10:21:00 -0000 [thread overview]
Message-ID: <93046857-508E-4560-8C37-3CEC91ABE441@adacore.com> (raw)
In-Reply-To: <20170224174232.13170-1-palmer@dabbelt.com>
> On 24 Feb 2017, at 18:42, Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> Here are the three RISC-V patches that aren't on the 2.28 branch but are on
> master. One has been submitted for 2.28, but I haven't gotten any feedback,
> while the other two are new.
>
> We'd really like these in the release so we can build Linux with the 2.28
> release rather that having to tell the Linux devs to patch it or get binutils
> master.
>
> Are these OK for the 2.28 branch?
>
> Also: I'd like to check on the policy for commiting to 2.28. I haven't gotten
> any feedback on my "OK for 2.28?" messages recently and I was told that I
> needed an OK for the 2.28 branch from Tristan Gingold. I haven't seen any mail
> from Tristan Gingold recently, but when I went to rebase I saw a bunch of
> patches committed. Am I asking for approval incorrectly?
Yes, they are OK.
You are asking correctly, but I have a backlog of emails to read. Sorry!
Thanks,
Tristan.
next prev parent reply other threads:[~2017-02-27 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 17:43 Palmer Dabbelt
2017-02-24 17:43 ` [PATCH 3/3] bfd: RISC-V: relax to gp in more cases Palmer Dabbelt
2017-02-24 17:43 ` [PATCH 1/3] Add SFENCE.VMA instruction Palmer Dabbelt
2017-02-24 17:43 ` [PATCH 2/3] Add new counter-enable CSRs Palmer Dabbelt
2017-02-27 10:21 ` Tristan Gingold [this message]
2017-02-27 17:47 ` binutils-2_28-branch: Various RISC-V Fixes Palmer Dabbelt
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=93046857-508E-4560-8C37-3CEC91ABE441@adacore.com \
--to=gingold@adacore.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=palmer@dabbelt.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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).