From: Alan Tull <atull@kernel.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>, Moritz Fischer <mdf@kernel.org>,
linux-fpga@vger.kernel.org
Subject: Re: [PATCH v3 21/27] MAINTAINERS: get rid of non-existing Documentation/fpga
Date: Thu, 14 Jun 2018 13:09:38 -0500 [thread overview]
Message-ID: <CANk1AXQwRpqR6LUTVRovcT7te=1q_2PQearZ1XMghhQUzLhxtA@mail.gmail.com> (raw)
In-Reply-To: <20180614135254.75cfc17d@coco.lan>
On Thu, Jun 14, 2018 at 11:52 AM, Mauro Carvalho Chehab
<mchehab+samsung@kernel.org> wrote:
> Em Thu, 14 Jun 2018 11:39:20 -0500
> Alan Tull <atull@kernel.org> escreveu:
>
>> On Thu, Jun 14, 2018 at 11:09 AM, Mauro Carvalho Chehab
>> <mchehab+samsung@kernel.org> wrote:
>> > This directory seems to have moved to a new place
>> > (Documentation/driver-api/fpga/), with is already at MAINTAINERS.
>> >
>> > So, get rid of the old location.
>>
>> Wow, you caught that fast!
>
> Just a coincidence :-) I had to rebase a pending patch series close to
> the end of the merge window.
>
> When I ran the check tool:
> ./scripts/documentation-file-ref-check
>
> It detected this.
Nice tool. Thanks for the explanation, it's always good to learn
about another one.
>
>> There's other documentation coming to this
>> directory soon. IMO we might as well leave it. We don't need to keep
>> adding and deleting this line from MAINTAINERS.
>
> Yeah, sure. I'll drop this hunk for v4.
>
Thanks!
>>
>> Also, why didn't you cc linux-fpga mailing list on this? I guess you
>> ran get_maintainer.pl after adding this patch? :)
>
> Yeah, that was the case. I also had to sanitize the c/c for this
> specific patch as get_maintainers.pl isn't good enough to check for
> MAINTAINERS access... it usually just get some random noise...
>
>>
>> Alan
>>
>> >
>> > Cc: Alan Tull <atull@kernel.org>
>> > Cc: Moritz Fischer <mdf@kernel.org>
>> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
>> > ---
>> > MAINTAINERS | 1 -
>> > 1 file changed, 1 deletion(-)
>> >
>> > diff --git a/MAINTAINERS b/MAINTAINERS
>> > index 783ce44b3e7a..67641f5bb373 100644
>> > --- a/MAINTAINERS
>> > +++ b/MAINTAINERS
>> > @@ -5632,7 +5632,6 @@ L: linux-fpga@vger.kernel.org
>> > S: Maintained
>> > T: git git://git.kernel.org/pub/scm/linux/kernel/git/atull/linux-fpga.git
>> > Q: http://patchwork.kernel.org/project/linux-fpga/list/
>> > -F: Documentation/fpga/
>> > F: Documentation/driver-api/fpga/
>> > F: Documentation/devicetree/bindings/fpga/
>> > F: drivers/fpga/
>> > --
>> > 2.17.1
>> >
>
>
>
> Thanks,
> Mauro
prev parent reply other threads:[~2018-06-14 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1528990947.git.mchehab+samsung@kernel.org>
[not found] ` <948d6c0304eecaf916d21af5cfb0be21df80ed42.1528990947.git.mchehab+samsung@kernel.org>
2018-06-14 16:39 ` [PATCH v3 21/27] MAINTAINERS: get rid of non-existing Documentation/fpga Alan Tull
2018-06-14 16:52 ` Mauro Carvalho Chehab
2018-06-14 18:09 ` Alan Tull [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='CANk1AXQwRpqR6LUTVRovcT7te=1q_2PQearZ1XMghhQUzLhxtA@mail.gmail.com' \
--to=atull@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=mdf@kernel.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).