From: puranjay12 at gmail.com (Puranjay Mohan)
Subject: [Linux-kernel-mentees] Seeking information about LKMP Project - "Linux PCI - Remove driver-local definitions of standard PCI symbols"
Date: Thu, 2 May 2019 02:37:17 +0530 [thread overview]
Message-ID: <20190501210717.GA30464@arch> (raw)
Hello,
I wanted to get a few things clarified in relation to the aforementioned project in the subject.
The description of the project states that some drivers define their own copies of PCI_COMMAND, PCI_STATUS, etc.
If we remove these definitions,
then for the driver to work it has to include "include/uapi/linux/pci_regs.h",
so should we also add the include statement in the driver source code or it is already included by some other way.
Kindly help me resolve this confusion as I am a beginner at this.
If the question sounds wrong or lame, please forgive me.
I want to work on this project as a part of the Linux kernel mentorship program.
Thanks and Regards
WARNING: multiple messages have this Message-ID (diff)
From: puranjay12@gmail.com (Puranjay Mohan)
Subject: [Linux-kernel-mentees] Seeking information about LKMP Project - "Linux PCI - Remove driver-local definitions of standard PCI symbols"
Date: Thu, 2 May 2019 02:37:17 +0530 [thread overview]
Message-ID: <20190501210717.GA30464@arch> (raw)
Message-ID: <20190501210717.E_YWXxepwICrE_SQYu2QdBRyaa6a0ZaLdMiZwuCSAvo@z> (raw)
Hello,
I wanted to get a few things clarified in relation to the aforementioned project in the subject.
The description of the project states that some drivers define their own copies of PCI_COMMAND, PCI_STATUS, etc.
If we remove these definitions,
then for the driver to work it has to include "include/uapi/linux/pci_regs.h",
so should we also add the include statement in the driver source code or it is already included by some other way.
Kindly help me resolve this confusion as I am a beginner at this.
If the question sounds wrong or lame, please forgive me.
I want to work on this project as a part of the Linux kernel mentorship program.
Thanks and Regards
next reply other threads:[~2019-05-01 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 21:07 puranjay12 [this message]
2019-05-01 21:07 ` [Linux-kernel-mentees] Seeking information about LKMP Project - "Linux PCI - Remove driver-local definitions of standard PCI symbols" Puranjay Mohan
[not found] ` <1e3ae604-1e71-b930-2d33-c84cdbf629ca@linuxfoundation.org>
2019-05-02 4:51 ` puranjay12
2019-05-02 4:51 ` Puranjay Mohan
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=20190501210717.GA30464@arch \
--to=unknown@example.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 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.