From: Andreas Schwab <schwab@suse.de>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@ozlabs.org, arndb@de.ibm.com
Subject: Re: [PATCH] powerpc: fix large nvram access
Date: Wed, 11 Jan 2006 00:22:25 +0100 [thread overview]
Message-ID: <jed5izmzwu.fsf@sykes.suse.de> (raw)
In-Reply-To: <20060110221313.GA24246@suse.de> (Olaf Hering's message of "Tue, 10 Jan 2006 23:13:14 +0100")
Olaf Hering <olh@suse.de> writes:
> this change breaks my nvsetenv binary on JS20.
>
> (none):/# mount proc ; nvsetenv
> Error reading /dev/nvram: Success
It was broken to begin with.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-01-10 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601091916.k09JGMJY004116@hera.kernel.org>
2006-01-10 22:13 ` [PATCH] powerpc: fix large nvram access Olaf Hering
2006-01-10 23:22 ` Andreas Schwab [this message]
2006-01-10 23:34 ` Arnd Bergmann
2006-01-11 10:25 ` Olaf Hering
2006-01-11 12:20 ` Olaf Hering
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=jed5izmzwu.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=arndb@de.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).