From: Sriram Yagnaraman <sriram.yagnaraman@est.tech>
Cc: qemu-devel@nongnu.org, Akihiko Odaki <akihiko.odaki@daynix.com>,
Jason Wang <jasowang@redhat.com>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Sriram Yagnaraman <sriram.yagnaraman@est.tech>
Subject: [PATCH v7 1/8] MAINTAINERS: Add Sriram Yagnaraman as a igb reviewer
Date: Thu, 9 Mar 2023 23:00:05 +0100 [thread overview]
Message-ID: <20230309220012.25642-2-sriram.yagnaraman@est.tech> (raw)
In-Reply-To: <20230309220012.25642-1-sriram.yagnaraman@est.tech>
I would like to review and be informed on changes to igb device
Signed-off-by: Sriram Yagnaraman <sriram.yagnaraman@est.tech>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 95c957d587..70685c9dab 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2251,6 +2251,7 @@ F: tests/qtest/libqos/e1000e.*
igb
M: Akihiko Odaki <akihiko.odaki@daynix.com>
+R: Sriram Yagnaraman <sriram.yagnaraman@est.tech>
S: Maintained
F: docs/system/devices/igb.rst
F: hw/net/igb*
--
2.34.1
next prev parent reply other threads:[~2023-03-12 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 22:00 [PATCH v7 0/8] igb: merge changes from <20221229190817.25500-1-sriram.yagnaraman@est.tech> Sriram Yagnaraman
2023-03-09 22:00 ` Sriram Yagnaraman [this message]
2023-03-09 22:00 ` [PATCH v7 2/8] igb: handle PF/VF reset properly Sriram Yagnaraman
2023-03-09 22:00 ` [PATCH v7 3/8] igb: add ICR_RXDW Sriram Yagnaraman
2023-03-09 22:00 ` [PATCH v7 4/8] igb: implement VFRE and VFTE registers Sriram Yagnaraman
2023-03-09 22:00 ` [PATCH v7 5/8] igb: check oversized packets for VMDq Sriram Yagnaraman
2023-03-09 22:00 ` [PATCH v7 6/8] igb: respect E1000_VMOLR_RSSE Sriram Yagnaraman
2023-03-09 22:00 ` [PATCH v7 7/8] igb: implement VF Tx and Rx stats Sriram Yagnaraman
2023-03-09 22:00 ` [PATCH v7 8/8] igb: respect VMVIR and VMOLR for VLAN Sriram Yagnaraman
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=20230309220012.25642-2-sriram.yagnaraman@est.tech \
--to=sriram.yagnaraman@est.tech \
--cc=akihiko.odaki@daynix.com \
--cc=dmitry.fleytman@gmail.com \
--cc=jasowang@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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 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).