From: Vladimir Oltean <olteanv@gmail.com>
To: Yuan Can <yuancan@huawei.com>
Cc: ioana.ciornei@nxp.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH] dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove()
Date: Thu, 8 Dec 2022 16:20:26 +0200 [thread overview]
Message-ID: <20221208142026.gxc4nvsejduoeirz@skbuf> (raw)
In-Reply-To: <0d769f50-bbd1-4291-c3c0-29527b40fb98@huawei.com>
On Thu, Dec 08, 2022 at 09:51:45AM +0800, Yuan Can wrote:
> Nice! Thanks for the suggestion, as the patch has been merged, let me send
> another patch to do this job.
The patch was merged at the same time as I was writing my reply.
Since the patch went to the "net.git" tree where only bug fixes are
accepted, any further rework would have to go to "net-next.git".
A resynchronization (merge net into net-next) takes place weekly, one
should take place later today or tomorrow, I think. So if you're going
to send a follow-up patch, I'd wait until "net-next" contains your
change.
That being said, it's not all that critical to follow up with another
patch. I simply hadn't noticed your patch was merged, but it does the
job as well, just not in the same style as the rest of these 2 functions.
prev parent reply other threads:[~2022-12-08 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 6:15 [PATCH] dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove() Yuan Can
2022-12-07 11:20 ` patchwork-bot+netdevbpf
2022-12-07 11:55 ` Vladimir Oltean
2022-12-08 1:51 ` Yuan Can
2022-12-08 14:20 ` Vladimir Oltean [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=20221208142026.gxc4nvsejduoeirz@skbuf \
--to=olteanv@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuancan@huawei.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