From: luzmaximilian@gmail.com (Maximilian Luz)
Subject: Potential bug in queue_count_set
Date: Fri, 12 Apr 2019 22:59:10 +0200 [thread overview]
Message-ID: <01d96ef2-bada-85fe-5287-4303e14c955d@gmail.com> (raw)
In-Reply-To: <20190411211557epcms2p7d5520c5762786ac4357bead574660bf6@epcms2p7>
On 4/11/19 11:15 PM, Minwoo Im wrote:
> I think I need to have a discussion about it, If user gives more than
> nr_possible_cpus, then:
> - It should be reduced to a possible value by automatically without
> any error.
> - It should return an error to let user know.
>
> Let's see how they think about it. Also we can have a discussion on that
> PATCH mail-loop.
Sounds good.
Maximilian
prev parent reply other threads:[~2019-04-12 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 13:33 Potential bug in queue_count_set Maximilian Luz
2019-04-10 14:11 ` Minwoo Im
2019-04-11 16:02 ` Minwoo Im
2019-04-11 17:39 ` Maximilian Luz
2019-04-11 21:15 ` Minwoo Im
2019-04-12 20:59 ` Maximilian Luz [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=01d96ef2-bada-85fe-5287-4303e14c955d@gmail.com \
--to=luzmaximilian@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.