netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "mowenroot@163.com" <mowenroot@163.com>
To: "Paul Moore" <paul@paul-moore.com>,  kuba <kuba@kernel.org>
Cc: 1985755126 <1985755126@qq.com>,  netdev <netdev@vger.kernel.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH] netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets
Date: Sun, 30 Mar 2025 19:09:10 +0800	[thread overview]
Message-ID: <202503301909090753553@163.com> (raw)
In-Reply-To: CAHC9VhRvrOCqBT-2xRF5zrkeDN3EvShUggOF=Uh47TXFc5Uu1w@mail.gmail.com

Hi Paul, Jakub, and all maintainers,

Thanks for your review and suggestions.

I have submitted the v2 patch and made the following improvements:

- Added a blank line between local variable declarations and the main logic for better readability.
- Removed unnecessary comments as the code is self-explanatory.
- Improved the commit message and included more detailed information, including the reproducer steps.

Many thanks to Paul for your careful guidance—you are a great teacher.

Thanks again for your feedback!

Thanks again.
 Debin Zhu & Bitao Ouyang

--
mowenroot@163.com

      parent reply	other threads:[~2025-03-30 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250326074355.24016-1-mowenroot@163.com>
2025-03-26 19:38 ` [PATCH] netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets Paul Moore
2025-03-28 12:02   ` Jakub Kicinski
2025-03-28 16:02     ` Paul Moore
2025-03-30 10:40       ` [PATCH v2] " Debin Zhu
2025-04-01 10:17         ` Paolo Abeni
2025-04-01 12:40           ` [PATCH v3] " Debin Zhu
2025-04-01 20:22             ` Paul Moore
2025-04-02  9:36             ` Simon Horman
2025-04-02 18:28               ` Paul Moore
2025-04-02 23:02                 ` Jakub Kicinski
2025-03-30 11:09       ` mowenroot [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=202503301909090753553@163.com \
    --to=mowenroot@163.com \
    --cc=1985755126@qq.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul@paul-moore.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;
as well as URLs for NNTP newsgroup(s).