From: Sean Paul <sean@poorly.run>
To: Eric Engestrom <eric.engestrom@intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH libdrm] headers/README: fix/add link to drm-next
Date: Tue, 18 Sep 2018 11:37:02 -0400 [thread overview]
Message-ID: <20180918153702.GR188300@art_vandelay> (raw)
In-Reply-To: <20180918152437.26624-1-eric.engestrom@intel.com>
On Tue, Sep 18, 2018 at 04:24:37PM +0100, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
> ---
> include/drm/README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/drm/README b/include/drm/README
> index 521630db8b4c52749188..ea2320cc9e7728a9c08b 100644
> --- a/include/drm/README
> +++ b/include/drm/README
> @@ -71,7 +71,7 @@ Note: One should not do _any_ changes to the files apart from the steps below.
>
> In order to update the files do the following:
> - Switch to a Linux kernel tree/branch which is not rebased.
> -For example: airlied/drm-next
> + For example: drm-next (https://cgit.freedesktop.org/drm/drm)
> - Install the headers via `make headers_install' to a separate location.
> - Copy the drm header[s] + git add + git commit.
> - Note: Your commit message must include:
> --
> Cheers,
> Eric
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-09-18 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 15:24 [PATCH libdrm] headers/README: fix/add link to drm-next Eric Engestrom
2018-09-18 15:37 ` Sean Paul [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=20180918153702.GR188300@art_vandelay \
--to=sean@poorly.run \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@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