From: kernel@martin.sperl.org
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: linux-spi@vger.kernel.org, Eric Anholt <eric@anholt.net>,
Mark Brown <broonie@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
Hubert Denkmair <h.denkmair@intence.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/9] spi: bcm2835aux: bug fixes and improvements
Date: Sun, 24 Feb 2019 21:11:23 +0100 [thread overview]
Message-ID: <5A8B7C11-DB72-4384-945F-97D35554CFA6@martin.sperl.org> (raw)
In-Reply-To: <1294540802.93488.1551036147867@email.ionos.de>
> On 24.02.2019, at 20:22, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>>
>> Finally we remove some dead code.
>>
>> Martin Sperl (9):
>> spi: bcm2835aux: fix driver to not allow 65535 (=-1) cs-gpios
>> spi: bcm2835aux: warn in dmesg that native cs is not really supported
>> spi: bcm2835aux: setup gpio-cs to output and correct level during
>> setup
>> spi: bcm2835aux: add driver specific stats to debugfs
>> spi: bcm2835aux: make the polling duration limits configurable
>> spi: bcm2835aux: unifying code between polling and interrupt driven
>> code
>> spi: bcm2835aux: remove dangerous uncontrolled read of fifo
>> spi: bcm2835aux: use BCM2835_AUX_SPI_STAT_RX_LVL
>> spi: bcm2835aux: remove dead code
>>
>
> i consider patch 7 and 8 as possible stable candidates. How about rearranging this series that these patches comes first and could be backported?
Well - as far as I know 6+7+8 can get applied independently
(and you will need 6 as otherwise you would need to apply
at least 8 in 2 places).
The one observation that I have made is that when applying those
against 4.14 you needed some more patches that have gone in since
4.14 to apply cleanly.
Martin
prev parent reply other threads:[~2019-02-24 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 12:54 [PATCH 0/9] spi: bcm2835aux: bug fixes and improvements kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 12:54 ` [PATCH 1/9] spi: bcm2835aux: fix driver to not allow 65535 (=-1) cs-gpios kernel
2019-02-24 12:54 ` [PATCH 6/9] spi: bcm2835aux: unifying code between polling and interrupt driven code kernel
[not found] ` <20190224125440.16117-1-kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
2019-02-24 12:54 ` [PATCH 2/9] spi: bcm2835aux: warn in dmesg that native cs is not really supported kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 12:54 ` [PATCH 3/9] spi: bcm2835aux: setup gpio-cs to output and correct level during setup kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 12:54 ` [PATCH 4/9] spi: bcm2835aux: add driver specific stats to debugfs kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 12:54 ` [PATCH 5/9] spi: bcm2835aux: make the polling duration limits configurable kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 12:54 ` [PATCH 7/9] spi: bcm2835aux: remove dangerous uncontrolled read of fifo kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 12:54 ` [PATCH 8/9] spi: bcm2835aux: use BCM2835_AUX_SPI_STAT_RX_LVL kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 12:54 ` [PATCH 9/9] spi: bcm2835aux: remove dead code kernel-TqfNSX0MhmxHKSADF0wUEw
2019-02-24 19:22 ` [PATCH 0/9] spi: bcm2835aux: bug fixes and improvements Stefan Wahren
2019-02-24 20:11 ` kernel [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=5A8B7C11-DB72-4384-945F-97D35554CFA6@martin.sperl.org \
--to=kernel@martin.sperl.org \
--cc=broonie@kernel.org \
--cc=eric@anholt.net \
--cc=h.denkmair@intence.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=stefan.wahren@i2se.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).