From: Muhammad Usama Anjum <usama.anjum@xxxxxxxxxxxxx> Date: Tue, 7 Mar 2023 21:53:48 +0500 > 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 Here[0]. > linux-next for sending patches. I'm not sure about the networking sub No, people use the corresponding mailing lists to send and repositories to base their patches on. > system. Would it be accepted if I send it against linux-next as in [PATCH > linux-next repost v2]? No. Please use net-next I provided above. Your subject prefix will be [PATCH net-next v3] since you'll have changes (specifying the correct tree). You can ask git-format-patch to generate it automatically via `git format-patch --subject-prefix='PATCH net-next' -v3 ...` > > One more note: I was participating in reviewing/discussing your first patch version, so please add all the participants to --cc when you send next versions. For this particular patch it means Jakub, Simon and me must be specified explicitly in --cc when you send v3. [0] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/ Thanks, Olek
