public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Alexander Dahl <ada@thorsis.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH v3 0/8] Use logging feature instead of FPGA_DEBUG
Date: Thu, 6 Oct 2022 16:44:29 +0200	[thread overview]
Message-ID: <5f7a9b48-8cb0-795f-464d-d91f87f69905@amd.com> (raw)
In-Reply-To: <20221005114421.24340-1-ada@thorsis.com>

Hi,

On 10/5/22 13:44, Alexander Dahl wrote:
> Hei hei,
> 
> while working on FPGA support for a new device I discovered debug
> logging in some FPGA drivers is still done as in the old days.  Bring
> that to what I thougt would be the currently preferred approach.
> 
> Notes: Adding those Kconfig symbols in patch 3 is just to be able to
> build those two old drivers.
> 
> All drivers touched were build tested with sandbox_defconfig and GCC 8
> on Debian GNU/Linux 10 (buster).
> 
> Lines with other possibly questionable output were not touched, only
> what seemed to be designated debug output, and only for FPGA drivers
> having that ancient FPGA_DEBUG / PRINTF macros, so there's room for
> future improvements.
> 
> Changelog:
> 
> v2 -> v3:
> - Patch introducing FPGA uclass was completely reworked, sent
>    independently from this series, and applied already, thus removed
> - Because requiring that new FPGA uclass changes, rebased on Michal's
>    microblaze branch '20221005'
> - Removed '"%s …", __func__' and '"%d …", __line__' from log messages,
>    because log framework can add those (enabled by CONFIG_LOGF_FUNC and
>    CONFIG_LOGF_LINE)
> 
> v1 -> v2:
> - Rebased on master
> - Added patch to introduce new FPGA uclass in front of the other patches
> - Use that new uclass as log category
> - Slightly reworded cover letter
> 
> Greets
> Alex
> 
> Cc: Michal Simek <michal.simek@amd.com>
> 
> Alexander Dahl (7):
>    fpga: altera: Use logging feature instead of FPGA_DEBUG
>    fpga: cyclon2: Use logging feature instead of FPGA_DEBUG
>    fpga: Add missing Kconfig symbols for old FPGA drivers
>    fpga: ACEX1K: Use logging feature instead of FPGA_DEBUG
>    fpga: spartan2: Use logging feature instead of FPGA_DEBUG
>    fpga: spartan3: Use logging feature instead of FPGA_DEBUG
>    fpga: virtex2: Use logging feature instead of FPGA_DEBUG
> 
>   drivers/fpga/ACEX1K.c   | 37 +++++++++----------
>   drivers/fpga/Kconfig    | 12 +++++++
>   drivers/fpga/altera.c   | 11 +++---
>   drivers/fpga/cyclon2.c  | 38 +++++++++-----------
>   drivers/fpga/spartan2.c | 80 +++++++++++++++++++----------------------
>   drivers/fpga/spartan3.c | 80 +++++++++++++++++++----------------------
>   drivers/fpga/virtex2.c  | 69 ++++++++++++++++-------------------
>   7 files changed, 152 insertions(+), 175 deletions(-)

I pushed it to CI loop and got failure.

https://source.denx.de/u-boot/custodians/u-boot-microblaze/-/jobs/508906

Building current source for 136 boards (64 threads, 1 job per thread)
       m68k:  +   astro_mcf5373l
+In file included from include/linux/printk.h:4,
+                 from include/common.h:20,
+                 from drivers/fpga/spartan3.c:14:
+drivers/fpga/spartan3.c: In function 'spartan3_sp_load':
+drivers/fpga/spartan3.c:112:27: error: too many arguments for format 
[-Werror=format-extra-args]
+  112 |                 log_debug("Function Table:\n"
+      |                           ^~~~~~~~~~~~~~~~~~~
+include/log.h:220:24: note: in definition of macro 'log'
+  220 |                 printf(_fmt, ##_args); \
+      |                        ^~~~
+drivers/fpga/spartan3.c:112:17: note: in expansion of macro 'log_debug'
+      |                 ^~~~~~~~~
+cc1: all warnings being treated as errors
+make[3]: *** [scripts/Makefile.build:258: drivers/fpga/spartan3.o] Error 1
+make[2]: *** [scripts/Makefile.build:398: drivers/fpga] Error 2
+make[1]: *** [Makefile:1883: drivers] Error 2

Please fix it up.

Thanks,
Michal

  parent reply	other threads:[~2022-10-06 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 11:44 [PATCH v3 0/8] Use logging feature instead of FPGA_DEBUG Alexander Dahl
2022-10-05 11:44 ` [PATCH v3 1/7] fpga: altera: " Alexander Dahl
2022-10-05 11:44 ` [PATCH v3 2/7] fpga: cyclon2: " Alexander Dahl
2022-10-05 11:44 ` [PATCH v3 3/7] fpga: Add missing Kconfig symbols for old FPGA drivers Alexander Dahl
2022-10-05 11:44 ` [PATCH v3 4/7] fpga: ACEX1K: Use logging feature instead of FPGA_DEBUG Alexander Dahl
2022-10-05 11:44 ` [PATCH v3 5/7] fpga: spartan2: " Alexander Dahl
2022-10-05 11:44 ` [PATCH v3 6/7] fpga: spartan3: " Alexander Dahl
2022-10-05 11:44 ` [PATCH v3 7/7] fpga: virtex2: " Alexander Dahl
2022-10-06 14:44 ` Michal Simek [this message]
2022-10-06 14:56   ` [PATCH v3 0/8] " Alexander Dahl
2022-10-07  6:34     ` Michal Simek
2022-10-07 12:21       ` Alexander Dahl

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=5f7a9b48-8cb0-795f-464d-d91f87f69905@amd.com \
    --to=michal.simek@amd.com \
    --cc=ada@thorsis.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