From: Emil Velikov <emil.l.velikov@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Eric Engestrom <eric.engestrom@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
emil.l.velikov@gmail.com
Subject: [PATCH libdrm] intel: annotate the intel genx helpers as private
Date: Thu, 6 Sep 2018 16:14:07 +0100 [thread overview]
Message-ID: <20180906151407.9744-1-emil.l.velikov@gmail.com> (raw)
From: Emil Velikov <emil.velikov@collabora.com>
They're used internally and never meant to be part of the API.
Add the drm_private notation, which should resolve that.
Cc: Eric Engestrom <eric.engestrom@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Fixes: 4e81d4f9c9b ("intel: add generic functions to check PCI ID")
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
---
intel/intel_chipset.c | 4 ++--
intel/intel_chipset.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/intel/intel_chipset.c b/intel/intel_chipset.c
index d5c33cc5..5aa4a2f2 100644
--- a/intel/intel_chipset.c
+++ b/intel/intel_chipset.c
@@ -44,7 +44,7 @@ static const struct pci_device {
INTEL_SKL_IDS(9),
};
-bool intel_is_genx(unsigned int devid, int gen)
+drm_private bool intel_is_genx(unsigned int devid, int gen)
{
const struct pci_device *p,
*pend = pciids + sizeof(pciids) / sizeof(pciids[0]);
@@ -66,7 +66,7 @@ bool intel_is_genx(unsigned int devid, int gen)
return false;
}
-bool intel_get_genx(unsigned int devid, int *gen)
+drm_private bool intel_get_genx(unsigned int devid, int *gen)
{
const struct pci_device *p,
*pend = pciids + sizeof(pciids) / sizeof(pciids[0]);
diff --git a/intel/intel_chipset.h b/intel/intel_chipset.h
index 9b1e64f1..63ddde7a 100644
--- a/intel/intel_chipset.h
+++ b/intel/intel_chipset.h
@@ -330,8 +330,8 @@
/* New platforms use kernel pci ids */
#include <stdbool.h>
-bool intel_is_genx(unsigned int devid, int gen);
-bool intel_get_genx(unsigned int devid, int *gen);
+drm_private bool intel_is_genx(unsigned int devid, int gen);
+drm_private bool intel_get_genx(unsigned int devid, int *gen);
#define IS_GEN9(devid) intel_is_genx(devid, 9)
#define IS_GEN10(devid) intel_is_genx(devid, 10)
--
2.18.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-09-06 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 15:14 Emil Velikov [this message]
2018-09-06 17:38 ` [PATCH libdrm] intel: annotate the intel genx helpers as private Chris Wilson
2018-09-06 17:51 ` Lucas De Marchi
2018-09-06 17:59 ` Chris Wilson
2018-09-06 19:45 ` Lucas De Marchi
2018-09-06 17:46 ` Lucas De Marchi
-- strict thread matches above, loose matches on Subject: below --
2018-09-11 21:22 Rodrigo Vivi
2018-09-12 10:44 ` Eric Engestrom
2018-09-12 15:50 ` Rodrigo Vivi
2018-09-12 16:03 ` Rodrigo Vivi
2018-09-13 7:19 ` Chih-Wei Huang
2018-09-13 8:45 ` Eric Engestrom
2018-09-13 17:43 ` Rodrigo Vivi
2018-09-13 18:25 ` Eric Engestrom
2018-09-13 18:23 ` Lucas De Marchi
2018-09-13 18:27 ` Chris Wilson
2018-09-19 7:47 ` Chih-Wei Huang
2018-09-19 23:18 ` Lucas De Marchi
2018-09-21 7:32 ` Chih-Wei Huang
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=20180906151407.9744-1-emil.l.velikov@gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.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