From: Paul Mundt <lethal@linux-sh.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, g.liakhovetski@gmx.de,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/05] fbdev: SH-Mobile MIPI-DSI Update
Date: Fri, 19 Nov 2010 08:05:36 +0000 [thread overview]
Message-ID: <20101119080536.GC28165@linux-sh.org> (raw)
In-Reply-To: <20101117064405.18139.57035.sendpatchset@t400s>
On Wed, Nov 17, 2010 at 03:44:05PM +0900, Magnus Damm wrote:
> fbdev: SH-Mobile MIPI-DSI Update
>
> [PATCH 01/05] fbdev: sh_mipi_dsi: Remove request/release mem region
> [PATCH 02/05] fbdev: sh_mipi_dsi: Make use of register names
> [PATCH 03/05] ARM: mach-shmobile: Extend AP4EVB MIPI-DSI resources
> [PATCH 04/05] fbdev: sh_mipi_dsi: Require two I/O resources
> [PATCH 05/05] fbdev: sh_mipi_dsi: Allow LCDC board callbacks
>
Ok, I've applied the updated version of this with 01/05 dropped and 04/05
replaced with the V2 version. In the future make sure to Cc the
linux-fbdev list, too.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, g.liakhovetski@gmx.de,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/05] fbdev: SH-Mobile MIPI-DSI Update
Date: Fri, 19 Nov 2010 17:05:36 +0900 [thread overview]
Message-ID: <20101119080536.GC28165@linux-sh.org> (raw)
In-Reply-To: <20101117064405.18139.57035.sendpatchset@t400s>
On Wed, Nov 17, 2010 at 03:44:05PM +0900, Magnus Damm wrote:
> fbdev: SH-Mobile MIPI-DSI Update
>
> [PATCH 01/05] fbdev: sh_mipi_dsi: Remove request/release mem region
> [PATCH 02/05] fbdev: sh_mipi_dsi: Make use of register names
> [PATCH 03/05] ARM: mach-shmobile: Extend AP4EVB MIPI-DSI resources
> [PATCH 04/05] fbdev: sh_mipi_dsi: Require two I/O resources
> [PATCH 05/05] fbdev: sh_mipi_dsi: Allow LCDC board callbacks
>
Ok, I've applied the updated version of this with 01/05 dropped and 04/05
replaced with the V2 version. In the future make sure to Cc the
linux-fbdev list, too.
next prev parent reply other threads:[~2010-11-19 8:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 6:44 [PATCH 00/05] fbdev: SH-Mobile MIPI-DSI Update Magnus Damm
2010-11-17 6:44 ` Magnus Damm
2010-11-17 6:44 ` [PATCH 01/05] fbdev: sh_mipi_dsi: Remove request/release mem region Magnus Damm
2010-11-17 6:44 ` Magnus Damm
2010-11-17 7:25 ` Paul Mundt
2010-11-17 7:25 ` Paul Mundt
2010-11-17 8:51 ` Magnus Damm
2010-11-17 8:51 ` Magnus Damm
2010-11-17 9:30 ` Paul Mundt
2010-11-17 9:30 ` Paul Mundt
2010-11-17 10:06 ` Magnus Damm
2010-11-17 10:06 ` Magnus Damm
2010-11-17 6:44 ` [PATCH 02/05] fbdev: sh_mipi_dsi: Make use of register names Magnus Damm
2010-11-17 6:44 ` Magnus Damm
2010-11-17 6:44 ` [PATCH 03/05] ARM: mach-shmobile: Extend AP4EVB MIPI-DSI resources Magnus Damm
2010-11-17 6:44 ` Magnus Damm
2010-11-17 6:44 ` [PATCH 04/05] fbdev: sh_mipi_dsi: Require two I/O resources Magnus Damm
2010-11-17 6:44 ` Magnus Damm
2010-11-17 6:44 ` [PATCH 05/05] fbdev: sh_mipi_dsi: Allow LCDC board callbacks Magnus Damm
2010-11-17 6:44 ` Magnus Damm
2010-11-17 7:48 ` [PATCH 00/05] fbdev: SH-Mobile MIPI-DSI Update Guennadi Liakhovetski
2010-11-17 7:48 ` Guennadi Liakhovetski
2010-11-19 8:05 ` Paul Mundt [this message]
2010-11-19 8:05 ` 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=20101119080536.GC28165@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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.