All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: andrey.smirnov@convergeddevices.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] [regmap] [RESEND] Add provisions to have user-defined read operation
Date: Mon, 14 Jan 2013 08:04:37 +0900	[thread overview]
Message-ID: <20130113230436.GH5041@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1358024054-9895-2-git-send-email-andrew.smirnov@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 283 bytes --]

On Sat, Jan 12, 2013 at 12:54:12PM -0800, Andrey Smirnov wrote:

> This commit is a preparatory commit to provide "no-bus" configuration
> option for regmap API. It adds necessary plumbing needed to have the
> ability to provide user define register read function.

Applied, thanks.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-13 23:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 20:54 [PATCH 0/3] [regmap] [RESEND] Add "no-bus" configuration for regmap API Andrey Smirnov
2013-01-12 20:54 ` [PATCH 1/3] [regmap] [RESEND] Add provisions to have user-defined read operation Andrey Smirnov
2013-01-13 23:04   ` Mark Brown [this message]
2013-01-12 20:54 ` [PATCH 2/3] [regmap] [RESEND] Add provisions to have user-defined write operation Andrey Smirnov
2013-01-13 23:04   ` Mark Brown
2013-01-12 20:54 ` [PATCH 3/3] [regmap] [RESEND] Add "no-bus" option for regmap API Andrey Smirnov
2013-01-13 23:18   ` Mark Brown
2013-01-14 17:08     ` Andrey Smirnov
2013-01-15  7:02       ` Mark Brown
2013-01-13 12:03 ` [PATCH 0/3] [regmap] [RESEND] Add "no-bus" configuration " 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=20130113230436.GH5041@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=andrey.smirnov@convergeddevices.net \
    --cc=linux-kernel@vger.kernel.org \
    /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.