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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210903170645.pkejqmg2ayw3ijgr@skbuf>
Date:   Fri, 3 Sep 2021 20:06:45 +0300
From:   Ioana Ciornei <ciorneiioana@...il.com>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     "Russell King (Oracle)" <linux@...linux.org.uk>,
        Ioana Ciornei <ciorneiioana@...il.com>,
        Heiner Kallweit <hkallweit1@...il.com>,
        "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
        Ioana Ciornei <ioana.ciornei@....com>,
        Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH net-next] net: dpaa2-mac: add support for more ethtool
 10G link modes

On Fri, Sep 03, 2021 at 03:11:36PM +0200, Andrew Lunn wrote:

> > Thanks. I wonder why searching for it via google and also via patchworks
> > search facility didn't find it.
> > 
> > So, it got incorrectly tagged by netdev maintainers, presumably because
> > they're too quick to classify a patch while discussion on the patch was
> > still ongoing - and there's no way for those discussing that to ever
> > know without finding it in patchwork. Which is pretty much impossible
> > unless you know the patchwork URL format and message ID, and are
> > prepared to regularly poll the patchwork website.
> > 
> > The netdev process, as a patch submitter or reviewer, is really very
> > unfriendly.
> 
> H Russell, Ioana
> 
> It sounds like at LPC there is going to be a time slot to talk about
> netdev processes.

Is this on the Networking track? I didn't find any session that would
appear to target this topic.

> I would like to find out and discuss the new policy
> for the time it takes to merge patches. Patchwork issues, and the lack
> of integration with email workflows could be another interesting topic
> to discuss.

It would be interesting to have patchwork send a notification of some
sorts to the submitter when a certain patch set's state was changed.

Ioana

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ