qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: arei.gonglei@huawei.com
Cc: peter.crosthwaite@xilinx.com, knut.omang@oracle.com,
	weidong.huang@huawei.com, marcel.a@redhat.com, armbru@redhat.com,
	luonengjun@huawei.com, qemu-devel@nongnu.org,
	peter.huangpeng@huawei.com, imammedo@redhat.com,
	pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v4 3/3] pcie: remove confused comments
Date: Tue, 30 Sep 2014 15:46:15 +0300	[thread overview]
Message-ID: <20140930124615.GA2012@redhat.com> (raw)
In-Reply-To: <1412071886-10192-4-git-send-email-arei.gonglei@huawei.com>

On Tue, Sep 30, 2014 at 06:11:26PM +0800, arei.gonglei@huawei.com wrote:
> From: Gonglei <arei.gonglei@huawei.com>
> 
> The below functions is not allocation functions, but
> find helper function. The only allocation function is
> pcie_add_capability(), but its argument names is not the
> same with the comments. So remove this comments which
> make people confused.
> 
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>

The comment applies to all functions below it.
Maybe simply replace
 s/capability allocation/capability list management/?

Also pls make this a separate patch, does not belong in
this series.

> ---
>  hw/pci/pcie.c | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
> index b82211a..f2b9d5d 100644
> --- a/hw/pci/pcie.c
> +++ b/hw/pci/pcie.c
> @@ -528,14 +528,6 @@ bool pcie_cap_is_arifwd_enabled(const PCIDevice *dev)
>          PCI_EXP_DEVCTL2_ARI;
>  }
>  
> -/**************************************************************************
> - * pci express extended capability allocation functions
> - * uint16_t ext_cap_id (16 bit)
> - * uint8_t cap_ver (4 bit)
> - * uint16_t cap_offset (12 bit)
> - * uint16_t ext_cap_size
> - */
> -
>  static uint16_t pcie_find_capability_list(PCIDevice *dev, uint16_t cap_id,
>                                            uint16_t *prev_p)
>  {
> -- 
> 1.7.12.4
> 

  reply	other threads:[~2014-09-30 12:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 10:11 [Qemu-devel] [PATCH v4 0/3] pcie: add check for ari capability of pcie devices arei.gonglei
2014-09-30 10:11 ` [Qemu-devel] [PATCH v4 1/3] qdev: Introduce a function to get qbus's parent arei.gonglei
2014-09-30 10:11 ` [Qemu-devel] [PATCH v4 2/3] pcie: add check for ari capability of pcie devices arei.gonglei
2014-09-30 11:59   ` Michael S. Tsirkin
2014-09-30 13:38     ` Gonglei
2014-09-30 13:58       ` Michael S. Tsirkin
2014-10-01  4:04         ` Gonglei
2014-10-01  5:26       ` Knut Omang
2014-10-01  7:15         ` Gonglei
2014-10-01 14:08         ` Marcel Apfelbaum
2014-10-03 11:22           ` Knut Omang
2014-10-03 14:30             ` Knut Omang
2014-10-08  3:23               ` Gonglei (Arei)
2014-09-30 10:11 ` [Qemu-devel] [PATCH v4 3/3] pcie: remove confused comments arei.gonglei
2014-09-30 12:46   ` Michael S. Tsirkin [this message]
2014-09-30 12:58     ` Gonglei

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=20140930124615.GA2012@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=knut.omang@oracle.com \
    --cc=luonengjun@huawei.com \
    --cc=marcel.a@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weidong.huang@huawei.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 NNTP newsgroup(s).