From: "Luck, Tony" <tony.luck@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Russell King <linux@arm.linux.org.uk>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"drbd-user@lists.linbit.com" <drbd-user@lists.linbit.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
"Dilger, Andreas" <andreas.dilger@intel.com>,
"codalist@coda.cs.cmu.edu" <codalist@TELEMANN.coda.cs.cmu.edu>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Jan Kara <jack@suse.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Boris Petkov <bp@suse.de>
Subject: RE: [PATCH] tree wide: Use kvfree() than conditional kfree()/vfree()
Date: Mon, 9 Nov 2015 23:25:44 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32B83DE2@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <5253459.IxnqkcU2vL@vostro.rjw.lan>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 500 bytes --]
> ACK for the ACPI changes (and CCing Tony and Boris for the heads-up as they
> are way more famailiar with the APEI code than I am).
Sure. If kvfree() really is smart enough to figure it out then there
it no point in the if (blah) kfree() else vfree().
The drivers/acpi/apei/erst.c code isn't doing anything subtle or magic here.
-Tony
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2015-11-09 23:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 11:56 [PATCH] tree wide: Use kvfree() than conditional kfree()/vfree() Tetsuo Handa
2015-11-09 12:11 ` Jan Kara
2015-11-09 16:26 ` David Miller
2015-11-09 16:07 ` Russell King - ARM Linux
2015-11-09 20:41 ` Dilger, Andreas
2015-11-09 21:48 ` Rafael J. Wysocki
2015-11-09 23:25 ` Luck, Tony [this message]
2015-11-10 13:34 ` [DRBD-user] " Lars Ellenberg
2015-11-19 0:23 ` David Rientjes
-- strict thread matches above, loose matches on Subject: below --
2015-11-07 11:44 Tetsuo Handa
2015-11-07 18:12 ` Joe Perches
2015-11-07 20:05 ` Andy Shevchenko
2015-11-07 20:13 ` Andy Shevchenko
2015-11-08 5:04 ` Tetsuo Handa
2015-11-08 5:30 ` Sergey Senozhatsky
2015-11-08 20:11 ` Andy Shevchenko
2015-11-09 10:48 ` Michal Hocko
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=3908561D78D1C84285E8C5FCA982C28F32B83DE2@ORSMSX114.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andreas.dilger@intel.com \
--cc=bp@suse.de \
--cc=codalist@TELEMANN.coda.cs.cmu.edu \
--cc=drbd-user@lists.linbit.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jack@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rjw@rjwysocki.net \
/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).