All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geliang Tang <geliang@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [6.6.y] "selftests/bpf: Add netkit to tc_redirect selftest" needs to be reverted
Date: Mon, 29 Apr 2024 12:59:16 +0200	[thread overview]
Message-ID: <2024042959-steering-periscope-a87b@gregkh> (raw)
In-Reply-To: <0d29b3a324d851402f247a33ef89efe6103e90da.camel@kernel.org>

On Fri, Apr 26, 2024 at 06:22:53PM +0800, Geliang Tang wrote:
> On Fri, 2024-04-26 at 12:21 +0200, Greg Kroah-Hartman wrote:
> > On Fri, Apr 26, 2024 at 06:12:22PM +0800, Geliang Tang wrote:
> > > cc stable@vger.kernel.org
> > 
> > I'm confused, where is the original message here?  You just forwarded
> > my
> > bot response to the list.
> > 
> > greg k-h
> 
> Hi Greg,
> 
> I'm writing to inform you that the commit adfeae2d243d ("selftests/bpf:
> Add netkit to tc_redirect selftest") on linux-stable should be reverted
> from linux-6.6.y. It depends on bpf netkit series [1] which isn't on
> linux-6.6.y branch yet. Otherwise, a bpf selftests building error
> "netlink_helpers.h: No such file or directory" occurs.
> 
> [1]
> https://lore.kernel.org/all/20231024214904.29825-1-daniel@iogearbox.net/

It does not revert cleanly, so can you provide a working revert for us
to queue up?

thanks,

greg k-h

      reply	other threads:[~2024-04-29 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ea05dcf2a0417aa2068a4dfa61bd562a6e8127d6.camel@kernel.org>
     [not found] ` <2024042610-tiring-overdue-a6b5@gregkh>
2024-04-26 10:12   ` [6.6.y] "selftests/bpf: Add netkit to tc_redirect selftest" needs to be reverted Geliang Tang
2024-04-26 10:21     ` Greg Kroah-Hartman
2024-04-26 10:22       ` Geliang Tang
2024-04-29 10:59         ` Greg Kroah-Hartman [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=2024042959-steering-periscope-a87b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=geliang@kernel.org \
    --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.