From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-pm@lists.linux-foundation.org, Takashi Iwai <tiwai@suse.de>,
netdev@vger.kernel.org, markgross@thegnar.org
Subject: Re: [linux-pm] [PATCH 3/3] pm_qos: get rid of the allocation in pm_qos_add_request()
Date: Mon, 28 Jun 2010 23:59:17 +0200 [thread overview]
Message-ID: <201006282359.18045.rjw@sisk.pl> (raw)
In-Reply-To: <1277747088.10879.201.camel@mulgrave.site>
On Monday, June 28, 2010, James Bottomley wrote:
> Since every caller has to squirrel away the returned pointer anyway,
> they might as well supply the memory area. This fixes a bug in a few of
> the call sites where the returned pointer was dereferenced without
> checking it for NULL (which gets returned if the kzalloc failed).
>
> I'd like to hear how sound and netdev feels about this: it will add
> about two more pointers worth of data to struct netdev and struct
> snd_pcm_substream .. but I think it's worth it. If you're OK, I'll add
> your acks and send through the pm tree.
>
> This also looks to me like an android independent clean up (even though
> it renders the request_add atomically callable). I also added include
> guards to include/linux/pm_qos_params.h
>
> cc: netdev@vger.kernel.org
> cc: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
I like all of the patches in this series, thanks a lot for doing this!
I guess it might be worth sending a CC to the LKML next round so that people
can see [1/3] (I don't expect any objections, but anyway it would be nice).
Thanks,
Rafael
next prev parent reply other threads:[~2010-06-28 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1277746434.10879.191.camel@mulgrave.site>
2010-06-28 17:44 ` [PATCH 3/3] pm_qos: get rid of the allocation in pm_qos_add_request() James Bottomley
2010-06-28 21:59 ` Rafael J. Wysocki [this message]
2010-06-28 22:10 ` [linux-pm] " James Bottomley
2010-06-29 9:20 ` Rafael J. Wysocki
2010-06-30 16:45 ` Daniel Walker
2010-06-29 4:39 ` mark gross
2010-07-01 22:23 ` [linux-pm] " Rafael J. Wysocki
2010-07-01 22:30 ` James Bottomley
2010-07-01 22:38 ` Rafael J. Wysocki
2010-07-05 6:41 ` Takashi Iwai
2010-07-05 14:02 ` James Bottomley
2010-07-05 19:16 ` mark gross
2010-07-05 21:07 ` [linux-pm] " Rafael J. Wysocki
2010-07-06 16:12 ` James Bottomley
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=201006282359.18045.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=James.Bottomley@suse.de \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=netdev@vger.kernel.org \
--cc=tiwai@suse.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).