From: Lukas Wunner <lukas@wunner.de>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
linux-pci@vger.kernel.org, bhelgaas@google.com,
Mitran Karthikeyan <kmitran@axiado.com>
Subject: Re: [PATCH] MAINTAINERS: Drop Karthikeyan Mitran from MOBIVEIL PCIE entry
Date: Thu, 18 Jun 2026 12:56:30 +0200 [thread overview]
Message-ID: <ajPO3lCupu_kyd0h@wunner.de> (raw)
In-Reply-To: <i5c7whfa7cgo4vdx6msika3shhqst3mcqp3x5cqeue4ihi4ktx@vbxxkhxokbug>
On Thu, Jun 18, 2026 at 12:44:17PM +0200, Manivannan Sadhasivam wrote:
> On Thu, Jun 18, 2026 at 11:06:18AM +0200, Lukas Wunner wrote:
> > On Thu, Jun 18, 2026 at 10:08:11AM +0200, Manivannan Sadhasivam wrote:
> > > +++ b/MAINTAINERS
> > > @@ -20438,7 +20438,6 @@ F: include/linux/switchtec.h
> > > F: include/uapi/linux/switchtec_ioctl.h
> > >
> > > PCI DRIVER FOR MOBIVEIL PCIE IP
> > > -M: Karthikeyan Mitran <m.karthikeyan@mobiveil.co.in>
> > > M: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
> > > L: linux-pci@vger.kernel.org
> > > S: Supported
> >
> > Maybe also update .mailmap to point the bouncing address
> > to kmitran@axiado.com ?
>
> I thought about it but wasn't sure if that is a good idea or not. We didn't
> receive any reply from Karthikeyan so far. So adding mailmap entry means, he
> will be contacted for his previous contributions that he didn't wish to
> receive.
Right, but the alternative is bouncing messages whenever the old address
is cc'ed. I don't now what the policy is for this.
prev parent reply other threads:[~2026-06-18 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 8:08 [PATCH] MAINTAINERS: Drop Karthikeyan Mitran from MOBIVEIL PCIE entry Manivannan Sadhasivam
2026-06-18 9:06 ` Lukas Wunner
2026-06-18 10:44 ` Manivannan Sadhasivam
2026-06-18 10:56 ` Lukas Wunner [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=ajPO3lCupu_kyd0h@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=kmitran@axiado.com \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.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.