From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>
Subject: [PATCH v2 0/2] spi: pxa2xx: Update documentation
Date: Fri, 8 Dec 2023 19:02:53 +0200 [thread overview]
Message-ID: <20231208170436.3309648-1-andriy.shevchenko@linux.intel.com> (raw)
A couple of documentation updates.
Since v1:
- spelled controller fully in patch 1
- fixed inconsistent indentation in patch 2
Andy Shevchenko (2):
spi: pxa2xx: Use inclusive language
spi: pxa2xx: Update DMA mapping and using logic in the documentation
Documentation/spi/pxa2xx.rst | 59 +++++++++++++++++-------------------
1 file changed, 28 insertions(+), 31 deletions(-)
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2023-12-08 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 17:02 Andy Shevchenko [this message]
2023-12-08 17:02 ` [PATCH v2 1/2] spi: pxa2xx: Use inclusive language Andy Shevchenko
2023-12-08 17:02 ` [PATCH v2 2/2] spi: pxa2xx: Update DMA mapping and using logic in the documentation Andy Shevchenko
2023-12-09 17:52 ` [PATCH v2 0/2] spi: pxa2xx: Update documentation Mark Brown
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=20231208170436.3309648-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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;
as well as URLs for NNTP newsgroup(s).