All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Thomas Monjalon
	<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: [PATCH 03/10] igb_uio: dont wrap pci_num_vf function needlessly
Date: Fri, 18 Jul 2014 09:14:50 -0700	[thread overview]
Message-ID: <20140718161516.157268908@networkplumber.org> (raw)
In-Reply-To: 20140718161447.020882834@networkplumber.org

[-- Attachment #1: igb_uio-better-pci-num-vf.patch --]
[-- Type: text/plain, Size: 1436 bytes --]

It is better style to just use the pci_num_vf directly, rather
than wrapping it with a local (but globally named) function with
the same effect.

Signed-off-by: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>


--- a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c	2014-06-19 14:29:57.587687790 -0700
+++ b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c	2014-06-19 14:59:14.000000000 -0700
@@ -83,9 +83,8 @@ igbuio_get_uio_pci_dev(struct uio_info *
 }
 
 /* sriov sysfs */
-int local_pci_num_vf(struct pci_dev *dev)
-{
 #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,34)
+static int pci_num_vf(struct pci_dev *dev)
 	struct iov {
 		int pos;
 		int nres;
@@ -100,17 +99,15 @@ int local_pci_num_vf(struct pci_dev *dev
 		return 0;
 
 	return iov->nr_virtfn;
-#else
-	return pci_num_vf(dev);
-#endif
 }
+#endif
 
 static ssize_t
 show_max_vfs(struct device *dev, struct device_attribute *attr,
 	     char *buf)
 {
-	return snprintf(buf, 10, "%u\n", local_pci_num_vf(
-				container_of(dev, struct pci_dev, dev)));
+	return snprintf(buf, 10, "%u\n",
+			pci_num_vf(container_of(dev, struct pci_dev, dev)));
 }
 
 static ssize_t
@@ -126,7 +123,7 @@ store_max_vfs(struct device *dev, struct
 
 	if (0 == max_vfs)
 		pci_disable_sriov(pdev);
-	else if (0 == local_pci_num_vf(pdev))
+	else if (0 == pci_num_vf(pdev))
 		err = pci_enable_sriov(pdev, max_vfs);
 	else /* do nothing if change max_vfs number */
 		err = -EINVAL;

  parent reply	other threads:[~2014-07-18 16:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 16:14 [PATCH 00/10] igb_uio related patches Stephen Hemminger
2014-07-18 16:14 ` [PATCH 01/10] igb_uio: use kernel standard log message Stephen Hemminger
2014-07-18 16:14 ` [PATCH 02/10] igb_uio: use standard uio naming Stephen Hemminger
2014-07-18 16:14 ` Stephen Hemminger [this message]
     [not found]   ` <20140718161516.157268908-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
2014-07-23  8:20     ` [PATCH 03/10] igb_uio: dont wrap pci_num_vf function needlessly Thomas Monjalon
2014-07-18 16:14 ` [PATCH 04/10] igb_uio: msix cleanups Stephen Hemminger
2014-07-18 16:14 ` [PATCH 05/10] igb_uio: propogate error numbers in probe code Stephen Hemminger
2014-07-18 16:14 ` [PATCH 06/10] igb_uio: make irq mode param read-only Stephen Hemminger
2014-07-18 16:14 ` [PATCH 07/10] igb_uio: fix IRQ mode handling Stephen Hemminger
2014-07-18 16:14 ` [PATCH 08/10] igb_uio: add missing locking to config access Stephen Hemminger
2014-07-18 16:14 ` [PATCH 09/10] igb_uio: allow msi mode Stephen Hemminger
2014-07-18 16:14 ` [PATCH 10/10] igb_uio: fix check patch warnings Stephen Hemminger
     [not found] ` <20140718161447.020882834-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
2014-07-19  0:16   ` [PATCH 00/10] igb_uio related patches Thomas Monjalon
2014-07-20  8:14     ` Yerden Zhumabekov
     [not found]       ` <53CB7A60.8000202-8EHiFRVJVgQ@public.gmane.org>
2014-07-21 10:28         ` Thomas Monjalon
2014-07-21 12:03           ` [igb_uio PATCH 0/3] igb_uio: fixed typos and pci lock/unlock calls Yerden Zhumabekov
     [not found]             ` <1405944234-50272-1-git-send-email-e_zhumabekov-8EHiFRVJVgQ@public.gmane.org>
2014-07-21 12:03               ` [igb_uio PATCH 1/3] igb_uio: fixed typos Yerden Zhumabekov
2014-07-21 12:03               ` [igb_uio PATCH 2/3] igb_uio: pci_config_lock/pci_config_unlock wrappers Yerden Zhumabekov
     [not found]                 ` <1405944234-50272-3-git-send-email-e_zhumabekov-8EHiFRVJVgQ@public.gmane.org>
2014-07-21 20:42                   ` Stephen Hemminger
2014-07-21 20:50                     ` Thomas Monjalon
2014-07-22 12:57                     ` Thomas Monjalon
2014-07-21 12:03               ` [igb_uio PATCH 3/3] igb_uio: renaming pci config lock/unlock functions Yerden Zhumabekov
2014-07-21 19:51               ` [igb_uio PATCH 0/3] igb_uio: fixed typos and pci lock/unlock calls Thomas Monjalon
2014-07-22 13:07               ` Thomas Monjalon
2014-07-24 21:50                 ` Thomas Monjalon
2014-07-25 16:51                   ` Stephen Hemminger
2014-07-21 15:38           ` [PATCH " Yerden Zhumabekov
     [not found]             ` <1405957094-53380-1-git-send-email-e_zhumabekov-8EHiFRVJVgQ@public.gmane.org>
2014-07-21 15:38               ` [PATCH 1/3] igb_uio: fixed typos Yerden Zhumabekov
2014-07-21 15:38               ` [PATCH 2/3] igb_uio: pci_config_lock/pci_config_unlock wrappers Yerden Zhumabekov
2014-07-21 15:38               ` [PATCH 3/3] igb_uio: renaming pci config lock/unlock functions Yerden Zhumabekov
2014-07-21 19:54               ` [PATCH 0/3] igb_uio: fixed typos and pci lock/unlock calls Thomas Monjalon

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=20140718161516.157268908@networkplumber.org \
    --to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.