From: Paul Wise <pabs3@bonedaddy.net>
To: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Jakub Wilk <jwilk@jwilk.net>, Neil Horman <nhorman@tuxdriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.4 116/174] coredump: split pipe command whitespace before expanding template
Date: Fri, 17 Jan 2020 08:57:35 +0800 [thread overview]
Message-ID: <2479db5788a3c776d3c38d2e3b87c570f9a41ea8.camel@bonedaddy.net> (raw)
In-Reply-To: <20200116174251.24326-116-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
On Thu, 2020-01-16 at 12:41 -0500, Sasha Levin wrote:
> From: Paul Wise <pabs3@bonedaddy.net>
>
> [ Upstream commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03 ]
Sasha, we already agreed in [1] and [2] that this patch should not get
backported to earlier versions of Linux, would you mind teaching your
patch autoselection about that so that it doesn't get backported?
1. https://lore.kernel.org/lkml/c835c71b722c3df3d11e7b7f8fd65bbd7da0d482.camel@bonedaddy.net/
2. https://lore.kernel.org/lkml/20190818014841.GF1318@sasha-vm/
--
bye,
pabs
https://bonedaddy.net/pabs3/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-17 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200116174251.24326-1-sashal@kernel.org>
2020-01-16 17:41 ` [PATCH AUTOSEL 4.4 116/174] coredump: split pipe command whitespace before expanding template Sasha Levin
2020-01-17 0:57 ` Paul Wise [this message]
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=2479db5788a3c776d3c38d2e3b87c570f9a41ea8.camel@bonedaddy.net \
--to=pabs3@bonedaddy.net \
--cc=akpm@linux-foundation.org \
--cc=jwilk@jwilk.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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).