From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@kernel.org>, Baoquan He <bhe@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Wei Yang <richardw.yang@linux.intel.com>
Subject: Re: [PATCH v2 1/2] mm/memory_hotplug: simplify calculation of number of pages in __remove_pages()
Date: Sun, 29 Mar 2020 13:09:36 -0700 [thread overview]
Message-ID: <CAHk-=wjEk_smqiRh4-JosHsRxzhedJddGf5EQV0JxqZtHYMdkA@mail.gmail.com> (raw)
In-Reply-To: <dca485fe-7024-392b-f51c-cd54550317ff@redhat.com>
On Sun, Mar 29, 2020 at 12:19 PM David Hildenbrand <david@redhat.com> wrote:
>
> This patch seems to have another of these weird MIME crap in it. (my
> other patches in -next seem to be fine)
>
> See
>
> https://lore.kernel.org/linux-mm/20200228095819.10750-2-david@redhat.com/raw
That email actually looks fine.
Yes, it has that
fro=
m
pattern, but it also has
Content-Transfer-Encoding: quoted-printable
so the recipient should be doing the right thing with that pattern.
The patch itself also has MIME encoding in it:
- cur_nr_pages =3D min(end_pfn - pfn, -(pfn | PAGE_SECTION_MASK));
+ cur_nr_pages =3D min(end_pfn - pfn,
so the patch wouldn't even apply unless the recipient did the proper
MIME decode of the message.
That's also why the non-raw message looks fine:
https://lore.kernel.org/linux-mm/20200228095819.10750-2-david@redhat.com/
because the raw message data has the proper encoding information.
In contrast, look at the email that Andrew sent me and that I complained about:
https://lore.kernel.org/linux-mm/20200329021719.MBKzW0xSl%25akpm@linux-foundation.org/
and notice how that *non-raw* email has that
Withou=
t
pattern in it. And when you look at the raw one:
https://lore.kernel.org/linux-mm/20200329021719.MBKzW0xSl%25akpm@linux-foundation.org/raw
it has no content transfer encoding line in the headers.
Linus
next prev parent reply other threads:[~2020-03-29 20:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 9:58 [PATCH v2 0/2] mm/memory_hotplug: __add_pages() and __remove_pages() cleanups David Hildenbrand
2020-02-28 9:58 ` [PATCH v2 1/2] mm/memory_hotplug: simplify calculation of number of pages in __remove_pages() David Hildenbrand
2020-02-28 10:22 ` Baoquan He
2020-02-28 13:25 ` Wei Yang
2020-03-29 19:19 ` David Hildenbrand
2020-03-29 20:09 ` Linus Torvalds [this message]
2020-03-29 20:17 ` David Hildenbrand
2020-03-29 20:26 ` Linus Torvalds
2020-03-29 20:18 ` Linus Torvalds
2020-03-29 20:41 ` David Hildenbrand
2020-03-30 22:14 ` Andrew Morton
2020-03-30 22:27 ` Linus Torvalds
2020-02-28 9:58 ` [PATCH v2 2/2] mm/memory_hotplug: cleanup __add_pages() David Hildenbrand
2020-02-28 10:34 ` Baoquan He
2020-02-28 11:14 ` David Hildenbrand
2020-03-01 5:39 ` Baoquan He
2020-02-28 13:26 ` Wei Yang
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-=wjEk_smqiRh4-JosHsRxzhedJddGf5EQV0JxqZtHYMdkA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=richardw.yang@linux.intel.com \
--cc=segher@kernel.crashing.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).