public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] regmap: Prepare LZO cache for variable block sizes
Date: Tue, 18 Oct 2011 12:02:43 +0100	[thread overview]
Message-ID: <20111018110243.GA2046@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318933633-5759-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On Tue, Oct 18, 2011 at 11:27:13AM +0100, Mark Brown wrote:
> Give regcache_lzo_block_count() a copy of the map so that when we decide
> we want to make the LZO cache more controllable we can more easily do so.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

Acked-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>

Thanks,
Dimitris

      reply	other threads:[~2011-10-18 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 10:27 [PATCH] regmap: Prepare LZO cache for variable block sizes Mark Brown
2011-10-18 11:02 ` Dimitris Papastamos [this message]

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=20111018110243.GA2046@opensource.wolfsonmicro.com \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    /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