DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Boyer <Andrew.Boyer@amd.com>
Cc: dev@dpdk.org, sean.morrissey@intel.com,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: [PATCH] eal: restore some needed header includes
Date: Wed, 28 Sep 2022 13:21:29 +0200	[thread overview]
Message-ID: <10469025.aFP6jjVeTY@thomas> (raw)
In-Reply-To: <82f0034b-d2f7-e333-4a86-630b4559db1d@amd.com>

23/09/2022 18:40, Ferruh Yigit:
> On 9/23/2022 3:12 PM, Andrew Boyer wrote:
> > These are necessary to build when HPET is enabled.
> > 
> > Fixes: 2ff3976e677c ("eal: remove unneeded header includes")
> > Cc: sean.morrissey@intel.com
> > 
> > Signed-off-by: Andrew Boyer <Andrew.Boyer@amd.com>
> 
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>

+Cc stable

Applied, thanks.




  reply	other threads:[~2022-09-28 11:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 14:12 Andrew Boyer
2022-09-23 16:40 ` Ferruh Yigit
2022-09-28 11:21   ` Thomas Monjalon [this message]
     [not found] <20220923132911.26996-1-Andrew.Boyer@amd.com>
2022-09-23 16:39 ` Ferruh Yigit

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=10469025.aFP6jjVeTY@thomas \
    --to=thomas@monjalon.net \
    --cc=Andrew.Boyer@amd.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=sean.morrissey@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;
as well as URLs for NNTP newsgroup(s).