From: Jon Mason <jdmason@kudzu.us>
To: Wesley Sheng <wesley.sheng@microchip.com>
Cc: dave.jiang@intel.com, allenbh@gmail.com,
linux-ntb@googlegroups.com, linux-kernel@vger.kernel.org,
wesleyshenggit@sina.com, logang@deltatee.com
Subject: Re: [PATCH] NTB: correct ntb_dev_ops and ntb_dev comment typos
Date: Thu, 13 Jun 2019 09:23:15 -0400 [thread overview]
Message-ID: <20190613132314.GB1572@kudzu.us> (raw)
In-Reply-To: <1556618669-2434-1-git-send-email-wesley.sheng@microchip.com>
On Tue, Apr 30, 2019 at 06:04:29PM +0800, Wesley Sheng wrote:
> The comment for ntb_dev_ops and ntb_dev incorrectly referred to
> ntb_ctx_ops and ntb_device.
>
> Signed-off-by: Wesley Sheng <wesley.sheng@microchip.com>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
Sorry for the delay. The series is now in the ntb branch. We've
missed window for 5.2, but it will be in the 5.3 pull request.
Thanks,
Jon
> ---
> include/linux/ntb.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/ntb.h b/include/linux/ntb.h
> index 56a92e3..604abc8 100644
> --- a/include/linux/ntb.h
> +++ b/include/linux/ntb.h
> @@ -205,7 +205,7 @@ static inline int ntb_ctx_ops_is_valid(const struct ntb_ctx_ops *ops)
> }
>
> /**
> - * struct ntb_ctx_ops - ntb device operations
> + * struct ntb_dev_ops - ntb device operations
> * @port_number: See ntb_port_number().
> * @peer_port_count: See ntb_peer_port_count().
> * @peer_port_number: See ntb_peer_port_number().
> @@ -404,7 +404,7 @@ struct ntb_client {
> #define drv_ntb_client(__drv) container_of((__drv), struct ntb_client, drv)
>
> /**
> - * struct ntb_device - ntb device
> + * struct ntb_dev - ntb device
> * @dev: Linux device object.
> * @pdev: PCI device entry of the ntb.
> * @topo: Detected topology of the ntb.
> --
> 2.7.4
>
prev parent reply other threads:[~2019-06-13 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 10:04 [PATCH] NTB: correct ntb_dev_ops and ntb_dev comment typos Wesley Sheng
2019-06-13 13:23 ` Jon Mason [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=20190613132314.GB1572@kudzu.us \
--to=jdmason@kudzu.us \
--cc=allenbh@gmail.com \
--cc=dave.jiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=logang@deltatee.com \
--cc=wesley.sheng@microchip.com \
--cc=wesleyshenggit@sina.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