From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] video: mxsfb: Adapt to new videomode API
Date: Fri, 12 Apr 2013 09:25:39 +0300 [thread overview]
Message-ID: <5167A8E3.7070109@ti.com> (raw)
In-Reply-To: <20130412020202.GC16970@S2101-09.ap.freescale.net>
On 2013-04-12 05:02, Shawn Guo wrote:
> On Wed, Apr 10, 2013 at 09:36:31AM -0300, Fabio Estevam wrote:
>> On Wed, Apr 10, 2013 at 5:27 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>>
>>> The mxsfb.c driver in my tree does not contain such code. Where is this
>>> patch meant to be applied?
>>
>> linux-next 20130408 is broken for mxs without this fix. Maybe Shawn can take it?
>
> I will take it and send it during -rc when Tomi's patches hit mainline.
> But I have a couple trivial comments on the patch. I'm replying to the
> patch.
Fine by me, but wouldn't it be easier to get the mxsfb driver changes
along with other fbdev changes via my tree? Or do you have dependencies
to arch changes or such in the mxsfb changes?
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130412/1a249917/attachment.sig>
next prev parent reply other threads:[~2013-04-12 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:16 [PATCH] video: mxsfb: Adapt to new videomode API Fabio Estevam
2013-04-10 8:27 ` Tomi Valkeinen
2013-04-10 12:36 ` Fabio Estevam
2013-04-12 2:02 ` Shawn Guo
2013-04-12 6:25 ` Tomi Valkeinen [this message]
2013-04-12 6:30 ` Shawn Guo
2013-04-12 6:32 ` Tomi Valkeinen
2013-04-12 2:11 ` Shawn Guo
2013-04-12 2:24 ` Fabio Estevam
2013-04-12 2:55 ` Shawn Guo
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=5167A8E3.7070109@ti.com \
--to=tomi.valkeinen@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).