From: Jakub Kicinski <kuba@kernel.org>
To: Li zeming <zeming@nfschina.com>
Cc: pabeni@redhat.com, vyasevich@gmail.com, nhorman@tuxdriver.com,
marcelo.leitner@gmail.com, davem@davemloft.net,
edumazet@google.com, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sctp: sm_statefuns: Remove unnecessary ‘NULL’ values from Pointer
Date: Fri, 18 Nov 2022 19:30:04 -0800 [thread overview]
Message-ID: <20221118193004.5a6fbf52@kernel.org> (raw)
In-Reply-To: <20221118014641.3035-1-zeming@nfschina.com>
On Fri, 18 Nov 2022 09:46:42 +0800 Li zeming wrote:
> - struct sctp_packet *packet = NULL;
> + struct sctp_packet *packet;
> struct sctp_chunk *chunk = arg;
> struct sctp_chunk *shut;
Please don't sent such patches to networking.
prev parent reply other threads:[~2022-11-19 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 1:46 [PATCH v2] sctp: sm_statefuns: Remove unnecessary ‘NULL’ values from Pointer Li zeming
2022-11-19 3:30 ` Jakub Kicinski [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=20221118193004.5a6fbf52@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.com \
--cc=vyasevich@gmail.com \
--cc=zeming@nfschina.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 read-only IMAP folder(s) and NNTP newsgroup(s).