From: Linus Walleij <linus.walleij@linaro.org>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: rostedt@goodmis.org, mingo@redhat.com, linux@armlinux.org.uk,
tony@atomide.com, bcousson@baylibre.com, paul@pwsan.com,
krzysztof.kozlowski@linaro.org, alim.akhtar@samsung.com,
stefan@agner.ch, rmk+kernel@armlinux.org.uk, broonie@kernel.org,
sebastian.reichel@collabora.co.uk,
linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM: ftrace: remove unused ftrace_graph_caller_old() declaration
Date: Mon, 3 Oct 2022 14:17:21 +0200 [thread overview]
Message-ID: <CACRpkdZPB9hm7kMUzpMdNu9RP94vgvxkrQ70OGb_Qm8k--2zsQ@mail.gmail.com> (raw)
In-Reply-To: <20220914034615.1240860-4-cuigaosheng1@huawei.com>
On Wed, Sep 14, 2022 at 5:46 AM Gaosheng Cui <cuigaosheng1@huawei.com> wrote:
> All uses of ftrace_graph_caller_old() were removed by
> commit d3c61619568c ("ARM: 8788/1: ftrace: remove old
> mcount support"), so remove the declaration, too.
>
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Please put this into Russell's patch tracker.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-03 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 3:46 [PATCH 0/3] Remove unused declarations for arm Gaosheng Cui
2022-09-14 3:46 ` [PATCH 1/3] ARM: OMAP2+: remove orphan declarations from omap2 Gaosheng Cui
2022-09-14 3:46 ` [PATCH 2/3] ARM: s3c: remove orphan declarations from arch/arm/mach-s3c/devs.h Gaosheng Cui
2022-09-14 9:18 ` Mark Brown
2022-09-19 10:19 ` (subset) " Krzysztof Kozlowski
2022-09-14 3:46 ` [PATCH 3/3] ARM: ftrace: remove unused ftrace_graph_caller_old() declaration Gaosheng Cui
2022-10-03 12:17 ` Linus Walleij [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=CACRpkdZPB9hm7kMUzpMdNu9RP94vgvxkrQ70OGb_Qm8k--2zsQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=cuigaosheng1@huawei.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=paul@pwsan.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=sebastian.reichel@collabora.co.uk \
--cc=stefan@agner.ch \
--cc=tony@atomide.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 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).