Re: [PATCH net-next v2] genetlink: do not parse attributes for families with zero maxattr

Thu, Oct 10, 2019 at 07:21:02PM CEST, jakub.kicin...@netronome.com wrote: >On Thu, 10 Oct 2019 12:34:02 +0200 (CEST), Michal Kubecek wrote: >> Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing >> to a separate function") moved attribute buffer allocation and attribute >>

Re: [PATCH net-next v2] genetlink: do not parse attributes for families with zero maxattr

On Thu, Oct 10, 2019 at 10:21:02AM -0700, Jakub Kicinski wrote: > On Thu, 10 Oct 2019 12:34:02 +0200 (CEST), Michal Kubecek wrote: > > Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing > > to a separate function") moved attribute buffer allocation and attribute > > parsing

Re: [PATCH net-next v2] genetlink: do not parse attributes for families with zero maxattr

On Thu, 10 Oct 2019 12:34:02 +0200 (CEST), Michal Kubecek wrote: > Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing > to a separate function") moved attribute buffer allocation and attribute > parsing from genl_family_rcv_msg_doit() into a separate function >

Re: [PATCH net-next v2] genetlink: do not parse attributes for families with zero maxattr

Thu, Oct 10, 2019 at 12:34:02PM CEST, mkube...@suse.cz wrote: >Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing >to a separate function") moved attribute buffer allocation and attribute >parsing from genl_family_rcv_msg_doit() into a separate function

[PATCH net-next v2] genetlink: do not parse attributes for families with zero maxattr

Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing to a separate function") moved attribute buffer allocation and attribute parsing from genl_family_rcv_msg_doit() into a separate function genl_family_rcv_msg_attrs_parse() which, unlike the previous code, calls