linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vasu Dev <vasu.dev-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Johannes Thumshirn <jthumshirn-l3A5Bk7waGM@public.gmane.org>,
	James Bottomley
	<jejb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
	"Martin K . Petersen"
	<martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: fcoe-devel-s9riP+hp16TNLxjTenLetw@public.gmane.org,
	Linux Kernel Mailinglist
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux SCSI Mailinglist
	<linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] MAINTAINERS: Change FCoE maintainer
Date: Tue, 28 Jun 2016 09:26:14 -0700	[thread overview]
Message-ID: <1467131174.19666.10.camel@linux.intel.com> (raw)
In-Reply-To: <20160623082228.22633-1-jthumshirn-l3A5Bk7waGM@public.gmane.org>

On Thu, 2016-06-23 at 10:22 +0200, Johannes Thumshirn wrote:
> Vasu is going to resign from his maintainer role and I'll take over.
> 
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e1b090f..70af8c0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4661,7 +4661,7 @@ S:	Maintained
>  F:	drivers/staging/fbtft/
>  
>  FCOE SUBSYSTEM (libfc, libfcoe, fcoe)
> -M:	Vasu Dev <vasu.dev@intel.com>
> +M:	Johannes Thumshirn <jth@kernel.org>
>  L:	fcoe-devel@open-fcoe.org
>  W:	www.Open-FCoE.org
>  S:	Supported

Acked-by : Vasu Dev <vasu.dev@intel.com>
_______________________________________________
fcoe-devel mailing list
fcoe-devel@open-fcoe.org
http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel

      parent reply	other threads:[~2016-06-28 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  8:22 [PATCH] MAINTAINERS: Change FCoE maintainer Johannes Thumshirn
     [not found] ` <20160623082228.22633-1-jthumshirn-l3A5Bk7waGM@public.gmane.org>
2016-06-28 16:26   ` Vasu Dev [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=1467131174.19666.10.camel@linux.intel.com \
    --to=vasu.dev-vuqaysv1563yd54fqh9/ca@public.gmane.org \
    --cc=fcoe-devel-s9riP+hp16TNLxjTenLetw@public.gmane.org \
    --cc=jejb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=jthumshirn-l3A5Bk7waGM@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.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).