From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Wagner <wagi@monom.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Julia Cartwright <julia@ni.com>,
tglx@linutronix.de, stable@vger.kernel.org,
Daniel Wagner <daniel.wagner@siemens.com>
Subject: Re: [PATCH 4.{9,14,16,17}] serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version
Date: Sun, 1 Jul 2018 10:48:22 +0200 [thread overview]
Message-ID: <20180701084822.GA13234@kroah.com> (raw)
In-Reply-To: <b2d99cbb-9e1d-f042-4457-f42cc9f82e90@monom.org>
On Fri, Jun 22, 2018 at 04:51:47PM +0200, Daniel Wagner wrote:
> > Does Ben need this patch in CIP?
>
> Renesas ported a lot of features back for the iwg20m board to the CIP tree.
> They have an strong interest to run the -rt spin on the CIP kernel too. I
> don't think Ben needs it but he also prefers the patch flow via the stable
> tree.
>
> That said, I don't mind adding the patch only to my cip-rt tree if that's
> the correct way for -rt specific fixes.
For any -rt specific fixes that are needed for those trees, I'll be glad
to take them in the stable tree if it makes their life easier. No need
for everyone to have to take the same fixes in lots of different trees,
might as well share the load. For a patch like this, I don't object to
taking it in my trees for that reason.
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-01 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 13:56 [PATCH 4.4] serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version Daniel Wagner
2018-06-22 13:56 ` [PATCH 4.{9,14,16,17}] " Daniel Wagner
2018-06-22 14:15 ` Sebastian Andrzej Siewior
2018-06-22 14:26 ` Daniel Wagner
2018-06-22 14:36 ` Sebastian Andrzej Siewior
2018-06-22 14:51 ` Daniel Wagner
2018-07-01 8:48 ` Greg KH [this message]
2018-06-22 16:12 ` Steven Rostedt
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=20180701084822.GA13234@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@siemens.com \
--cc=julia@ni.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.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).