Date: Tue, 2 Jun 2020 20:49:18 +0200 From: Peter Eriksson <pen@lysator.liu.se> To: freebsd-hackers@freebsd.org Cc: Daniel Ebdrup Jensen <debdrup@freebsd.org>, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Subject: Re: Is the "ciss" driver unmaintained? (For HP RAID/HBA cards) Message-ID: <85F9C3DF-B9DF-42F1-8229-A701EDF5AC11@lysator.liu.se> In-Reply-To: <202006020304.05234hp0015172@gndrsh.dnsmgr.net> References: <202006020304.05234hp0015172@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks. I hope someone steps forward. I=E2=80=99d love to have some = interaction with someone soon=E2=80=A6 :-) For the moment I have a test server (running 12.1-STABLE, but if needed = I could boot it with a 13-CURRENT kernel on it to test stuff) set up = with two HP H241 SmartHBA controllers and three HP D6020 70-drive JBOD = external cabinets attached (two of the D6020:s are connected to one = controller so I can test with 140 12TB drives on one controller right = now, the third D6020 only have 10 drives or so).=20 However, I=E2=80=99ll have to move the fully equipped ones to production = servers sometime in the near future and then it=E2=80=99ll be more = difficult to test stuff... - Peter > On 2 Jun 2020, at 05:04, Rodney W. Grimes = <freebsd-rwg@gndrsh.dnsmgr.net> wrote: >=20 >> On Mon, Jun 01, 2020 at 11:39:36PM +0200, Peter Eriksson wrote: >>> I submitted a couple of bug reports (and patches) for the ?ciss? = driver about a month ago but it seems there is no response to it? >>>=20 >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246279 = <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246279>; >>>=20 >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246280 = <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246280>; >>>=20 >>> Now I can run a locally built kernel but I prefer to stay away from = that if possible so would really like to have it merged into the = official release (if possible) in the long run. >>>=20 >>> Is there some way to find out who (if anyone) is responsible for = that part of the kernel? Or should I just assume it?s abandoned and try = to submit a fix somewhere else? And if so how? >>>=20 >>> - Peter >>>=20 >>=20 >> Hi Peter, >>=20 >> I'm not yet a commiter, so I can't speak on behalf of those that are = - but when=20 >> working on documentation for man-pages I tend to following procedure: >>=20 >> To start with the first thing I do is look in src/MAINTAINERS or, = failing that,=20 >> see who last had a good set of commits going for the chunk of code = that's being=20 >> touched - and then simply try reaching out to them. >>=20 >> If you have a patch prepared that applies against the head of the = tree, and on=20 >> top of that if it's build and runtime tested in production, that at = least mean=20 >> you've done everything that can be reasonably expected. >>=20 >> Who knows, you may be in luck that someone who's interested might = read hackers@=20 >> too. :) >=20 > It looks like these bugs have not been triaged by bugmaster@ they > are still on the incomping bugs@ mail list. But after a quick read > of them I boldly stuck imp@ on them who is probably the person most > knowing about the cam layer and large storage arrays. >=20 > He can slap my hand later... >=20 >> Yours, >> Daniel Ebdrup Jensen >=20 > --=20 > Rod Grimes = rgrimes@freebsd.org <mailto:rgrimes@freebsd.org> > _______________________________________________ > freebsd-hackers@freebsd.org <mailto:freebsd-hackers@freebsd.org> = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers = <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>; > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org = <mailto:freebsd-hackers-unsubscribe@freebsd.org>"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85F9C3DF-B9DF-42F1-8229-A701EDF5AC11>