On 3/7/23 9:38 PM, Simon Horman wrote: > 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@xxxxxxxxxxxxx> >>> >>> # 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:Sorry, I didn't know. I'll repost it. > > 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. I don't know much about net tree and its location. This is why people use linux-next for sending patches. I'm not sure about the networking sub system. Would it be accepted if I send it against linux-next as in [PATCH linux-next repost v2]? -- BR, Muhammad Usama Anjum
