linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: linux-snps-arc@lists.infradead.org
Cc: , linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ARC: perf: Accommodate big-endian CPU
Date: Sat, 26 Oct 2019 13:10:41 +0000	[thread overview]
Message-ID: <20191026131042.73A7E206DD@mail.kernel.org> (raw)
In-Reply-To: <20191022140411.10193-1-abrodkin@synopsys.com>

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.3.7, v4.19.80, v4.14.150, v4.9.197, v4.4.197.

v5.3.7: Build OK!
v4.19.80: Failed to apply! Possible dependencies:
    0e956150fe09f ("ARC: perf: introduce Kernel PMU events support")
    14f81a91ad29a ("ARC: perf: trivial code cleanup")
    baf9cc85ba01f ("ARC: perf: move HW events mapping to separate function")

v4.14.150: Failed to apply! Possible dependencies:
    0e956150fe09f ("ARC: perf: introduce Kernel PMU events support")
    14f81a91ad29a ("ARC: perf: trivial code cleanup")
    4d431290402c8 ("ARCv2: perf: tweak overflow interrupt")
    baf9cc85ba01f ("ARC: perf: move HW events mapping to separate function")

v4.9.197: Failed to apply! Possible dependencies:
    0e956150fe09f ("ARC: perf: introduce Kernel PMU events support")
    14f81a91ad29a ("ARC: perf: trivial code cleanup")
    4d431290402c8 ("ARCv2: perf: tweak overflow interrupt")
    baf9cc85ba01f ("ARC: perf: move HW events mapping to separate function")

v4.4.197: Failed to apply! Possible dependencies:
    05c74e5e53f6c ("bpf: add bpf_skb_load_bytes helper")
    0e956150fe09f ("ARC: perf: introduce Kernel PMU events support")
    14f81a91ad29a ("ARC: perf: trivial code cleanup")
    3379e0c3effa8 ("perf tools: Document the perf sysctls")
    45d8390c56bd2 ("bpf: hash: move select_bucket() out of htab's spinlock")
    538950a1b7527 ("soreuseport: setsockopt SO_ATTACH_REUSEPORT_[CE]BPF")
    568b329a02f75 ("perf: generalize perf_callchain")
    6591f1e6662dd ("bpf: hash: use atomic count")
    688ecfe602205 ("bpf: hash: use per-bucket spinlock")
    75925e1ad7f5a ("perf/x86: Optimize stack walk user accesses")
    781c53bc5d562 ("bpf: export helper function flags and reject invalid ones")
    824bd0ce6c7c4 ("bpf: introduce BPF_MAP_TYPE_PERCPU_HASH map")
    a10423b87a7ea ("bpf: introduce BPF_MAP_TYPE_PERCPU_ARRAY map")
    baf9cc85ba01f ("ARC: perf: move HW events mapping to separate function")
    c5dfd78eb7985 ("perf core: Allow setting up max frame stack depth via sysctl")
    c6c33454072fc ("bpf: support ipv6 for bpf_skb_{set,get}_tunnel_key")
    cfbcf468454ab ("perf core: Pass max stack as a perf_callchain_entry context")
    d5a3b1f691865 ("bpf: introduce BPF_MAP_TYPE_STACK_TRACE")
    e32ea7e747271 ("soreuseport: fast reuseport UDP socket selection")
    ef456144da8ef ("soreuseport: define reuseport groups")
    f8ffad69c9f8b ("bpf: add skb_postpush_rcsum and fix dev_forward_skb occasions")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks,
Sasha

_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

  reply	other threads:[~2019-10-26 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 14:04 [PATCH] ARC: perf: Accommodate big-endian CPU Alexey Brodkin
2019-10-26 13:10 ` Sasha Levin [this message]
2019-11-05 19:52   ` Alexey Brodkin
2019-11-21 20:39     ` Greg Kroah-Hartman
2019-11-27  8:02       ` Alexey Brodkin
2019-11-27  8:01 Alexey Brodkin
2019-11-27  8:32 ` Greg Kroah-Hartman

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=20191026131042.73A7E206DD@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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).