public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
	Jeff Garzik <jeff@garzik.org>, Tony Luck <tony.luck@intel.com>,
	Roland Dreier <rolandd@cisco.com>,
	David Brownell <dbrownell@users.sourceforge.net>,
	James Smart <james.smart@emulex.com>,
	Hansjoerg Lipp <hjlipp@web.de>, Jean Delvare <khali@linux-fr.org>,
	"Mark M. Hoffman" <mhoffman@lightlink.com>,
	Jeremy Fitzhardinge <jeremy@xensource.com>
Subject: Re: [PATCH] Add missing newlines to some uses of dev_<level> messages
Date: Thu, 09 Aug 2007 08:33:14 +0200	[thread overview]
Message-ID: <46BAB52A.4080408@gmail.com> (raw)
In-Reply-To: <1186535381.11897.29.camel@localhost>

Joe Perches napsal(a):
> Found these while looking at printk uses.
> 
> Add missing newlines to dev_<level> uses
> Add missing KERN_<level> prefixes to multiline dev_<level>s
> Fixed a wierd->weird spelling typo
> Added a newline to a printk
> 
> Signed-off-by:  Joe Perches <joe@perches.com>


>  drivers/char/isicom.c                  |   10 ++++++--

Acked-by: Jiri Slaby <jirislaby@gmail.com>

-- 
Jiri Slaby (jirislaby@gmail.com)
Faculty of Informatics, Masaryk University

  parent reply	other threads:[~2007-08-09  6:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  1:09 [PATCH] Add missing newlines to some uses of dev_<level> messages Joe Perches
2007-08-08  1:34 ` James Smart
2007-08-08  2:01   ` Jeff Garzik
2007-08-08  3:00 ` Nish Aravamudan
2007-08-10 20:34   ` Jean Delvare
2007-08-09  2:52 ` Mark M. Hoffman
2007-08-09  6:30 ` David Brownell
2007-08-09  6:33 ` Jiri Slaby [this message]
2007-08-11  7:23 ` Jean Delvare
2007-08-11 19:31   ` David Brownell

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=46BAB52A.4080408@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=hjlipp@web.de \
    --cc=james.smart@emulex.com \
    --cc=jeff@garzik.org \
    --cc=jeremy@xensource.com \
    --cc=joe@perches.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhoffman@lightlink.com \
    --cc=rolandd@cisco.com \
    --cc=tony.luck@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