All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Charkov <alchark@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: "Janorkar, Mayuresh" <mayur@ti.com>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"vt8500-wm8505-linux-kernel@googlegroups.com" 
	<vt8500-wm8505-linux-kernel@googlegroups.com>
Subject: Re: [PATCH 2/2] fbdev: Modify vsync timing calculation in wm8505fb
Date: Mon, 20 Dec 2010 19:04:53 +0300	[thread overview]
Message-ID: <AANLkTik9kD3gW1dQ6xe-jpyK9RQxOQJofekaO9Z9FXcC@mail.gmail.com> (raw)
In-Reply-To: <20101220160018.GE26766@linux-sh.org>

2010/12/20 Paul Mundt <lethal@linux-sh.org>:
> On Mon, Dec 20, 2010 at 04:09:57PM +0300, Alexey Charkov wrote:
>> This removes the '+1' in vsync timing calculation for wm8505fb to
>> directly use values provided from the board setup code.
>>
>> Signed-off-by: Alexey Charkov <alchark@gmail.com>
>
> This is queued for .37, thanks.
>

Paul, in fact, relevant code is only scheduled for merge in .38 (it is
in linux-next right now). This does not apply to .37.

Thanks,
Alexey

WARNING: multiple messages have this Message-ID (diff)
From: Alexey Charkov <alchark@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: "Janorkar, Mayuresh" <mayur@ti.com>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"vt8500-wm8505-linux-kernel@googlegroups.com"
	<vt8500-wm8505-linux-kernel@googlegroups.com>
Subject: Re: [PATCH 2/2] fbdev: Modify vsync timing calculation in wm8505fb
Date: Mon, 20 Dec 2010 16:04:53 +0000	[thread overview]
Message-ID: <AANLkTik9kD3gW1dQ6xe-jpyK9RQxOQJofekaO9Z9FXcC@mail.gmail.com> (raw)
In-Reply-To: <20101220160018.GE26766@linux-sh.org>

2010/12/20 Paul Mundt <lethal@linux-sh.org>:
> On Mon, Dec 20, 2010 at 04:09:57PM +0300, Alexey Charkov wrote:
>> This removes the '+1' in vsync timing calculation for wm8505fb to
>> directly use values provided from the board setup code.
>>
>> Signed-off-by: Alexey Charkov <alchark@gmail.com>
>
> This is queued for .37, thanks.
>

Paul, in fact, relevant code is only scheduled for merge in .38 (it is
in linux-next right now). This does not apply to .37.

Thanks,
Alexey

  reply	other threads:[~2010-12-20 16:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 18:13 [PATCH] fbdev: Minor cleanup in WM8505-related code Alexey Charkov
2010-12-19 18:13 ` Alexey Charkov
2010-12-20  5:06 ` Janorkar, Mayuresh
2010-12-20  5:18   ` Janorkar, Mayuresh
2010-12-20 13:03   ` [PATCH 1/2] " Alexey Charkov
2010-12-20 13:03     ` Alexey Charkov
2010-12-20 13:09     ` [PATCH 2/2] fbdev: Modify vsync timing calculation in wm8505fb Alexey Charkov
2010-12-20 13:09       ` Alexey Charkov
2010-12-20 16:00       ` Paul Mundt
2010-12-20 16:00         ` Paul Mundt
2010-12-20 16:04         ` Alexey Charkov [this message]
2010-12-20 16:04           ` Alexey Charkov
2010-12-20 16:05           ` Paul Mundt
2010-12-20 16:05             ` Paul Mundt
2010-12-20 16:00     ` [PATCH 1/2] fbdev: Minor cleanup in WM8505-related code Paul Mundt
2010-12-20 16:00       ` Paul Mundt

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=AANLkTik9kD3gW1dQ6xe-jpyK9RQxOQJofekaO9Z9FXcC@mail.gmail.com \
    --to=alchark@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mayur@ti.com \
    --cc=vt8500-wm8505-linux-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.