From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Paul Mundt <lethal@linux-sh.org>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH 1/3] OMAP: VRAM: improve VRAM error prints
Date: Wed, 10 Nov 2010 12:04:14 +0000 [thread overview]
Message-ID: <1289390654.3297.202.camel@tubuntu> (raw)
In-Reply-To: <20101110115148.GA2120@linux-sh.org>
On Wed, 2010-11-10 at 12:51 +0100, ext Paul Mundt wrote:
> On Wed, Nov 10, 2010 at 11:45:18AM +0200, Tomi Valkeinen wrote:
> > Improve the error prints to give more information about the offending
> > address & size.
> >
> > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@nokia.com>
>
> 1-3 queued for .37, thanks.
They were just for review =).
If it's ok to you, I'll pick all OMAP display related patches to my
tree, and send you a pull request when I think they are ready.
But for these three patches it's ok if you already queued them: they are
quite high priority, as the OMAP framebuffer doesn't work at all without
the second patch.
Tomi
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Paul Mundt <lethal@linux-sh.org>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH 1/3] OMAP: VRAM: improve VRAM error prints
Date: Wed, 10 Nov 2010 14:04:14 +0200 [thread overview]
Message-ID: <1289390654.3297.202.camel@tubuntu> (raw)
In-Reply-To: <20101110115148.GA2120@linux-sh.org>
On Wed, 2010-11-10 at 12:51 +0100, ext Paul Mundt wrote:
> On Wed, Nov 10, 2010 at 11:45:18AM +0200, Tomi Valkeinen wrote:
> > Improve the error prints to give more information about the offending
> > address & size.
> >
> > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@nokia.com>
>
> 1-3 queued for .37, thanks.
They were just for review =).
If it's ok to you, I'll pick all OMAP display related patches to my
tree, and send you a pull request when I think they are ready.
But for these three patches it's ok if you already queued them: they are
quite high priority, as the OMAP framebuffer doesn't work at all without
the second patch.
Tomi
next prev parent reply other threads:[~2010-11-10 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 9:45 [PATCH 1/3] OMAP: VRAM: improve VRAM error prints Tomi Valkeinen
2010-11-10 9:45 ` Tomi Valkeinen
2010-11-10 9:45 ` [PATCH 2/3] OMAP: VRAM: Fix boot-time memory allocation Tomi Valkeinen
2010-11-10 9:45 ` Tomi Valkeinen
2010-11-17 18:08 ` Felipe Contreras
2010-11-17 18:08 ` Felipe Contreras
2010-11-10 9:45 ` [PATCH 3/3] OMAP: DSS: Fix documentation regarding 'vram' kernel parameter Tomi Valkeinen
2010-11-10 9:45 ` Tomi Valkeinen
2010-11-10 11:51 ` [PATCH 1/3] OMAP: VRAM: improve VRAM error prints Paul Mundt
2010-11-10 11:51 ` Paul Mundt
2010-11-10 12:04 ` Tomi Valkeinen [this message]
2010-11-10 12:04 ` Tomi Valkeinen
2010-11-10 12:08 ` Paul Mundt
2010-11-10 12:08 ` 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=1289390654.3297.202.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@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 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.