From: Ian Abbott <abbotti@mev.co.uk>
To: Conrad Meyer <cemeyer@uw.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: H Hartley Sweeten <hsweeten@visionengravers.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Conrad Meyer <cse.cem@gmail.com>
Subject: Re: [PATCH] Staging: comedi: fixup: dev_warn() with correct dev
Date: Tue, 11 Mar 2014 15:22:55 +0000 [thread overview]
Message-ID: <531F2A4F.8010902@mev.co.uk> (raw)
In-Reply-To: <1394549897-15186-1-git-send-email-cse.cem@gmail.com>
On 2014-03-11 14:58, Conrad Meyer wrote:
> Replace hw_dev with class_dev in new dev_warn()s.
>
> Sending this as a patch on top of the one already applied, since GregKH already
> took that one. If this is the wrong way to fix it, please let me know how I
> should proceed, I'm new.
>
> Thanks!
>
> Signed-off-by: Conrad Meyer <cse.cem@gmail.com>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
Though only the patch subject, the first line of the description and the
Signed-off-by line are relevant. All the other stuff should have gone
between the Signed-off-by (and similar) line(s) and the actual patch,
separated by three dashes like this:
Signed-off-by: x
---
Commentary that shouldn't go in the commit message goes here.
---
start of patch goes here.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2014-03-11 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 2:42 [PATCH 1/3] Staging: comedi: Fix some raw printks with dev_warn() Conrad Meyer
2014-03-11 14:19 ` Ian Abbott
2014-03-11 14:58 ` [PATCH] Staging: comedi: fixup: dev_warn() with correct dev Conrad Meyer
2014-03-11 15:22 ` Ian Abbott [this message]
2014-03-17 21:00 ` Greg Kroah-Hartman
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=531F2A4F.8010902@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=cemeyer@uw.edu \
--cc=cse.cem@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.