From: Joe Perches <joe@perches.com>
To: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] framebuffer: Use fb_<level>
Date: Sun, 13 Oct 2013 17:39:52 +0000 [thread overview]
Message-ID: <1381685992.8864.32.camel@joe-AO722> (raw)
In-Reply-To: <8e7d2ced3f358961988c2602b8d1dff673f569c0.1379640011.git.joe@perches.com>
On Thu, 2013-09-19 at 18:35 -0700, Joe Perches wrote:
> Neaten and shorten the code using the new fb_<level> macros.
[]
> 59 files changed, 186 insertions(+), 224 deletions(-)
ping?
next prev parent reply other threads:[~2013-10-13 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 1:35 [PATCH 1/2] framebuffer: Add fb_<level> convenience logging macros Joe Perches
2013-09-20 1:35 ` [PATCH 2/2] framebuffer: Use fb_<level> Joe Perches
2013-10-13 17:39 ` Joe Perches [this message]
2013-10-13 17:39 ` [PATCH 1/2] framebuffer: Add fb_<level> convenience logging macros Joe Perches
2013-10-29 10:56 ` 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=1381685992.8864.32.camel@joe-AO722 \
--to=joe@perches.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).