From: Greg KH <gregkh@linuxfoundation.org>
To: Ivan Babrou <ivan@cloudflare.com>
Cc: Ignat Korchagin <ignat@cloudflare.com>,
stable@vger.kernel.org, Daniel Dao <dqminh@cloudflare.com>,
Alex Forster <aforster@cloudflare.com>
Subject: Re: Cross-compiling libbpf from Linux 4.14 tree
Date: Thu, 10 Jan 2019 17:13:29 +0100 [thread overview]
Message-ID: <20190110161329.GA12438@kroah.com> (raw)
In-Reply-To: <CABWYdi3e+usMqXicgrNtuczwZc+o1TxHNVT2aAfrez75hgPY2A@mail.gmail.com>
On Thu, Jan 10, 2019 at 08:03:53AM -0800, Ivan Babrou wrote:
> We've also seen issues with Mellanox hardware on 4.19, like this one:
>
> * https://www.mail-archive.com/netdev@vger.kernel.org/msg253346.html
Ugh, ok, thanks for testing and letting people know about this type of
thing. Sorry it's causing problems. I wonder why the "normal"
netfilter testing didn't catch your issues, that might be good to add to
the test suite after it's all done...
thanks,
greg k-h
prev parent reply other threads:[~2019-01-10 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 18:52 Cross-compiling libbpf from Linux 4.14 tree Ignat Korchagin
2019-01-10 14:01 ` Greg KH
2019-01-10 14:12 ` Ignat Korchagin
2019-01-10 16:03 ` Ivan Babrou
2019-01-10 16:13 ` Greg KH [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=20190110161329.GA12438@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aforster@cloudflare.com \
--cc=dqminh@cloudflare.com \
--cc=ignat@cloudflare.com \
--cc=ivan@cloudflare.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).