linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Colton Lewis <colton.w.lewis@protonmail.com>
Cc: linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: correct kernel-doc inconsistency
Date: Mon, 20 Jul 2020 15:36:55 +0100	[thread overview]
Message-ID: <20200720143655.GA5949@sirena.org.uk> (raw)
In-Reply-To: <20200719195630.148075-1-colton.w.lewis@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 228 bytes --]

On Sun, Jul 19, 2020 at 07:56:40PM +0000, Colton Lewis wrote:
> Silence documentation build warnings by correcting kernel-doc comment
> for spi_transfer struct.

This doesn't apply against current code, please check and resend.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-20 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 19:56 [PATCH] spi: correct kernel-doc inconsistency Colton Lewis
2020-07-20 14:36 ` Mark Brown [this message]
2020-07-25  5:02   ` [PATCH v2] " Colton Lewis
2020-07-27 13:56     ` Mark Brown
2020-07-27 13:56 ` [PATCH] " 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=20200720143655.GA5949@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=colton.w.lewis@protonmail.com \
    --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).