All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamal Dasu <kdasu.kdev@gmail.com>
To: ulf.hansson@linaro.org, linux-kernel@vger.kernel.org,
	alcooperx@gmail.com, linux-arm-kernel@lists.infradead.org,
	adrian.hunter@intel.com, linux-mmc@vger.kernel.org
Cc: f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
	Kamal Dasu <kdasu.kdev@gmail.com>
Subject: [PATCH] MAINTAINERS: Update maintainer for SDHCI Broadcom BRCMSTB driver
Date: Fri,  2 Dec 2022 16:21:19 -0500	[thread overview]
Message-ID: <20221202212119.43214-1-kdasu.kdev@gmail.com> (raw)

Taking over as upstream maintainer for Broadcom SDHCI
driver from Al Cooper.

Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1daadaa4d48b..90beddcf84b0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18497,6 +18497,7 @@ K:	\bsecure_computing
 K:	\bTIF_SECCOMP\b
 
 SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI) Broadcom BRCMSTB DRIVER
+M:	Kamal Dasu <kdasu.kdev@gmail.com>
 M:	Al Cooper <alcooperx@gmail.com>
 R:	Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
 L:	linux-mmc@vger.kernel.org
-- 
2.17.1


WARNING: multiple messages have this Message-ID (diff)
From: Kamal Dasu <kdasu.kdev@gmail.com>
To: ulf.hansson@linaro.org, linux-kernel@vger.kernel.org,
	alcooperx@gmail.com, linux-arm-kernel@lists.infradead.org,
	adrian.hunter@intel.com, linux-mmc@vger.kernel.org
Cc: f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
	Kamal Dasu <kdasu.kdev@gmail.com>
Subject: [PATCH] MAINTAINERS: Update maintainer for SDHCI Broadcom BRCMSTB driver
Date: Fri,  2 Dec 2022 16:21:19 -0500	[thread overview]
Message-ID: <20221202212119.43214-1-kdasu.kdev@gmail.com> (raw)

Taking over as upstream maintainer for Broadcom SDHCI
driver from Al Cooper.

Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1daadaa4d48b..90beddcf84b0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18497,6 +18497,7 @@ K:	\bsecure_computing
 K:	\bTIF_SECCOMP\b
 
 SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI) Broadcom BRCMSTB DRIVER
+M:	Kamal Dasu <kdasu.kdev@gmail.com>
 M:	Al Cooper <alcooperx@gmail.com>
 R:	Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
 L:	linux-mmc@vger.kernel.org
-- 
2.17.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-12-02 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 21:21 Kamal Dasu [this message]
2022-12-02 21:21 ` [PATCH] MAINTAINERS: Update maintainer for SDHCI Broadcom BRCMSTB driver Kamal Dasu
2022-12-02 22:01 ` Florian Fainelli
2022-12-02 22:01   ` Florian Fainelli
2022-12-05  8:16 ` Adrian Hunter
2022-12-05  8:16   ` Adrian Hunter
2022-12-07 12:37 ` Ulf Hansson
2022-12-07 12:37   ` Ulf Hansson

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=20221202212119.43214-1-kdasu.kdev@gmail.com \
    --to=kdasu.kdev@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=alcooperx@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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.