All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	namhyung@kernel.org, atrajeev@linux.vnet.ibm.com,
	eranian@google.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Remove unused declarations
Date: Fri, 9 Sep 2022 10:30:12 -0300	[thread overview]
Message-ID: <Yxs/5FvhOKg4i9lb@kernel.org> (raw)
In-Reply-To: <20220909044542.1087870-1-cuigaosheng1@huawei.com>

Em Fri, Sep 09, 2022 at 12:45:40PM +0800, Gaosheng Cui escreveu:
> This series contains a few cleanup patches, to remove unused
> declarations which have been removed. Thanks!

Thanks, applied.

- Arnaldo

 
> Gaosheng Cui (2):
>   perf sort: remove hist_entry__sort_list and sort__first_dimension
>     declaration
>   perf tools: remove perf_pmu_lex declaration
> 
>  tools/perf/util/pmu.y  | 2 --
>  tools/perf/util/sort.h | 2 --
>  2 files changed, 4 deletions(-)
> 
> -- 
> 2.25.1

-- 

- Arnaldo

  parent reply	other threads:[~2022-09-09 13:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  4:45 [PATCH 0/2] Remove unused declarations Gaosheng Cui
2022-09-09  4:45 ` [PATCH 1/2] perf sort: remove hist_entry__sort_list and sort__first_dimension declaration Gaosheng Cui
2022-09-09  4:45 ` [PATCH 2/2] perf tools: remove perf_pmu_lex declaration Gaosheng Cui
2022-09-09 10:29   ` James Clark
2022-09-09 13:43     ` Arnaldo Carvalho de Melo
2022-09-09 13:46       ` Arnaldo Carvalho de Melo
2022-09-09 13:30 ` Arnaldo Carvalho de Melo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-09  3:54 [PATCH 0/2] Remove unused declarations Gaosheng Cui
2022-09-09  3:54 ` Gaosheng Cui
2022-09-09  7:10 ` Takashi Iwai
2022-09-09  7:10   ` Takashi Iwai

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=Yxs/5FvhOKg4i9lb@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=cuigaosheng1@huawei.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@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.