From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rob Herring <robh@kernel.org>, Maxime Ripard <mripard@kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Linus Walleij <linus.walleij@linaro.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>
Subject: Re: Linux 5.17-rc5
Date: Mon, 21 Feb 2022 12:44:12 -0800 [thread overview]
Message-ID: <46ca0731-0d4f-9cd1-cd2b-4d8cf73cbfcc@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgyJOBhc9PQr-iAW7yYWoni8Gr+O30vtwDR--opn8hyTA@mail.gmail.com>
On 2/21/22 10:31, Linus Torvalds wrote:
> On Mon, Feb 21, 2022 at 10:10 AM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> Oh, that is "just" the result of the netfilter build problem.
>
> Oh, ok. I assumed it was some runtime failure since it was under the
> qemu rubric.
>
Sorry for the confusion. I'll try to clarify if that happens again
in the future.
Guenter
>> The real question is why to patch introducing the problem made it
>> upstream even though the problem was reported several days before
>> the push request was sent.
>
> Yeah, there's a separate gripe-thread for that. The fix is in the
> netfilter tree and has been there for a week...
>
> Linus
next prev parent reply other threads:[~2022-02-21 20:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 17:44 Linus Torvalds
2022-02-21 18:10 ` Guenter Roeck
2022-02-21 18:31 ` Linus Torvalds
2022-02-21 20:44 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-20 21:19 Linus Torvalds
2022-02-20 23:37 ` Robert Gadsdon
2022-02-21 16:11 ` Woody Suwalski
2022-02-21 14:23 ` Woody Suwalski
2022-02-21 17:56 ` Linus Torvalds
2022-02-21 18:01 ` Eric Dumazet
2022-02-21 18:07 ` Linus Torvalds
2022-02-21 18:21 ` Eric Dumazet
2022-02-21 18:25 ` Pablo Neira Ayuso
2022-02-21 18:28 ` Eric Dumazet
2022-02-21 18:42 ` Pablo Neira Ayuso
2022-02-21 18:22 ` Woody Suwalski
2022-02-21 18:25 ` Pablo Neira Ayuso
2022-02-21 19:52 ` Robert Gadsdon
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=46ca0731-0d4f-9cd1-cd2b-4d8cf73cbfcc@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®