From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/3] eal/linuxapp: fix invalid syntax in interrupts
Date: Fri, 13 Jul 2018 11:45:21 +0200 [thread overview]
Message-ID: <1759071.m1mZFXhsnA@xps> (raw)
In-Reply-To: <5f73e30c5159ff7476641036f2d81c78d15b38a3.1527843615.git.anatoly.burakov@intel.com>
01/06/2018 11:08, Anatoly Burakov:
> Parentheses were missing. It worked because macro is enclosed in
> parentheses, so syntax was valid after macro expansion.
>
> Bugzilla ID: 58
> Fixes: 0a45657a6794 ("pci: rework interrupt handling")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Series applied, thanks
prev parent reply other threads:[~2018-07-13 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 9:08 Anatoly Burakov
2018-06-01 9:08 ` [dpdk-dev] [PATCH 2/3] eal/linux: fix uninitialized value Anatoly Burakov
2018-06-01 9:08 ` [dpdk-dev] [PATCH 3/3] vfio: fix uninitialized variable Anatoly Burakov
2018-07-13 9:45 ` Thomas Monjalon [this message]
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=1759071.m1mZFXhsnA@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.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 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).