From: Palmer Dabbelt <palmer@dabbelt.com>
To: JBeulich@suse.com
Cc: rufus@andestech.com
Cc: binutils@sourceware.org
Subject: Re: [PATCH 2/3] Fix DW_CFA_advance_loc relocation.
Date: Tue, 14 Mar 2017 16:18:00 -0000 [thread overview]
Message-ID: <mhng-f7bb54e8-499c-4bb5-939f-77a58e7a0ee2@palmer-si-x1c4> (raw)
In-Reply-To: <58C7DA2D0200007800142B83@prv-mh.provo.novell.com>
On Tue, 14 Mar 2017 03:55:25 PDT (-0700), JBeulich@suse.com wrote:
>>>> On 13.03.17 at 22:47, <palmer@dabbelt.com> wrote:
>> From: Kuan-Lin Chen <rufus@andestech.com>
>>
>> gas/ChangeLog:
>>
>> 2017-03-02 Kuan-Lin Chen <rufus@andestech.com>
>>
>> * config/tc-riscv.c (md_apply_fix): Set fx_frag and
>> fx_next->fx_frag for CFA_advance_loc relocations.
>
> As this appears to recur - may I please ask that for patches which
> can't otherwise be identified to affect a certain architecture only
> (instead of common code), you name that architecture in the patch
> title (e.g. by a prefix to the subject) or include it in a marker
> similar to [PATCH]?
Sorry about that, I'll be sure to tag our stuff with RISC-V in the future.
next prev parent reply other threads:[~2017-03-14 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 21:48 Fix RISC-V CFA relocations Palmer Dabbelt
2017-03-13 21:48 ` [PATCH 3/3] Define DWARF2_USE_FIXED_ADVANCE_PC Palmer Dabbelt
2017-03-15 9:28 ` Nick Clifton
2017-03-13 21:48 ` [PATCH 2/3] Fix DW_CFA_advance_loc relocation Palmer Dabbelt
2017-03-14 10:55 ` Jan Beulich
2017-03-14 16:18 ` Palmer Dabbelt [this message]
2017-03-15 9:27 ` Nick Clifton
2017-03-13 21:48 ` [PATCH 1/3] Fix the offset of CFA relocation Palmer Dabbelt
2017-03-15 9:27 ` Nick Clifton
2017-03-14 17:01 ` Fix RISC-V CFA relocations 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=mhng-f7bb54e8-499c-4bb5-939f-77a58e7a0ee2@palmer-si-x1c4 \
--to=palmer@dabbelt.com \
--cc=JBeulich@suse.com \
--cc=rufus@andestech.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).