mbox series

[00/16] Staging: rtl8192e: Rename struct rx_ts_record references

Message ID 20230812201702.83421-1-tdavies@darkphysics.net
Headers
Series Staging: rtl8192e: Rename struct rx_ts_record references |

Message

Tree Davies Aug. 12, 2023, 8:16 p.m. UTC 
  This patch series fixes checkpatch warning Avoid CamelCase, for all references
of struct rx_ts_record, and renames them to rx_ts for consistency and 
readability. Each patch renames references for a single function.

Thank you in advance to the reviewers
~ Tree 

Tree Davies (16):
  Staging: rtl8192e: Rename variable pBa in function rx_ts_delete_ba()
  Staging: rtl8192e: Rename variable pTS in function
    rtllib_rx_ADDBAReq()
  Staging: rtl8192e: Rename variable pRxTs in function rtllib_rx_DELBA()
  Staging: rtl8192e: Rename variable pRxTs in function
    rtllib_ts_init_del_ba()
  Staging: rtl8192e: Rename variable pRxTs in function
    rtllib_rx_ba_inact_timeout()
  Staging: rtl8192e: Rename variable pRxTs in function
    RxPktPendingTimeout()
  Staging: rtl8192e: Rename variable pTS in function ResetRxTsEntry()
  Staging: rtl8192e: Rename variable pRxTS in function TSInitialize()
  Staging: rtl8192e: Rename variable tmp in function GetTs()
  Staging: rtl8192e: Rename variable pRxTS in function RemoveTsEntry()
  Staging: rtl8192e: Rename variable pTS in function prototype
    rtllib_FlushRxTsPendingPkts()
  Staging: rtl8192e: Rename variable pTS in function AddReorderEntry()
  Staging: rtl8192e: Rename variable pTS in function
    rtllib_indicate_packets()
  Staging: rtl8192e: Rename variable pTS in function
    rtllib_FlushRxTsPendingPkts()
  Staging: rtl8192e: Rename variable pRxTS in function
    rtllib_rx_check_duplicate()
  Staging: rtl8192e: Rename variable pTS in function
    rtllib_rx_InfraAdhoc()

 drivers/staging/rtl8192e/rtl819x_BAProc.c | 36 ++++-----
 drivers/staging/rtl8192e/rtl819x_TSProc.c | 72 ++++++++---------
 drivers/staging/rtl8192e/rtllib.h         |  2 +-
 drivers/staging/rtl8192e/rtllib_rx.c      | 94 +++++++++++------------
 4 files changed, 102 insertions(+), 102 deletions(-)

Comments

Nam Cao Aug. 12, 2023, 9:13 p.m. UTC | #1 
On Sat, Aug 12, 2023 at 01:16:46PM -0700, Tree Davies wrote:
> This patch series fixes checkpatch warning Avoid CamelCase, for all references
> of struct rx_ts_record, and renames them to rx_ts for consistency and 
> readability. Each patch renames references for a single function.
> 
> Thank you in advance to the reviewers
> ~ Tree 
> 
> Tree Davies (16):

Here it says there are 16 patches, but you have only sent 6 patches. Are some
of them missing?

Best regards,
Nam
Tree Davies Aug. 12, 2023, 11:11 p.m. UTC | #2 
On Sat, Aug 12, 2023 at 11:13:56PM +0200, Nam Cao wrote:
> On Sat, Aug 12, 2023 at 01:16:46PM -0700, Tree Davies wrote:
> > This patch series fixes checkpatch warning Avoid CamelCase, for all references
> > of struct rx_ts_record, and renames them to rx_ts for consistency and 
> > readability. Each patch renames references for a single function.
> > 
> > Thank you in advance to the reviewers
> > ~ Tree 
> > 
> > Tree Davies (16):
> 
> Here it says there are 16 patches, but you have only sent 6 patches. Are some
> of them missing?
> 
> Best regards,
> Nam
> 
Thanks Nam,

Yes they are missing. git send-email errored during submition. 
I will resend. 
Question: In this case do I need to send it as a v2?

Tree
Tree Davies Aug. 13, 2023, 12:15 a.m. UTC | #3 
On Sat, Aug 12, 2023 at 04:11:53PM -0700, Tree Davies wrote:
> On Sat, Aug 12, 2023 at 11:13:56PM +0200, Nam Cao wrote:
> > On Sat, Aug 12, 2023 at 01:16:46PM -0700, Tree Davies wrote:
> > > This patch series fixes checkpatch warning Avoid CamelCase, for all references
> > > of struct rx_ts_record, and renames them to rx_ts for consistency and 
> > > readability. Each patch renames references for a single function.
> > > 
> > > Thank you in advance to the reviewers
> > > ~ Tree 
> > > 
> > > Tree Davies (16):
> > 
> > Here it says there are 16 patches, but you have only sent 6 patches. Are some
> > of them missing?
> > 
> > Best regards,
> > Nam
> > 
> Thanks Nam,
> 
> Yes they are missing. git send-email errored during submition. 
> I will resend. 
> Question: In this case do I need to send it as a v2?
> 
> Tree
> 

OK, I know what happened. I was rate limited by my email provider.
I've requested a limit increase.

I suppose I could break up the patch-set into multiple series and label
them as series A, B, and C?

Tree
Greg KH Aug. 13, 2023, 6:30 a.m. UTC | #4 
On Sat, Aug 12, 2023 at 05:15:15PM -0700, Tree Davies wrote:
> On Sat, Aug 12, 2023 at 04:11:53PM -0700, Tree Davies wrote:
> > On Sat, Aug 12, 2023 at 11:13:56PM +0200, Nam Cao wrote:
> > > On Sat, Aug 12, 2023 at 01:16:46PM -0700, Tree Davies wrote:
> > > > This patch series fixes checkpatch warning Avoid CamelCase, for all references
> > > > of struct rx_ts_record, and renames them to rx_ts for consistency and 
> > > > readability. Each patch renames references for a single function.
> > > > 
> > > > Thank you in advance to the reviewers
> > > > ~ Tree 
> > > > 
> > > > Tree Davies (16):
> > > 
> > > Here it says there are 16 patches, but you have only sent 6 patches. Are some
> > > of them missing?
> > > 
> > > Best regards,
> > > Nam
> > > 
> > Thanks Nam,
> > 
> > Yes they are missing. git send-email errored during submition. 
> > I will resend. 
> > Question: In this case do I need to send it as a v2?
> > 
> > Tree
> > 
> 
> OK, I know what happened. I was rate limited by my email provider.
> I've requested a limit increase.

Your email provider does not allow you to send more than 7 emails at
once?  You might want to switch companies if that's the case.

> I suppose I could break up the patch-set into multiple series and label
> them as series A, B, and C?

No, series are not labeled that way, sorry.

greg k-h