From: Dan Carpenter <dan.carpenter@oracle.com>
To: Martin Kepplinger <martink@posteo.de>
Cc: gregkh@linuxfoundation.org, pavel@ucw.cz,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RESEND] staging: winbond: use dev_err() instead of printk()
Date: Mon, 19 May 2014 13:59:43 +0300 [thread overview]
Message-ID: <20140519105943.GQ16255@mwanda> (raw)
In-Reply-To: <1400496911-11658-1-git-send-email-martink@posteo.de>
On Mon, May 19, 2014 at 12:55:11PM +0200, Martin Kepplinger wrote:
> For obvious error messages, use dev_err() in order to provide userspace
> with more useful information and use the common kernel coding style.
>
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
> ---
> i just waited a week or so. this applies to next-20140516.
A week is too short a time. You will always get a message that your
patch was either applied or dropped.
>
> greetings from Linuxdays Vienna, Austria
Hi hi. Greetings from Africa. :)
regards,
dan carpenter
prev parent reply other threads:[~2014-05-19 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 11:38 [PATCH] staging: winbond: use dev_err() instead of printk() Martin Kepplinger
2014-05-08 11:48 ` Dan Carpenter
2014-05-09 8:21 ` Pavel Machek
2014-05-19 10:55 ` [PATCH][RESEND] " Martin Kepplinger
2014-05-19 10:59 ` Dan Carpenter [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=20140519105943.GQ16255@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=pavel@ucw.cz \
/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).