From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "Mike Travis" <travis@sgi.com>
Cc: "Paul Jackson" <pj@sgi.com>,
"WANG Cong" <xiyou.wangcong@gmail.com>,
mingo@elte.hu, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Fix calculus of bitmap_scnprintf_len()
Date: Mon, 28 Apr 2008 19:31:31 +0200 [thread overview]
Message-ID: <36ca99e90804281031v5b211833sfb7cda05fedcea6@mail.gmail.com> (raw)
In-Reply-To: <481604BD.7000009@sgi.com>
On Mon, Apr 28, 2008 at 7:09 PM, Mike Travis <travis@sgi.com> wrote:
> Paul Jackson wrote:
> > Bert wrote:
> >> The function bitmap_scnprintf_len() is currently not used
> >
> > Paul Jackson wrote:
> >> How about we just remove that function?
> >
> > WANG Cong wrote:
> >> I am afraid no. See:
> >>
> >> include/linux/cpumask.h:292: return bitmap_scnprintf_len(len);
> >
> > Good point.
> >
> >
> > Then how about we also remove from cpumask.h:
> >
> > #define cpumask_scnprintf_len(len) \
> > __cpumask_scnprintf_len((len))
> > static inline int __cpumask_scnprintf_len(int len)
> > {
> > return bitmap_scnprintf_len(len);
> > }
> >
>
> That's fine with me. A later version of the patch did have
> the function removed but it didn't get picked up. The other
> changes there were to use function pointers instead of the
> flag variable to select list or mask output format, and the
> addition of mask variants for the cpu/{present,possible,
> online,system} map outputs.
I'm fine with this too. I did a hasty audit of cpumask_scnprintf()
users, and no one can use these functions.
But one last note to the cpumask_scnprintf_len() macro: this macro
should really not have an argument, it should be forced to NR_CPUS.
Else a user could have a too small buffer for the call to
cpumask_scnprintf(), which always calls bitmap_scnprintf() with
NR_CPUS nbits.
>
> I'll dig that one back up and resubmit it.
Fine.
Regards.
Bert
>
> Thanks,
> Mike
>
prev parent reply other threads:[~2008-04-28 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 20:43 [PATCH] Fix calculus of bitmap_scnprintf_len() Bert Wesarg
2008-04-27 21:01 ` Paul Jackson
2008-04-28 6:14 ` WANG Cong
2008-04-28 13:13 ` Paul Jackson
2008-04-28 17:09 ` Mike Travis
2008-04-28 17:31 ` Bert Wesarg [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=36ca99e90804281031v5b211833sfb7cda05fedcea6@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.com \
--cc=xiyou.wangcong@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