From: Joe Perches <joe@perches.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: Reduce code size of drm_err and DRM_DEBUG[_<FOO>] uses
Date: Tue, 04 Nov 2014 07:26:00 -0800 [thread overview]
Message-ID: <1415114760.24560.8.camel@perches.com> (raw)
In-Reply-To: <20141104085240.GA26941@phenom.ffwll.local>
On Tue, 2014-11-04 at 09:52 +0100, Daniel Vetter wrote:
> On Tue, Nov 04, 2014 at 12:03:46AM -0800, Joe Perches wrote:
> > Using %pf, __builtin_return_address(0) instead ofy
> > "%s", __func__ reduces code size by eliminating
> > a function argument.
[]
> I have an earlier version from you of this patch already, and it's in
> linux-next. And this patch here lacks the changelog indicating what
> changed exactly. Can you please rebase on top of linux-next and improve
> the commit message?
I was working on another tree and didn't
see the first patch. Ignore this please.
prev parent reply other threads:[~2014-11-04 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 8:03 [PATCH] drm: Reduce code size of drm_err and DRM_DEBUG[_<FOO>] uses Joe Perches
2014-11-04 8:52 ` Daniel Vetter
2014-11-04 15:26 ` Joe Perches [this message]
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=1415114760.24560.8.camel@perches.com \
--to=joe@perches.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox