From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the perf tree
Date: Thu, 23 Nov 2023 19:20:16 -0300 [thread overview]
Message-ID: <ZV/QIFsBVmn8BXKJ@kernel.org> (raw)
In-Reply-To: <20231124091458.535a0437@canb.auug.org.au>
Em Fri, Nov 24, 2023 at 09:14:58AM +1100, Stephen Rothwell escreveu:
> Hi all,
>
> The following commit is also in the perf-current tree as a different
> commit (but the same patch):
>
> a399ee6773d6 ("tools: Disable __packed attribute compiler warning due to -Werror=attributes")
>
> This is commit
>
> 57686a72da08 ("tools: Disable __packed attribute compiler warning due to -Werror=attributes")
>
> in the perf-current tree.
Yeah, We're in the first phases of versioned co-maintainership and when
I tried to test perf-tools, now being maintained by Namhyung, I noticed
a problem that had been fixed on perf-tools-next, that I'm maintaining,
so I asked Namhyung to cherry-pick something slated for 6.8 to the 6.7
tree.
- Arnaldo
next prev parent reply other threads:[~2023-11-23 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 22:14 linux-next: duplicate patch in the perf tree Stephen Rothwell
2023-11-23 22:20 ` Arnaldo Carvalho de Melo [this message]
2023-12-01 3:16 Stephen Rothwell
2024-04-28 23:04 Stephen Rothwell
2024-05-19 21:34 Stephen Rothwell
2024-05-21 22:34 ` Stephen Rothwell
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=ZV/QIFsBVmn8BXKJ@kernel.org \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).