From: Kevin Buettner <kevinb@redhat.com>
To: Jiangshuai Li via Gdb-patches <gdb-patches@sourceware.org>
Cc: Jiangshuai Li <jiangshuai_li@linux.alibaba.com>
Subject: Re: [PATCH] gdb/csky support .reg2 for kernel 4.x and later
Date: Sat, 23 Jul 2022 14:42:45 -0700 [thread overview]
Message-ID: <20220723144245.07768aa7@f35-zws-1> (raw)
In-Reply-To: <20220722055446.2836-1-jiangshuai_li@linux.alibaba.com>
On Fri, 22 Jul 2022 13:54:46 +0800
Jiangshuai Li via Gdb-patches <gdb-patches@sourceware.org> wrote:
> static void
> csky_supply_gregset (const struct regset *regset,
> - struct regcache *regcache, int regnum,
> - const void *regs, size_t len)
> + struct regcache *regcache, int regnum,
> + const void *regs, size_t len)
> {
> int i, gregset_num;
> const gdb_byte *gregs = (const gdb_byte *) regs ;
> @@ -77,8 +79,8 @@ csky_supply_gregset (const struct regset *regset,
> for (i = 0; i < gregset_num; i++)
> {
> if ((regnum == csky_gregset_offset[i] || regnum == -1)
> - && csky_gregset_offset[i] != -1)
> - regcache->raw_supply (csky_gregset_offset[i], gregs + 4 * i);
> + && csky_gregset_offset[i] != -1)
> + regcache->raw_supply (csky_gregset_offset[i], gregs + 4 * i);
> }
> }
>
So... in the above two hunks of this patch, plus in many other places
in the patch, it seems that the only change was to convert tabs to
spaces.
Could you please resend your patch without these whitespace changes?
Not only will it be easier to review, but I think we still prefer the
use of tabs in place of leading spaces in GDB's source code. Even if
such a change were desirable, we'd prefer to see a separate patch for
whitespace changes.
Thanks,
Kevin
prev parent reply other threads:[~2022-07-23 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 5:54 Jiangshuai Li
2022-07-23 21:42 ` Kevin Buettner [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=20220723144245.07768aa7@f35-zws-1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jiangshuai_li@linux.alibaba.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).