From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Jin, Yao" <yao.jin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Kan Liang <kan.liang@intel.com>, Ian Rogers <irogers@google.com>
Subject: Re: [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to v1.08
Date: Fri, 25 Sep 2020 16:23:41 -0400 [thread overview]
Message-ID: <20200925202341.k2zznmefv7tcjsnc@chatter.i7.local> (raw)
In-Reply-To: <20200925180527.GA2883319@kernel.org>
On Fri, Sep 25, 2020 at 03:05:27PM -0300, Arnaldo Carvalho de Melo wrote:
> Things like b4 help with this and probably have to take into account
> attachments as well, that is why I'm adding Konstantin to the Cc: list
> of this message.
>
> Konstantin, is this case covered? I.e. patches that get botched and then
> require attachments to be sent to then gets processed?
Hmm... it's complicated. The trouble with handling corner-cases is
unexpected ways this can affect other mail. For example, what do we do
when we see a patch in the body, but also a patch as an attachment --
should the attachment win, or did the developer mean something entirely
different ("this is the fixed patch -- I attached the previous version
for your reference").
I am working on a service that will automatically "explode" pull
requests into patch series, so this may help work around this particular
issue. For example, a developer would send a pull-request to the list
and cc "exploderbot@kernel.org" (or someone else can follow up with a cc
to that address). When the bot sees the cc, it will automatically
convert the pull request into patch series and send it to the same
recipients as on the original pull request.
This should help avoid the problem of terrible mail relays and nasty
mail clients.
B4 can already do most of that (see "b4 pr --explode"), so adding the
remaining bits should be easy enough. If this functionality is
interesting to you, I would be happy to have early beta testers.
-K
next prev parent reply other threads:[~2020-09-25 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 3:19 [PATCH v2 0/2] perf: Update CascadelakeX and SkylakeX events list Jin Yao
2020-09-22 19:22 ` Andi Kleen
[not found] ` <20200922031918.3723-2-yao.jin@linux.intel.com>
2020-09-22 19:42 ` [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to v1.08 Arnaldo Carvalho de Melo
[not found] ` <4db737f2-0705-5183-6971-9031acfd123b@linux.intel.com>
2020-09-23 21:04 ` Ian Rogers
2020-09-25 18:05 ` Arnaldo Carvalho de Melo
2020-09-25 18:36 ` Andi Kleen
2020-09-25 19:21 ` Arnaldo Carvalho de Melo
2020-09-25 19:43 ` Ian Rogers
2020-09-25 20:23 ` Konstantin Ryabitsev [this message]
2020-10-09 3:45 ` Jin, Yao
2020-09-28 11:47 ` Arnaldo Carvalho de Melo
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=20200925202341.k2zznmefv7tcjsnc@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.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.