public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrii Nakryiko <andrii@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Jonathan Haslam <jonathan.haslam@gmail.com>,
	Kui-Feng Lee <thinker.li@gmail.com>,
	Stephen Brennan <stephen.s.brennan@oracle.com>,
	Ye Bin <yebin10@huawei.com>, Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] probes updates for v6.10
Date: Sun, 19 May 2024 08:46:24 +0900	[thread overview]
Message-ID: <20240519084624.dce1a405a42684189fb356fe@kernel.org> (raw)
In-Reply-To: <CAHk-=wiMwMviFKdSDyTDdgvapN0W9gFB-DH_1FDP3TDpkMOeGw@mail.gmail.com>

On Sat, 18 May 2024 08:55:55 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Sat, 18 May 2024 at 07:38, Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > Ah, and I missed to build it with W=1.
> 
> Note that I do *not* at all expect people to build with W=1. It gets
> very noisy depending on your compiler version etc, and a lot of the
> W=1 errors are not at all worth worrying about.
> 
> But what I do expect is for merge window pull  requests to have been
> in linux-next, which will give it at least reasonable build coverage
> from the bots,

This is completely my fault that I forgot to push my probes/for-next
and made a pull request to you. I will push the for-next before -rc6 and
if I forgot it I will defer it to next for-next.

> 
> I'm not sure whether it was because I built witch clang (which gives
> some warnings that gcc does not, and vice versa) or whether it was
> just that my clang build has a different Kconfig. Regardless, if this
> had been in linux-next, I'm pretty sure that it would have been found
> before I hit it.

Yes, I missed to build check with clang. I'll make sure to check with
both clang and gcc for release.

I'm sorry for causing you trouble and thanks for fixing the it.

Thank you,

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2024-05-18 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16  0:52 [GIT PULL] probes updates for v6.10 Masami Hiramatsu
2024-05-18  1:54 ` pr-tracker-bot
2024-05-18  2:12 ` Linus Torvalds
2024-05-18  2:23   ` Stephen Brennan
2024-05-18 14:38   ` Masami Hiramatsu
2024-05-18 15:55     ` Linus Torvalds
2024-05-18 23:46       ` Masami Hiramatsu [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=20240519084624.dce1a405a42684189fb356fe@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=andrii@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=jonathan.haslam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stephen.s.brennan@oracle.com \
    --cc=thinker.li@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yebin10@huawei.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