From: Jakub Kicinski <kuba@kernel.org>
To: Ayush Sawal <ayush.sawal@chelsio.com>
Cc: Kees Cook <keescook@chromium.org>,
Raju Rangoju <Raju.Rangoju@amd.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-hardening@vger.kernel.org, sourabh.sagar@chelsio.com,
bharat@chelsio.com
Subject: Re: [PATCH 0/5] chelsio: Annotate structs with __counted_by
Date: Fri, 6 Oct 2023 07:27:44 -0700 [thread overview]
Message-ID: <20231006072744.66a1b412@kernel.org> (raw)
In-Reply-To: <6a750af0-1de2-3bec-3d52-a4007f3afe92@chelsio.com>
On Fri, 6 Oct 2023 01:58:54 +0530 Ayush Sawal wrote:
> The current maintainer for cxgb4 driver is Sourabh Sagar
> <sourabh.sagar@chelsio.com>, I have added him in the CC.
> He will update the MAINTAINERS file for cxgb4 driver.
Thanks & looking forward to the update!
next prev parent reply other threads:[~2023-10-06 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 18:11 [PATCH 0/5] chelsio: Annotate structs with __counted_by Kees Cook
2023-09-29 18:11 ` [PATCH 1/5] chelsio/l2t: Annotate struct l2t_data " Kees Cook
2023-09-30 6:39 ` Christophe JAILLET
2023-10-01 6:33 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 2/5] cxgb4: Annotate struct clip_tbl " Kees Cook
2023-10-01 6:35 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 3/5] cxgb4: Annotate struct cxgb4_tc_u32_table " Kees Cook
2023-10-01 6:36 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 4/5] cxgb4: Annotate struct sched_table " Kees Cook
2023-10-01 6:36 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 5/5] cxgb4: Annotate struct smt_data " Kees Cook
2023-10-01 6:37 ` Gustavo A. R. Silva
2023-09-29 19:44 ` [PATCH 0/5] chelsio: Annotate structs " Kees Cook
2023-10-02 18:31 ` Jakub Kicinski
2023-10-05 20:28 ` Ayush Sawal
2023-10-06 14:27 ` Jakub Kicinski [this message]
2023-10-04 22:50 ` patchwork-bot+netdevbpf
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=20231006072744.66a1b412@kernel.org \
--to=kuba@kernel.org \
--cc=Raju.Rangoju@amd.com \
--cc=ayush.sawal@chelsio.com \
--cc=bharat@chelsio.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sourabh.sagar@chelsio.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 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.