From: Hartley Sweeten <HartleyS-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: RE: [PATCH v2] spi: spi-ep93xx: simplify GPIO chip selects
Date: Thu, 16 Feb 2017 19:15:46 +0000 [thread overview]
Message-ID: <SN1PR0101MB15656A6802EDBAAA6E7C4F1BD05A0@SN1PR0101MB1565.prod.exchangelabs.com> (raw)
In-Reply-To: <20170216190109.kvsgigo4wlnaacvm-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Thursday, February 16, 2017 12:01 PM, Mark Brown wrote:
> On Thu, Feb 16, 2017 at 11:26:14AM -0700, H Hartley Sweeten wrote:
>> This driver requires a GPIO line to be used for the chip select of
>> each SPI device.
>
> This doesn't apply against current code, there's conflicts in the arch
> code. What's the story here (should I just apply after -rc1?)?
Oops. The conflict is probably with arch/arm/mach-ep93xx/simone.c.
I have another patch to that file that is still under review.
I'll rebase this and post a v3 shortly.
Regards,
Hartley
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-02-16 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 18:26 [PATCH v2] spi: spi-ep93xx: simplify GPIO chip selects H Hartley Sweeten
[not found] ` <20170216182614.47941-1-hsweeten-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org>
2017-02-16 19:01 ` Mark Brown
[not found] ` <20170216190109.kvsgigo4wlnaacvm-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-02-16 19:15 ` Hartley Sweeten [this message]
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=SN1PR0101MB15656A6802EDBAAA6E7C4F1BD05A0@SN1PR0101MB1565.prod.exchangelabs.com \
--to=hartleys-3ff4nkcrg1de2c76skzgb0eocmrvltnr@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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).