From: Linus Torvalds <torvalds@linux-foundation.org>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Android Kernel Team <kernel-team@android.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] arm64 fixes for -rc3
Date: Fri, 21 Feb 2020 16:07:56 -0800 [thread overview]
Message-ID: <CAHk-=wjyde11qnRQAMgibwcvNCd0bQX5chFgdu58tP0NPhnk_Q@mail.gmail.com> (raw)
In-Reply-To: <20200221160126.GB19330@willie-the-truck>
On Fri, Feb 21, 2020 at 8:01 AM Will Deacon <will@kernel.org> wrote:
>
> That said, this is core code and I know you'd prefer to limit the change
> to brk(), so the patch is sitting on top of the branch in case you prefer
> not to include it. If you decide to tweak it manually, please can you
> update the docs at the same time?
I've taken it as-is, since I don't think any of the solutions were wrong.
The mremap() case looks odd, with the _old_ address untagged, but the
new one not. I see the logic, but because it looks so odd I think it
might be worth a comment.
Not a big deal, and more of a "if you get around to it later" note.
Linus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-22 0:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 16:01 [GIT PULL] arm64 fixes for -rc3 Will Deacon
2020-02-22 0:07 ` Linus Torvalds [this message]
2020-02-22 0:15 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 11:11 Will Deacon
2024-02-02 20:43 ` pr-tracker-bot
2023-09-22 16:19 Will Deacon
2023-09-22 20:19 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31 4:25 ` pr-tracker-bot
2019-01-20 0:04 Will Deacon
2019-01-20 3:29 ` Linus Torvalds
2019-01-20 4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 Will Deacon
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='CAHk-=wjyde11qnRQAMgibwcvNCd0bQX5chFgdu58tP0NPhnk_Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.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 NNTP newsgroup(s).