All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Schremmer, Steven" <Steve.Schremmer@netapp.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
	Martin Wilck <mwilck@suse.com>
Cc: DM-DEVEL ML <dm-devel@redhat.com>,
	"Schremmer, Steven" <Steve.Schremmer@netapp.com>,
	ng-eseries-upstream-maintainers
	<ng-eseries-upstream-maintainers@netapp.com>
Subject: Re: [dm-devel] [PATCH resend] multipath-tools: delete duplicate RDAC maintainer entries
Date: Thu, 2 Dec 2021 14:23:26 +0000	[thread overview]
Message-ID: <SA1PR06MB8198B615586A2698D7E72BBE8C699@SA1PR06MB8198.namprd06.prod.outlook.com> (raw)
In-Reply-To: <7514be21-8209-f3ab-2d83-4f8639e53458@gmail.com>

> From: Xose Vazquez Perez <xose.vazquez@gmail.com>
> Sent: Thursday, December 2, 2021 6:42 AM
> 
> On 12/2/21 08:56, Martin Wilck wrote:
> 
> >
> > I'd like to have this acked by Netapp before merging it. Actually, I'd
> > prefer to have it acked by Fujitsu and Lenovo, too, but we don't have
> > contact addresses for them, so be it.
> >
> > My €0.02: I'd rather not have this, because it's not obvious to
> > everybody that these arrays are actually Netapp systems and are thus
> > maintained not by their vendors but Netapp.
> 
> There are 25 RDAC arrays in hwtable, only two of them(those included in
> the patch) and the NetApp one have a "Maintainer" entry.
> And they can easily identified, .checker_name and .prio_name are RDAC.

NetApp would like those Maintainer entries to remain in the file as we have
agreements with Fujitsu and Lenovo to handle it this way.

Thanks,
Steve

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2021-12-03  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 22:35 [dm-devel] [PATCH resend] multipath-tools: add DellEMC/ME4 (PowerVault ME4) to hardware table Xose Vazquez Perez
2021-12-01 22:35 ` [dm-devel] [PATCH resend] multipath-tools: delete duplicate RDAC maintainer entries Xose Vazquez Perez
2021-12-02  7:56   ` Martin Wilck
2021-12-02 12:41     ` Xose Vazquez Perez
2021-12-02 14:23       ` Schremmer, Steven [this message]
2021-12-01 22:35 ` [dm-devel] [PATCH resend] multipath-tools: dm-devel is a closed ml Xose Vazquez Perez
2021-12-02  7:45   ` Martin Wilck
2021-12-03 18:17     ` Xose Vazquez Perez
2021-12-06 10:16       ` Martin Wilck
2021-12-01 22:35 ` [dm-devel] [PATCH resend] multipath-tools: remove Hannes as IBM arrays maintainer Xose Vazquez Perez

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=SA1PR06MB8198B615586A2698D7E72BBE8C699@SA1PR06MB8198.namprd06.prod.outlook.com \
    --to=steve.schremmer@netapp.com \
    --cc=dm-devel@redhat.com \
    --cc=mwilck@suse.com \
    --cc=ng-eseries-upstream-maintainers@netapp.com \
    --cc=xose.vazquez@gmail.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.