Re: kern/43986 (ataraid(4) doesn't seem to handle weird array configs very gracefully)

["Andrius V via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/43986; it has been noted by GNATS.

From: Andrius V <vezhlys%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: "Greg A. Woods" <woods%planix.com@localhost>
Subject: Re: kern/43986 (ataraid(4) doesn't seem to handle weird array configs
 very gracefully)
Date: Wed, 30 Jul 2025 21:28:29 +0300

 On Sun, Jul 27, 2025 at 11:40=E2=80=AFPM Greg A. Woods via gnats
 <gnats-admin%netbsd.org@localhost> wrote:
 >
 > The following reply was made to PR kern/43986; it has been noted by GNATS=
 .
 >
 > From: "Greg A. Woods" <Greg.A.Woods%avoncote.ca@localhost>
 > To: NetBSD GNATS <gnats-bugs%NetBSD.org@localhost>
 > Cc:
 > Subject: Re: kern/43986 (ataraid(4) doesn't seem to handle weird array co=
 nfigs very gracefully)
 > Date: Sun, 27 Jul 2025 13:28:32 -0700
 >
 >  --pgp-sign-Multipart_Sun_Jul_27_13:28:19_2025-1
 >  Content-Type: text/plain; charset=3DUS-ASCII
 >
 >  At Sun, 20 Jul 2025 21:34:12 +0000 (UTC), andvar%NetBSD.org@localhost wrote:
 >  > closing: fixed and pulled up months ago.
 >  >
 >  > was waiting for the additional confirmation, but I guess there's no
 >  > time or interest to do it anytime soon.
 >
 >  Sorry, yeah, spring and summer activities have overwhelmed time
 >  available for computer activities....  That and I don't seem to have a
 >  spare working monitor available for it either -- but I'll need to fix
 >  that problem sooner or later for many reasons....
 >
 >  --
 >                                         Greg A. Woods <gwoods%acm.org@localhost>
 >
 >  Kelowna, BC     +1 250 762-7675           RoboHack <woods%robohack.ca@localhost>
 >  Planix, Inc. <woods%planix.com@localhost>     Avoncote Farms <woods%avoncote.ca@localhost>
 >
 >  --pgp-sign-Multipart_Sun_Jul_27_13:28:19_2025-1
 >  Content-Type: application/pgp-signature
 >  Content-Transfer-Encoding: 7bit
 >  Content-Description: OpenPGP Digital Signature
 >
 >  -----BEGIN PGP SIGNATURE-----
 >
 >  iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCaIaL5QAKCRBmfXG3eL/0
 >  f9zcAJ9H8d4VYLJ1UagNVQJ5kHP2bxpEagCeNNS4tQryi5GLcqKfJDJoxbJ6BFg=3D
 >  =3Dms/+
 >  -----END PGP SIGNATURE-----
 >
 >  --pgp-sign-Multipart_Sun_Jul_27_13:28:19_2025-1--
 >
 
 
 No worries, will all busy, it's understandable, and this functionality
 is not extremely relevant these days..
 If you will have a chance to test, feedback is still welcome. There
 were few other PRs which may be fixed by now. Thanks.