From: Gopi Kumar Bulusu <gopi@sankhya.com>
To: Simon Marchi <simark@simark.ca>
Cc: Michael Eager <eager@eagercon.com>,
binutils@sourceware.org, gdb-patches@sourceware.org,
Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v2] gdb/MicroBlaze: Add support for native linux gdb
Date: Thu, 11 Jun 2026 07:14:20 +0530 [thread overview]
Message-ID: <CAL1P33wqEW3yZGwdMJsV3dWqqc4ZhxL=11zQsa=-S-OUisrW+A@mail.gmail.com> (raw)
In-Reply-To: <4f2b9910-6366-44c8-b468-59a27183597c@simark.ca>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
namaskaaram
On Thu, Jun 11, 2026, 7:11 AM Simon Marchi <simark@simark.ca> wrote:
> On 6/10/26 9:19 PM, Gopi Kumar Bulusu wrote:
> >
> > namaskaaram
> >
> > On Thu, Jun 11, 2026, 6:09 AM Michael Eager <eager@eagercon.com <mailto:
> eager@eagercon.com>> wrote:
> >
> > Hi Gopi --
> >
> > I (or more accurately, git) fixed several whitespace issues.
> >
> >
> > Please share. I did check all the whitespace issues flagged by git-diff.
>
> For whitespaces, I suggest to install pre-commit, there is a hook that
> checks it. See:
>
> https://sourceware.org/gdb/wiki/DeveloperTips#Setting_up_pre-commit
Thanks, I will install it.
dhanyavaadaaha
gopi
> Simon
>
[-- Attachment #2: Type: text/html, Size: 1772 bytes --]
next prev parent reply other threads:[~2026-06-11 1:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 11:32 [PATCH] " Gopi Kumar Bulusu
2026-05-26 11:33 ` Gopi Kumar Bulusu
2026-05-29 14:56 ` Tom Tromey
2026-05-29 15:01 ` Simon Marchi
2026-06-01 6:30 ` Gopi Kumar Bulusu
2026-06-01 6:38 ` Gopi Kumar Bulusu
2026-06-02 0:28 ` Michael Eager
2026-06-02 5:05 ` [PATCH v2] " Gopi Kumar Bulusu
2026-06-11 0:39 ` Michael Eager
2026-06-11 1:19 ` Gopi Kumar Bulusu
2026-06-11 1:41 ` Simon Marchi
2026-06-11 1:44 ` Gopi Kumar Bulusu [this message]
2026-06-11 12:52 ` Michael Eager
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='CAL1P33wqEW3yZGwdMJsV3dWqqc4ZhxL=11zQsa=-S-OUisrW+A@mail.gmail.com' \
--to=gopi@sankhya.com \
--cc=binutils@sourceware.org \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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