From: Benoit Parrot <bparrot@ti.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<tomi.valkeinen@ti.com>, <laurent.pinchart@ideasonboard.com>,
<peter.ujfalusi@ti.com>, <praneeth@ti.com>,
<yamonkar@cadence.com>, <sjakhade@cadence.com>,
<sam@ravnborg.org>, <robh+dt@kernel.org>, <maxime@cerno.tech>
Subject: Re: [PATCH v5 5/5] MAINTAINERS: add entry for tidss
Date: Mon, 13 Jan 2020 16:06:50 -0600 [thread overview]
Message-ID: <20200113220650.p4dhulzhdhm6oxtm@ti.com> (raw)
In-Reply-To: <fdb8bc85150c39e039869974b4160a36c71ec9b5.1576857145.git.jsarha@ti.com>
Jyri Sarha <jsarha@ti.com> wrote on Fri [2019-Dec-20 17:55:13 +0200]:
> Add entry for tidss DRM driver.
>
> Version history:
>
> v2: no change
>
> v3: - Move tidss entry after omapdrm
> - Add "T: git git://anongit.freedesktop.org/drm/drm-misc"
>
> v4: no change
>
> v5: no change
>
> Signed-off-by: Jyri Sarha <jsarha@ti.com>
Reviewed-by: Benoit Parrot <bparrot@ti.com>
prev parent reply other threads:[~2020-01-13 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 15:55 [PATCH v5 0/5] drm/tidss: New driver for TI Keystone platform Display SubSystem Jyri Sarha
2019-12-20 15:55 ` [PATCH v5 1/5] dt-bindings: display: ti,k2g-dss: Add dt-schema yaml binding Jyri Sarha
2019-12-20 15:56 ` Maxime Ripard
2019-12-26 23:05 ` Rob Herring
2020-01-13 22:04 ` Benoit Parrot
2019-12-20 15:55 ` [PATCH v5 2/5] dt-bindings: display: ti,am65x-dss: " Jyri Sarha
2019-12-20 15:57 ` Maxime Ripard
2019-12-26 23:07 ` Rob Herring
2020-01-13 22:04 ` Benoit Parrot
2019-12-20 15:55 ` [PATCH v5 3/5] dt-bindings: display: ti,j721e-dss: " Jyri Sarha
2019-12-20 15:57 ` Maxime Ripard
2019-12-26 23:11 ` Rob Herring
2020-01-13 22:05 ` Benoit Parrot
2019-12-20 15:55 ` [PATCH v5 4/5] drm/tidss: New driver for TI Keystone platform Display SubSystem Jyri Sarha
2020-01-13 22:06 ` Benoit Parrot
2019-12-20 15:55 ` [PATCH v5 5/5] MAINTAINERS: add entry for tidss Jyri Sarha
2020-01-13 22:06 ` Benoit Parrot [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=20200113220650.p4dhulzhdhm6oxtm@ti.com \
--to=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=maxime@cerno.tech \
--cc=peter.ujfalusi@ti.com \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sjakhade@cadence.com \
--cc=tomi.valkeinen@ti.com \
--cc=yamonkar@cadence.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).