From: Ralf Baechle <ralf@linux-mips.org>
To: Mike Crowe <mac@mcrowe.com>
Cc: linux-mips@linux-mips.org, Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] MIPS: Convert printk statements during kernel setup to use severity levels
Date: Wed, 30 Jul 2008 14:49:18 +0100 [thread overview]
Message-ID: <20080730134918.GA20791@linux-mips.org> (raw)
In-Reply-To: <20080728121251.GA17679@mcrowe.com>
On Mon, Jul 28, 2008 at 01:12:52PM +0100, Mike Crowe wrote:
> From: Mike Crowe <mac@mcrowe.com>
> Date: Mon, 28 Jul 2008 13:12:52 +0100
> To: linux-mips@linux-mips.org
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Subject: [PATCH] MIPS: Convert printk statements during kernel setup to use
> severity levels
> Content-Type: text/plain; charset=us-ascii
>
> Signed-off-by: Mike Crowe <mac@mcrowe.com>
Thanks, applied.
Ralf
prev parent reply other threads:[~2008-07-30 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 13:44 [PATCH] MIPS: Add severity levels to printk statements during kernel setup Mike Crowe
2008-07-25 18:04 ` Geert Uytterhoeven
2008-07-26 12:59 ` Mike Crowe
2008-07-26 13:19 ` Geert Uytterhoeven
2008-07-28 12:12 ` [PATCH] MIPS: Convert printk statements during kernel setup to use severity levels Mike Crowe
2008-07-30 13:49 ` Ralf Baechle [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=20080730134918.GA20791@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=mac@mcrowe.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