public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 06/11] lib/sha*.c: Update header list
Date: Sat, 9 Dec 2023 10:48:54 -0500	[thread overview]
Message-ID: <20231209154854.GI2513409@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0_U0-9y9o_FZ3-snLmBauuhUW1uoL5ghC=dTRdy3xcKw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

On Sat, Dec 02, 2023 at 11:23:13AM -0700, Simon Glass wrote:
> Hi Tom,
> 
> On Wed, 22 Nov 2023 at 06:12, Tom Rini <trini@konsulko.com> wrote:
> >
> > Cleanup the list of headers we include here. For the tools build we only
> > need to exclude <cyclic.h> as that's used by the target build for the
> > prototype for schedule(), and we don't need to get that via
> > <watchdog.h>. We can also make use of our <string.h> intentionally
> > existing as a redirection to <linux/string.h> to reduce ifdef'd lines.
> >
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> >  lib/sha1.c   | 7 ++-----
> >  lib/sha256.c | 7 ++-----
> >  lib/sha512.c | 6 +-----
> >  3 files changed, 5 insertions(+), 15 deletions(-)
> 
> As mentioned in my series this will prevent dropping the #ifdefs in this file:
> 
> #if defined(CONFIG_HW_WATCHDOG) || defined(CONFIG_WATCHDOG)
> 
> Actually I see that I didn't send the v2 so I just did that now[1].
> 
> Regards,
> Simon
> 
> [1] https://patchwork.ozlabs.org/project/uboot/patch/20231202153400.537050-2-sjg@chromium.org/

Yes, I prefer what I did here instead of [1].

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-12-09 15:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 13:11 [PATCH 01/11] global: Remove duplicate common.h inclusions Tom Rini
2023-11-22 13:11 ` [PATCH 02/11] arm: Remove <asm/types.h> from asm/global_data.h Tom Rini
2023-12-02 18:23   ` Simon Glass
2023-11-22 13:11 ` [PATCH 03/11] sandbox: Add <linux/types.h> to asm/global_data.h and asm/io.h Tom Rini
2023-11-30  2:45   ` Simon Glass
2023-11-22 13:11 ` [PATCH 04/11] m68k: Rework asm/global_data.h slightly Tom Rini
2023-11-22 21:04   ` Angelo Dureghello
2023-11-22 21:09     ` Tom Rini
2023-11-23 20:44       ` Angelo Dureghello
2023-11-22 13:11 ` [PATCH 05/11] global: Rework architecture global_data.h to include <linux/types.h> Tom Rini
2023-12-02 18:23   ` Simon Glass
2023-11-22 13:11 ` [PATCH 06/11] lib/sha*.c: Update header list Tom Rini
2023-12-02 18:23   ` Simon Glass
2023-12-09 15:48     ` Tom Rini [this message]
2023-11-22 13:11 ` [PATCH 07/11] rmobile: Add <mach/rmobile.h> to cpu_info-rzg2l.c Tom Rini
2023-11-22 16:15   ` Marek Vasut
2023-11-22 13:11 ` [PATCH 08/11] efi_loader: Remove <common.h> Tom Rini
2023-11-22 13:46   ` Ilias Apalodimas
2023-11-22 13:11 ` [PATCH 09/11] display_options: Clean up headers Tom Rini
2023-11-30  2:45   ` Simon Glass
2023-11-22 13:11 ` [PATCH 10/11] include: Further cleanup includes Tom Rini
2023-12-02 18:23   ` Simon Glass
2023-11-22 13:11 ` [PATCH 11/11] lib: Remove <common.h> inclusion from these files Tom Rini
2023-12-01 18:44   ` Simon Glass
2023-12-02 18:23 ` [PATCH 01/11] global: Remove duplicate common.h inclusions Simon Glass

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=20231209154854.GI2513409@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=sjg@chromium.org \
    --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