From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
stable@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>
Subject: Re: Regression in v4.4.124 due to 'genirq: Use irqd_get_trigger_type to compare ..'
Date: Thu, 29 Mar 2018 10:54:34 -0700 [thread overview]
Message-ID: <20180329175434.GA8446@roeck-us.net> (raw)
In-Reply-To: <20180329063201.GA1816@kroah.com>
On Thu, Mar 29, 2018 at 08:32:01AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Mar 28, 2018 at 02:59:18PM -0700, Guenter Roeck wrote:
> > Hi Greg,
> >
> > commit 9d0273bb1c4b64 ("genirq: Use irqd_get_trigger_type to compare the trigger
> > type for shared IRQs") causes a regression in v4.4.124. The problem has been fixed
> > upstream with commit 4f8413a3a799 ("genirq: Track whether the trigger type has
> > been set"). Please apply that patch to v4.4.y at your earliest convenience.
> >
> > The patch does not apply cleanly; you'll get a conflict include/linux/irq.h.
> > The fix is simple - just take the version introduced by the patch. It adds
> > a couple of extra defines, but those don't hurt and just keep the code aligned
> > with upstream.
>
> Thanks, this was also needed for 4.9.y and 3.18.y.
>
Odd that I didn't see the problem there. But then I still see the following
in 4.4.y after the above was added.
genirq: Flags mismatch irq 24. 00000080 ([PCI] PME) vs. 00000080 ([EDAC] PCI err)
This is with powerpc:mpc8544ds:mpc85xx_defconfig. I do _not_ see this problem
in v4.9+.
Looks like I'll need to spend more time on this.
Guenter
next prev parent reply other threads:[~2018-03-29 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 21:59 Regression in v4.4.124 due to 'genirq: Use irqd_get_trigger_type to compare ..' Guenter Roeck
2018-03-29 6:32 ` Greg Kroah-Hartman
2018-03-29 17:54 ` Guenter Roeck [this message]
2018-03-29 20:28 ` Guenter Roeck
2018-03-29 21:07 ` Nathan Chancellor
2018-03-29 21:45 ` Guenter Roeck
2018-03-30 6:26 ` Greg Kroah-Hartman
2018-03-30 8:59 ` Greg Kroah-Hartman
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=20180329175434.GA8446@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--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 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.