public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Bart Van Assche <bvanassche@acm.org>,
	linux-parisc <linux-parisc@vger.kernel.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Broken Domain Validation in 6.1.84+
Date: Thu, 4 Apr 2024 16:07:28 -0400	[thread overview]
Message-ID: <db784080-2268-4e6d-84bd-b33055a3331b@bell.net> (raw)
In-Reply-To: <d1fc0b8d-4858-4234-8b66-c8980f612ea2@acm.org>

On 2024-04-04 12:32 p.m., Bart Van Assche wrote:
> Can you please help with verifying whether this kernel warning is only
> triggered by the 6.1 stable kernel series or whether it is also
> triggered by a vanilla kernel, e.g. kernel v6.8? That will tell us
> whether we need to review the upstream changes or the backports on the
> v6.1 branch.
Stable kernel v6.8.3 is okay.

-- 
John David Anglin  dave.anglin@bell.net


  reply	other threads:[~2024-04-04 20:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 16:20 Broken Domain Validation in 6.1.84+ John David Anglin
2024-04-04 16:32 ` Bart Van Assche
2024-04-04 20:07   ` John David Anglin [this message]
2024-04-05 19:36     ` Bart Van Assche
2024-04-06 14:30       ` John David Anglin
2024-04-06 15:06         ` James Bottomley
2024-04-06 16:16           ` John David Anglin
2024-04-06 18:51             ` James Bottomley
2024-04-07  6:16               ` Greg KH
2024-04-07 13:19             ` Martin K. Petersen
2024-04-08  0:58               ` John David Anglin
2024-04-08 13:46                 ` Martin K. Petersen
2024-04-08 14:17                   ` John David Anglin
2024-04-08 14:32                     ` Martin K. Petersen
2024-04-08 15:17               ` John David Anglin
2024-04-08 17:19                 ` Martin K. Petersen
2024-04-11  4:40                   ` Cyril Brulebois
2024-04-11  7:29                   ` Greg KH

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=db784080-2268-4e6d-84bd-b33055a3331b@bell.net \
    --to=dave.anglin@bell.net \
    --cc=bvanassche@acm.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-scsi@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