From: "Jules Maselbas" <jmaselbas@zdiv.net>
To: "Ahmad Fatoum" <a.fatoum@pengutronix.de>, <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/6] compile test fixes
Date: Fri, 14 Mar 2025 15:43:24 +0100 [thread overview]
Message-ID: <D8G2HOCHLZHE.3FCQMJ924J7NR@zdiv.net> (raw)
In-Reply-To: <a87dbd9c-10fb-4451-abd3-f3d9d49c13e2@pengutronix.de>
On Fri Mar 14, 2025 at 2:08 PM CET, Ahmad Fatoum wrote:
> Hi Jules,
>
> On 3/14/25 11:40, Jules Maselbas wrote:
>> Small patches series of fixes discovered with a compile test on sandbox (x86_64)
>> The compile test has been against the next branch but all the patches applies on
>> commits that are already in the master branch.
>
> This partially duplicates fixes in my clang-analyzer series here:
> https://lore.barebox.org/barebox/20250313073445.764875-1-a.fatoum@pengutronix.de/T/#t
>
> Can you rebase?
Only patch 6 is conflicting and can be dropped because it is already fixed by
9b815da01ff4b88c6634c4a7541c581a35ad96d8 ("treewide: fix missing headers in sandbox allyesconfig")
>
> Thanks,
> Ahmad
>
>>
>> Jules Maselbas (6):
>> dma-devices: k3-udma: cleanup headers
>> dma-devices: k3-udma: use snprintf instead of sprintf
>> mfd: tps65219: add missing include
>> pmdomain: ti-k3: add missing include
>> pmdomain: ti-k3: remove trailing whitespace
>> regulator: tps65219: add missing include
>>
>> drivers/dma/ti/k3-udma.c | 5 ++---
>> drivers/mfd/tps65219.c | 1 +
>> drivers/pmdomain/ti/ti-k3.c | 9 +++++----
>> drivers/regulator/tps65219-regulator.c | 1 +
>> 4 files changed, 9 insertions(+), 7 deletions(-)
>>
next prev parent reply other threads:[~2025-03-14 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 10:40 Jules Maselbas
2025-03-14 10:40 ` [PATCH 1/6] dma-devices: k3-udma: cleanup headers Jules Maselbas
2025-03-14 10:40 ` [PATCH 2/6] dma-devices: k3-udma: use snprintf instead of sprintf Jules Maselbas
2025-03-14 10:40 ` [PATCH 3/6] mfd: tps65219: add missing include Jules Maselbas
2025-03-14 10:40 ` [PATCH 4/6] pmdomain: ti-k3: " Jules Maselbas
2025-03-14 10:40 ` [PATCH 5/6] pmdomain: ti-k3: remove trailing whitespace Jules Maselbas
2025-03-14 10:40 ` [PATCH 6/6] regulator: tps65219: add missing include Jules Maselbas
2025-03-14 13:08 ` [PATCH 0/6] compile test fixes Ahmad Fatoum
2025-03-14 14:43 ` Jules Maselbas [this message]
2025-03-14 14:49 ` Ahmad Fatoum
2025-03-14 15:00 ` Jules Maselbas
2025-03-14 15:09 ` [PATCH v2 0/3] compile test cleanups Jules Maselbas
2025-03-14 15:09 ` [PATCH v2 1/3] dma-devices: k3-udma: remove duplicated include Jules Maselbas
2025-03-14 15:09 ` [PATCH v2 2/3] dma-devices: k3-udma: use snprintf instead of sprintf Jules Maselbas
2025-03-14 15:09 ` [PATCH v2 3/3] pmdomain: ti-k3: remove trailing whitespace Jules Maselbas
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=D8G2HOCHLZHE.3FCQMJ924J7NR@zdiv.net \
--to=jmaselbas@zdiv.net \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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