From: Linus Walleij <linus.walleij@linaro.org>
To: John Keeping <john@metanate.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Julia Cartwright <julia@ni.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] pinctrl: rockchip: PREEMPT_RT_FULL fixes
Date: Thu, 23 Mar 2017 10:20:06 +0100 [thread overview]
Message-ID: <CACRpkdbcnuPGQGuNG-0ZdARbKdJRMrXGZsoeG4NPVFTMg5p6sw@mail.gmail.com> (raw)
In-Reply-To: <20170317182430.27400-1-john@metanate.com>
On Fri, Mar 17, 2017 at 7:24 PM, John Keeping <john@metanate.com> wrote:
> The aim of the series is to make the Rockchip pinctrl irq_chip
> implementation safe for use with RT_FULL which requires that raw
> spinlocks are used to avoid sleeping in hardirq context.
>
> This is the same as version 2 [1] with the 2.1 version of patch 1
> included, but I'm rolling it up as a new version so it's simpler to
> apply.
This v3 does not apply either so please rebase and resend.
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] pinctrl: rockchip: PREEMPT_RT_FULL fixes
Date: Thu, 23 Mar 2017 10:20:06 +0100 [thread overview]
Message-ID: <CACRpkdbcnuPGQGuNG-0ZdARbKdJRMrXGZsoeG4NPVFTMg5p6sw@mail.gmail.com> (raw)
In-Reply-To: <20170317182430.27400-1-john@metanate.com>
On Fri, Mar 17, 2017 at 7:24 PM, John Keeping <john@metanate.com> wrote:
> The aim of the series is to make the Rockchip pinctrl irq_chip
> implementation safe for use with RT_FULL which requires that raw
> spinlocks are used to avoid sleeping in hardirq context.
>
> This is the same as version 2 [1] with the 2.1 version of patch 1
> included, but I'm rolling it up as a new version so it's simpler to
> apply.
This v3 does not apply either so please rebase and resend.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-03-23 9:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 18:24 [PATCH v3 0/4] pinctrl: rockchip: PREEMPT_RT_FULL fixes John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` [PATCH v3 1/4] pinctrl: rockchip: remove unnecessary locking John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` [PATCH v3 2/4] pinctrl: rockchip: convert to raw spinlock John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` [PATCH v3 3/4] pinctrl: rockchip: split out verification of mux settings John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` [PATCH v3 4/4] pinctrl: rockchip: avoid hardirq-unsafe functions in irq_chip John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-17 18:24 ` John Keeping
2017-03-23 9:20 ` Linus Walleij [this message]
2017-03-23 9:20 ` [PATCH v3 0/4] pinctrl: rockchip: PREEMPT_RT_FULL fixes Linus Walleij
2017-03-23 9:20 ` Linus Walleij
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=CACRpkdbcnuPGQGuNG-0ZdARbKdJRMrXGZsoeG4NPVFTMg5p6sw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=heiko@sntech.de \
--cc=john@metanate.com \
--cc=julia@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.