mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] glibc: fix typo in Y2038 check
Date: Thu, 8 Jun 2023 14:57:24 +0200	[thread overview]
Message-ID: <ZIHQNPyuMorbj9Ts@pengutronix.de> (raw)
In-Reply-To: <ZIFlqkbvHcmzBsoe@lenoch>

On Thu, Jun 08, 2023 at 07:22:50AM +0200, Ladislav Michl wrote:
> From: Ladislav Michl <ladis@linux-mips.org>
> 
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> ---
>  Note: The previous commit message had a typo as well...
> 
>  rules/glibc.make | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/rules/glibc.make b/rules/glibc.make
> index 0f54bb181..a550f4b92 100644
> --- a/rules/glibc.make
> +++ b/rules/glibc.make
> @@ -32,7 +32,7 @@ ifdef PTXCONF_GLIBC_Y2038
>  	@echo Checking Y2038 support...
>  	@echo 'static_assert(sizeof(time_t) == 8, "y2038");' | \
>  		$(CROSS_CC) -c -x c -include sys/types.h -include assert.h - &>/dev/null || \
> -		ptxd_bailout "PTXCONF_GLIBC_Y2038 is enabled but the toolchain has no Y2028 support!"
> +		ptxd_bailout "PTXCONF_GLIBC_Y2038 is enabled but the toolchain has no Y2038 support!"

Right, luckily we do have a few more years... :-)

Michael

>  endif
>  	@$(call touch)
>  
> -- 
> 2.32.0
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2023-06-08 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  5:22 Ladislav Michl
2023-06-08 12:57 ` Michael Olbrich [this message]
2023-06-21  8:51 ` [ptxdist] [APPLIED] " Michael Olbrich

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=ZIHQNPyuMorbj9Ts@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=oss-lists@triops.cz \
    --cc=ptxdist@pengutronix.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