public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Miquel Sabaté Solà" <mikisabate@gmail•com>
To: linuxppc-dev@lists•ozlabs.org
Cc: linux-kernel@vger•kernel.org,  maddy@linux•ibm.com,
	 mpe@ellerman•id.au, npiggin@gmail•com,
	 christophe.leroy@csgroup•eu
Subject: Re: [PATCH] powerpc: kgdb: Remove OUTBUFMAX constant
Date: Wed, 15 Oct 2025 11:37:53 +0200	[thread overview]
Message-ID: <68ef6b76.5d0a0220.39b228.4064@mx.google.com> (raw)
In-Reply-To: <68da3e7e.050a0220.8efdc.f1ab@mx.google.com> ("Miquel Sabaté	Solà"'s message of "Mon, 29 Sep 2025 10:08:29 +0200")

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Hello,

Miquel Sabaté Solà @ 2025-09-29 10:08 +02:

> Miquel Sabaté Solà @ 2025-09-15 16:18 +02:
>
>> This constant was introduced in commit 17ce452f7ea3 ("kgdb, powerpc:
>> arch specific powerpc kgdb support"), but it is no longer used anywhere
>> in the source tree.
>>
>> Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail•com>
>> ---
>>  arch/powerpc/include/asm/kgdb.h | 1 -
>>  1 file changed, 1 deletion(-)
>>
>> diff --git a/arch/powerpc/include/asm/kgdb.h b/arch/powerpc/include/asm/kgdb.h
>> index 715c18b75334..4c0afde87e97 100644
>> --- a/arch/powerpc/include/asm/kgdb.h
>> +++ b/arch/powerpc/include/asm/kgdb.h
>> @@ -25,7 +25,6 @@
>>
>>  #define BREAK_INSTR_SIZE	4
>>  #define BUFMAX			((NUMREGBYTES * 2) + 512)
>> -#define OUTBUFMAX		((NUMREGBYTES * 2) + 512)
>>
>>  #define BREAK_INSTR		0x7d821008	/* twge r2, r2 */
>
> Gently ping :)

Ping again :)

Does anyone have some time to review this patch?

Thanks!
Miquel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2025-10-15  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 14:18 [PATCH] powerpc: kgdb: Remove OUTBUFMAX constant Miquel Sabaté Solà
2025-09-29  8:08 ` Miquel Sabaté Solà
2025-10-15  9:37   ` Miquel Sabaté Solà [this message]
2025-10-15  9:52 ` Christophe Leroy

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=68ef6b76.5d0a0220.39b228.4064@mx.google.com \
    --to=mikisabate@gmail$(echo .)com \
    --cc=christophe.leroy@csgroup$(echo .)eu \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=maddy@linux$(echo .)ibm.com \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=npiggin@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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