From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] spi: Group cs_change and cs_off flags together in struct spi_transfer
Date: Thu, 8 Sep 2022 16:02:48 +0300 [thread overview]
Message-ID: <Yxnn+Puts9Bv2f+a@smile.fi.intel.com> (raw)
In-Reply-To: <20220908125444.30727-1-andriy.shevchenko@linux.intel.com>
On Thu, Sep 08, 2022 at 03:54:44PM +0300, Andy Shevchenko wrote:
> The commit 5e0531f6b90a ("spi: Add capability to perform some transfer
> with chipselect off") added a new flag but squezed it into a wrong
> group of struct spi_transfer members (note that SPI_NBITS_* are macros
> for easier interpretation of the tx_nbits and rx_nbits bitfields.
Besides some small issues with the grammar above, I would like also to
reshuffle the documentation part. Hence, please wait for v2 of this.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-09-08 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 12:54 [PATCH v1 1/1] spi: Group cs_change and cs_off flags together in struct spi_transfer Andy Shevchenko
2022-09-08 13:02 ` Andy Shevchenko [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=Yxnn+Puts9Bv2f+a@smile.fi.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).