From: Andrew Morton <akpm@linux-foundation.org>
To: Jann Horn <jannh@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: Fixes tag needs some work in the mm tree
Date: Wed, 23 Nov 2022 16:13:12 -0800 [thread overview]
Message-ID: <20221123161312.48c1a103da3e4c2df8da7bf9@linux-foundation.org> (raw)
In-Reply-To: <CAG48ez31N1S6g1h8HT8Wxvt8a5m7Y1gJ6JKkVTB2z9G8AGbONA@mail.gmail.com>
On Thu, 24 Nov 2022 00:06:28 +0100 Jann Horn <jannh@google.com> wrote:
> On Wed, Nov 23, 2022 at 11:08 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > In commit
> >
> > d5d60d30f574 ("mmu_gather: Use macro arguments more carefully")
> >
> > Fixes tag
> >
> > Fixes: a6d60245d6d9 ("asm-generic/tlb: Track which levels of the page table=
> >
> > has these problem(s):
>
> I'm not sure what happened here - when I apply the mail that I sent
> with "git am", the "Fixes" line is properly one line. But in the
> version that landed in the tree, it looks as if the quoted-printable
> encoding was not decoded for that one line?
My email client has trouble decoding the quoted-printable stuff. I
have a nightly script which tells me about stragglers, but Stephen
sometimes gets there first. 99% of people use
Content-Transfer-Encoding: 8bit.
next prev parent reply other threads:[~2022-11-24 0:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 22:08 linux-next: Fixes tag needs some work in the mm tree Stephen Rothwell
2022-11-23 23:06 ` Jann Horn
2022-11-24 0:13 ` Andrew Morton [this message]
2022-11-24 13:37 ` Jann Horn
-- strict thread matches above, loose matches on Subject: below --
2025-02-09 6:22 Stephen Rothwell
2024-07-09 22:54 Stephen Rothwell
2024-02-25 21:18 Stephen Rothwell
2024-02-04 21:29 Stephen Rothwell
2023-12-12 20:59 Stephen Rothwell
2023-12-13 1:04 ` Andrew Morton
2023-10-17 4:33 Stephen Rothwell
2023-10-10 5:47 Stephen Rothwell
2023-10-10 15:42 ` Zi Yan
2022-11-23 22:00 Stephen Rothwell
2022-09-18 22:21 Stephen Rothwell
2022-09-19 14:47 ` Zach O'Keefe
2022-09-19 21:04 ` Andrew Morton
2022-09-21 18:24 ` Zach O'Keefe
2022-07-26 23:23 Stephen Rothwell
2022-07-27 0:02 ` Andrew Morton
2022-06-30 3:37 Stephen Rothwell
2022-06-30 15:28 ` Liam Howlett
2022-06-30 18:16 ` Andrew Morton
2022-06-30 3:32 Stephen Rothwell
2022-06-30 15:20 ` Liam Howlett
2022-05-25 0:27 Stephen Rothwell
2022-05-25 0:36 ` Zi Yan
2022-05-13 6:56 Stephen Rothwell
2022-04-27 22:42 Stephen Rothwell
2022-04-28 2:37 ` Liam Howlett
2022-04-28 3:09 ` 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=20221123161312.48c1a103da3e4c2df8da7bf9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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