From: Jon Derrick <jonathan.derrick@intel.com>
Cc: Jon Derrick <jonathan.derrick@intel.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
Scott Bauer <scott.bauer@intel.com>,
Rafael Antognolli <rafael.antognolli@intel.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCHv3 4/4] MAINTAINERS: Remove powerpc's opal match
Date: Wed, 15 Feb 2017 12:42:09 -0700 [thread overview]
Message-ID: <1487187731-10293-5-git-send-email-jonathan.derrick@intel.com> (raw)
In-Reply-To: <1487187731-10293-1-git-send-email-jonathan.derrick@intel.com>
PPC's 'opal' match pattern also matches block/sed-opal.c, where it looks
like the 'arch/powerpc' file pattern should be enough to match powerpc
opal code by itself. Remove the opal regex pattern from powerpc.
Signed-off-by: Jon Derrick <jonathan.derrick@intel.com>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index b983b25..430dd02 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7404,7 +7404,6 @@ F: drivers/pci/hotplug/pnv_php.c
F: drivers/pci/hotplug/rpa*
F: drivers/scsi/ibmvscsi/
F: tools/testing/selftests/powerpc
-N: opal
N: /pmac
N: powermac
N: powernv
--
1.8.3.1
next prev parent reply other threads:[~2017-02-15 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 19:42 [PATCHv3 0/4] OPAL patches Jon Derrick
2017-02-15 19:42 ` [PATCHv3 1/4] block/sed: Use ssize_t on atom parsers to return errors Jon Derrick
2017-02-15 21:04 ` Scott Bauer
2017-02-15 19:42 ` [PATCHv3 2/4] block/sed: Add helper to qualify response tokens Jon Derrick
2017-02-15 21:19 ` Scott Bauer
2017-02-15 19:42 ` [PATCHv3 3/4] block/sed: Check received header lengths Jon Derrick
2017-02-15 21:09 ` Scott Bauer
2017-02-15 19:42 ` Jon Derrick [this message]
2017-02-16 0:37 ` [PATCHv3 4/4] MAINTAINERS: Remove powerpc's opal match Stewart Smith
2017-02-16 1:00 ` Andrew Donnellan
2017-02-19 11:33 ` [PATCHv3,4/4] " Michael Ellerman
2017-02-16 5:23 ` [PATCHv3 4/4] " Michael Ellerman
2017-02-16 16:14 ` Jon Derrick
2017-02-17 16:40 ` Elliott, Robert (Persistent Memory)
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=1487187731-10293-5-git-send-email-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rafael.antognolli@intel.com \
--cc=scott.bauer@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox