From: "Måns Rullgård" <mans@mansr.com>
To: Cyrille Pitchen <cyrille.pitchen@atmel.com>
Cc: <linux-arm-kernel@lists.infradead.org>, "Yang\,
Wenyou" <Wenyou.Yang@atmel.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Mark Brown <broonie@kernel.org>, <linux-spi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] spi: atmel: improve internal vs gpio chip-select choice
Date: Tue, 12 Jan 2016 08:51:00 +0000 [thread overview]
Message-ID: <yw1xmvsbuqob.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <5694BBCD.8020700@atmel.com> (Cyrille Pitchen's message of "Tue, 12 Jan 2016 09:39:41 +0100")
Cyrille Pitchen <cyrille.pitchen@atmel.com> writes:
> Hi Mans,
>
> I've tried to apply your patch on a next-20160112 branch to test it but it
> failed. I've also looked at the for-next branch of the SPI sub-system git
> tree.
>
> It seems that one issue occurred within a chunk patching the atmel_spi_setup()
> function. Please see below.
>
> Le 11/01/2016 17:01, Mans Rullgard a écrit :
> [...]
>> diff --git a/drivers/spi/spi-atmel.c b/drivers/spi/spi-atmel.c
>> index 08cbb3e43c76..d4a806e24060 100644
>> --- a/drivers/spi/spi-atmel.c
>> +++ b/drivers/spi/spi-atmel.c
> [...]
>> @@ -1603,6 +1611,7 @@ static int atmel_spi_setup(struct spi_device *spi)
>> }
>>
>> asd->npcs_pin = npcs_pin;
>> + asd->use_cs_gpio = use_cs_gpio;
>> spi->controller_state = asd;
>> } else {
>> atmel_spi_lock(as);
> [...]
>
> There is no 'else' statement in the source code I'm looking at.
Sorry, I'll send a new patch against the correct base. I forgot I had
something else earlier in my local branch.
--
Måns Rullgård
next prev parent reply other threads:[~2016-01-12 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 16:01 Mans Rullgard
2016-01-11 16:13 ` Mark Brown
2016-01-11 16:16 ` Måns Rullgård
2016-01-11 16:24 ` Mark Brown
2016-01-12 8:39 ` Cyrille Pitchen
2016-01-12 8:51 ` Måns Rullgård [this message]
2016-01-12 8:52 ` Nicolas Ferre
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=yw1xmvsbuqob.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=Wenyou.Yang@atmel.com \
--cc=broonie@kernel.org \
--cc=cyrille.pitchen@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nicolas.ferre@atmel.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
all inboxes | Powered by JetHome®