From: Andrew Morton <akpm@linux-foundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Segher Boessenkool <segher@kernel.crashing.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: Mon, 30 Mar 2020 15:14:41 -0700 [thread overview]
Message-ID: <20200330151441.e3a704f7c98dc70cdce95d0e@linux-foundation.org> (raw)
In-Reply-To: <F45052AF-D619-4993-AFF4-1E417C3BF424@redhat.com>
On Sun, 29 Mar 2020 22:41:18 +0200 David Hildenbrand <david@redhat.com> wrote:
> > https://lore.kernel.org/linux-mm/20200128093542.6908-1-david@redhat.com/raw
> >
> > and that one *does* have the "Withou=\nt" pattern in it. But it still
> > has the proper
> >
> > Content-Transfer-Encoding: quoted-printable
> >
> > in it, so the recipient should decode it just fine (and again, you can
> > see that in the non-raw email - it looks just fine).
> >
> > So your emails on lore look fine. I'm not seeing how that got corrupted.
>
> *maybe* Andrew updated only the patch description, copying the raw content. Eventually he converts MIME only when importing, so the description got corrupted.
>
> ... or the mail he received via cc got messed up by my mailing infrastructure.
Something like that. It's sylpheed being weird. In some situations
(save as...) it will perform the mime conversion but in others (%f in
an action menu) it does not. So for David's patches I do save-as for
the patch and manually edit the mime out of changelog. It's basically
"only David" so I haven't got around to doing anything smarter.
My nightly check-all-the-patches-for-various-cruft script emails me
about =3D but I didn't' have a test for "o=$m". I just added one.
next prev parent reply other threads:[~2020-03-30 22:14 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
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 [this message]
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=20200330151441.e3a704f7c98dc70cdce95d0e@linux-foundation.org \
--to=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 \
--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;
as well as URLs for NNTP newsgroup(s).