public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Pavel Machek <pavel@denx.de>,
	cip-dev <cip-dev@lists.cip-project.org>,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: WIFI in 6.1.X was Re: Potential ext4 corruption in 6.1.64-cip10
Date: Mon, 11 Dec 2023 21:27:45 +0100	[thread overview]
Message-ID: <ZXdwwdiA6lh3VcYR@duo.ucw.cz> (raw)
In-Reply-To: <df30a458-00c9-4b64-8963-27c556603981@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

Hi!

> Ah, that missing dependency of the patch - subtle as it was written.
> 
> > I'll just do 6.1.66 based -cip and -cip-rt releases, unless someone
> > stops me.

Ok, this is not good week for 6.1.X.

https://www.phoronix.com/news/Linux-6.6.6-Released

There's wifi regression in 6.1.66. I guess that's better than ext4
regression, and 6.1.67 is not nice round number, so I guess we do not
need to do anything just now... but if someone is affected by the
problem let me know.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-12-11 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11  6:33 Potential ext4 corruption in 6.1.64-cip10 Jan Kiszka
2023-12-11  9:36 ` Pavel Machek
2023-12-11  9:42   ` Jan Kiszka
2023-12-11  9:53     ` Pavel Machek
2023-12-11  9:58       ` Jan Kiszka
2023-12-11 20:27         ` Pavel Machek [this message]
2023-12-12  5:38           ` WIFI in 6.1.X was " Jan Kiszka

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=ZXdwwdiA6lh3VcYR@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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