From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 00/29] Use display information in info not in var for panning
Date: Wed, 15 Jun 2011 06:14:07 +0000 [thread overview]
Message-ID: <20110615061404.GM17891@linux-sh.org> (raw)
In-Reply-To: <1308043507-11083-1-git-send-email-laurent.pinchart@ideasonboard.com>
On Tue, Jun 14, 2011 at 11:24:38AM +0200, Laurent Pinchart wrote:
> I've split the fixes in one patch per driver for easier review and handling of
> potential problems. The patches can be squashed together if needed. I've tried
> to CC individual driver maintainers when possible, and Acked-by lines received
> in reply to the first version have been included.
>
> Compared to v1, I've fixed a couple of subject lines that mentioned the wrong
> driver name, and replaced var->bits_per_pixel in the mx3fb driver.
>
> Not all patches have been tested on real hardware and acked. Geert Uytterhoeven
> acked the overall idea, and I believe the patches are now ready to be applied.
>
This seems like a good direction in general, so it's certainly with
proceeding with. I've applied the series to the fbdev/panning-fixes topic
branch, which I will subsequently merge so it's possible to get wider
coverage via -next.
Individual driver authors have had a few weeks to ack/nack accordingly,
so it's fairly reasonable to expect that you're not likely to be
collecting much more feedback before the whole thing gets merged anyways.
If it ends up horribly breaking a number of drivers then it's still
trivial to revert the branch merge and convert drivers incrementally, but
I don't expect that to really be a problem.
prev parent reply other threads:[~2011-06-15 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 9:24 [PATCH v2 00/29] Use display information in info not in var for panning Laurent Pinchart
2011-06-15 6:14 ` Paul Mundt [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=20110615061404.GM17891@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@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 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).