All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] ACPI / LPSS: set an error code
Date: Tue, 07 Jul 2015 07:50:36 +0000	[thread overview]
Message-ID: <20150707075036.GB4341@mwanda> (raw)
In-Reply-To: <1480350.L34Aud6LIR@vostro.rjw.lan>

On Tue, Jul 07, 2015 at 12:56:21AM +0200, Rafael J. Wysocki wrote:
> This looks insufficient to my eyes, as we leak memory here too.
> 
> What about the following instead?

Yeah.  You are, of course, correct.

regards,
dan carpenter



WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] ACPI / LPSS: set an error code
Date: Tue, 7 Jul 2015 10:50:36 +0300	[thread overview]
Message-ID: <20150707075036.GB4341@mwanda> (raw)
In-Reply-To: <1480350.L34Aud6LIR@vostro.rjw.lan>

On Tue, Jul 07, 2015 at 12:56:21AM +0200, Rafael J. Wysocki wrote:
> This looks insufficient to my eyes, as we leak memory here too.
> 
> What about the following instead?

Yeah.  You are, of course, correct.

regards,
dan carpenter



  reply	other threads:[~2015-07-07  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  8:56 [patch] ACPI / LPSS: set an error code Dan Carpenter
2015-07-03  8:56 ` Dan Carpenter
2015-07-06 22:56 ` Rafael J. Wysocki
2015-07-06 22:56   ` Rafael J. Wysocki
2015-07-07  7:50   ` Dan Carpenter [this message]
2015-07-07  7:50     ` Dan Carpenter

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=20150707075036.GB4341@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --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 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.