From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
torvalds <torvalds@linux-foundation.org>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] docbook: fix s390 fatal error after header files moved
Date: Wed, 06 Aug 2008 10:24:57 +0200 [thread overview]
Message-ID: <1218011097.20769.0.camel@localhost> (raw)
In-Reply-To: <20080805145929.0443f8bf.randy.dunlap@oracle.com>
On Tue, 2008-08-05 at 14:59 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
>
> Fix (fatal error) s390 docbook file to handle renamed header files.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> Documentation/DocBook/s390-drivers.tmpl | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Oops.. thanks Randy.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2008-08-06 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 21:59 [PATCH] docbook: fix s390 fatal error after header files moved Randy Dunlap
2008-08-06 8:24 ` Martin Schwidefsky [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=1218011097.20769.0.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox