All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: TAKANO Mitsuhiro <takano32@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	James Clark <james.clark@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the perf tree with the perf-current tree
Date: Thu, 12 Nov 2026 23:21:40 -0800	[thread overview]
Message-ID: <ava6hCDZ2kOjS5oR@google.com> (raw)
In-Reply-To: <179449737932.73597.12778815944082557280@gmail.com>

Hello,

On Thu, Nov 12, 2026 at 03:29:39PM +0000, TAKANO Mitsuhiro wrote:
> Hi Mark,
> 
> Thanks for the notice. One thing worth knowing: the full stop is
> intentional, so keeping it in the resolution is the right outcome.
> 
> It came out of review. James asked for it on v2:
> 
>   https://lore.kernel.org/all/a188c604-46c0-48fb-9cbd-9eacad88b5c9@linaro.org/
> 
> and v3 added it:
> 
>   https://lore.kernel.org/all/20261107022145.1713159-1-takano32@gmail.com/
> 
> The copy in the perf tree is that v3. The copy in perf-current is the v2
> that predates the review, so perf-current is the stale one - nothing more
> than the period is missing from it.

Thanks for the clarification.  Sorry I missed Arnaldo already took this
patch into the current tree.  I'll merge it once it land on the mainline
and will resolve it correctly.

I think it's trivial so it'd be fine to leave v7.4 without the period.

Thanks,
Namhyung


      reply	other threads:[~2026-11-13  7:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 13:10 linux-next: manual merge of the perf tree with the perf-current tree Mark Brown
2026-11-12 15:29 ` TAKANO Mitsuhiro
2026-11-13  7:21   ` Namhyung Kim [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=ava6hCDZ2kOjS5oR@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=broonie@kernel.org \
    --cc=james.clark@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=takano32@gmail.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.