From: Namhyung Kim <namhyung at gmail.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [RFC/PATCH] devices: Use new(std::nothrow) for creating devices
Date: Fri, 19 Oct 2012 00:44:57 +0900 [thread overview]
Message-ID: <1350575097.1610.12.camel@leonhard> (raw)
In-Reply-To: 508021E5.8070209@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
2012-10-18 (목), 08:36 -0700, Arjan van de Ven:
> On 10/18/2012 8:32 AM, Namhyung Kim wrote:
> > When allocation fails, just skip the device and proceed if possible.
> > This is also for consistency with others.
>
> hmm...
> if we're that low on memory something is so seriously wrong, exiting is the right answer really.
>
> I'm getting strong advice from other userspace coders that checking allocations like this is actually
> pointless...
> based on that, I'd say we need to go for better code readability, not more complexity for no actual gain.
>
Understood. Thanks for the quick reply!
Namhyung
next reply other threads:[~2012-10-18 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 15:44 Namhyung Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-18 15:36 [Powertop] [RFC/PATCH] devices: Use new(std::nothrow) for creating devices Arjan van de Ven
2012-10-18 15:32 Namhyung Kim
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=1350575097.1610.12.camel@leonhard \
--to=powertop@lists.01.org \
/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.