From: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
To: Daniel Mack <zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org
Subject: Re: [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure
Date: Wed, 25 Jul 2012 20:33:59 +0100 [thread overview]
Message-ID: <20120725193359.GB9792@sirena.org.uk> (raw)
In-Reply-To: <1343216652-1463-1-git-send-email-zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Wed, Jul 25, 2012 at 01:44:11PM +0200, Daniel Mack wrote:
> The spi-gpio driver currently assumes the chipselect gpio number is
> stored in ->controller_data of the device's static board information.
Always CC maintainers on things... you've not CCed Grant or Linus W,
and for now I'm handling SPI patches (though I'm not in MAINTAINERS so
missing me is less surprising).
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
next prev parent reply other threads:[~2012-07-25 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 11:44 [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure Daniel Mack
[not found] ` <1343216652-1463-1-git-send-email-zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-25 11:44 ` [PATCH 2/2] SPI: spi-gpio: Add DT bindings Daniel Mack
[not found] ` <20120725121131.GA2628@pengutronix.de>
[not found] ` <20120725121131.GA2628-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-07-25 12:17 ` Daniel Mack
[not found] ` <20120725123244.GB2628@pengutronix.de>
[not found] ` <20120725123244.GB2628-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-07-25 12:35 ` Daniel Mack
2012-07-25 19:33 ` Mark Brown [this message]
[not found] ` <20120725193359.GB9792-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-07-25 19:38 ` [PATCH 1/2] SPI: spi-gpio: store chipselect information in private structure Daniel Mack
[not found] ` <50104B52.7090509-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-25 19:52 ` Mark Brown
[not found] ` <20120725195203.GC9792-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-07-25 20:00 ` Daniel Mack
[not found] ` <50105052.4000603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-25 20:12 ` Mark Brown
[not found] ` <20120725201227.GE9792-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-07-25 20:22 ` Daniel Mack
2012-08-01 20:45 ` Daniel Mack
[not found] ` <5019955F.3030108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-01 20:51 ` Mark Brown
[not found] ` <20120801205135.GA29157-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-08-01 20:58 ` Daniel Mack
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=20120725193359.GB9792@sirena.org.uk \
--to=broonie-gfdadszt00ze9xe1eozjha@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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).