From: Jonathan Corbet <corbet@lwn.net>
To: Shayenne Moura <shayenneluzmoura@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/doc: Remove solved KMS cleanup task
Date: Fri, 8 Feb 2019 12:47:11 -0700 [thread overview]
Message-ID: <20190208124711.030102e0@lwn.net> (raw)
In-Reply-To: <20190208153539.esik2dy7xvoi4p4e@smtp.gmail.com>
On Fri, 8 Feb 2019 13:35:39 -0200
Shayenne Moura <shayenneluzmoura@gmail.com> wrote:
> Remove KMS cleanup task from documentation solved by patchset
> https://patchwork.freedesktop.org/series/54310/
>
> Signed-off-by: Shayenne Moura <shayenneluzmoura@gmail.com>
This seems like a worthy change, but Documentation/gpu is managed by the
DRM maintainers. Could I ask you to resend the patch to them instead?
You can find the relevant addresses in the MAINTAINERS file or with
scripts/get_maintainer.pl.
Thanks,
jon
next prev parent reply other threads:[~2019-02-08 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 15:35 [PATCH] drm/doc: Remove solved KMS cleanup task Shayenne Moura
2019-02-08 19:47 ` Jonathan Corbet [this message]
2019-02-08 19:53 Shayenne Moura
2019-02-11 8:30 ` Daniel Vetter
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=20190208124711.030102e0@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shayenneluzmoura@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 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).