From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jiri Olsa <jolsa@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 16
Date: Thu, 16 Sep 2021 18:43:37 -0300 [thread overview]
Message-ID: <8850F8DA-5C73-4A2C-92C7-FE17ADCD2ADB@gmail.com> (raw)
In-Reply-To: <CAADnVQJ+BnWKf61rfDhKsOv05yFRXeRrMs4d443dcSOycaTRcg@mail.gmail.com>
On September 16, 2021 2:30:04 PM GMT-03:00, Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
>On Wed, Sep 15, 2021 at 11:11 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Hi all,
>>
>> Changes since 20210915:
>>
>> The bpf-next tree still had its build failure so I used the version from
>> next-20210913.
>
>Arnaldo,
>
>could you please push Andrii's fix into your tree asap
>and then cleanup/follow up with a better fix if necessary?
It's there since yesterday:
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=00e0ca3721cf2ddcb38cf676a3de61933640d31d
Replying just now since it's a holiday here and I was AFK.
- Arnaldo
next prev parent reply other threads:[~2021-09-16 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 6:11 linux-next: Tree for Sep 16 Stephen Rothwell
2021-09-16 17:30 ` Alexei Starovoitov
2021-09-16 21:43 ` Arnaldo Carvalho de Melo [this message]
2021-09-16 22:49 ` Stephen Rothwell
2021-09-16 22:53 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2022-09-16 6:52 Stephen Rothwell
2020-09-16 7:39 Stephen Rothwell
2019-09-16 22:38 Mark Brown
2016-09-16 4:45 Stephen Rothwell
2015-09-16 3:15 Stephen Rothwell
2014-09-16 7:56 Stephen Rothwell
2014-09-17 18:12 ` Guenter Roeck
2013-09-16 3:13 Stephen Rothwell
2013-09-16 3:13 ` 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=8850F8DA-5C73-4A2C-92C7-FE17ADCD2ADB@gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 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.