From: Kalle Valo <kvalo@codeaurora.org>
To: amit karwar <amitkarwar@gmail.com>
Cc: Brian Norris <briannorris@chromium.org>,
Ganapathi Bhat <gbhat@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
Xinming Hu <huxm@marvell.com>
Subject: Re: [PATCH] MAINTAINERS: drop akarwar from mwifiex
Date: Wed, 19 Apr 2017 17:26:03 +0300 [thread overview]
Message-ID: <87vaq079tw.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAEhWJFmmawzF8+=xNNv7XvpWZrg4nSSFqheeyQqFWRA0iu4f5Q@mail.gmail.com> (amit karwar's message of "Mon, 17 Apr 2017 11:19:19 +0530")
amit karwar <amitkarwar@gmail.com> writes:
> On Thu, Apr 13, 2017 at 6:47 PM, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Brian Norris <briannorris@chromium.org> writes:
>>
>>> His email is bouncing, and I expect he's not doing this work any more.
>>>
>>> Cc: Amitkumar Karwar <amitkarwar@gmail.com>
>>> Cc: Nishant Sarmukadam <nishants@marvell.com>
>>> Cc: Ganapathi Bhat <gbhat@marvell.com>
>>> Cc: Xinming Hu <huxm@marvell.com>
>>> Signed-off-by: Brian Norris <briannorris@chromium.org>
>>> ---
>>> Or alternatively, we can update his email address. I just don't want to keep
>>> seeing bounced emails :)
>>
>> Me neither :) So Amitkumar, which one do you prefer?
>>
>
> Updating email address would be fine. Please replace
> akarwar@marvell.com with amitkarwar@gmail.com
Sounds good. Brian, can you cook up a new patch?
--
Kalle Valo
next prev parent reply other threads:[~2017-04-19 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 17:42 [PATCH] MAINTAINERS: drop akarwar from mwifiex Brian Norris
2017-04-13 13:17 ` Kalle Valo
2017-04-17 5:14 ` [EXT] " Ganapathi Bhat
2017-04-17 5:49 ` amit karwar
2017-04-19 14:26 ` Kalle Valo [this message]
2017-04-19 17:13 ` Brian Norris
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=87vaq079tw.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=amitkarwar@gmail.com \
--cc=briannorris@chromium.org \
--cc=gbhat@marvell.com \
--cc=huxm@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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.