From: "Allen Hubbe" <Allen.Hubbe@dell.com>
To: 'Aaron Sierra' <asierra@xes-inc.com>
Cc: 'Jon Mason' <jdmason@kudzu.us>,
'Dave Jiang' <dave.jiang@intel.com>,
'linux-ntb' <linux-ntb@googlegroups.com>,
'Jiri Kosina' <trivial@kernel.org>
Subject: RE: correct ntb_spad_count comment typo
Date: Wed, 7 Dec 2016 13:35:39 -0500 [thread overview]
Message-ID: <000301d250b8$b5cf6c40$216e44c0$@dell.com> (raw)
In-Reply-To: <1763865308.471858.1481132031876.JavaMail.zimbra@xes-inc.com>
From: Aaron Sierra
> This is the exact subject that I sent out:
>
> [PATCH] NTB: correct ntb_spad_count comment typo
>
> Hopefully, this is just a glitch between me and you.
You're right, I replied with the wrong subject.
Thanks for the patch! Already acked.
Allen
prev parent reply other threads:[~2016-12-07 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 1:09 [PATCH] NTB: correct ntb_spad_count comment typo Aaron Sierra
2016-12-07 15:04 ` Allen Hubbe
2016-12-07 15:09 ` Allen Hubbe
2016-12-07 17:33 ` Aaron Sierra
2016-12-07 18:35 ` Allen Hubbe [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='000301d250b8$b5cf6c40$216e44c0$@dell.com' \
--to=allen.hubbe@dell.com \
--cc=asierra@xes-inc.com \
--cc=dave.jiang@intel.com \
--cc=jdmason@kudzu.us \
--cc=linux-ntb@googlegroups.com \
--cc=trivial@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