Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Gopi Kumar Bulusu <gopi@sankhya.com>, Michael Eager <eager@eagercon.com>
Cc: 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: Wed, 10 Jun 2026 21:41:11 -0400	[thread overview]
Message-ID: <4f2b9910-6366-44c8-b468-59a27183597c@simark.ca> (raw)
In-Reply-To: <CAL1P33wZrnkuH+Tw+Ur0ULmcjbdHiWCV_ufVs5o6RtQa4EeBGQ@mail.gmail.com>

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

Simon

  reply	other threads:[~2026-06-11  1:41 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 [this message]
2026-06-11  1:44               ` Gopi Kumar Bulusu
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=4f2b9910-6366-44c8-b468-59a27183597c@simark.ca \
    --to=simark@simark.ca \
    --cc=binutils@sourceware.org \
    --cc=eager@eagercon.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gopi@sankhya.com \
    --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