From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Johan Hovold <jhovold@gmail.com>, Olof Johansson <olof@lixom.net>,
<FlorianSchandinat@gmx.de>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-fbdev@vger.kernel.org>,
<jacmet@sunsite.dk>
Subject: Re: [PATCH 0/5] at91: atmel_lcdfb: regression fixes and cpu_is removal
Date: Fri, 15 Mar 2013 11:16:17 +0100 [thread overview]
Message-ID: <5142F4F1.60006@atmel.com> (raw)
In-Reply-To: <201303142303.42283.arnd@arndb.de>
On 03/15/2013 12:03 AM, Arnd Bergmann :
> On Wednesday 13 March 2013, Nicolas Ferre wrote:
>> In case we end-up with an agreement on the path those fixes should
>> follow, here is the location of my updated material rebased on top of 3.9-rc2:
>>
>> The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
>>
>> Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
>>
>> are available in the git repository at:
>>
>> git://github.com/at91linux/linux-at91.git at91-3.9-fixesLCD
>>
>> for you to fetch changes up to bbd44f6bd9d1aa735b180b29b5719d63a8e87b55:
>>
>> ARM: at91/avr32/atmel_lcdfb: add platform device-id table (2013-03-13 11:05:12 +0100)
>>
>> ----------------------------------------------------------------
>> Johan Hovold (5):
>> atmel_lcdfb: fix 16-bpp modes on older SOCs
>> ARM: at91: fix LCD-wiring mode
>> ARM: at91/avr32/atmel_lcdfb: add bus-clock entry
>> atmel_lcdfb: move lcdcon2 register access to compute_hozval
>> ARM: at91/avr32/atmel_lcdfb: add platform device-id table
>>
>
> I have merged the first two patches into the fixes branch now, from up to commit
> 67cf9c0a. Please resubmit the remaining ones on top of this commit for 3.10, either
> through arm-soc or through the framebuffer tree.
Thanks a lot.
I have just sent the pull-request for remaining material. Tell me if it
is what you've expected.
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2013-03-15 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:35 [PATCH 0/5] at91: atmel_lcdfb: regression fixes and cpu_is removal Nicolas Ferre
2013-02-08 16:35 ` [PATCH 1/5] atmel_lcdfb: fix 16-bpp modes on older SOCs Nicolas Ferre
2013-02-08 16:35 ` [PATCH 2/5] ARM: at91/neocore926: fix LCD-wiring mode Nicolas Ferre
2013-02-08 16:35 ` [PATCH 3/5] ARM: at91/avr32/atmel_lcdfb: add bus-clock entry Nicolas Ferre
2013-02-08 16:35 ` [PATCH 4/5] atmel_lcdfb: move lcdcon2 register access to compute_hozval Nicolas Ferre
2013-02-08 16:35 ` [PATCH 5/5] ARM: at91/avr32/atmel_lcdfb: add platform device-id table Nicolas Ferre
2013-02-08 16:52 ` [PATCH 0/5] at91: atmel_lcdfb: regression fixes and cpu_is removal Jean-Christophe PLAGNIOL-VILLARD
2013-02-10 0:47 ` Olof Johansson
2013-02-10 18:45 ` Johan Hovold
2013-03-08 9:37 ` Nicolas Ferre
2013-03-13 10:12 ` Nicolas Ferre
2013-03-14 23:03 ` Arnd Bergmann
2013-03-15 10:16 ` Nicolas Ferre [this message]
2013-03-04 14:51 ` Johan Hovold
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=5142F4F1.60006@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=FlorianSchandinat@gmx.de \
--cc=arnd@arndb.de \
--cc=jacmet@sunsite.dk \
--cc=jhovold@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox