From: linas@austin.ibm.com
To: David Gibson <david@gibson.dropbear.id.au>,
paulus@au1.ibm.com, paulus@samba.org,
linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PPC64: lockfix for rtas error log
Date: Wed, 30 Jun 2004 11:58:08 -0500 [thread overview]
Message-ID: <20040630115808.R21634@forte.austin.ibm.com> (raw)
In-Reply-To: <20040630011708.GG26251@zax>; from david@gibson.dropbear.id.au on Wed, Jun 30, 2004 at 11:17:08AM +1000
On Wed, Jun 30, 2004 at 11:17:08AM +1000, David Gibson wrote:
> On Tue, Jun 29, 2004 at 05:50:07PM -0500, linas@austin.ibm.com wrote:
> >
> > Paul,
> >
> > Could you please apply the following path to the ameslab tree, and/or
> > forward it to the main 2.6 kernel maintainers.
> >
> > This patch moves the location of a lock in order to protect
> > the contents of a buffer until it has been copied to its final
> > destination. Prior to this, a race existed whereby the buffer
> > could be filled even while it was being emptied.
> >
> > Signed-off-by: Linas Vepstas <linas@linas.org>
>
> Hmm... I note that log_error() does nothing but call ppc_md.log_error,
> and I can't see anywhere that that is set to be non-NULL...
grep log_error *.c
chrp_setup.c: ppc_md.log_error = pSeries_log_error;
--linas
next prev parent reply other threads:[~2004-06-30 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 22:50 linas
2004-06-30 1:17 ` David Gibson
2004-06-30 16:58 ` linas [this message]
2004-06-30 1:44 ` Benjamin Herrenschmidt
2004-06-30 17:36 ` linas
2004-06-30 18:47 ` Benjamin Herrenschmidt
2004-06-30 19:02 ` Olof Johansson
2004-06-30 19:02 ` Benjamin Herrenschmidt
2004-06-30 20:31 ` [PATCH] 2.6 PPC64: lockfix for rtas error log (third-times-a-charm?) linas
2004-06-30 11:27 ` [PATCH] PPC64: lockfix for rtas error log Paul Mackerras
2004-06-30 17:50 ` linas
2004-06-30 23:07 ` Paul Mackerras
2004-07-01 16:31 ` Jake Moilanen
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=20040630115808.R21634@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=paulus@au1.ibm.com \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome