From: Ido Schimmel <idosch@idosch•org>
To: Simon Horman <horms@kernel•org>
Cc: Vlad Buslov <vladbu@nvidia•com>,
davem@davemloft•net, kuba@kernel•org, edumazet@google•com,
pabeni@redhat•com, netdev@vger•kernel.org,
amir.hanania@intel•com, jeffrey.t.kirsher@intel•com,
john.fastabend@gmail•com
Subject: Re: [PATCH net] vlan: Fix VLAN 0 memory leak
Date: Mon, 31 Jul 2023 18:45:23 +0300 [thread overview]
Message-ID: <ZMfXExktiYeVEo/3@shredder> (raw)
In-Reply-To: <ZMeEU/Aqq0ljY8NE@kernel.org>
On Mon, Jul 31, 2023 at 11:52:19AM +0200, Simon Horman wrote:
> perhaps it would be worth including the information added
> by Ido above in the patch description. Not a hard requirement
> from my side, just an idea.
I agree (assuming my analysis is correct).
next prev parent reply other threads:[~2023-07-31 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 16:31 [PATCH net] vlan: Fix VLAN 0 memory leak Vlad Buslov
2023-07-30 15:30 ` Ido Schimmel
2023-07-31 9:52 ` Simon Horman
2023-07-31 15:45 ` Ido Schimmel [this message]
2023-07-31 19:11 ` Vlad Buslov
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=ZMfXExktiYeVEo/3@shredder \
--to=idosch@idosch$(echo .)org \
--cc=amir.hanania@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=vladbu@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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