linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 linux-mm@kvack.org, mm-commits@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] hotfixes for 6.3-rc1
Date: Mon, 06 Mar 2023 09:25:06 +0800	[thread overview]
Message-ID: <87jzzu7jt9.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <CAHk-=wiHX2NQiVH8uQZ_U8vB=qnzmQHauGAqAkC=4ZWp95ya8w@mail.gmail.com> (Linus Torvalds's message of "Sat, 4 Mar 2023 15:37:11 -0800")

Hi, Linus,

Linus Torvalds <torvalds@linux-foundation.org> writes:

> On Sat, Mar 4, 2023 at 3:21 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> Ah. Ying did it this way:
>
> Yeah, I saw that patch flying past, but I actually think that it only
> silences the warning almost by mistake. There's nothing fundamental in
> there that a compiler wouldn't just follow across two assignments, and
> it just happens to now not trigger any more.
>
> Assigning to a union entry is a more fundamental operation in that
> respect. Not that the compiler still doesn't see that it's assigning a
> value that in the end is not really type compatible, so a different
> version of gcc could still warn, but at that point I feel like it's
> more of an actual compiler bug than just "oh, the compiler didn't
> happen to follow the cast through a temporary".

Yes.  Your fix is much better.  This can be used for
__page_set_anon_rmap() family too to make the code look better?

Best Regards,
Huang, Ying


  reply	other threads:[~2023-03-06  1:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 21:15 Andrew Morton
2023-03-04 22:26 ` pr-tracker-bot
2023-03-04 22:35 ` Linus Torvalds
2023-03-04 23:20   ` Andrew Morton
2023-03-04 23:37     ` Linus Torvalds
2023-03-06  1:25       ` Huang, Ying [this message]
2023-03-08 10:39         ` Vlastimil Babka
2023-03-09  8:37           ` Huang, Ying
2023-03-14 23:54 Andrew Morton
2023-03-15  2:41 ` pr-tracker-bot

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=87jzzu7jt9.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=torvalds@linux-foundation.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