public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pavel Machek <pavel@denx.de>
Cc: cip-dev <cip-dev@lists.cip-project.org>,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: WIFI in 6.1.X was Re: Potential ext4 corruption in 6.1.64-cip10
Date: Tue, 12 Dec 2023 06:38:15 +0100	[thread overview]
Message-ID: <b5c05ce7-1548-4dbb-8917-c677e15958eb@siemens.com> (raw)
In-Reply-To: <ZXdwwdiA6lh3VcYR@duo.ucw.cz>

On 11.12.23 21:27, Pavel Machek wrote:
> 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.

Yeah, time to generally reflect on testing and other workflows, it looks
like.

Jan

-- 
Siemens AG, Technology
Linux Expert Center



      reply	other threads:[~2023-12-12  5:38 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         ` WIFI in 6.1.X was " Pavel Machek
2023-12-12  5:38           ` Jan Kiszka [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=b5c05ce7-1548-4dbb-8917-c677e15958eb@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.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