From: Dennis Zhou <dennis@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Dennis Zhou <dennis@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-doc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] include/bitmap.h: add new functions to documentation
Date: Thu, 5 Mar 2020 16:33:27 -0500 [thread overview]
Message-ID: <20200305213327.GA79880@dennisz-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200305082415.GA1079@ninjato>
On Thu, Mar 05, 2020 at 09:24:15AM +0100, Wolfram Sang wrote:
>
> > > I found these functions only by chance although I was looking exactly
> > > for something like them. So, add them to the list of functions to make
> > > them more visible.
> > >
> > > Fixes: e837dfde15a4 ("bitmap: genericize percpu bitmap region iterators")
> > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > Cc: Dennis Zhou <dennis@kernel.org>
> >
> > Ah thanks. That was a miss not adding the documentation. I can pick
> > these up unless Andrew would rather run them through his tree. I have a
> > few other miscellaneous documentation cleanups for percpu I need to run
> > anyway.
>
> That sounds like a good fit to me. Will you take both of the patches?
>
> Thanks,
>
> Wolfram
>
I've picked up both in percpu for-5.7.
Thanks,
Dennis
next prev parent reply other threads:[~2020-03-05 21:33 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 [this message]
2020-03-05 21:29 ` [PATCH 0/2] include/bitmap.h: updates to docs Dennis Zhou
2020-03-06 8:17 ` 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=20200305213327.GA79880@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 \
--cc=wsa@the-dreams.de \
/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).