From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: PERF_EVENT_IOC_SET_FILTER has different values based on bitness
Date: Wed, 8 Oct 2014 12:22:04 -0300 [thread overview]
Message-ID: <20141008152204.GN14113@kernel.org> (raw)
In-Reply-To: <54355592.6000604@gmail.com>
Em Wed, Oct 08, 2014 at 09:17:38AM -0600, David Ahern escreveu:
> On 10/8/14, 1:23 AM, Peter Zijlstra wrote:
> >Should be fixed for a while now
> >
> >---
> >commit b3f207855f57b9c8f43a547a801340bb5cbc59e5
> >Author: Pawel Moll <pawel.moll@arm.com>
> >Date: Fri Jun 13 16:03:32 2014 +0100
> >
> > perf: Handle compat ioctl
> >
>
> that works. Can we get this queued to the stable releases (at least as far
> back as v3.4)?
I wonder how that works best, being on the receiving side of such requests
from time to time.
I guess that to scale, that would be better done by:
1. Reporter tests if the patch applies (and works) on the desired
targets.
2. Reporter sends the request, with the above test results, to
stable@kernel.org, following whatever conventions are to get the
attention of the stable release maintainers.
- Arnaldo
next prev parent reply other threads:[~2014-10-08 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 23:07 PERF_EVENT_IOC_SET_FILTER has different values based on bitness David Ahern
2014-10-07 23:17 ` David Ahern
2014-10-08 0:50 ` Andi Kleen
2014-10-08 0:53 ` David Ahern
2014-10-08 0:54 ` Andi Kleen
2014-10-08 7:23 ` Peter Zijlstra
2014-10-08 15:17 ` David Ahern
2014-10-08 15:22 ` Arnaldo Carvalho de Melo [this message]
2014-10-08 15:25 ` David Ahern
2014-10-09 6:54 ` Ingo Molnar
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=20141008152204.GN14113@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).