This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] RISC-V: Fix disassemble for c.li, c.andi and c.addiw
- From: Nick Clifton <nickc at redhat dot com>
- To: Palmer Dabbelt <palmer at dabbelt dot com>
- Cc: binutils at sourceware dot org, patches at groups dot riscv dot org, kito dot cheng at gmail dot com
- Date: Thu, 4 May 2017 16:06:25 +0100
- Subject: Re: [PATCH] RISC-V: Fix disassemble for c.li, c.andi and c.addiw
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=nickc at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 0E7B57D4E5
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 0E7B57D4E5
- References: <mhng-dc0432dc-ab72-46c3-81b5-4960a3de2c8d@palmer-si-x1c4>
Hi Palmer,
>> Note - given that you are a maintainer for the RISC-V port, you can go
>> ahead and apply patches like this without waiting for approval. (Although
>> please do still post the patches to this list, just add [COMMIT] to the
>> subject line). The rule is - if the patch only affects RISC-V specific
>> code then go ahead and review/apply it yourself. If it affects other
>> targets, or has the potential to affect them, then post the patch for
>> review.
>
> Thanks. I've been submitting all my patches before committing them because I've
> found people have useful suggestions, but if the patch goes unanswered for more
> than a day or two I just commit it anyway.
That's fine. I just wanted to be sure that you knew that if a RISC-V patch
was simple and obvious you did not have to wait for peer review. Unless you
want to, of course.
Cheers
Nick