linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: mlan@cpu.lu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: up-to-date patch for PMac nvram in 2.3.99
Date: Fri, 07 Apr 2000 01:14:36 +0200	[thread overview]
Message-ID: <38ED1A5C.3E00C037@wanadoo.fr> (raw)
In-Reply-To: 200004062057.WAA00323@piglet.grunz.lu


Michel Lanners wrote:
>
> Hi list,
>
> Following the nvram discussion a month ago, here is an updated working
> patch to re-enable nvram functionality in Paul's rsync 2.3.99 tree.
>
> IMHO I think nvram is an important functionality, and I think this
> patch or something to the same effect needs to go into 2.4.0.
>
> So, can all of you check this patch, try it out, and report any trouble
> or objections?

Seems to work OK for me, even with devfs.
Pmac 6400, bitkeeper kernel.

--
Martin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-04-06 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-06 20:57 up-to-date patch for PMac nvram in 2.3.99 Michel Lanners
2000-04-06 23:14 ` Martin Costabel [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=38ED1A5C.3E00C037@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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).