mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: 20181129133119.29387-1-linus.walleij@linaro.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Jason Cooper <jason@lakedaemon.net>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH] irq: Request and release resources for chained IRQs
Date: Thu, 18 Jun 2020 20:42:40 +0200	[thread overview]
Message-ID: <87tuz8b4gv.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <TZHZBQ.SOVDZ4DJB30O1@ixit.cz>

David Heidelberg <david@ixit.cz> writes:
> is there chance to get this patch included or could be this issue 
> solved with different approach?

Included into what? This patch is incorrect as I pointed out in review
here:

  https://lore.kernel.org/lkml/alpine.DEB.2.21.1812071143480.14498@nanos.tec.linutronix.de/

So why are you even asking?

I recommended to switch this away from chained handler and then the
whole story ended with this mail:

  https://lore.kernel.org/lkml/alpine.DEB.2.21.1812071404140.14498@nanos.tec.linutronix.de/

I have no idea how the GPIO people solved that problem, but certainly
not by applying this.

Thanks,

        tglx

  parent reply	other threads:[~2020-06-18 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:23 David Heidelberg
2020-06-15 21:16 ` Greg KH
2020-06-18 18:42 ` Thomas Gleixner [this message]
2020-07-07 11:47   ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2018-11-29 13:31 Linus Walleij
2018-12-07 10:09 ` Linus Walleij
2018-12-07 11:51   ` Thomas Gleixner
2018-12-07 12:57     ` Linus Walleij
2018-12-07 13:46       ` Thomas Gleixner

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=87tuz8b4gv.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=20181129133119.29387-1-linus.walleij@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jason@lakedaemon.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®