Message ID | ZL9tmaSHxKh2JCau@basil |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:9010:0:b0:3e4:2afc:c1 with SMTP id l16csp2280137vqg; Mon, 24 Jul 2023 23:52:09 -0700 (PDT) X-Google-Smtp-Source: APBJJlGF9tvcK7A3hzgWyWrbWpYrC3mqcZOHhZgkj434VuM/lcvnqvqJKOEmRRXehT1Gl22HabXr X-Received: by 2002:a17:907:7708:b0:993:d589:8b75 with SMTP id kw8-20020a170907770800b00993d5898b75mr1622880ejc.2.1690267928754; Mon, 24 Jul 2023 23:52:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690267928; cv=none; d=google.com; s=arc-20160816; b=xSOO/xm7zTIW6TLK9vxfh8QO+nYD/UKNCQDfMdJNb9AZ0uucqSEDWoceyA5Y7elYyQ MSCdh5YEMj4lKQhfMrCb33GPQPEOc1LgZA2Qq+0Q0+w0gMJrwInd9RAYHNFVFKmGGQR2 hedbGc12DFiZ+fSeK8TMdL39WbptbWVPSSXlIRLQryFAOHm4AlIFvhb2RGRqtzzru6sq 9FKZs9kIkIl8E/s5vyEg39jRVAM7rKz6iwVXEQ+PW4YzivT2063DT0qs/XUDuqicdGcj H5xlqPFUv0wd7jaRIfh5p1TyIH+k04Vc0i9ntTklAgqgiYVfSXeV5lNKVdc1RMov/Fa3 WEzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-disposition:mime-version:message-id :subject:cc:to:from:date:dkim-signature:dkim-signature; bh=f6WBlxfFXNjygQqUTuKkNk/ehVxipOLNzQ+LZdlCxhk=; fh=3jvUQscqe8rwMJMYm8BR5N83dgzqgjDCTpIcxqpBKxM=; b=whpDq4oeYEykjIobHAx2iU1kDMtvxQ5h/PjsFK47iohp29auJAoC0x7Kh3jHzM9eHu J0BHujqfGJYR7K23J8oW1YXZjLe86dpjCbFDlIfShkOJNs5pLZ0FZRnG1Znh3YBqredJ PISQKhZyHrA7U47pfPMOW5McZe372SvrMbhorNFaYQV7cnrkbKGtCP2qI7AiqqXnvXG2 kzTvV4zPLL9PxifjOhcUa3UDD3L0fwrs0eJ7ffNY8Zn9zl7UGXiuBHKObGdvb5gAQScu sPusCjzh8oVjmRLsFgUwwVT2SZk2GN+1JrK4SOjQTckXKU9wVvtGiSrsCl+/KMLxcqfj /MHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@pobox.com header.s=sasl header.b=LfhAS+dD; dkim=temperror (no key for signature) header.i=@darkphysics.net header.s=2019-09.pbsmtp header.b=CReEI5WF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q4-20020a1709060e4400b0098ed8a311besi7785696eji.114.2023.07.24.23.51.45; Mon, 24 Jul 2023 23:52:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@pobox.com header.s=sasl header.b=LfhAS+dD; dkim=temperror (no key for signature) header.i=@darkphysics.net header.s=2019-09.pbsmtp header.b=CReEI5WF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232178AbjGYGf6 (ORCPT <rfc822;kloczko.tomasz@gmail.com> + 99 others); Tue, 25 Jul 2023 02:35:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49436 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229678AbjGYGf4 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 25 Jul 2023 02:35:56 -0400 Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3185810FA for <linux-kernel@vger.kernel.org>; Mon, 24 Jul 2023 23:35:54 -0700 (PDT) Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 75FDB1AB033; Tue, 25 Jul 2023 02:35:53 -0400 (EDT) (envelope-from tdavies@darkphysics.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=date:from :to:cc:subject:message-id:mime-version:content-type; s=sasl; bh= M4bcjTSuguIzt8VRc6ssYWZBjrp4kdLVW3B9gSrZzTc=; b=LfhAS+dDcHws6/a7 IxwNSJA/w8wF3YzLo5TBa+1xmLu6MxWLpIbA18WbYXQgCsA+Ao3Mb0z/jblewRMX MK7fcGGVQLWbzNgwYhDASNEDs+pVcOsiC8nV7QbCdN3CM93JFDoTNtnk+qUz/x+I 09+SIrVLQtpl4n+UXI+NWv1QhCs= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 6D3461AB031; Tue, 25 Jul 2023 02:35:53 -0400 (EDT) (envelope-from tdavies@darkphysics.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=darkphysics.net; h=date:from:to:cc:subject:message-id:mime-version:content-type; s=2019-09.pbsmtp; bh=M4bcjTSuguIzt8VRc6ssYWZBjrp4kdLVW3B9gSrZzTc=; b=CReEI5WFSELWZG7nqXL6N8l0FlS2/mVzeGYJboXTlLsQ/rn7e1j9gmOTOvnDHpn5gJ9l/Egvz/zWDEB/rydz/dzN9MMKLpGxw4VT7JKShGqAub41GHzk8VjeQOCBrwQ4ckJDIhyuk3NZGZZCh3BNMf5QD4BCUPudXD0MdHDBfKs= Received: from basil (unknown [76.146.178.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id DE6BE1AB030; Tue, 25 Jul 2023 02:35:51 -0400 (EDT) (envelope-from tdavies@darkphysics.net) Date: Mon, 24 Jul 2023 23:37:13 -0700 From: Tree Davies <tdavies@darkphysics.net> To: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com, anjan@momi.ca, error27@gmail.com Cc: tdavies@darkphysics.net, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org Subject: [PATCH 0/5] Staging: rtl8192e: Function name cleanup series 1 Message-ID: <ZL9tmaSHxKh2JCau@basil> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Pobox-Relay-ID: 804A52EA-2AB5-11EE-9D48-307A8E0A682E-45285927!pb-smtp2.pobox.com X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,NO_DNS_FOR_FROM,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1772374383537129180 X-GMAIL-MSGID: 1772374383537129180 |
Series |
Staging: rtl8192e: Function name cleanup series 1
|
|
Message
Tree Davies
July 25, 2023, 6:37 a.m. UTC
Rename functions to fix checkpatch warning: Avoid CamelCase Tree Davies (5): Staging: rtl8192e: Rename function ActivateBAEntry Staging: rtl8192e: Rename function DeActivateBAEntry Staging: rtl8192e: Rename function TxTsDeleteBA Staging: rtl8192e: Rename function RxTsDeleteBA Staging: rtl8192e: Rename function ResetBaEntry drivers/staging/rtl8192e/rtl819x_BAProc.c | 44 +++++++++++------------ drivers/staging/rtl8192e/rtl819x_TSProc.c | 6 ++-- drivers/staging/rtl8192e/rtllib.h | 2 +- 3 files changed, 26 insertions(+), 26 deletions(-)
Comments
On Mon, Jul 24, 2023 at 11:37:13PM -0700, Tree Davies wrote: > Rename functions to fix checkpatch warning: Avoid CamelCase > > Tree Davies (5): > Staging: rtl8192e: Rename function ActivateBAEntry > Staging: rtl8192e: Rename function DeActivateBAEntry > Staging: rtl8192e: Rename function TxTsDeleteBA > Staging: rtl8192e: Rename function RxTsDeleteBA > Staging: rtl8192e: Rename function ResetBaEntry > > drivers/staging/rtl8192e/rtl819x_BAProc.c | 44 +++++++++++------------ > drivers/staging/rtl8192e/rtl819x_TSProc.c | 6 ++-- > drivers/staging/rtl8192e/rtllib.h | 2 +- > 3 files changed, 26 insertions(+), 26 deletions(-) Odd, how did you send these patches? They are not properly "threaded" or "connected" such that if you look them up on lore.kernel.org, or in your email client, they show that they should be connected. Here's what they look like in my inbox right now: 1 T Jul 24 Tree Davies (0.6K) [PATCH 0/5] Staging: rtl8192e: Function name cleanup series 1 2 N T Jul 24 Tree Davies (1.9K) [PATCH 3/5] Staging: rtl8192e: Rename function TxTsDeleteBA 3 F Jul 25 To linux-kernel ( 29) [PATCH v2] Documentation: embargoed-hardware-issues.rst: add AMD to the list 4 N T Jul 24 Tree Davies (2.5K) [PATCH 5/5] Staging: rtl8192e: Rename function ResetBaEntry 5 N T Jul 24 Tree Davies (1.8K) [PATCH 4/5] Staging: rtl8192e: Rename function RxTsDeleteBA 6 N T Jul 24 Tree Davies (3.1K) [PATCH 2/5] Staging: rtl8192e: Rename function DeActivateBAEntry 7 N T Jul 24 Tree Davies (1.7K) [PATCH 1/5] Staging: rtl8192e: Rename function ActivateBAEntry While if I look at a different recent series sent for staging patches, send correctly, they look like: 372 T Jul 22 Franziska Naepe (0.9K) [PATCH 0/9] staging: rtl8723bs: ioctl_linux: Fix checkpatch issues 373 C Jul 22 Franziska Naepe (0.8K) ├─>[PATCH 9/9] staging: rtl8723bs: ioctl_linux: Fix comparison to false 374 C Jul 22 Franziska Naepe (7.2K) ├─>[PATCH 8/9] staging: rtl8723bs: ioctl_linux: Add preferred spaces 375 C Jul 22 Franziska Naepe (2.2K) ├─>[PATCH 7/9] staging: rtl8723bs: ioctl_linux: Fix alignment on open parenthesis 376 C Jul 22 Franziska Naepe ( 10K) ├─>[PATCH 6/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary parentheses 377 C Jul 22 Franziska Naepe (5.9K) ├─>[PATCH 5/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary blank lines 378 C Jul 22 Franziska Naepe (4.1K) ├─>[PATCH 4/9] staging: rtl8723bs: ioctl_linux: Remove multiple blank lines 379 C Jul 22 Franziska Naepe (1.0K) ├─>[PATCH 3/9] staging: rtl8723bs: ioctl_linux: Fix block comment alignment 380 C Jul 22 Franziska Naepe (0.9K) ├─>[PATCH 2/9] staging: rtl8723bs: ioctl_linux: Fix code indent 381 C Jul 22 Franziska Naepe (0.9K) └─>[PATCH 1/9] staging: rtl8723bs: ioctl_linux: Fix else on next line See the difference with the -> and such? No other messages in the middle of the thread, and they are all connected together so that our tools can handle them as a series, not as individual patches. If you use 'git send-email' to send the whole back of patches at once, they will be properly connected together, so I do recommend using that if you are starting out. Please fix up and try again, thanks. greg k-h
On Tue, Jul 25, 2023 at 08:48:28AM +0200, Greg KH wrote: > On Mon, Jul 24, 2023 at 11:37:13PM -0700, Tree Davies wrote: > > Rename functions to fix checkpatch warning: Avoid CamelCase > > > > Tree Davies (5): > > Staging: rtl8192e: Rename function ActivateBAEntry > > Staging: rtl8192e: Rename function DeActivateBAEntry > > Staging: rtl8192e: Rename function TxTsDeleteBA > > Staging: rtl8192e: Rename function RxTsDeleteBA > > Staging: rtl8192e: Rename function ResetBaEntry > > > > drivers/staging/rtl8192e/rtl819x_BAProc.c | 44 +++++++++++------------ > > drivers/staging/rtl8192e/rtl819x_TSProc.c | 6 ++-- > > drivers/staging/rtl8192e/rtllib.h | 2 +- > > 3 files changed, 26 insertions(+), 26 deletions(-) > > Odd, how did you send these patches? They are not properly "threaded" > or "connected" such that if you look them up on lore.kernel.org, or in > your email client, they show that they should be connected. > > Here's what they look like in my inbox right now: > > > 1 T Jul 24 Tree Davies (0.6K) [PATCH 0/5] Staging: rtl8192e: Function name cleanup series 1 > 2 N T Jul 24 Tree Davies (1.9K) [PATCH 3/5] Staging: rtl8192e: Rename function TxTsDeleteBA > 3 F Jul 25 To linux-kernel ( 29) [PATCH v2] Documentation: embargoed-hardware-issues.rst: add AMD to the list > 4 N T Jul 24 Tree Davies (2.5K) [PATCH 5/5] Staging: rtl8192e: Rename function ResetBaEntry > 5 N T Jul 24 Tree Davies (1.8K) [PATCH 4/5] Staging: rtl8192e: Rename function RxTsDeleteBA > 6 N T Jul 24 Tree Davies (3.1K) [PATCH 2/5] Staging: rtl8192e: Rename function DeActivateBAEntry > 7 N T Jul 24 Tree Davies (1.7K) [PATCH 1/5] Staging: rtl8192e: Rename function ActivateBAEntry > > While if I look at a different recent series sent for staging patches, send > correctly, they look like: > > 372 T Jul 22 Franziska Naepe (0.9K) [PATCH 0/9] staging: rtl8723bs: ioctl_linux: Fix checkpatch issues > 373 C Jul 22 Franziska Naepe (0.8K) ├─>[PATCH 9/9] staging: rtl8723bs: ioctl_linux: Fix comparison to false > 374 C Jul 22 Franziska Naepe (7.2K) ├─>[PATCH 8/9] staging: rtl8723bs: ioctl_linux: Add preferred spaces > 375 C Jul 22 Franziska Naepe (2.2K) ├─>[PATCH 7/9] staging: rtl8723bs: ioctl_linux: Fix alignment on open parenthesis > 376 C Jul 22 Franziska Naepe ( 10K) ├─>[PATCH 6/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary parentheses > 377 C Jul 22 Franziska Naepe (5.9K) ├─>[PATCH 5/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary blank lines > 378 C Jul 22 Franziska Naepe (4.1K) ├─>[PATCH 4/9] staging: rtl8723bs: ioctl_linux: Remove multiple blank lines > 379 C Jul 22 Franziska Naepe (1.0K) ├─>[PATCH 3/9] staging: rtl8723bs: ioctl_linux: Fix block comment alignment > 380 C Jul 22 Franziska Naepe (0.9K) ├─>[PATCH 2/9] staging: rtl8723bs: ioctl_linux: Fix code indent > 381 C Jul 22 Franziska Naepe (0.9K) └─>[PATCH 1/9] staging: rtl8723bs: ioctl_linux: Fix else on next line > > > See the difference with the -> and such? No other messages in the middle of > the thread, and they are all connected together so that our tools can handle > them as a series, not as individual patches. > > If you use 'git send-email' to send the whole back of patches at once, they > will be properly connected together, so I do recommend using that if you are > starting out. > > Please fix up and try again, thanks. > > greg k-h Greg, I got git send-email working. Do I send this series as a v2, even though the patches are the same, and how I send them is 'the change'? The last commit I see in linux-next for rtl8192e is 4a22870cede374d80c5d2f9c5b79253a5a667832. Can I send patches from that state? Tree
On Wed, Jul 26, 2023 at 09:37:47PM -0700, Tree Davies wrote: > On Tue, Jul 25, 2023 at 08:48:28AM +0200, Greg KH wrote: > > On Mon, Jul 24, 2023 at 11:37:13PM -0700, Tree Davies wrote: > > > Rename functions to fix checkpatch warning: Avoid CamelCase > > > > > > Tree Davies (5): > > > Staging: rtl8192e: Rename function ActivateBAEntry > > > Staging: rtl8192e: Rename function DeActivateBAEntry > > > Staging: rtl8192e: Rename function TxTsDeleteBA > > > Staging: rtl8192e: Rename function RxTsDeleteBA > > > Staging: rtl8192e: Rename function ResetBaEntry > > > > > > drivers/staging/rtl8192e/rtl819x_BAProc.c | 44 +++++++++++------------ > > > drivers/staging/rtl8192e/rtl819x_TSProc.c | 6 ++-- > > > drivers/staging/rtl8192e/rtllib.h | 2 +- > > > 3 files changed, 26 insertions(+), 26 deletions(-) > > > > Odd, how did you send these patches? They are not properly "threaded" > > or "connected" such that if you look them up on lore.kernel.org, or in > > your email client, they show that they should be connected. > > > > Here's what they look like in my inbox right now: > > > > > > 1 T Jul 24 Tree Davies (0.6K) [PATCH 0/5] Staging: rtl8192e: Function name cleanup series 1 > > 2 N T Jul 24 Tree Davies (1.9K) [PATCH 3/5] Staging: rtl8192e: Rename function TxTsDeleteBA > > 3 F Jul 25 To linux-kernel ( 29) [PATCH v2] Documentation: embargoed-hardware-issues.rst: add AMD to the list > > 4 N T Jul 24 Tree Davies (2.5K) [PATCH 5/5] Staging: rtl8192e: Rename function ResetBaEntry > > 5 N T Jul 24 Tree Davies (1.8K) [PATCH 4/5] Staging: rtl8192e: Rename function RxTsDeleteBA > > 6 N T Jul 24 Tree Davies (3.1K) [PATCH 2/5] Staging: rtl8192e: Rename function DeActivateBAEntry > > 7 N T Jul 24 Tree Davies (1.7K) [PATCH 1/5] Staging: rtl8192e: Rename function ActivateBAEntry > > > > While if I look at a different recent series sent for staging patches, send > > correctly, they look like: > > > > 372 T Jul 22 Franziska Naepe (0.9K) [PATCH 0/9] staging: rtl8723bs: ioctl_linux: Fix checkpatch issues > > 373 C Jul 22 Franziska Naepe (0.8K) ├─>[PATCH 9/9] staging: rtl8723bs: ioctl_linux: Fix comparison to false > > 374 C Jul 22 Franziska Naepe (7.2K) ├─>[PATCH 8/9] staging: rtl8723bs: ioctl_linux: Add preferred spaces > > 375 C Jul 22 Franziska Naepe (2.2K) ├─>[PATCH 7/9] staging: rtl8723bs: ioctl_linux: Fix alignment on open parenthesis > > 376 C Jul 22 Franziska Naepe ( 10K) ├─>[PATCH 6/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary parentheses > > 377 C Jul 22 Franziska Naepe (5.9K) ├─>[PATCH 5/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary blank lines > > 378 C Jul 22 Franziska Naepe (4.1K) ├─>[PATCH 4/9] staging: rtl8723bs: ioctl_linux: Remove multiple blank lines > > 379 C Jul 22 Franziska Naepe (1.0K) ├─>[PATCH 3/9] staging: rtl8723bs: ioctl_linux: Fix block comment alignment > > 380 C Jul 22 Franziska Naepe (0.9K) ├─>[PATCH 2/9] staging: rtl8723bs: ioctl_linux: Fix code indent > > 381 C Jul 22 Franziska Naepe (0.9K) └─>[PATCH 1/9] staging: rtl8723bs: ioctl_linux: Fix else on next line > > > > > > See the difference with the -> and such? No other messages in the middle of > > the thread, and they are all connected together so that our tools can handle > > them as a series, not as individual patches. > > > > If you use 'git send-email' to send the whole back of patches at once, they > > will be properly connected together, so I do recommend using that if you are > > starting out. > > > > Please fix up and try again, thanks. > > > > greg k-h > > Greg, > I got git send-email working. Do I send this series as a v2, even though the > patches are the same, and how I send them is 'the change'? Yes. > The last commit I see in linux-next for rtl8192e is 4a22870cede374d80c5d2f9c5b79253a5a667832. > Can I send patches from that state? Sure, or just work off of my staging.git tree with the staging-next branch. thanks, greg k-h