LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com> To: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org, borntraeger@de.ibm.com, bjsdjshi@linux.ibm.com, pasic@linux.ibm.com, pmorel@linux.ibm.com Subject: Re: [PATCH v2 2/5] vfio: ccw: shorten kernel doc description for pfn_array_pin() Date: Mon, 23 Apr 2018 13:44:19 +0200 [thread overview] Message-ID: <20180423134419.630e7606.cohuck@redhat.com> (raw) In-Reply-To: <20180423110113.59385-3-bjsdjshi@linux.vnet.ibm.com> On Mon, 23 Apr 2018 13:01:10 +0200 Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> wrote: > The kernel doc description for usage of the struct pfn_array in > pfn_array_pin() is unnecessary long. Let's shorten it by describing > the contents of the struct pfn_array fields at the struct's definition > instead. > > Suggested-by: Cornelia Huck <cohuck@redhat.com> > Signed-off-by: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> > --- > drivers/s390/cio/vfio_ccw_cp.c | 14 ++++++-------- > 1 file changed, 6 insertions(+), 8 deletions(-) > > diff --git a/drivers/s390/cio/vfio_ccw_cp.c b/drivers/s390/cio/vfio_ccw_cp.c > index 62d66e195304..e8fe7450702e 100644 > --- a/drivers/s390/cio/vfio_ccw_cp.c > +++ b/drivers/s390/cio/vfio_ccw_cp.c > @@ -23,9 +23,13 @@ > #define CCWCHAIN_LEN_MAX 256 > > struct pfn_array { > + /* Starting guest physical I/O address. */ > unsigned long pa_iova; > + /* Array that stores PFNs of the pages need to pin. */ s/need to pin/needing to be pinned/ ? Or "we need to pin"? Or even simply "to pin"? (Pre-exiting, but we can as well fix it up. Can also do while applying.) > unsigned long *pa_iova_pfn; > + /* Array that receives PFNs of the pages pinned. */ > unsigned long *pa_pfn; > + /* Number of pages to pin/pinned from @pa_iova. */ > int pa_nr; > }; > > @@ -53,14 +57,8 @@ struct ccwchain { > * Attempt to pin user pages in memory. > * > * Usage of pfn_array: > - * @pa->pa_iova starting guest physical I/O address. Assigned by caller. > - * @pa->pa_iova_pfn array that stores PFNs of the pages need to pin. Allocated > - * by caller. > - * @pa->pa_pfn array that receives PFNs of the pages pinned. Allocated by > - * caller. > - * @pa->pa_nr number of pages from @pa->pa_iova to pin. Assigned by > - * caller. > - * number of pages pinned. Assigned by callee. > + * Any field in this structure should be initialized by caller. > + * We expect @pa->pa_nr > 0, and its value will be assigned by callee. > * > * Returns: > * Number of pages pinned on success. Otherwise, looks good.
next prev parent reply other threads:[~2018-04-23 11:44 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-23 11:01 [PATCH v2 0/5] vfio: ccw: error handling fixes and improvements Dong Jia Shi 2018-04-23 11:01 ` [PATCH v2 1/5] vfio: ccw: fix cleanup if cp_prefetch fails Dong Jia Shi 2018-04-23 11:38 ` Halil Pasic 2018-04-23 11:40 ` Cornelia Huck 2018-04-23 12:00 ` Halil Pasic 2018-04-24 9:31 ` Cornelia Huck [not found] ` <20180425024341.GY12194@bjsdjshi@linux.vnet.ibm.com> 2018-04-25 11:19 ` Halil Pasic 2018-04-23 11:01 ` [PATCH v2 2/5] vfio: ccw: shorten kernel doc description for pfn_array_pin() Dong Jia Shi 2018-04-23 11:44 ` Cornelia Huck [this message] 2018-04-23 11:01 ` [PATCH v2 3/5] vfio: ccw: refactor and improve pfn_array_alloc_pin() Dong Jia Shi 2018-04-23 11:01 ` [PATCH v2 4/5] vfio: ccw: set ccw->cda to NULL defensively Dong Jia Shi 2018-04-23 11:01 ` [PATCH v2 5/5] vfio: ccw: add traceponits for interesting error paths Dong Jia Shi 2018-04-27 10:13 ` Cornelia Huck [not found] ` <20180428055023.GS5428@bjsdjshi@linux.vnet.ibm.com> 2018-04-30 11:51 ` Cornelia Huck 2018-04-30 14:14 ` Halil Pasic 2018-04-30 15:03 ` Cornelia Huck 2018-04-30 16:51 ` Halil Pasic [not found] ` <20180502022330.GT5428@bjsdjshi@linux.vnet.ibm.com> [not found] ` <20180516065355.GB6363@bjsdjshi@linux.ibm.com> 2018-05-22 12:55 ` Cornelia Huck 2018-04-23 11:32 ` [PATCH v2 0/5] vfio: ccw: error handling fixes and improvements Cornelia Huck
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=20180423134419.630e7606.cohuck@redhat.com \ --to=cohuck@redhat.com \ --cc=bjsdjshi@linux.ibm.com \ --cc=bjsdjshi@linux.vnet.ibm.com \ --cc=borntraeger@de.ibm.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-s390@vger.kernel.org \ --cc=pasic@linux.ibm.com \ --cc=pmorel@linux.ibm.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: linkBe 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 NNTP newsgroup(s).