All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: m.wa@wwu.de
Cc: linux-ide@vger.kernel.org
Subject: Re: Wiki account on ata.wiki.kernel.org?
Date: Mon, 4 Dec 2017 13:00:32 -0800	[thread overview]
Message-ID: <20171204210032.GJ2421075@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <f2bb97f4-9006-6a38-a8b5-e7f581255d18@uni-muenster.de>

Hello,

On Mon, Dec 04, 2017 at 09:36:46PM +0100, Matthias Peter Walther wrote:
> okay thanks, I guess you've been the one who unlocked my account today.
> So you wouldn't spend the time to update that page?

That wasn't me and no I wouldn't.

> Where is the in-kernel documentation? I'm rather new to this. Is this
> within the kernel's git or where do I find it?

There's driver-api/libata.rst in the source tree but it's also
horribly outdated.  If we want up-to-date hardware support
documentation, I think we'd have to move it into the source code and
generate it from there.  However, I'm not sure how useful it all
really is.  The wiki hasn't been updated for eons, most other
subsystems don't have the counterpart, and not much is really painful
because of that.

But, regardless of what we're gonna do in the long term, if someone is
interested in keeping it fresh, that is really great.  The other thing
is that libata development is pretty stale at this point, so maybe we
don't need a grand long term plan and just bringing the wiki
up-to-date is enough.

Thanks.

-- 
tejun

      reply	other threads:[~2017-12-04 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-02 13:54 Wiki account on ata.wiki.kernel.org? Matthias Peter Walther
2017-12-04 20:24 ` Tejun Heo
2017-12-04 20:36   ` Matthias Peter Walther
2017-12-04 21:00     ` Tejun Heo [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=20171204210032.GJ2421075@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=m.wa@wwu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.