From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Andrew Lunn <andrew@lunn.ch>, <netdev@vger.kernel.org>,
<netdev-driver-reviewers@vger.kernel.org>
Subject: Re: [ANN] netdev call - May 7th
Date: Thu, 13 Jun 2024 06:50:34 -0700 [thread overview]
Message-ID: <20240613065034.51c3ef37@kernel.org> (raw)
In-Reply-To: <4a2236c6-1a1a-45bb-89d5-bbb66a8e79b3@intel.com>
On Thu, 13 Jun 2024 14:11:11 +0200 Przemek Kitszel wrote:
> Was it discussed? Any conclusions?
Y'all keep reinventing and working around locks with gazillion flags.
I really hope the step 0 for you will be to figure out a sane locking
scheme :( guard() is not gonna change the math.
prev parent reply other threads:[~2024-06-13 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 14:52 [ANN] netdev call - May 7th Jakub Kicinski
2024-05-07 14:05 ` Andrew Lunn
2024-06-13 12:11 ` Przemek Kitszel
2024-06-13 13:20 ` Andrew Lunn
2024-06-13 13:50 ` 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=20240613065034.51c3ef37@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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).