From: David Miller <davem@davemloft.net>
To: vakul.garg@nxp.com
Cc: davejwatson@fb.com, netdev@vger.kernel.org, borisp@mellanox.com,
aviadye@mellanox.com, doronrk@fb.com
Subject: Re: [net-next v5 3/3] net/tls: Remove redundant array allocation.
Date: Mon, 23 Jul 2018 21:49:12 -0700 (PDT) [thread overview]
Message-ID: <20180723.214912.1848385256984977067.davem@davemloft.net> (raw)
In-Reply-To: <DB7PR04MB4252DEFEDC63C40EF287F22D8B550@DB7PR04MB4252.eurprd04.prod.outlook.com>
From: Vakul Garg <vakul.garg@nxp.com>
Date: Tue, 24 Jul 2018 04:43:55 +0000
> Can you still apply the rest of two patches in the series or do I
> need to send them again separately?
When a change of any kind needs to be made to a patch series, you must
always resubmit the entire series.
Thank you.
next prev parent reply other threads:[~2018-07-24 5:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 16:26 [net-next v5 0/3] net/tls: Minor code cleanup patches Vakul Garg
2018-07-19 16:26 ` [net-next v5 1/3] net/tls: Use socket data_ready callback on record availability Vakul Garg
2018-07-19 16:26 ` [net-next v5 2/3] net/tls: Remove redundant variable assignments and wakeup Vakul Garg
2018-07-19 16:26 ` [net-next v5 3/3] net/tls: Remove redundant array allocation Vakul Garg
2018-07-22 2:25 ` David Miller
2018-07-23 16:35 ` Dave Watson
2018-07-24 4:41 ` David Miller
2018-07-24 4:43 ` Vakul Garg
2018-07-24 4:49 ` David Miller [this message]
2018-07-24 8:22 ` Vakul Garg
2018-07-25 21:01 ` Dave Watson
2018-07-27 9:34 ` Vakul Garg
2018-07-27 15:38 ` Dave Watson
2018-08-01 13:49 ` Vakul Garg
2018-08-01 20:52 ` Dave Watson
-- strict thread matches above, loose matches on Subject: below --
2018-07-19 16:23 [net-next v4 0/3] net/tls: Minor code cleanup patches Vakul Garg
2018-07-19 16:23 ` [net-next v5 3/3] net/tls: Remove redundant array allocation Vakul Garg
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=20180723.214912.1848385256984977067.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davejwatson@fb.com \
--cc=doronrk@fb.com \
--cc=netdev@vger.kernel.org \
--cc=vakul.garg@nxp.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.