From: Lee Jones <lee.jones@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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>, 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: Mon, 24 Oct 2016 11:22:15 +0100 [thread overview]
Message-ID: <20161024102215.GN14477@dell> (raw)
In-Reply-To: <alpine.DEB.2.20.1610211006370.4797@nanos>
On Fri, 21 Oct 2016, Thomas Gleixner wrote:
> 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.
Did this get in? I still have people complaining about it.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] kernel: irq: fix build failure
Date: Mon, 24 Oct 2016 11:22:15 +0100 [thread overview]
Message-ID: <20161024102215.GN14477@dell> (raw)
In-Reply-To: <alpine.DEB.2.20.1610211006370.4797@nanos>
On Fri, 21 Oct 2016, Thomas Gleixner wrote:
> 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.
Did this get in? I still have people complaining about it.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-10-24 10:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 17:36 [PATCH] kernel: irq: fix build failure Sudip Mukherjee
2016-10-10 15:55 ` Sudip Mukherjee
2016-10-10 15:55 ` Sudip Mukherjee
2016-10-20 12:55 ` Thomas Gleixner
2016-10-20 12:55 ` Thomas Gleixner
2016-10-21 1:00 ` Stephen Rothwell
2016-10-21 1:00 ` Stephen Rothwell
2016-10-21 8:07 ` Thomas Gleixner
2016-10-21 8:07 ` Thomas Gleixner
2016-10-21 10:20 ` Stephen Rothwell
2016-10-21 10:20 ` Stephen Rothwell
2016-10-24 10:22 ` Lee Jones [this message]
2016-10-24 10:22 ` Lee Jones
2016-10-24 11:32 ` Stephen Rothwell
2016-10-24 11:32 ` Stephen Rothwell
2016-10-24 12:08 ` Lee Jones
2016-10-24 12:08 ` Lee Jones
2016-10-21 8:27 ` [tip:irq/urgent] kernel/irq: Export irq_set_parent() tip-bot for Sudip Mukherjee
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=20161024102215.GN14477@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.niestroj@grinn-global.com \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
/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.