Date: Mon, 1 Jun 2020 23:48:32 +0200 From: Daniel Ebdrup Jensen <debdrup@FreeBSD.org> To: freebsd-hackers@freebsd.org Subject: Re: Is the "ciss" driver unmaintained? (For HP RAID/HBA cards) Message-ID: <20200601214832.jpudeti7he6u626j@nerd-thinkpad.local> In-Reply-To: <2D6FFED4-41F5-47E9-BA59-D762363AE6CE@lysator.liu.se> References: <2D6FFED4-41F5-47E9-BA59-D762363AE6CE@lysator.liu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
--rids5i3gvpfrnise Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 01, 2020 at 11:39:36PM +0200, Peter Eriksson wrote: >I submitted a couple of bug reports (and patches) for the =E2=80=9Cciss=E2= =80=9D driver about a month ago but it seems there is no response to it=E2= =80=A6 > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246279 <https://bug= s.freebsd.org/bugzilla/show_bug.cgi?id=3D246279> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246280 <https://bugs= =2Efreebsd.org/bugzilla/show_bug.cgi?id=3D246280> > >Now I can run a locally built kernel but I prefer to stay away from that i= f possible so would really like to have it merged into the official release= (if possible) in the long run. > >Is there some way to find out who (if anyone) is responsible for that part= of the kernel? Or should I just assume it=E2=80=99s abandoned and try to s= ubmit a fix somewhere else? And if so how? > >- Peter > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Hi Peter, 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: To start with the first thing I do is look in src/MAINTAINERS or, failing t= hat,=20 see who last had a good set of commits going for the chunk of code that's b= eing=20 touched - and then simply try reaching out to them. 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 m= ean=20 you've done everything that can be reasonably expected. Who knows, you may be in luck that someone who's interested might read hack= ers@=20 too. :) Yours, Daniel Ebdrup Jensen --rids5i3gvpfrnise Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEDonNJPbg/JLIMoS6Ps5hSHzN87oFAl7Vd7BfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDBF ODlDRDI0RjZFMEZDOTJDODMyODRCQTNFQ0U2MTQ4N0NDREYzQkEACgkQPs5hSHzN 87qltAgAo2inpOy7g2lat0Mq5ZngXbllwas692HL49upgsOK56zFsqhaOnaKlWXn R84cxb+2IdfQ796rvj38fwOjsprcsfpwDxMxtbsqWnB9llXAJaHAITgDJrH0kEsH dyaCIjkidtFTM/If59+vkUfAn/4OwEcumE5Eov5ofTdD2WwHaj3C1yOxVxUn1YMX JIqVnVmhvDWc1eXwhmL6UIYhmFFG4lcUE7QYSnsv+7FFkXc+8H+TRO1rCohYsEcd Ff2RFlbchLVX1Cc0dch3zaWW4rGAkANrzkYraArUVxXmf+uXT3bYFyXdpZYkgyP7 bQ0ZozxNZTZTtw8z3F1WIuRJfz+8cg== =SwI9 -----END PGP SIGNATURE----- --rids5i3gvpfrnise--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200601214832.jpudeti7he6u626j>