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] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 7 Mar 2023 17:38:34 +0100
From:   Simon Horman <simon.horman@...igine.com>
To:     Muhammad Usama Anjum <usama.anjum@...labora.com>
Cc:     Jakub Kicinski <kuba@...nel.org>, Ariel Elior <aelior@...vell.com>,
        Manish Chopra <manishc@...vell.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Paolo Abeni <pabeni@...hat.com>, kernel@...labora.com,
        kernel-janitors@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] qede: remove linux/version.h and linux/compiler.h

On Tue, Mar 07, 2023 at 06:39:20PM +0500, Muhammad Usama Anjum wrote:
> On 3/4/23 4:54 AM, Jakub Kicinski wrote:
> > On Fri,  3 Mar 2023 23:53:50 +0500 Muhammad Usama Anjum wrote:
> >> make versioncheck reports the following:
> >> ./drivers/net/ethernet/qlogic/qede/qede.h: 10 linux/version.h not needed.
> >> ./drivers/net/ethernet/qlogic/qede/qede_ethtool.c: 7 linux/version.h not needed.
> >>
> >> So remove linux/version.h from both of these files. Also remove
> >> linux/compiler.h while at it as it is also not being used.
> >>
> >> Signed-off-by: Muhammad Usama Anjum <usama.anjum@...labora.com>
> > 
> > # Form letter - net-next is closed
> > 
> > The merge window for v6.3 has begun and therefore net-next is closed
> > for new drivers, features, code refactoring and optimizations.
> > We are currently accepting bug fixes only.
> > 
> > Please repost when net-next reopens after Mar 6th.
> It is Mar 7th. Please review.

I think that the way it works is that you need to repost the patch.
Probably with REPOST in the subject if it is unchanged:

Subject: [PATCH net-next repost v2] ...

Or bumped to v3 if there are changes.

Subject: [PATCH net-next v3] ...

Also, as per the examples above, the target tree, in this case
'net-next' should be included in the subject.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ