linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Zhou <dennis@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-doc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Dennis Zhou <dennis@kernel.org>
Subject: Re: [PATCH 0/2] include/bitmap.h: updates to docs
Date: Thu, 5 Mar 2020 16:29:50 -0500	[thread overview]
Message-ID: <20200305212950.GA79796@dennisz-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200304140920.6109-1-wsa+renesas@sang-engineering.com>

On Wed, Mar 04, 2020 at 03:09:18PM +0100, Wolfram Sang wrote:
> While looking for functions to handle region of bits, I stumbled over
> two issues in the documentation part of bitmap.h. These two patches
> address them.
> 
> My guess is that this could go in via Jon's documentation tree, but I
> am CCing Andrew nonetheless.
> 
> Based on v5.6-rc1.
> 
> Looking forward to comments!
> 
>    Wolfram
> 
> 
> Wolfram Sang (2):
>   include/bitmap.h: add missing parameter in docs
>   include/bitmap.h: add new functions to documentation
> 
>  include/linux/bitmap.h | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> -- 
> 2.20.1
> 
> 

I've applied this to percpu for-5.7.

Thanks,
Dennis

  parent reply	other threads:[~2020-03-05 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 14:09 [PATCH 0/2] include/bitmap.h: updates to docs Wolfram Sang
2020-03-04 14:09 ` [PATCH 1/2] include/bitmap.h: add missing parameter in docs Wolfram Sang
2020-03-04 14:09 ` [PATCH 2/2] include/bitmap.h: add new functions to documentation Wolfram Sang
2020-03-04 20:40   ` Dennis Zhou
2020-03-05  8:24     ` Wolfram Sang
2020-03-05 21:33       ` Dennis Zhou
2020-03-05 21:29 ` Dennis Zhou [this message]
2020-03-06  8:17   ` [PATCH 0/2] include/bitmap.h: updates to docs Wolfram Sang

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=20200305212950.GA79796@dennisz-mbp.dhcp.thefacebook.com \
    --to=dennis@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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).