From: ezequiel@vanguardiasur.com.ar (Ezequiel García)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RESEND 0/9] drm: tilcdc driver fixes
Date: Wed, 2 Jul 2014 17:38:58 -0300 [thread overview]
Message-ID: <20140702203858.GA9576@arch.cereza> (raw)
In-Reply-To: <CAPM=9tzQR446Xc2xnrSOGa+VetO44KskMFrkPqbatwsmv1dHXQ@mail.gmail.com>
On 02 Jul 02:08 PM, Dave Airlie wrote:
> On 2 July 2014 12:31, Darren Etheridge <detheridge@ti.com> wrote:
> > On 07/01/2014 06:39 PM, Guido Mart?nez wrote:
> >>
> >> On Fri, Jun 27, 2014 at 05:08:51PM -0500, Darren Etheridge wrote:
> >>>
> >>> [snip]
> >>>
> >>> Otherwise I think this is a good and useful patch series.
> >>
> >> It that a Tested-by tag? :)
> >
> >
> > Sure - I would prefer that the WARN_ON was silenced when the tilcdc module
> > is removed, but the series adds improvements over what is there now. I have
> > tested it across a few variants of AM335x boards and attached display
> > hardware in both module form and built-in to the kernel, therefore:
> >
> > Tested-by: Darren Etheridge <detheridge@ti.com>
>
> Has someone gathered that tags and put these in a git tree by any chance?
>
I don't think anyone has. Is that a problem?
If you need a pull request with these, I can prepare something in bitbucket.
Would that work you?
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2014-07-02 20:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1402110128-30471-1-git-send-email-guido@vanguardiasur.com.ar>
2014-06-17 14:17 ` [PATCH/RESEND 0/9] drm: tilcdc driver fixes Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 1/9] drm/i2c: tda998x: move drm_i2c_encoder_destroy call Guido Martínez
2014-06-24 16:38 ` Russell King - ARM Linux
2014-06-25 3:55 ` Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 2/9] drm/tilcdc: panel: fix dangling sysfs connector node Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 3/9] drm/tilcdc: slave: " Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 4/9] drm/tilcdc: tfp410: " Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 5/9] drm/tilcdc: panel: fix leak when unloading the module Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 6/9] drm/tilcdc: fix release order on exit Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 7/9] drm/tilcdc: fix double kfree Guido Martínez
2014-06-17 14:17 ` [PATCH/RESEND 8/9] drm/tilcdc: remove submodule destroy calls Guido Martínez
2014-06-24 22:06 ` Darren Etheridge
2014-06-25 3:53 ` Guido Martínez
2014-06-25 14:53 ` Ezequiel García
2014-06-17 14:17 ` [PATCH/RESEND 9/9] drm/tilcdc: replace late_initcall with module_init Guido Martínez
2014-06-24 22:04 ` Darren Etheridge
2014-06-25 13:00 ` Russell King - ARM Linux
2014-06-25 13:13 ` Russell King - ARM Linux
2014-06-25 14:32 ` Ezequiel García
2014-06-25 14:46 ` Russell King - ARM Linux
2014-06-25 15:48 ` Ezequiel García
2014-06-19 13:41 ` [PATCH/RESEND 0/9] drm: tilcdc driver fixes Darren Etheridge
2014-06-19 16:25 ` Guido Martínez
2014-06-24 0:26 ` Guido Martínez
2014-06-27 22:08 ` Darren Etheridge
2014-06-28 10:51 ` Rob Clark
2014-07-08 10:03 ` Daniel Vetter
2014-07-01 23:39 ` Guido Martínez
2014-07-02 2:31 ` Darren Etheridge
2014-07-02 4:08 ` Dave Airlie
2014-07-02 20:38 ` Ezequiel García [this message]
2014-07-08 1:32 ` Dave Airlie
2014-07-01 23:52 ` Guido Martínez
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=20140702203858.GA9576@arch.cereza \
--to=ezequiel@vanguardiasur.com.ar \
--cc=linux-arm-kernel@lists.infradead.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