From: Michael Ellerman <mpe@ellerman.id.au>
To: Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Bad file pattern in MAINTAINERS section 'IBM Power Virtual Accelerator Switchboard'
Date: Wed, 27 Mar 2019 22:39:11 +1100 [thread overview]
Message-ID: <87k1gko8bk.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190325233521.31094-1-joe@perches.com>
Joe Perches <joe@perches.com> writes:
> A file pattern line in this section of the MAINTAINERS file in linux-next
> does not have a match in the linux source files.
>
> This could occur because a matching filename was never added, was deleted
> or renamed in some other commit.
I think it was removed before the final submission.
> The commits that added and if found renamed or removed the file pattern
> are shown below.
>
> Please fix this defect appropriately.
Sukadev can you send me a patch to fix it please?
cheers
> 1: ---------------------------------------------------------------------------
>
> linux-next MAINTAINERS section:
>
> 7396 IBM Power Virtual Accelerator Switchboard
> 7397 M: Sukadev Bhattiprolu
> 7398 L: linuxppc-dev@lists.ozlabs.org
> 7399 S: Supported
> 7400 F: arch/powerpc/platforms/powernv/vas*
> 7401 F: arch/powerpc/platforms/powernv/copy-paste.h
> 7402 F: arch/powerpc/include/asm/vas.h
> --> 7403 F: arch/powerpc/include/uapi/asm/vas.h
>
> 2: ---------------------------------------------------------------------------
>
> The most recent commit that added or modified file pattern 'arch/powerpc/include/uapi/asm/vas.h':
>
> commit 4dea2d1a927c61114a168d4509b56329ea6effb7
> Author: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> Date: Mon Aug 28 23:23:33 2017 -0700
>
> powerpc/powernv/vas: Define vas_init() and vas_exit()
>
> Implement vas_init() and vas_exit() functions for a new VAS module.
> This VAS module is essentially a library for other device drivers
> and kernel users of the NX coprocessors like NX-842 and NX-GZIP.
> In the future this will be extended to add support for user space
> to access the NX coprocessors.
>
> VAS is currently only supported with 64K page size.
>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>
> .../devicetree/bindings/powerpc/ibm,vas.txt | 22 +++
> MAINTAINERS | 8 ++
> arch/powerpc/platforms/powernv/Kconfig | 14 ++
> arch/powerpc/platforms/powernv/Makefile | 1 +
> arch/powerpc/platforms/powernv/vas-window.c | 19 +++
> arch/powerpc/platforms/powernv/vas.c | 151 +++++++++++++++++++++
> arch/powerpc/platforms/powernv/vas.h | 2 +
> 7 files changed, 217 insertions(+)
>
> 3: ---------------------------------------------------------------------------
>
> No commit with file pattern 'arch/powerpc/include/uapi/asm/vas.h' was found
prev parent reply other threads:[~2019-03-27 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 23:35 ` Bad file pattern in MAINTAINERS section 'IBM Power Virtual Accelerator Switchboard' Joe Perches
2019-03-25 23:38 ` Joe Perches
2019-03-27 11:39 ` Michael Ellerman [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=87k1gko8bk.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sukadev@linux.vnet.ibm.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