From: Kyle McMartin <kyle@mcmartin.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Luck, Tony" <tony.luck@intel.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] Correct printk %pF to work on all architectures
Date: Tue, 9 Sep 2008 14:08:40 -0400 [thread overview]
Message-ID: <20080909180840.GA1940@phobos.i.cabal.ca> (raw)
In-Reply-To: <1220969561.3334.7.camel@localhost.localdomain>
On Tue, Sep 09, 2008 at 09:12:41AM -0500, James Bottomley wrote:
> OK, so could we get this in to -rc5 please? It's a bug fix for parisc
> since we're currently printing rubbish.
>
While I suppose it's a "parisc" patch, I'm not going to try to push it
unless either Linus just applies it, or we get an ack from the ppc/ia64
folks too.
... That said, please apply it, Linus. :)
Acked-by: Kyle McMartin <kyle@mcmartin.ca>
regards, Kyle
WARNING: multiple messages have this Message-ID (diff)
From: Kyle McMartin <kyle@mcmartin.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Luck, Tony" <tony.luck@intel.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] Correct printk %pF to work on all architectures
Date: Tue, 09 Sep 2008 18:08:40 +0000 [thread overview]
Message-ID: <20080909180840.GA1940@phobos.i.cabal.ca> (raw)
In-Reply-To: <1220969561.3334.7.camel@localhost.localdomain>
On Tue, Sep 09, 2008 at 09:12:41AM -0500, James Bottomley wrote:
> OK, so could we get this in to -rc5 please? It's a bug fix for parisc
> since we're currently printing rubbish.
>
While I suppose it's a "parisc" patch, I'm not going to try to push it
unless either Linus just applies it, or we get an ack from the ppc/ia64
folks too.
... That said, please apply it, Linus. :)
Acked-by: Kyle McMartin <kyle@mcmartin.ca>
regards, Kyle
WARNING: multiple messages have this Message-ID (diff)
From: Kyle McMartin <kyle@mcmartin.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Correct printk %pF to work on all architectures
Date: Tue, 9 Sep 2008 14:08:40 -0400 [thread overview]
Message-ID: <20080909180840.GA1940@phobos.i.cabal.ca> (raw)
In-Reply-To: <1220969561.3334.7.camel@localhost.localdomain>
On Tue, Sep 09, 2008 at 09:12:41AM -0500, James Bottomley wrote:
> OK, so could we get this in to -rc5 please? It's a bug fix for parisc
> since we're currently printing rubbish.
>
While I suppose it's a "parisc" patch, I'm not going to try to push it
unless either Linus just applies it, or we get an ack from the ppc/ia64
folks too.
... That said, please apply it, Linus. :)
Acked-by: Kyle McMartin <kyle@mcmartin.ca>
regards, Kyle
next prev parent reply other threads:[~2008-09-09 18:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 20:18 [PATCH] Correct printk %pF to work on all architectures James Bottomley
2008-09-03 20:18 ` James Bottomley
2008-09-03 20:18 ` James Bottomley
2008-09-03 21:22 ` Linus Torvalds
2008-09-03 21:22 ` Linus Torvalds
2008-09-03 21:22 ` Linus Torvalds
2008-09-03 22:42 ` James Bottomley
2008-09-03 22:42 ` James Bottomley
2008-09-03 22:42 ` James Bottomley
2008-09-03 22:42 ` James Bottomley
2008-09-03 22:54 ` Linus Torvalds
2008-09-03 22:54 ` Linus Torvalds
2008-09-03 22:54 ` Linus Torvalds
2008-09-03 23:00 ` James Bottomley
2008-09-03 23:00 ` James Bottomley
2008-09-03 23:00 ` James Bottomley
2008-09-03 23:15 ` Linus Torvalds
2008-09-03 23:15 ` Linus Torvalds
2008-09-03 23:15 ` Linus Torvalds
2008-09-03 23:33 ` James Bottomley
2008-09-03 23:33 ` James Bottomley
2008-09-03 23:33 ` James Bottomley
2008-09-04 0:01 ` Linus Torvalds
2008-09-04 0:01 ` Linus Torvalds
2008-09-04 0:01 ` Linus Torvalds
2008-09-04 1:43 ` James Bottomley
2008-09-04 1:43 ` James Bottomley
2008-09-04 1:43 ` James Bottomley
2008-09-04 22:36 ` Benjamin Herrenschmidt
2008-09-04 22:36 ` Benjamin Herrenschmidt
2008-09-04 22:36 ` Benjamin Herrenschmidt
2008-09-04 23:07 ` Luck, Tony
2008-09-04 23:07 ` Luck, Tony
2008-09-04 23:07 ` Luck, Tony
2008-09-09 14:12 ` James Bottomley
2008-09-09 14:12 ` James Bottomley
2008-09-09 14:12 ` James Bottomley
2008-09-09 18:08 ` Kyle McMartin [this message]
2008-09-09 18:08 ` Kyle McMartin
2008-09-09 18:08 ` Kyle McMartin
2008-09-09 22:05 ` Benjamin Herrenschmidt
2008-09-09 22:05 ` Benjamin Herrenschmidt
2008-09-09 22:05 ` Benjamin Herrenschmidt
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=20080909180840.GA1940@phobos.i.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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.