public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mohamed Khalfella <mkhalfella@purestorage•com>
To: Koichiro Den <koichiro.den@canonical•com>
Cc: "Jan Kiszka" <jan.kiszka@siemens•com>,
	"Kieran Bingham" <kbingham@kernel•org>,
	"Andrew Morton" <akpm@linux-foundation•org>,
	"Etienne Buira" <etienne.buira@free•fr>,
	"Andrew Ballance" <andrewjballance@gmail•com>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	"Thomas Weißschuh" <linux@weissschuh•net>
Subject: Re: [PATCH] scripts/gdb/symbols: follow up on refactoring for const struct bin_attribute
Date: Wed, 26 Feb 2025 17:05:08 -0800	[thread overview]
Message-ID: <20250227010508.GA392458-mkhalfella@purestorage.com> (raw)
In-Reply-To: <5vhttz23b4v4fs57fv5o7e74bn2uewrmy6jdgeenwztwufjo5b@o72abjlumepw>

On 2025-02-27 09:59:23 +0900, Koichiro Den wrote:
> 
> Sorry for the delayed response.
> I have no objections. Please go ahead and submit your patch. There is no
> need to mention this original submission, nor CC me.
> 
> Thanks!

Koichiro - You reported this issue first and came up with a fix for it.
Unless you do not want to, I think you should the one who fixes this
bug. How about you re-submit a patch with combination of your original
patch and the diff I posted?

      reply	other threads:[~2025-02-27  1:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-12 12:21 [PATCH] scripts/gdb/symbols: follow up on refactoring for const struct bin_attribute Koichiro Den
2025-02-13  4:38 ` Mohamed Khalfella
2025-02-27  0:17   ` Mohamed Khalfella
2025-02-27  0:59     ` Koichiro Den
2025-02-27  1:05       ` Mohamed Khalfella [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=20250227010508.GA392458-mkhalfella@purestorage.com \
    --to=mkhalfella@purestorage$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=andrewjballance@gmail$(echo .)com \
    --cc=etienne.buira@free$(echo .)fr \
    --cc=jan.kiszka@siemens$(echo .)com \
    --cc=kbingham@kernel$(echo .)org \
    --cc=koichiro.den@canonical$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux@weissschuh$(echo .)net \
    /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