From: Jiri Olsa <olsajiri@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Slade Watkins <srw@sladewatkins.net>,
kernel test robot <lkp@intel.com>,
stable@vger.kernel.org, kbuild-all@lists.01.org
Subject: Re: [PATCH stable 5.10 5/5] kbuild: Add skip_encoding_btf_enum64 option to pahole
Date: Thu, 20 Oct 2022 09:22:45 +0200 [thread overview]
Message-ID: <Y1D3RTnJXuVaVplU@krava> (raw)
In-Reply-To: <Y1DYPbYZ39vMnh/I@kroah.com>
On Thu, Oct 20, 2022 at 07:10:21AM +0200, Greg KH wrote:
> On Wed, Oct 19, 2022 at 09:35:23PM -0400, Slade Watkins wrote:
> > On Wed, Oct 19, 2022 at 9:14 PM kernel test robot <lkp@intel.com> wrote:
> > >
> > > Hi,
> > >
> > > Thanks for your patch.
> > >
> > > FYI: kernel test robot notices the stable kernel rule is not satisfied.
the patch 5/5 does not have equivalent commit in linus tree,
so I wonder the warning is because of that
jirka
> > >
> > > Rule: 'Cc: stable@vger.kernel.org' or 'commit <sha1> upstream.'
> > > Subject: [PATCH stable 5.10 5/5] kbuild: Add skip_encoding_btf_enum64 option to pahole
> > > Link: https://lore.kernel.org/stable/20221019085604.1017583-6-jolsa%40kernel.org
> >
> > Uh, this should be fine though, right? The stable list was the primary
> > recipient and all show up for me in my stable folder.
>
> Yes, this is fine, this bot is not that smart at times.
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Olsa <olsajiri@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH stable 5.10 5/5] kbuild: Add skip_encoding_btf_enum64 option to pahole
Date: Thu, 20 Oct 2022 09:22:45 +0200 [thread overview]
Message-ID: <Y1D3RTnJXuVaVplU@krava> (raw)
In-Reply-To: <Y1DYPbYZ39vMnh/I@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On Thu, Oct 20, 2022 at 07:10:21AM +0200, Greg KH wrote:
> On Wed, Oct 19, 2022 at 09:35:23PM -0400, Slade Watkins wrote:
> > On Wed, Oct 19, 2022 at 9:14 PM kernel test robot <lkp@intel.com> wrote:
> > >
> > > Hi,
> > >
> > > Thanks for your patch.
> > >
> > > FYI: kernel test robot notices the stable kernel rule is not satisfied.
the patch 5/5 does not have equivalent commit in linus tree,
so I wonder the warning is because of that
jirka
> > >
> > > Rule: 'Cc: stable(a)vger.kernel.org' or 'commit <sha1> upstream.'
> > > Subject: [PATCH stable 5.10 5/5] kbuild: Add skip_encoding_btf_enum64 option to pahole
> > > Link: https://lore.kernel.org/stable/20221019085604.1017583-6-jolsa%40kernel.org
> >
> > Uh, this should be fine though, right? The stable list was the primary
> > recipient and all show up for me in my stable folder.
>
> Yes, this is fine, this bot is not that smart at times.
next prev parent reply other threads:[~2022-10-20 7:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 8:55 [PATCH stable 5.10 0/5] kbuild: Fix compilation for latest pahole release Jiri Olsa
2022-10-19 8:56 ` [PATCH stable 5.10 1/5] bpf: Generate BTF_KIND_FLOAT when linking vmlinux Jiri Olsa
2022-10-19 8:56 ` [PATCH stable 5.10 2/5] kbuild: Quote OBJCOPY var to avoid a pahole call break the build Jiri Olsa
2022-10-19 10:28 ` Greg KH
2022-10-19 11:18 ` Jiri Olsa
2022-10-19 8:56 ` [PATCH stable 5.10 3/5] kbuild: skip per-CPU BTF generation for pahole v1.18-v1.21 Jiri Olsa
2022-10-19 8:56 ` [PATCH stable 5.10 4/5] kbuild: Unify options for BTF generation for vmlinux and modules Jiri Olsa
2022-10-19 8:56 ` [PATCH stable 5.10 5/5] kbuild: Add skip_encoding_btf_enum64 option to pahole Jiri Olsa
2022-10-20 1:13 ` kernel test robot
2022-10-20 1:35 ` Slade Watkins
2022-10-20 1:35 ` Slade Watkins
2022-10-20 5:10 ` Greg KH
2022-10-20 5:10 ` Greg KH
2022-10-20 7:22 ` Jiri Olsa [this message]
2022-10-20 7:22 ` Jiri Olsa
2022-10-19 14:55 ` [PATCH stable 5.10 0/5] kbuild: Fix compilation for latest pahole release Greg KH
2022-10-19 15:30 ` Jiri Olsa
2022-10-26 16:44 ` Greg KH
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=Y1D3RTnJXuVaVplU@krava \
--to=olsajiri@gmail.com \
--cc=greg@kroah.com \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.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.