From: Thomas Gleixner <tglx@linutronix•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail•com>,
linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
Marcin Niestroj <m.niestroj@grinn-global•com>,
Grygorii Strashko <grygorii.strashko@ti•com>,
Tony Lindgren <tony@atomide•com>,
Lee Jones <lee.jones@linaro•org>, Mark Brown <broonie@kernel•org>,
kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org
Subject: Re: [PATCH] kernel: irq: fix build failure
Date: Fri, 21 Oct 2016 10:07:41 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610211006370.4797@nanos> (raw)
In-Reply-To: <20161021120020.52b3fa35@canb.auug.org.au>
On Fri, 21 Oct 2016, Stephen Rothwell wrote:
> On Thu, 20 Oct 2016 14:55:45 +0200 (CEST) Thomas Gleixner <tglx@linutronix•de> wrote:
> > I know. This is under discussion with the driver folks as we are not going
> > to blindly export stuff just because someone slapped a irq_set_parent()
> > into the code w/o knowing why.
>
> Do we have any idea if a resolution is close. This was first reported
> in linux-next in September 14/15. :-(
Grr. Yes. As much as I hate it, I'll go and export it for now. Should be
able to get it into rc2.
Thanks,
tglx
next prev parent reply other threads:[~2016-10-21 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1475775403-27207-1-git-send-email-sudipm.mukherjee@gmail.com>
[not found] ` <57FBBA0B.9070500@gmail.com>
[not found] ` <alpine.DEB.2.20.1610201454410.5073@nanos>
2016-10-21 1:00 ` [PATCH] kernel: irq: fix build failure Stephen Rothwell
2016-10-21 8:07 ` Thomas Gleixner [this message]
2016-10-21 10:20 ` Stephen Rothwell
2016-10-24 10:22 ` Lee Jones
2016-10-24 11:32 ` Stephen Rothwell
2016-10-24 12:08 ` Lee Jones
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=alpine.DEB.2.20.1610211006370.4797@nanos \
--to=tglx@linutronix$(echo .)de \
--cc=broonie@kernel$(echo .)org \
--cc=grygorii.strashko@ti$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=lee.jones@linaro$(echo .)org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.niestroj@grinn-global$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sudipm.mukherjee@gmail$(echo .)com \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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