public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@xilinx.com>,
	Simon Glass <sjg@chromium.org>,  Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v2 0/3] trace: Fix flyrecord alignment issue
Date: Thu, 21 Sep 2023 13:07:43 +0200	[thread overview]
Message-ID: <ab72c480-e9f8-416e-adf5-726f7d40c4f5@amd.com> (raw)
In-Reply-To: <cover.1694779918.git.michal.simek@amd.com>



On 9/15/23 14:12, Michal Simek wrote:
> Hi,
> 
> sandbox is getting bigger and bigger and I have reached the case that
> adding some more functions ends up in CI loop failure. After some
> investigation I found that flyrecord header have incorrect information
> about data offset which is caused by incorrect alignment calculation.
> That's why this series is fixing alignment calculation.
> I have done it via 3 patches where the first two are just preparing code
> for actual fixup.
> 
> Thanks,
> Michal
> 
> Changes in v2:
> - s/start_addr/start_ofs/g'
> 
> Michal Simek (3):
>    trace: Use 64bit variable for start and len
>    trace: Move trace_clocks description above record offset calculation
>    trace: Fix alignment logic in flyrecord header
> 
>   tools/proftool.c | 39 ++++++++++++++++++++++++++++++++++-----
>   1 file changed, 34 insertions(+), 5 deletions(-)
> 

Applied.
M

      parent reply	other threads:[~2023-09-21 11:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 12:12 [PATCH v2 0/3] trace: Fix flyrecord alignment issue Michal Simek
2023-09-15 12:12 ` [PATCH v2 1/3] trace: Use 64bit variable for start and len Michal Simek
2023-09-23 18:13   ` Simon Glass
2023-09-15 12:12 ` [PATCH v2 2/3] trace: Move trace_clocks description above record offset calculation Michal Simek
2023-09-23 18:13   ` Simon Glass
2023-09-15 12:12 ` [PATCH v2 3/3] trace: Fix alignment logic in flyrecord header Michal Simek
2023-09-23 18:13   ` Simon Glass
2023-09-25  6:05     ` Michal Simek
2023-09-25 13:10       ` Simon Glass
2023-09-25 13:38         ` Michal Simek
2023-09-25 14:01           ` Simon Glass
2023-09-25 14:10             ` Michal Simek
2023-09-25 14:19               ` Tom Rini
2023-09-25 14:21                 ` Michal Simek
2023-09-25 14:33                   ` Tom Rini
2023-10-24 12:33                     ` Michal Simek
2023-10-24 18:03                       ` Tom Rini
2023-10-25  7:33                         ` Michal Simek
2023-10-25 14:19                           ` Tom Rini
2023-09-25 14:28             ` Tom Rini
2023-09-25 14:43               ` Michal Simek
2023-09-21 11:07 ` Michal Simek [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=ab72c480-e9f8-416e-adf5-726f7d40c4f5@amd.com \
    --to=michal.simek@amd.com \
    --cc=git@xilinx.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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