From: santosh.shilimkar@oracle.com
To: Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH] linux-next: DOC: RDS: Fix a typo in rds.txt
Date: Wed, 12 Jun 2019 09:27:56 -0700 [thread overview]
Message-ID: <b3fae27d-633d-e164-9f59-44eabf74ed7e@oracle.com> (raw)
In-Reply-To: <20190612122934.3515-1-standby24x7@gmail.com>
On 6/12/19 5:29 AM, Masanari Iida wrote:
> This patch fixes a spelling typo in rds.txt
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> Documentation/networking/rds.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/rds.txt b/Documentation/networking/rds.txt
> index 0235ae69af2a..f2a0147c933d 100644
> --- a/Documentation/networking/rds.txt
> +++ b/Documentation/networking/rds.txt
> @@ -389,7 +389,7 @@ Multipath RDS (mprds)
> a common (to all paths) part, and a per-path struct rds_conn_path. All
> I/O workqs and reconnect threads are driven from the rds_conn_path.
> Transports such as TCP that are multipath capable may then set up a
> - TPC socket per rds_conn_path, and this is managed by the transport via
> + TCP socket per rds_conn_path, and this is managed by the transport via
> the transport privatee cp_transport_data pointer.
>
> Transports announce themselves as multipath capable by setting the
>
Thanks !!
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
next prev parent reply other threads:[~2019-06-12 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 12:29 [PATCH] linux-next: DOC: RDS: Fix a typo in rds.txt Masanari Iida
2019-06-12 16:27 ` santosh.shilimkar [this message]
2019-06-12 16:56 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2020-03-09 10:43 Masanari Iida
2020-03-09 17:06 ` David Miller
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=b3fae27d-633d-e164-9f59-44eabf74ed7e@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=standby24x7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox