linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Aditya Srivastava <yashsri421@gmail.com>,
	linux-mips@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 0/3] mips: expunge kernel-doc warnings
Date: Wed, 28 Jul 2021 11:25:39 +0200	[thread overview]
Message-ID: <20210728092539.GA6545@alpha.franken.de> (raw)
In-Reply-To: <20210725160258.28950-1-rdunlap@infradead.org>

On Sun, Jul 25, 2021 at 09:02:55AM -0700, Randy Dunlap wrote:
> Remove all kernel-doc warnings from arch/mips/ (as reported by the
> kernel test robot).
> 
> [PATCH 1/3] mips: clean up (remove) kernel-doc in cavium-octeon/executive/
> [PATCH 2/3] mips: clean up kernel-doc in cavium-octeon/*.c
> [PATCH 3/3] mips: clean up kernel-doc in mm/c-octeon.c
> 
> Cc: Aditya Srivastava <yashsri421@gmail.com>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: linux-mips@vger.kernel.org
> Cc: kernel test robot <lkp@intel.com>
> 
>  arch/mips/cavium-octeon/executive/cvmx-bootmem.c      |   10 +-
>  arch/mips/cavium-octeon/executive/cvmx-cmd-queue.c    |   12 +-
>  arch/mips/cavium-octeon/executive/cvmx-helper-board.c |    8 -
>  arch/mips/cavium-octeon/executive/cvmx-helper-rgmii.c |   12 +-
>  arch/mips/cavium-octeon/executive/cvmx-helper-xaui.c  |    8 -
>  arch/mips/cavium-octeon/executive/cvmx-l2c.c          |    9 --
>  arch/mips/cavium-octeon/executive/cvmx-pko.c          |   22 ++---
>  arch/mips/cavium-octeon/executive/cvmx-spi.c          |   20 ++--
>  arch/mips/cavium-octeon/flash_setup.c                 |    2 
>  arch/mips/cavium-octeon/setup.c                       |   43 +++++-----
>  arch/mips/cavium-octeon/smp.c                         |   14 +--
>  arch/mips/mm/c-octeon.c                               |   29 +++---
>  12 files changed, 93 insertions(+), 96 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2021-07-28  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 16:02 [PATCH 0/3] mips: expunge kernel-doc warnings Randy Dunlap
2021-07-25 16:02 ` [PATCH 1/3] mips: clean up (remove) kernel-doc in cavium-octeon/executive/ Randy Dunlap
2021-07-25 16:02 ` [PATCH 2/3] mips: clean up kernel-doc in cavium-octeon/*.c Randy Dunlap
2021-07-25 16:02 ` [PATCH 3/3] mips: clean up kernel-doc in mm/c-octeon.c Randy Dunlap
2021-07-28  9:25 ` Thomas Bogendoerfer [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=20210728092539.GA6545@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rdunlap@infradead.org \
    --cc=yashsri421@gmail.com \
    /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).