From: Thomas Monjalon <thomas@monjalon.net>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, Kevin Laatz <kevin.laatz@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, fengchengwen <fengchengwen@huawei.com>
Subject: Re: [PATCH v2] dmadev: standardize alignment
Date: Mon, 19 Feb 2024 02:32:38 +0100 [thread overview]
Message-ID: <9404336.gsGJI6kyIV@thomas> (raw)
In-Reply-To: <c62af716-50e7-b080-10be-d9353e092e2d@huawei.com>
> > Align fp_objects based on cacheline size defined
> > by build configuration.
> >
> > Signed-off-by: Pavan Nikhilesh<pbhagavatula@marvell.com>
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
Applied, thanks.
prev parent reply other threads:[~2024-02-19 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 9:06 [PATCH] dmadev: standardize alignment and allocation pbhagavatula
2024-02-04 1:38 ` fengchengwen
2024-02-10 6:20 ` [EXT] " Pavan Nikhilesh Bhagavatula
2024-02-10 6:27 ` [PATCH v2] dmadev: standardize alignment pbhagavatula
2024-02-10 11:34 ` fengchengwen
2024-02-19 1:32 ` 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=9404336.gsGJI6kyIV@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.com \
--cc=pbhagavatula@marvell.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).