From: Jason Cooper <jason@lakedaemon.net>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] irqchip: gic: Allow gic_arch_extn hooks to call into scheduler
Date: Sun, 17 Aug 2014 21:54:30 -0400 [thread overview]
Message-ID: <20140818015430.GN12769@titan.lakedaemon.net> (raw)
In-Reply-To: <alpine.LFD.2.11.1408172131550.29347@knanqh.ubzr>
On Sun, Aug 17, 2014 at 09:35:11PM -0400, Nicolas Pitre wrote:
> On Sun, 17 Aug 2014, Jason Cooper wrote:
>
> > On Sun, Aug 17, 2014 at 08:04:45PM -0400, Nicolas Pitre wrote:
> > > On Sun, 17 Aug 2014, Jason Cooper wrote:
> > > > On Sun, Aug 17, 2014 at 07:55:23PM +0100, Russell King - ARM Linux wrote:
> > > > > On Sun, Aug 17, 2014 at 01:32:36PM -0400, Jason Cooper wrote:
> > > > > > Applied to irqchip/urgent with Nico's Ack.
> > > > >
> > > > > Interesting, so I'm discussing this patch, and it gets applied anyway...
> > > > > yes, that's great.
> > > >
> > > > Quoting Nico:
> > > >
> > > > "Of course it would be good to clarify things wrt Russell's remark
> > > > independently from this patch."
> > > >
> > > > I took 'independently' to mean "This patch is ok, *and* we need to
> > > > address Russell's concerns in a follow-up patch."
> > > >
> > > > Nico's Reviewed-by with that comment was sent August 13th. The most
> > > > recent activity on this thread was also August 13th. After four days, I
> > > > reasoned there were no objections to his comment.
> > >
> > > Well... I mentioned this patch is a nice cleanup independently of the
> > > reason why it was created in the first place.
> >
> > Ah, fair enough.
> >
> > > Maybe that shouldn't be sorted as "urgent" in that case, especially
> > > when the code having problem with the current state of things is
> > > living out of mainline.
> >
> > hmmm, yes. I've been grappling with the semantics of '/urgent' vice
> > '/fixes'. With mvebu, /fixes is the branch for all changes needing to go
> > into the current -rcX cycle. For irqchip, Thomas suggested /urgent for
> > the equivalent branch. To me, they serve the same purpose.
> > Unfortunately, I occasionally hear "Well, it's not _urgent_ ...". I
> > suppose I'll put up with it for one more cycle and then change it to
> > /fixes. :)
> >
> > wrt this patch, I need to drop it anyway. I was a bit rusty (it's been
> > a few weeks) and forgot to add the Cc -stable and Fixes: tags. I do
> > agree, though, it's certainly not urgent.
>
> Given the raised issue has to do with out-of-tree code, there is no need
> to CC stable in that case anyway.
I could go either way here. On the one hand, a fix is a fix is a fix.
On the other, if it can't be triggered in mainline, we shouldn't accept
it at all.
Stephen, is the out of tree code that triggered this bound for mainline?
thx,
Jason.
next prev parent reply other threads:[~2014-08-18 1:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 13:57 Stephen Boyd
2014-08-13 14:22 ` Russell King - ARM Linux
2014-08-13 14:53 ` Daniel Thompson
2014-08-13 14:55 ` Stephen Boyd
2014-08-13 15:05 ` Russell King - ARM Linux
2014-08-13 15:31 ` Stephen Boyd
2014-08-13 15:44 ` Nicolas Pitre
2014-08-17 17:32 ` Jason Cooper
2014-08-17 18:55 ` Russell King - ARM Linux
2014-08-17 19:04 ` Jason Cooper
2014-08-17 21:41 ` Russell King - ARM Linux
2014-08-18 0:17 ` Nicolas Pitre
2014-08-20 19:11 ` Stephen Boyd
2014-08-18 1:32 ` Jason Cooper
2014-08-18 0:04 ` Nicolas Pitre
2014-08-18 1:25 ` Jason Cooper
2014-08-18 1:35 ` Nicolas Pitre
2014-08-18 1:54 ` Jason Cooper [this message]
2014-08-18 2:18 ` Nicolas Pitre
2014-08-20 19:16 ` Stephen Boyd
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=20140818015430.GN12769@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
/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®