Show a cover letter.

GET /api/covers/54771/?format=api
Content-Type: application/json
Vary: Accept

    "id": 54771,
    "url": "",
    "web_url": "",
    "project": {
        "id": 1,
        "url": "",
        "name": "DPDK",
        "link_name": "dpdk",
        "list_id": "",
        "list_email": "",
        "web_url": "",
        "scm_url": "git://",
        "webscm_url": ""
    "msgid": "<>",
    "date": "2019-06-13T14:23:34",
    "name": "[v2,0/10] dpdk: introduce __rte_internal tag",
    "submitter": {
        "id": 32,
        "url": "",
        "name": "Neil Horman",
        "email": ""
    "mbox": "",
    "series": [
            "id": 5004,
            "url": "",
            "web_url": "",
            "date": "2019-06-13T14:23:34",
            "name": "dpdk: introduce __rte_internal tag",
            "version": 2,
            "mbox": ""
    "comments": "",
    "headers": {
        "X-Mailer": "git-send-email 2.20.1",
        "List-Id": "DPDK patches and discussions <>",
        "From": "Neil Horman <>",
        "List-Help": "<>",
        "Date": "Thu, 13 Jun 2019 10:23:34 -0400",
        "X-Mailman-Version": "2.1.15",
        "Delivered-To": "",
        "List-Subscribe": "<>,\n\t<>",
        "Cc": "Neil Horman <>,\n\tJerin Jacob Kollanukkaran <>,\n\tBruce Richardson <>,\n\tThomas Monjalon <>",
        "To": "",
        "Errors-To": "",
        "References": "<>",
        "Content-Transfer-Encoding": "8bit",
        "Return-Path": "<>",
        "List-Unsubscribe": "<>,\n\t<>",
        "List-Post": "<>",
        "Received": [
            "from [] (localhost [])\n\tby (Postfix) with ESMTP id 7192B1D5E6;\n\tThu, 13 Jun 2019 16:24:01 +0200 (CEST)",
            "from ( [])\n\tby (Postfix) with ESMTP id B1D5E1D5E0\n\tfor <>; Thu, 13 Jun 2019 16:23:59 +0200 (CEST)",
            "from [] (\n\tby with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)\n\t(envelope-from <>)\n\tid 1hbQdt-0000fv-JK; Thu, 13 Jun 2019 10:23:56 -0400",
            "from (localhost [])\n\tby (8.15.2/8.15.2) with ESMTP id\n\tx5DENlK9009315; Thu, 13 Jun 2019 10:23:47 -0400",
            "(from nhorman@localhost)\n\tby (8.15.2/8.15.2/Submit) id\n\tx5DENkKj009314; Thu, 13 Jun 2019 10:23:46 -0400"
        "List-Archive": "<>",
        "Sender": "\"dev\" <>",
        "Subject": "[dpdk-dev] [PATCH v2 0/10] dpdk: introduce __rte_internal tag",
        "In-Reply-To": "<>",
        "MIME-Version": "1.0",
        "Message-Id": "<>",
        "X-Spam-Score": "-2.9 (--)",
        "Precedence": "list",
        "X-Spam-Status": "No",
        "X-BeenThere": "",
        "X-Original-To": ""
    "content": "Hey-\n        Based on our recent conversations regarding the use of symbols only\nmeant for internal dpdk consumption (between dpdk libraries), this is an idea\nthat I've come up with that I'd like to get some feedback on\n\nSummary:\n1) We have symbols in the DPDK that are meant to be used between DPDK libraries,\nbut not by applications linking to them\n2) We would like to document those symbols in the code, so as to note them\nclearly as for being meant for internal use only\n3) Linker symbol visibility is a very coarse grained tool, and so there is no\ngood way in a single library to mark items as being meant for use only by other\nDPDK libraries, at least not without some extensive runtime checking\n\n\nProposal:\nI'm proposing that we introduce the __rte_internal tag.  From a coding\nstandpoint it works a great deal like the __rte_experimental tag in that it\nexpempts the tagged symbol from ABI constraints (as the only users should be\nrepresented in the DPDK build environment).  Additionally, the __rte_internal\nmacro resolves differently based on the definition of the BUILDING_RTE_SDK flag\n(working under the assumption that said flag should only ever be set if we are\nactually building DPDK libraries which will make use of internal calls).  If the\nBUILDING_RTE_SDK flag is set __rte_internal resolves to __attribute__((section\n\"text.internal)), placing it in a special text section which is then used to\nvalidate that the the symbol appears in the INTERNAL section of the\ncorresponding library version map).  If BUILDING_RTE_SDK is not set, then\n__rte_internal resolves to __attribute__((error(\"...\"))), which causes any\ncaller of the tagged function to throw an error at compile time, indicating that\nthe symbol is not available for external use.\n\nThis isn't a perfect solution, as applications can still hack around it of\ncourse, but I think it hits some of the high points, restricting symbol access\nfor any library that prototypes its public and private symbols in the same\nheader file, excluding the internal symbols from ABI constraints, and clearly\ndocumenting those symbols which we wish to limit to internal usage.\n\nSigned-off-by: Neil Horman <>\nCC: Jerin Jacob Kollanukkaran <>\nCC: Bruce Richardson <>\nCC: Thomas Monjalon <>\n\n---\nChange notes\n\nv1->v2\nMoved rename to earlier in the series\nUpdated meson build environment to support BUILDING_RTE_SDK"