linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Florian Fainelli <florian@openwrt.org>
Cc: Shubhrajyoti Datta <omaplinuxkernel@gmail.com>,
	Tanguy Bouzeloc <tanguy.bouzeloc@efixo.com>,
	linux-mips@linux-mips.org, ralf@linux-mips.org,
	spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH spi-next] spi: add Broadcom BCM63xx SPI controller driver
Date: Wed, 7 Dec 2011 22:27:10 +0100	[thread overview]
Message-ID: <20111207212710.GD3744@pengutronix.de> (raw)
In-Reply-To: <201111232041.18477.florian@openwrt.org>

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

> > Could we move to dev pm ops?
> 
> Sure, I have fixed that in version 2 of the patch.

Have you sent that already?

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

  reply	other threads:[~2011-12-07 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 20:16 [PATCH spi-next] spi: add Broadcom BCM63xx SPI controller driver Florian Fainelli
     [not found] ` <1321906615-11392-1-git-send-email-florian-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2011-11-22  8:26   ` Shubhrajyoti Datta
     [not found]     ` <CAM=Q2cudxgW-B_TEDgBrdk4CFB9LgZqE9db6vDH+MJEgJeCQcg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-23 19:41       ` Florian Fainelli
2011-12-07 21:27         ` Wolfram Sang [this message]
     [not found]           ` <20111207212710.GD3744-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-07 22:02             ` Florian Fainelli
2011-12-07 23:04 ` Wolfram Sang

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=20111207212710.GD3744@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=omaplinuxkernel@gmail.com \
    --cc=ralf@linux-mips.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=tanguy.bouzeloc@efixo.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;
as well as URLs for NNTP newsgroup(s).