From: Pavel Skripkin <paskripkin@gmail.com>
To: gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net,
phil@philpotter.co.uk, straube.linux@gmail.com,
dan.carpenter@oracle.com
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
Pavel Skripkin <paskripkin@gmail.com>
Subject: [PATCH v3 4/4] MAINTAINERS: add myself as r8188eu reviewer
Date: Mon, 6 Jun 2022 22:37:12 +0300 [thread overview]
Message-ID: <a5e93a54a2481f7a0c1921b7c9914972a5a93e45.1654543286.git.paskripkin@gmail.com> (raw)
In-Reply-To: <cover.1654543286.git.paskripkin@gmail.com>
I was reviewing r8188eu patches for a while, but I am missing some of
them, since I am not in CC list. I want to be CC'ed to help reviewing
and testing more patches.
Acked-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
Acked-by: Phillip Potter <phil@philpotter.co.uk>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0a635f2ae5b9..bd38a2e465cc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18716,6 +18716,7 @@ F: drivers/staging/olpc_dcon/
STAGING - REALTEK RTL8188EU DRIVERS
M: Larry Finger <Larry.Finger@lwfinger.net>
M: Phillip Potter <phil@philpotter.co.uk>
+R: Pavel Skripkin <paskripkin@gmail.com>
S: Supported
F: drivers/staging/r8188eu/
--
2.36.1
next prev parent reply other threads:[~2022-06-06 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 19:36 [PATCH v3 0/4] staging: r8188eu: add error handling of usb read errors Pavel Skripkin
2022-06-06 19:36 ` [PATCH v3 1/4] staging: r8188eu: add error handling of rtw_read8 Pavel Skripkin
2022-06-06 19:37 ` [PATCH v3 2/4] staging: r8188eu: add error handling of rtw_read16 Pavel Skripkin
2022-06-06 19:37 ` [PATCH v3 3/4] staging: r8188eu: add error handling of rtw_read32 Pavel Skripkin
2022-06-06 19:37 ` Pavel Skripkin [this message]
2022-06-07 11:07 ` [PATCH v3 0/4] staging: r8188eu: add error handling of usb read errors Greg KH
2022-06-07 19:04 ` Pavel Skripkin
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=a5e93a54a2481f7a0c1921b7c9914972a5a93e45.1654543286.git.paskripkin@gmail.com \
--to=paskripkin@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@gmail.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
all inboxes | Powered by JetHome®