From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PULL for v3.6] SH Mobile LCDC fixes and planes support
Date: Wed, 20 Jun 2012 08:31:18 +0000 [thread overview]
Message-ID: <1370110.yCkUojHsRN@avalon> (raw)
In-Reply-To: <3246665.HJN7RE5zfe@avalon>
Hi Florian,
On Wednesday 20 June 2012 01:01:31 Florian Tobias Schandinat wrote:
> On 06/16/2012 02:07 PM, Laurent Pinchart wrote:
> > Hi Florian,
> >
> > Could you please pull the following LCDC patches ?
>
> looks good, except...
>
> > The following changes since commit
b67989515defba7412acff01162e5bb1f0f5923a:
> > video: s3c-fb: fix possible division by zero in s3c_fb_calc_pixclk
> >
> > (2012-06-13 17:34:16 +0000)
> >
> > are available in the git repository at:
> > git://linuxtv.org/pinchartl/fbdev.git planes
> >
> > Guennadi Liakhovetski (1):
> > fbdev: sh_mipi_dsi: fix a section mismatch
> >
> > Laurent Pinchart (4):
> > fbdev: sh_mobile_lcdc: Don't confuse line size with pitch
>
> ...for this patch it would have been better if you based your work on a
> more recent tree of Linus that already contains it instead of asking me
> to pull it again [I now forwarded my fbdev-next to -rc3]. It's not a big
> issue as git handles such situations but pushing patches around that are
> essentially nops should be avoided I think. Well, if you decide to fix
> it I'd be happy, otherwise I'll pull this in a few days nonetheless.
Sorry about that. I've rebased the branch on top of the latest fbdev-next and
pushed it to git://linuxtv.org/pinchartl/fbdev.git planes, that no-op patches
isn't present anymore.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-06-20 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 14:07 [PULL for v3.6] SH Mobile LCDC fixes and planes support Laurent Pinchart
2012-06-20 1:01 ` Florian Tobias Schandinat
2012-06-20 8:31 ` Laurent Pinchart [this message]
2012-06-24 21:01 ` Florian Tobias Schandinat
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=1370110.yCkUojHsRN@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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