From: Sam Ravnborg <sam@ravnborg.org>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
Russell King <linux+etnaviv@armlinux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
The etnaviv authors <etnaviv@lists.freedesktop.org>
Subject: Re: [PATCH v2 0/6] update hwdw for gc400
Date: Mon, 6 Jan 2020 17:28:02 +0100 [thread overview]
Message-ID: <20200106162802.GA20675@ravnborg.org> (raw)
In-Reply-To: <CAH9NwWd7C+DzAKe97kURm=sGjDH+KQJOif3j=w6K+99xmYGncQ@mail.gmail.com>
Hi Christian.
> To be honest.. I forgot the change log thing this time - sorry.
It was small changes - so no worries.
> So the rule
> is to have the change log in the normal commit message?
This is what Danial Vetter tell people - but it is not documented as
far as I can tell.
> Funny - Lucas told me something different:
>
> "Please move those changelogs below the 3 dashes, so they don't end up
> in the commit message. They don't really add any value to the
> persistent kernel history."
> https://lkml.org/lkml/2019/9/13/107
Lucas is maintainer of etnaviv driver - so do as he says.
Keep up the good work on etnaviv in mesa too!
Sam
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
The etnaviv authors <etnaviv@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Russell King <linux+etnaviv@armlinux.org.uk>
Subject: Re: [PATCH v2 0/6] update hwdw for gc400
Date: Mon, 6 Jan 2020 17:28:02 +0100 [thread overview]
Message-ID: <20200106162802.GA20675@ravnborg.org> (raw)
In-Reply-To: <CAH9NwWd7C+DzAKe97kURm=sGjDH+KQJOif3j=w6K+99xmYGncQ@mail.gmail.com>
Hi Christian.
> To be honest.. I forgot the change log thing this time - sorry.
It was small changes - so no worries.
> So the rule
> is to have the change log in the normal commit message?
This is what Danial Vetter tell people - but it is not documented as
far as I can tell.
> Funny - Lucas told me something different:
>
> "Please move those changelogs below the 3 dashes, so they don't end up
> in the commit message. They don't really add any value to the
> persistent kernel history."
> https://lkml.org/lkml/2019/9/13/107
Lucas is maintainer of etnaviv driver - so do as he says.
Keep up the good work on etnaviv in mesa too!
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-01-06 16:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 15:16 [PATCH v2 0/6] update hwdw for gc400 Christian Gmeiner
2020-01-06 15:16 ` Christian Gmeiner
2020-01-06 15:16 ` [PATCH v2 1/6] drm/etnaviv: update hardware headers from rnndb Christian Gmeiner
2020-01-06 15:16 ` Christian Gmeiner
2020-02-26 15:23 ` Lucas Stach
2020-02-26 15:23 ` Lucas Stach
2020-01-06 15:16 ` [PATCH v2 2/6] drm/etnaviv: determine product, customer and eco id Christian Gmeiner
2020-01-06 15:16 ` Christian Gmeiner
2020-01-06 15:16 ` [PATCH v2 3/6] drm/etnaviv: show identity information in debugfs Christian Gmeiner
2020-01-06 15:16 ` Christian Gmeiner
2020-01-06 15:16 ` [PATCH v2 4/6] drm/etnaviv: update gc7000 chip identity entry Christian Gmeiner
2020-01-06 15:16 ` Christian Gmeiner
2020-01-06 15:16 ` [PATCH v2 5/6] drm/etnaviv: update hwdb selection logic Christian Gmeiner
2020-01-06 15:16 ` Christian Gmeiner
2020-01-06 15:16 ` [PATCH v2 6/6] drm/etnaviv: add hwdb entry for gc400 found in STM32 Christian Gmeiner
2020-01-06 15:16 ` Christian Gmeiner
2020-01-06 15:36 ` [PATCH v2 0/6] update hwdw for gc400 Sam Ravnborg
2020-01-06 15:36 ` Sam Ravnborg
2020-01-06 16:01 ` Christian Gmeiner
2020-01-06 16:01 ` Christian Gmeiner
2020-01-06 16:28 ` Sam Ravnborg [this message]
2020-01-06 16:28 ` Sam Ravnborg
2020-02-24 13:16 ` Christian Gmeiner
2020-02-24 13:16 ` Christian Gmeiner
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=20200106162802.GA20675@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.