lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <f8daefff-fe19-18f7-df57-f8e00ea1c7ad@datenfreihafen.org> Date: Mon, 20 Feb 2023 22:44:45 +0100 From: Stefan Schmidt <stefan@...enfreihafen.org> To: Jakub Kicinski <kuba@...nel.org>, Miquel Raynal <miquel.raynal@...tlin.com> Cc: davem@...emloft.net, linux-wpan@...r.kernel.org, alex.aring@...il.com, netdev@...r.kernel.org, linux-bluetooth@...r.kernel.org Subject: Re: pull-request: ieee802154-next 2023-02-02 Hello Jakub. On 04.02.23 20:18, Jakub Kicinski wrote: > On Sat, 4 Feb 2023 12:46:56 +0100 Miquel Raynal wrote: >>> I left some comments on the netlink part, sorry for not looking >>> at it earlier. >> >> As I'm not extremely comfortable with all the netlink conventions I >> might have squeezed "important" checks, I will try to make the code >> more robust as you suggested. >> >> I will do my best to address these, probably next week, do you prefer >> to wait for these additional changes to apply on top of wpan-next and >> Stefan to rush with another PR before -rc8? Or do you accept to pull the >> changes now and to receive a couple of patches in a following fixes >> PR? (the latter would be the best IMHO, but it's of course up to you). > > I have a slight preference to wait with the pulling until the fixes/ > refactoring arrives. The new pull request as v2 has just been posted. regards Stefan Schmidt
Powered by blists - more mailing lists