Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
	       Maxim Grigoriev <maxim2405@gmail.com>,
	Woody LaRue <larue@cadence.com>,
	       Marc Gauthier <marc@cadence.com>,
	       "linux-xtensa@linux-xtensa.org"
	<linux-xtensa@linux-xtensa.org>,
	       Daniel Jacobowitz <drow@false.org>
Subject: Re: [PATCH 2/2] gdbserver/xtensa: fix typo in XCHAL_HAVE_LOOPS
Date: Fri, 17 Apr 2015 14:12:00 -0000	[thread overview]
Message-ID: <553114A4.9070906@redhat.com> (raw)
In-Reply-To: <CAMo8BfK0oVBW-MMZSaamZbA0oqTb+gCTCcePpKTwLQhRqZdEvQ@mail.gmail.com>

On 04/17/2015 01:50 PM, Max Filippov wrote:
> On Fri, Apr 17, 2015 at 2:29 PM, Pedro Alves <palves@redhat.com> wrote:
>> On 04/17/2015 02:14 AM, Max Filippov wrote:
>>> This fixes lbeg/lend/lcount registers handling through gdbserver.
>>>
>>> 2015-04-17  Max Filippov  <jcmvbkbc@gmail.com>
>>> gdb/gdbserver/
>>>       * linux-xtensa-low.c (xtensa_fill_gregset,
>>>       xtensa_store_gregset): fix typo in XCHAL_HAVE_LOOPS
>>
>> I was curious on whether it might have been that XCHAL_HAVE_LOOP
>> used to exist and was later renamed ("as in, how did this ever work
> 
> It did work, only these three registers were inaccessible.

That's what I'd call "not work". :-)

(the point of that was that in case of a rename, it'd be
probably better to check both XCHAL_HAVE_LOOP/XCHAL_HAVE_LOOPS.)

>> OK with that change.
> 
> Ok. Can I check it in (I have write-after-approval access to binutils),
> or do I need to request such access to gdb separately?

Once the copyright issue is sorted out, please add yourself
to the gdb/MAINTAINERS file under Write After Approval.
(it's preapproved, just push it in and post it to the
gdb-patches@ list).

Since the fixes/patches are trivial, it's OK to push them
in before that is resolved.  Feel free to do that any time.

Thanks,
Pedro Alves


      reply	other threads:[~2015-04-17 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  1:15 [PATCH 0/2] Fixes for xtensa gdbserver Max Filippov
2015-04-17  1:15 ` [PATCH 1/2] gdbserver/xtensa: drop xtensa_usrregs_info Max Filippov
2015-04-17 11:29   ` Pedro Alves
2015-04-17  1:15 ` [PATCH 2/2] gdbserver/xtensa: fix typo in XCHAL_HAVE_LOOPS Max Filippov
2015-04-17 11:29   ` Pedro Alves
2015-04-17 12:50     ` Max Filippov
2015-04-17 14:12       ` Pedro Alves [this message]

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=553114A4.9070906@redhat.com \
    --to=palves@redhat.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=larue@cadence.com \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=marc@cadence.com \
    --cc=maxim2405@gmail.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