From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH 3/7] compat: backport IORESOURCE_REG definition
Date: Sat, 13 Apr 2013 22:57:27 +0200 [thread overview]
Message-ID: <1365886647.1089.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1365862424-6530-4-git-send-email-mcgrof@do-not-panic.com> (sfid-20130413_161406_771904_BD2A16FF)
On Sat, 2013-04-13 at 07:13 -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
>
> This was added to help regmap drivers avoid having
> to use some non memory mapped equivalent, IORESOURCE_IO,
> to help avoid confusion. This is simply carried over.
Applied.
johannes
next prev parent reply other threads:[~2013-04-13 20:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 14:13 [PATCH 0/7] backport: pending backlog Luis R. Rodriguez
2013-04-13 14:13 ` [PATCH 1/7] backports: add support for backport_srctree Luis R. Rodriguez
2013-04-13 20:55 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 2/7] compat: add missing header includes for DMA backports Luis R. Rodriguez
2013-04-13 20:57 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 3/7] compat: backport IORESOURCE_REG definition Luis R. Rodriguez
2013-04-13 20:57 ` Johannes Berg [this message]
2013-04-13 14:13 ` [PATCH 4/7] gentree.py: add support to explicitly disable a config Luis R. Rodriguez
2013-04-13 20:59 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 5/7] backports: add support for voltage / current regulator drivers Luis R. Rodriguez
2013-04-13 21:01 ` Johannes Berg
2013-04-15 16:26 ` Mark Brown
2013-04-15 16:33 ` Johannes Berg
2013-04-22 13:11 ` Mark Brown
2013-04-23 6:18 ` Luis R. Rodriguez
2013-04-15 16:25 ` Mark Brown
2013-04-13 14:13 ` [PATCH 6/7] backports: add media subsystem drivers Luis R. Rodriguez
2013-04-13 21:02 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 7/7] backports: add intel_ips support Luis R. Rodriguez
2013-04-13 21:03 ` Johannes Berg
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=1365886647.1089.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=mcgrof@do-not-panic.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 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.