From: Tomas Henzl <thenzl@redhat.com>
To: Kashyap Desai <kashyap.desai@broadcom.com>, linux-scsi@vger.kernel.org
Cc: martin.petersen@oracle.com, jejb@linux.vnet.ibm.com,
sumit.saxena@broadcom.com
Subject: Re: [PATCH v3 6/8] MAINTAINERS: Update megaraid maintainers list
Date: Tue, 8 Nov 2016 15:50:07 +0100 [thread overview]
Message-ID: <60504200-bdda-ec69-11e6-ab9f7894fef5@redhat.com> (raw)
In-Reply-To: <1477056816-7058-7-git-send-email-kashyap.desai@broadcom.com>
On 21.10.2016 15:33, Kashyap Desai wrote:
> Update MEGARAID drivers maintainers list.
>
> Signed-off-by: Sumit Saxena <sumit.saxena@broadcom.com>
> Reviewed-by: Hannes Reinecke <hare@suse.com>
> ---
> MAINTAINERS | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f0ee7a6..8b9117f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7612,12 +7612,12 @@ S: Maintained
> F: drivers/net/wireless/mediatek/mt7601u/
>
> MEGARAID SCSI/SAS DRIVERS
> -M: Kashyap Desai <kashyap.desai@avagotech.com>
> -M: Sumit Saxena <sumit.saxena@avagotech.com>
> -M: Uday Lingala <uday.lingala@avagotech.com>
> -L: megaraidlinux.pdl@avagotech.com
> +M: Kashyap Desai <kashyap.desai@broadcom.com>
> +M: Sumit Saxena <sumit.saxena@broadcom.com>
> +M: Shivasharan S <shivasharan.srikanteshwara@broadcom.com>
> +L: megaraidlinux.pdl@broadcom.com
> L: linux-scsi@vger.kernel.org
> -W: http://www.lsi.com
> +W: http://www.avagotech.com/support/
I like the phase delay, everything moved to Broadcom, so it's good time
to switch the support page to from LSI to Avago..
Reviewed-by: Tomas Henzl <thenzl@redhat.com>
next prev parent reply other threads:[~2016-11-08 14:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 13:33 [PATCH v3 0/7] megaraid_sas: Updates for scsi-next Kashyap Desai
2016-10-21 13:33 ` [PATCH v3 1/8] megaraid_sas: For SRIOV enabled firmware, ensure VF driver waits for 30secs before reset Kashyap Desai
2016-10-21 13:33 ` [PATCH v3 2/8] megaraid_sas: Send correct PhysArm to FW for R1 VD downgrade Kashyap Desai
2016-10-21 13:33 ` [PATCH v3 3/8] megaraid_sas: Do not fire DCMDs during PCI shutdown/detach Kashyap Desai
2016-10-24 14:34 ` Hannes Reinecke
2016-10-21 13:33 ` [PATCH v3 4/8] megaraid_sas: Send SYNCHRONIZE_CACHE for non-raid to firmware Kashyap Desai
2016-10-21 16:02 ` Tomas Henzl
2016-10-24 14:35 ` Hannes Reinecke
2016-10-24 14:35 ` Hannes Reinecke
2016-10-24 16:00 ` Ewan D. Milne
2016-10-25 1:33 ` Martin K. Petersen
2016-10-21 13:33 ` [PATCH v3 5/8] megaraid_sas: Send SYNCHRONIZE_CACHE for VD " Kashyap Desai
2016-10-21 15:59 ` Tomas Henzl
2016-10-24 14:36 ` Hannes Reinecke
2016-10-24 16:00 ` Ewan D. Milne
2016-10-21 13:33 ` [PATCH v3 6/8] MAINTAINERS: Update megaraid maintainers list Kashyap Desai
2016-11-08 14:50 ` Tomas Henzl [this message]
2016-10-21 13:33 ` [PATCH v3 7/8] megaraid_sas: Do not set MPI2_TYPE_CUDA for JBOD FP path for FW which does not support JBOD sequence map Kashyap Desai
2016-10-21 13:33 ` [PATCH v3 8/8] megaraid_sas: driver version upgrade Kashyap Desai
2016-10-24 14:36 ` Hannes Reinecke
2016-11-08 23:05 ` Martin K. Petersen
2016-10-25 2:01 ` [PATCH v3 0/7] megaraid_sas: Updates for scsi-next Martin K. Petersen
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=60504200-bdda-ec69-11e6-ab9f7894fef5@redhat.com \
--to=thenzl@redhat.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sumit.saxena@broadcom.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.