From: Jonathan Corbet <corbet@lwn.net>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jan Harkes <jaharkes@cs.cmu.edu>,
coda@cs.cmu.edu, codalist@coda.cs.cmu.edu,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v1] coda: Fix typo in the struct CodaCred documentation
Date: Fri, 26 Jul 2019 14:43:33 -0600 [thread overview]
Message-ID: <20190726144333.244ea568@lwn.net> (raw)
In-Reply-To: <20190723165750.66229-1-andriy.shevchenko@linux.intel.com>
On Tue, 23 Jul 2019 19:57:50 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> Documentation mistakenly refers to a different type while explaining
> the contents of the struct CodaCred.
>
> Fix the typo in the struct CodaCred description in the documentation.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
People still use coda? :)
Applied, thanks.
jon
prev parent reply other threads:[~2019-07-26 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 16:57 [PATCH v1] coda: Fix typo in the struct CodaCred documentation Andy Shevchenko
2019-07-26 20:43 ` Jonathan Corbet [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=20190726144333.244ea568@lwn.net \
--to=corbet@lwn.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-doc@vger.kernel.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