linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Dan Williams <dan.j.williams@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Heiko Carstens <heiko.carstens@de.ibm.com>,
	Karel Zak <kzak@redhat.com>,  Linux-MM <linux-mm@kvack.org>,
	Michal Hocko <mhocko@kernel.org>, Michal Hocko <mhocko@suse.com>,
	 mm-commits@vger.kernel.org, ndfont@gmail.com,
	pbadari@us.ibm.com,  Rafael Wysocki <rafael@kernel.org>,
	rcj@linux.vnet.ibm.com, stable <stable@vger.kernel.org>,
	 steve.scargall@intel.com
Subject: Re: [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable
Date: Sun, 29 Mar 2020 12:55:09 -0700	[thread overview]
Message-ID: <CAHk-=wheAem=MzY=F0ox7tuxFR47SgUj7zB+2S_KOhEB49zsPA@mail.gmail.com> (raw)
In-Reply-To: <20200329194354.xrbzlvlbjimy3pzz@chatter.i7.local>

On Sun, Mar 29, 2020 at 12:43 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> It would appear that the workflow Andrew uses to queue up patches from
> you isn't expecting quoted-printable formatting, which is why when Linus
> gets them, they are mangled.

I don't think that's the case.

Why? Because I see _proper_ handling of MIME and quoted-printable from
Andrew all the time.

For example, anything from Jérôme Glisse always ends up having been
quoted-printable, simply because of how Jérôme's emails look, and
because he has 8-bit characters in his name.

There are other examples of the same thing - a lot of the emails I get
from Andrew do end up having quoted-printable encoding.

It's only David's patches that then end up having lost the encoding
marker, but have QP sequences in the commit message.

The odd thing is that the *patches* are fine, even if they have equals
signs etc that would have been QP-encoded too. So it's literally just
the commit message that tends to be corrupt.

Which is why I was suspecting people cut-and-pasting the raw emails
for examplanations or something similar.

                Linus


  reply	other threads:[~2020-03-29 19:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29  2:14 incoming Andrew Morton
2020-03-29  2:17 ` [patch 1/5] mm/swapfile.c: move inode_lock out of claim_swapfile Andrew Morton
2020-03-29  2:17 ` [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable Andrew Morton
2020-03-29 16:46   ` Linus Torvalds
2020-03-29 18:03     ` David Hildenbrand
2020-03-29 18:28       ` Linus Torvalds
2020-03-29 19:11         ` David Hildenbrand
2020-03-29 19:15           ` Linus Torvalds
2020-03-29 19:43       ` Konstantin Ryabitsev
2020-03-29 19:55         ` Linus Torvalds [this message]
2020-03-29 19:56           ` Linus Torvalds
2020-03-30 14:46           ` Konstantin Ryabitsev
2020-03-30 14:54         ` David Hildenbrand
2020-04-01 13:35           ` David Hildenbrand
2020-04-01 15:33             ` Konstantin Ryabitsev
2020-04-01 15:40               ` David Hildenbrand
2020-03-29  2:17 ` [patch 3/5] hugetlb_cgroup: fix illegal access to memory Andrew Morton
2020-03-29  2:17 ` [patch 4/5] mm: fork: fix kernel_stack memcg stats for various stack implementations Andrew Morton
2020-03-29 16:41   ` Linus Torvalds
2020-03-29  2:17 ` [patch 5/5] mm/sparse: fix kernel crash with pfn_section_valid check Andrew Morton

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-=wheAem=MzY=F0ox7tuxFR47SgUj7zB+2S_KOhEB49zsPA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=kzak@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=ndfont@gmail.com \
    --cc=pbadari@us.ibm.com \
    --cc=rafael@kernel.org \
    --cc=rcj@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=steve.scargall@intel.com \
    --subject='Re: [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox