From: Joe Perches <joe@perches.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] block: skd_main: Neaten pr_debug uses by adding and using skd_dbg
Date: Sun, 14 Aug 2016 19:59:15 -0700 [thread overview]
Message-ID: <1471229955.4075.63.camel@perches.com> (raw)
In-Reply-To: <201608151059.XJYZ9DEW%fengguang.wu@intel.com>
On Mon, 2016-08-15 at 10:53 +0800, kbuild test robot wrote:
> Hi Joe,
Hi Fengguang.
None of these are "new" errors, it's just using a new
and different call.
I'm not suggesting these shouldn't be fixed later,
just that these shouldn't be fixed in this specific
patch as it would intermix a style with a fix patch.
cheers, Joe
next prev parent reply other threads:[~2016-08-15 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 2:16 [PATCH 0/2] block: skd_main: Neatening and object size reduction Joe Perches
2016-08-15 2:16 ` [PATCH 1/2] block: skd_main: Neaten pr_debug uses by adding and using skd_dbg Joe Perches
2016-08-15 2:53 ` kbuild test robot
2016-08-15 2:59 ` Joe Perches [this message]
2016-08-15 2:16 ` [PATCH 2/2] block: skd_main: Reduce dynamic_debug size Joe Perches
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=1471229955.4075.63.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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