From: Bob Pearson <rpearsonhpe@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: I resent 05/13 because it was missing the for-next
Date: Sat, 29 Oct 2022 12:02:13 -0500 [thread overview]
Message-ID: <cc2c5c4c-0519-71bc-ff27-2752a0941c5c@gmail.com> (raw)
In-Reply-To: <Y11Py4dE9my3i3Ys@nvidia.com>
On 10/29/22 11:07, Jason Gunthorpe wrote:
> On Fri, Oct 28, 2022 at 10:14:55PM -0500, Bob Pearson wrote:
>> I had put them in by hand and missed one.
>
> Every time you do that it messes up patchworks
>
> You need to find a flow that doesn't have these manual fixups in it
>
> Jason
Apologies. I'll work on it.
prev parent reply other threads:[~2022-10-29 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 3:14 I resent 05/13 because it was missing the for-next Bob Pearson
2022-10-29 16:07 ` Jason Gunthorpe
2022-10-29 17:02 ` Bob Pearson [this message]
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=cc2c5c4c-0519-71bc-ff27-2752a0941c5c@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox