[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221208142026.gxc4nvsejduoeirz@skbuf>
Date: Thu, 8 Dec 2022 16:20:26 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Yuan Can <yuancan@...wei.com>
Cc: ioana.ciornei@....com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH] dpaa2-switch: Fix memory leak in
dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove()
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.
Powered by blists - more mailing lists