From: Jiri Olsa <olsajiri@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, "Andrii Nakryiko" <andrii@kernel.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
bpf@vger.kernel.org, "Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Philip Müller" <philm@manjaro.org>
Subject: Re: [PATCH stable 5.10 2/5] kbuild: Quote OBJCOPY var to avoid a pahole call break the build
Date: Wed, 19 Oct 2022 13:18:03 +0200 [thread overview]
Message-ID: <Y0/c68JMlnwUojzq@krava> (raw)
In-Reply-To: <Y0/RXjwt6y1Dfh9y@kroah.com>
On Wed, Oct 19, 2022 at 12:28:46PM +0200, Greg KH wrote:
> On Wed, Oct 19, 2022 at 10:56:01AM +0200, Jiri Olsa wrote:
> > From: Javier Martinez Canillas <javierm@redhat.com>
> >
> > commit ff2e6efda0d5c51b33e2bcc0b0b981ac0a0ef214 upstream.
>
> I only see patches 2, 3, and 4 of this series, same with
> lore.kernel.org:
> https://lore.kernel.org/all/20221019085604.1017583-3-jolsa@kernel.org/
>
> Are the remaining ones somewhere else?
hum, the 'git send-email' log says it was sent to stable@vger.kernel.org
(plus other emails) all with no problem.. maybe some mailing list hiccup?
I'd give it some time
jirka
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2022-10-19 11:41 UTC|newest]
Thread overview: 11+ 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 [this message]
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-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=Y0/c68JMlnwUojzq@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=iii@linux.ibm.com \
--cc=javierm@redhat.com \
--cc=nathan@kernel.org \
--cc=philm@manjaro.org \
--cc=stable@vger.kernel.org \
--cc=yakoyoku@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox