From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia@diku.dk>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] sound/soc: keep pointer to resource so it can be freed
Date: Sat, 22 Oct 2011 10:47:08 +0100 [thread overview]
Message-ID: <20111022094708.GB3382@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318950399-17201-1-git-send-email-julia@diku.dk>
On Tue, Oct 18, 2011 at 05:06:39PM +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Add a new variable for storing resources accessed subsequent to the one
> accessed using request_mem_region, so the one accessed using
> request_mem_region can be released if needed.
Applied, thanks.
Please try to match your subject lines with those normally used for the
subsystem.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia@diku.dk>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] sound/soc: keep pointer to resource so it can be freed
Date: Sat, 22 Oct 2011 09:47:08 +0000 [thread overview]
Message-ID: <20111022094708.GB3382@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318950399-17201-1-git-send-email-julia@diku.dk>
On Tue, Oct 18, 2011 at 05:06:39PM +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Add a new variable for storing resources accessed subsequent to the one
> accessed using request_mem_region, so the one accessed using
> request_mem_region can be released if needed.
Applied, thanks.
Please try to match your subject lines with those normally used for the
subsystem.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia@diku.dk>
Cc: Liam Girdwood <lrg@ti.com>,
kernel-janitors@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound/soc: keep pointer to resource so it can be freed
Date: Sat, 22 Oct 2011 10:47:08 +0100 [thread overview]
Message-ID: <20111022094708.GB3382@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318950399-17201-1-git-send-email-julia@diku.dk>
On Tue, Oct 18, 2011 at 05:06:39PM +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Add a new variable for storing resources accessed subsequent to the one
> accessed using request_mem_region, so the one accessed using
> request_mem_region can be released if needed.
Applied, thanks.
Please try to match your subject lines with those normally used for the
subsystem.
next prev parent reply other threads:[~2011-10-22 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 15:06 [PATCH] sound/soc: keep pointer to resource so it can be freed Julia Lawall
2011-10-18 15:06 ` Julia Lawall
2011-10-18 15:06 ` Julia Lawall
2011-10-22 9:47 ` Mark Brown [this message]
2011-10-22 9:47 ` Mark Brown
2011-10-22 9:47 ` Mark Brown
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=20111022094708.GB3382@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--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 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.