From: Tree Davies <tdavies@darkphysics.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Nam Cao <namcaov@gmail.com>,
philipp.g.hortmann@gmail.com, anjan@momi.ca, error27@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/16] Staging: rtl8192e: Rename struct rx_ts_record references
Date: Mon, 14 Aug 2023 10:27:17 -0700 [thread overview]
Message-ID: <ZNpj9RDhm3Q0sSmO@basil> (raw)
In-Reply-To: <2023081310-unearth-buddhist-4caf@gregkh>
On Sun, Aug 13, 2023 at 08:30:02AM +0200, Greg KH wrote:
> 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.
From what I understand it is 7 email-recipients x 16 patches in the set
violates their 50 email per 5 minute policy.
>
> > 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
next prev parent reply other threads:[~2023-08-14 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 20:16 [PATCH 00/16] Staging: rtl8192e: Rename struct rx_ts_record references Tree Davies
2023-08-12 20:16 ` [PATCH 01/16] Staging: rtl8192e: Rename variable pBa in function rx_ts_delete_ba() Tree Davies
2023-08-12 20:16 ` [PATCH 02/16] Staging: rtl8192e: Rename variable pTS in function rtllib_rx_ADDBAReq() Tree Davies
2023-08-12 20:16 ` [PATCH 03/16] Staging: rtl8192e: Rename variable pRxTs in function rtllib_rx_DELBA() Tree Davies
2023-08-12 20:16 ` [PATCH 04/16] Staging: rtl8192e: Rename variable pRxTs in function rtllib_ts_init_del_ba() Tree Davies
2023-08-12 20:16 ` [PATCH 05/16] Staging: rtl8192e: Rename variable pRxTs in function rtllib_rx_ba_inact_timeout() Tree Davies
2023-08-12 20:16 ` [PATCH 06/16] Staging: rtl8192e: Rename variable pRxTs in function RxPktPendingTimeout() Tree Davies
2023-08-12 21:13 ` [PATCH 00/16] Staging: rtl8192e: Rename struct rx_ts_record references Nam Cao
2023-08-12 23:11 ` Tree Davies
2023-08-13 0:15 ` Tree Davies
2023-08-13 6:30 ` Greg KH
2023-08-14 17:27 ` Tree Davies [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-20 0:47 Tree Davies
2023-08-20 4:40 ` Philipp Hortmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZNpj9RDhm3Q0sSmO@basil \
--to=tdavies@darkphysics.net \
--cc=anjan@momi.ca \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcaov@gmail.com \
--cc=philipp.g.hortmann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.