From: Jani Nikula <jani.nikula@linux.intel.com>
To: Joe Perches <joe@perches.com>,
Eric Engestrom <eric.engestrom@imgtec.com>
Cc: Rob Clark <robdclark@gmail.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: drm_printer: add __printf validation
Date: Tue, 21 Feb 2017 10:26:14 +0200 [thread overview]
Message-ID: <87a89gkl09.fsf@intel.com> (raw)
In-Reply-To: <1487610643.2853.6.camel@perches.com>
On Mon, 20 Feb 2017, Joe Perches <joe@perches.com> wrote:
> On Mon, 2017-02-20 at 12:17 +0000, Eric Engestrom wrote:
>> On Wednesday, 2017-02-15 15:33:18 -0800, Joe Perches wrote:
>> > drm_printf does not currently use the compiler to verify
>> > format and arguments. Make it do so.
>> >
>> > Miscellanea:
>> >
>> > o Add appropriate #include files for __printf and struct va_format
>> > o Convert dev_printk to dev_info
>>
>> I think these unrelated changes should be in 4 patches:
>> 1 - add annotation to check the format string against the arguments
>> (linux/compiler.h should be added here)
>> 2 - add missing linux/printk.h header for struct va_format
>> Note that I think a forward declaration is more appropriate here, as
>> we only use pointers to this struct in this file, we never try to
>> look inside. On the other hand:
>> 3 - drm_print.c needs the header in drm_printf(), but as a separate
>> patch
>> 4 - convert dev_printk to dev_info (you need to include linux/device.h
>> there)
>
> I am not a big fan of making trivial patches into a series.
It's standard procedure in kernel development to split out unrelated
changes into individual patches, regardless of whether you think they
are trivial or not. Four is probably excessive, but you get the idea.
>> You can add my r-b on all four patches when you send them to the list :)
>
> If you want to break it up, go ahead.
You know how this stuff works, please split it up to get the stuff
merged.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-02-21 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 23:33 [PATCH] drm: drm_printer: add __printf validation Joe Perches
2017-02-20 12:17 ` Eric Engestrom
2017-02-20 17:10 ` Joe Perches
2017-02-21 8:26 ` Jani Nikula [this message]
2017-02-21 8:32 ` Joe Perches
2017-02-21 9:02 ` Jani Nikula
2017-02-21 9:18 ` Joe Perches
2017-02-26 20:43 ` Daniel Vetter
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=87a89gkl09.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@imgtec.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.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