From: Jakub Kicinski <kuba@kernel.org>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Dec 2022 call minutes
Date: Tue, 6 Dec 2022 10:58:56 -0800 [thread overview]
Message-ID: <20221206105856.17129932@kernel.org> (raw)
In-Reply-To: <20221206105832.7ade246d@kernel.org>
On Tue, 6 Dec 2022 10:58:32 -0800 Jakub Kicinski wrote:
> Hi,
>
> I've added the meeting notes to this doc:
>
> https://docs.google.com/document/d/1iq7vuleJVyFPZnO-Ey-N7AumxUTgLdnnfR8nuLuNLxw/
>
> And will just use this doc going forward.
>
>
> Thanks to Pavan for reviews last week, and nVidia's reviews which
> are already flowing!
Well, shit, I sent this to the wrong list. Let me send one more email
then...
prev parent reply other threads:[~2022-12-06 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 18:58 Dec 2022 call minutes Jakub Kicinski
2022-12-06 18:58 ` 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=20221206105856.17129932@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.