From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [GIT PULL] fbdev fixes for 3.19
Date: Mon, 29 Dec 2014 08:13:12 +0000 [thread overview]
Message-ID: <54A10D18.1060308@ti.com> (raw)
In-Reply-To: <20141223111250.GA30284@amd>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Hi,
On 23/12/14 13:12, Pavel Machek wrote:
>>> I test-merged 3315764efceaccfb02c7d4c99ef8eed6716cd861, and boom,
>>> video is gone.
>>
>> I reverted
>> 4b4123f0c7b02f7cf1a3189f967f079197578c3a..9051909e451a0368c95ccf74562adb53fd2719f8
>> in 3.19, and voila, video is back.
>
> Tomi?
>
> Your merge causes regression on my hardware. I'd expect some
> communication from you. If you don't have time right now, can we
> revert the merge until its fixed?
I've posted a fix on the "n900 regressions" thread.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [GIT PULL] fbdev fixes for 3.19
Date: Mon, 29 Dec 2014 10:13:12 +0200 [thread overview]
Message-ID: <54A10D18.1060308@ti.com> (raw)
In-Reply-To: <20141223111250.GA30284@amd>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Hi,
On 23/12/14 13:12, Pavel Machek wrote:
>>> I test-merged 3315764efceaccfb02c7d4c99ef8eed6716cd861, and boom,
>>> video is gone.
>>
>> I reverted
>> 4b4123f0c7b02f7cf1a3189f967f079197578c3a..9051909e451a0368c95ccf74562adb53fd2719f8
>> in 3.19, and voila, video is back.
>
> Tomi?
>
> Your merge causes regression on my hardware. I'd expect some
> communication from you. If you don't have time right now, can we
> revert the merge until its fixed?
I've posted a fix on the "n900 regressions" thread.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-29 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:41 [GIT PULL] fbdev fixes for 3.19 Tomi Valkeinen
2014-12-11 13:41 ` Tomi Valkeinen
2014-12-11 20:55 ` Linus Torvalds
2014-12-11 20:55 ` Linus Torvalds
2014-12-11 22:58 ` Rafael J. Wysocki
2014-12-11 22:58 ` Rafael J. Wysocki
2014-12-12 0:59 ` Rob Herring
2014-12-12 0:59 ` Rob Herring
2014-12-12 15:25 ` Rafael J. Wysocki
2014-12-12 15:25 ` Rafael J. Wysocki
2014-12-20 21:01 ` Pavel Machek
2014-12-20 21:01 ` Pavel Machek
2014-12-20 21:20 ` Pavel Machek
2014-12-20 21:20 ` Pavel Machek
2014-12-20 21:57 ` Pavel Machek
2014-12-20 21:57 ` Pavel Machek
2014-12-23 11:12 ` Pavel Machek
2014-12-23 11:12 ` Pavel Machek
2014-12-29 8:13 ` Tomi Valkeinen [this message]
2014-12-29 8:13 ` Tomi Valkeinen
2014-12-30 11:44 ` Tomi Valkeinen
2014-12-30 11:44 ` Tomi Valkeinen
2015-01-15 11:23 ` Tomi Valkeinen
2015-01-15 11:23 ` Tomi Valkeinen
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=54A10D18.1060308@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=broonie@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.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 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.