All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Martin Doucha <martin.doucha@suse.com>,
	jhs@mojatatu.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] tcindex01: fix compilation errors due to missing TCA_TCINDEX_ constants
Date: Wed, 17 Jan 2024 10:08:28 +0100	[thread overview]
Message-ID: <20240117090828.GA2665992@pevik> (raw)
In-Reply-To: <CAEemH2dOHxT__TjWuDJY7Dq0p8-n7ZdRHD2nU7sw9aawUFqLfg@mail.gmail.com>

> On Tue, Jan 16, 2024 at 8:12 PM Petr Vorel <pvorel@suse.cz> wrote:

> > Hi Li,,

> > > The change addresses compilation errors encountered in the tcindex01.c
> > > test when compiled against kernel-6.7 and above.

> > "against kernel-6.7". But 82b2545ed9a will be released in 6.8, right?


> It's already contained in the kernel-6.7 release.

Well, it's not that important (and was already merged anyway), but just for
clarity:

on updated kernel tree (with fetched tags):
$ git tag --contains 82b2545ed9a
next-20240104
next-20240105
next-20240109
next-20240110
next-20240112

Also, LTP tree without this patch compiles on Tumbleweed with 6.7 kernel
headers.

gitk shows:
$ gitk -1 82b2545ed9a
Follows: v6.7-rc6
Precedes: next-20240104, next-20240105, next-20240109, next-20240110, next-20240112
=> IMHO netdev merge window started at v6.7-rc6, but it's window for v6.8-rc1.

> Patch merged, thanks!

Thanks for spotting this early enough!

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-01-17  9:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16  3:17 [LTP] [PATCH] tcindex01: fix compilation errors due to missing TCA_TCINDEX_ constants Li Wang
2024-01-16 12:12 ` Petr Vorel
2024-01-17  1:42   ` Li Wang
2024-01-17  9:08     ` Petr Vorel [this message]
2024-01-16 12:38 ` Martin Doucha
2024-01-16 16:10   ` Petr Vorel
2024-01-17 15:52 ` Jamal Hadi Salim
2024-01-18  0:48   ` Li Wang
2024-01-21 17:24     ` Jamal Hadi Salim

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=20240117090828.GA2665992@pevik \
    --to=pvorel@suse.cz \
    --cc=jhs@mojatatu.com \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.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 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.