From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Mark Brown <broonie@kernel.org>,
Philipp Zabel <philipp.zabel@gmail.com>,
Paul Parsons <lost.distance@yahoo.com>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>
Subject: Re: [PATCH] ARM: pxa: Remove unused clock_enable field from struct pxa2xx_spi_master
Date: Sat, 26 Sep 2015 21:47:53 +0200 [thread overview]
Message-ID: <87io6xezdi.fsf@belgarion.home> (raw)
In-Reply-To: <87k2rlq9go.fsf@belgarion.home> (Robert Jarzmik's message of "Sun, 20 Sep 2015 19:36:23 +0200")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Jarkko Nikula <jarkko.nikula@linux.intel.com> writes:
>
>> Use for struct pxa2xx_spi_master clock_enable field was removed years ago
>> from the pxa2xx-spi driver by the commit 2f1a74e5a2de ("[ARM] pxa: make
>> pxa2xx_spi driver use ssp_request()/ssp_free()").
>>
>> Therefore remove it from structure definition, documentation and from
>> couple affected board files.
>>
>> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>> ---
>> I propose this to be merged via ARM tree. I don't see we would need to do
>> other SPI related changes to struct pxa2xx_spi_master in near future (knock
>> on wood).
> I'll take that through the pxa/for-next tree in a couple of days, thanks.
Queued in pxa/for-next, thanks.
Cheers.
--
Robert
prev parent reply other threads:[~2015-09-26 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 7:14 [PATCH] ARM: pxa: Remove unused clock_enable field from struct pxa2xx_spi_master Jarkko Nikula
2015-09-19 14:47 ` Mark Brown
2015-09-20 17:36 ` Robert Jarzmik
2015-09-26 19:47 ` Robert Jarzmik [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=87io6xezdi.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lost.distance@yahoo.com \
--cc=marek.vasut@gmail.com \
--cc=philipp.zabel@gmail.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