9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] ehci/uhci interrupts
Date: Sun,  4 May 2014 07:12:10 +0200	[thread overview]
Message-ID: <ad00635822fff872369f310379f008bd@proxima.alt.za> (raw)
In-Reply-To: <659b566a0bf4993ee7360622c493fb21@brasstown.quanstro.net>

> there are lots of small ways to improve things, too.  i'd be happy
> to talk about that on or off list.  one thing that immediately springs
> to mind is additions to charles' kernel man pages.

The list is not very busy and, I hate to admit, somewhat remote from
Bell Labs.  As a result, I think there would be no serious objection
to add pertinent traffic to it.

Personally, kernel pages would be a god-send (but an update of Nemo's
commentaries would be even more so) and I would like to add discussion
on the various Plan 9 flavours and how their differences should be
consolidated or, if necessary, properly set down as distinguishing
features.

The same for patches that have not yet been accepted in the Bell Labs
release, I believe they ought to be discussed here with a view to make
them conform, where necessary, to Bell Labs' specifications so they
can be incorporated.

Maybe the long term discussions belong elesewhere, but right now, here
is where we all are.

++L





  reply	other threads:[~2014-05-04  5:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 15:26 erik quanstrom
2014-05-02 18:34 ` erik quanstrom
2014-05-03  5:14   ` lucio
2014-05-03  9:42     ` tlaronde
2014-05-03 19:45       ` erik quanstrom
2014-05-04  5:12         ` lucio [this message]
2014-05-04 10:41           ` tlaronde
2014-05-04 19:29             ` erik quanstrom
2014-05-05 10:50               ` tlaronde
2014-05-04 17:14           ` erik quanstrom

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=ad00635822fff872369f310379f008bd@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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).