From: Xu Yilun <yilun.xu@intel.com>
To: Tom Rix <trix@redhat.com>
Cc: Marco Pagani <marpagan@redhat.com>,
Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Tull <atull@kernel.org>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fpga: bridge: fix kernel-doc parameter description
Date: Sat, 4 Mar 2023 23:29:59 +0800 [thread overview]
Message-ID: <ZANj9+SILtNZkqUE@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <4e15feab-5d75-6748-324d-ff58d0f862b8@redhat.com>
On 2023-03-02 at 04:51:43 -0800, Tom Rix wrote:
>
> On 3/1/23 6:03 AM, Marco Pagani wrote:
> > Fix the kernel-doc description for the "struct fpga_image_info *info"
> > parameter of the fpga_bridge_get() function.
> >
> > Fixes: 060ac5c8fa7b ("fpga: bridge: kernel-doc fixes")
> > Signed-off-by: Marco Pagani <marpagan@redhat.com>
> Reviewed-by: Tom Rix <trix@redhat.com>
Acked-by: Xu Yilun <yilun.xu@intel.com>
> > ---
> > drivers/fpga/fpga-bridge.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/fpga/fpga-bridge.c b/drivers/fpga/fpga-bridge.c
> > index 5cd40acab5bf..ff4470067ed5 100644
> > --- a/drivers/fpga/fpga-bridge.c
> > +++ b/drivers/fpga/fpga-bridge.c
> > @@ -115,7 +115,7 @@ static int fpga_bridge_dev_match(struct device *dev, const void *data)
> > /**
> > * fpga_bridge_get - get an exclusive reference to an fpga bridge
> > * @dev: parent device that fpga bridge was registered with
> > - * @info: fpga manager info
> > + * @info: fpga image specific information
> > *
> > * Given a device, get an exclusive reference to an fpga bridge.
> > *
>
prev parent reply other threads:[~2023-03-04 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 14:03 [PATCH] fpga: bridge: fix kernel-doc parameter description Marco Pagani
2023-03-02 12:51 ` Tom Rix
2023-03-04 15:29 ` Xu Yilun [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=ZANj9+SILtNZkqUE@yilunxu-OptiPlex-7050 \
--to=yilun.xu@intel.com \
--cc=atull@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marpagan@redhat.com \
--cc=mdf@kernel.org \
--cc=trix@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).