From: Ingo Molnar <mingo@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <peterz@infradead.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: Thu, 9 Oct 2014 08:54:02 +0200 [thread overview]
Message-ID: <20141009065402.GA20178@gmail.com> (raw)
In-Reply-To: <5435575E.2090308@gmail.com>
* David Ahern <dsahern@gmail.com> wrote:
> On 10/8/14, 9:22 AM, Arnaldo Carvalho de Melo wrote:
> >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.
>
> My understanding is that subsystem maintainers do the stable
> requests.
At least for perf bits, the usual workflow is that pretty much
anyone can make requests for backports that we maintainers
missed, and subsystem maintainers look over them and object if
they don't like the suggestion. (Obviously you need to Cc:
maintainers.)
In other words, feel free to forward (tested!) backport commit
IDs to -stable, with maintainers Cc:-ed, and feel free to provide
conflict resolution as well, in cases where they don't apply
cleanly.
> A patch adjustment is needed for v3.4 and v3.10. I am willing
> to do the necessary patch mods for 3.4, 3.10, and 3.14.
That would be useful.
Thanks,
Ingo
prev parent reply other threads:[~2014-10-09 6:54 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
2014-10-08 15:25 ` David Ahern
2014-10-09 6:54 ` Ingo Molnar [this message]
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=20141009065402.GA20178@gmail.com \
--to=mingo@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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 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.