From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Shubhrajyoti D <shubhrajyoti@ti.com>
Cc: spi-devel-general@lists.sourceforge.net,
grant.likely@secretlab.ca, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/3] spi: omap2-mcspi: spi cleanups
Date: Wed, 22 Aug 2012 17:59:33 +0100 [thread overview]
Message-ID: <20120822165933.GU7995@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1345615515-26745-1-git-send-email-shubhrajyoti@ti.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
On Wed, Aug 22, 2012 at 11:35:11AM +0530, Shubhrajyoti D wrote:
> This patch does the following
>
> Calls the pm_runtime_* functions directly.
> Remove the MOD_REG_BIT macro usage thereby removiing un-needed branch.
> At remove dont use the autosuspend runtime calls.
Applied all, thanks.
> The following changes since commit 23dcfa61bac244e1200ff9ad19c6e9144dcb6bb5:
>
> Merge branch 'akpm' (Andrew's patch-bomb) (2012-08-21 17:22:22 -0700)
When sending pull requests please always base them off a tag of some
kind, normally one of Linus' is a good option if you've no special
needs. This one looks like it's based off -next so can't be pulled into
any other tree, -next is rebased daily.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-22 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 6:05 [PATCHv2 0/3] spi: omap2-mcspi: spi cleanups Shubhrajyoti D
[not found] ` <1345615515-26745-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2012-08-22 6:05 ` [PATCHv2 1/3] spi: omap2-mcspi: Call pm_runtime_* functions directly Shubhrajyoti D
2012-08-22 6:05 ` [PATCHv2 2/3] spi: omap2-mcspi: Remove the macro MOD_REG_BIT Shubhrajyoti D
2012-08-22 6:05 ` [PATCHv2 3/3] spi: omap2-mcspi: At remove dont use the runtime_autosuspend calls Shubhrajyoti D
2012-08-22 16:59 ` Mark Brown [this message]
2012-08-22 17:03 ` [PATCHv2 0/3] spi: omap2-mcspi: spi cleanups Shubhrajyoti Datta
2012-08-22 17:13 ` 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=20120822165933.GU7995@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=shubhrajyoti@ti.com \
--cc=spi-devel-general@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).