virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: vdasa@vmware.com
Cc: pv-drivers@vmware.com, bryantan@vmware.com,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] VMCI: Update maintainers for VMCI
Date: Mon, 25 Jul 2022 20:05:51 +0200	[thread overview]
Message-ID: <Yt7bfyANrfdPxdS8@kroah.com> (raw)
In-Reply-To: <20220725163246.38486-1-vdasa@vmware.com>

On Mon, Jul 25, 2022 at 09:32:46AM -0700, vdasa@vmware.com wrote:
> From: Vishnu Dasa <vdasa@vmware.com>
> 
> Remove Rajesh as a maintainer for the VMCI driver.

Why?

> 
> Acked-by: Bryan Tan <bryantan@vmware.com>
> Signed-off-by: Vishnu Dasa <vdasa@vmware.com>

I need an ack from the person that is being removed here, for obvious
reasons.  Any specific reason you didn't cc: them on this patch?

thanks,

greg k-h
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2022-07-25 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 16:32 [PATCH] VMCI: Update maintainers for VMCI vdasa--- via Virtualization
2022-07-25 18:05 ` Greg KH [this message]
2022-07-25 18:29   ` Vishnu Dasa via Virtualization
2022-07-26 15:10     ` Greg KH
2022-07-26 15:55       ` Vishnu Dasa via Virtualization
2022-07-26 16:18         ` Joe Perches
2022-07-26 17:10           ` Vishnu Dasa via Virtualization
     [not found]         ` <CAJ60do+Lgnx6gfHncckF-=8F=zzn81tCiFNLOmg_8TyuLGUotw@mail.gmail.com>
2022-07-28  8:44           ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2022-02-27 21:05 Jorgen Hansen

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=Yt7bfyANrfdPxdS8@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bryantan@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    --cc=vdasa@vmware.com \
    --cc=virtualization@lists.linux-foundation.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).