public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Sunil Pandey <skpgkp2@gmail.com>
To: Libc-stable Mailing List <libc-stable@sourceware.org>,
	schwab@linux-m68k.org
Subject: Re: [backport] Fix misplaced const
Date: Tue, 3 May 2022 11:52:16 -0700	[thread overview]
Message-ID: <CAMAf5_cFjDpxxY6-jr5y=0PSfq7rbZypcQXe4YhyQkm7jqYbsQ@mail.gmail.com> (raw)
In-Reply-To: <CAMAf5_dg9oc-L1eR-Dsz8oi6cfWnua=PLGGK=bZiWJWt+724+Q@mail.gmail.com>

On Mon, May 2, 2022 at 7:09 AM Sunil Pandey <skpgkp2@gmail.com> wrote:
>
> I would like to backport this patch to release branches.
> Any comments or objections?
>
> $ git show 31f6488722
> commit 31f64887222597bb15b7a814d8dadb7cb667bcb9
> Author: Andreas Schwab <schwab@linux-m68k.org>
> Date:   Mon Jan 25 14:29:45 2021 +0100
>
>     Fix misplaced const
>
>     Constify __x86_cacheinfo_p and __x86_cpu_features_p, not their pointer
>     target types.
>
> diff --git a/sysdeps/x86/cacheinfo.c b/sysdeps/x86/cacheinfo.c
> index 350cba5fda..7b8df45e3b 100644
> --- a/sysdeps/x86/cacheinfo.c
> +++ b/sysdeps/x86/cacheinfo.c
> @@ -77,7 +77,7 @@ __cache_sysconf (int name)
>  # include <ifunc-init.h>
>
>  extern void __x86_cacheinfo (void) attribute_hidden;
> -const void (*__x86_cacheinfo_p) (void) attribute_hidden
> +void (*const __x86_cacheinfo_p) (void) attribute_hidden
>    = __x86_cacheinfo;
>
>  __ifunc (__x86_cacheinfo, __x86_cacheinfo, NULL, void, init_cacheinfo);
> diff --git a/sysdeps/x86/dl-get-cpu-features.c
> b/sysdeps/x86/dl-get-cpu-features.c
> index 99e3aa7d04..839803c746 100644
> --- a/sysdeps/x86/dl-get-cpu-features.c
> +++ b/sysdeps/x86/dl-get-cpu-features.c
> @@ -28,7 +28,7 @@
>     once by IFUNC relocation.  In dynamic executable, it is called twice
>     by DL_PLATFORM_INIT and by IFUNC relocation.  */
>  extern void __x86_cpu_features (void) attribute_hidden;
> -const void (*__x86_cpu_features_p) (void) attribute_hidden
> +void (*const __x86_cpu_features_p) (void) attribute_hidden
>    = __x86_cpu_features;
>
>  void

I have to stop backporting at 2.33.

There is major x86 restructuring and inter patch dependency in the 2.32 branch.
Resolving backport conflict in the 2.32 branch has a cascading effect
on existing
patches.

--Sunil

      reply	other threads:[~2022-05-03 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 14:09 Sunil Pandey
2022-05-03 18:52 ` Sunil Pandey [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='CAMAf5_cFjDpxxY6-jr5y=0PSfq7rbZypcQXe4YhyQkm7jqYbsQ@mail.gmail.com' \
    --to=skpgkp2@gmail.com \
    --cc=libc-stable@sourceware.org \
    --cc=schwab@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).