public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Mashiro Chen <mashiro.chen@mailbox.org>
To: kuba@kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
	mashiro.chen@mailbox.org, netdev@vger.kernel.org,
	pabeni@redhat.com
Subject: Re: [PATCH 0/5] hamradio: mkiss: modernize and clean up mkiss driver
Date: Mon, 30 Mar 2026 03:19:23 +0800	[thread overview]
Message-ID: <20260329191923.821284-1-mashiro.chen@mailbox.org> (raw)
In-Reply-To: <20260329103508.4905cc09@kernel.org>

Hi Jakub,

Thank you for the quick review and for pointing out the Netdev policy
regarding clean-up patches. I apologize for the noise; I was not fully
aware of the specific guidelines for the Netdev subsystem in this regard.

I will respect these guidelines and focus my further contributions on
functional improvements or bug fixes.

Regarding the current series, I understand them do not meet the Netdev
Standard for clean-up patches and I will drop these submissions.

Thank you again for your time and guidance.

Best Regards,
Mashiro Chen

      reply	other threads:[~2026-03-29 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 14:34 [PATCH 0/5] hamradio: mkiss: modernize and clean up mkiss driver Mashiro Chen
2026-03-29 14:34 ` [PATCH 1/5] hamradio: mkiss: move assignments out of if conditions Mashiro Chen
2026-03-29 14:34 ` [PATCH 2/5] hamradio: mkiss: remove redundant static initialization to 0 Mashiro Chen
2026-03-29 14:34 ` [PATCH 3/5] hamradio: mkiss: fix spacing around assignment operator Mashiro Chen
2026-03-29 14:34 ` [PATCH 4/5] hamradio: mkiss: modernize logging with netdev and pr macros Mashiro Chen
2026-03-29 14:34 ` [PATCH 5/5] hamradio: mkiss: cleanup indentation and coding style Mashiro Chen
2026-03-29 17:35 ` [PATCH 0/5] hamradio: mkiss: modernize and clean up mkiss driver Jakub Kicinski
2026-03-29 19:19   ` Mashiro Chen [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=20260329191923.821284-1-mashiro.chen@mailbox.org \
    --to=mashiro.chen@mailbox.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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