From: Sasha Levin <sashal@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: stable <stable@vger.kernel.org>
Subject: Re: [STABLE candidates] backport candidates from Allwinner kernels
Date: Mon, 1 Apr 2019 10:34:32 -0400 [thread overview]
Message-ID: <20190401143432.GB2792@sasha-vm> (raw)
In-Reply-To: <CAK8P3a2Fs7yxNJygj9p-O3jyt+kN7Hy5o9Am0_arpNfK5dHBMQ@mail.gmail.com>
On Thu, Mar 28, 2019 at 11:02:16AM +0800, Arnd Bergmann wrote:
>On Wed, Mar 27, 2019 at 11:59 PM Sasha Levin <sashal@kernel.org> wrote:
>>
>> On Fri, Mar 22, 2019 at 09:46:18PM +0100, Arnd Bergmann wrote:
>
>> Hi Arnd,
>>
>> I've queued all but the following, which didn't look like fixes to me:
>
>Ok, thanks!
>
>> block: partition: add partition specific uevent callbacks for partition info
>> coresight: removing bind/unbind options from sysfs
>> stm class: Hide STM-specific options if STM is disabled
>> arm64: mm: mark fault_info table const
>> dma mapping : export caller to vmallocinfo
>> s390: add DEBUG_RODATA support
>> arm64: support keyctl() system call in 32-bit mode
>>
>> Any reason they should be included?
>
>The keyctl patch is probably the only one that makes
>a difference here, please include that to fix a bug in the
>compat layer of lacking keyctl access.
>
>The coresight unbind fix is a bugfix that avoids a user
>triggered kernel oops, but since unbind requires root
>permissions, it's not a critical fix.
>
>I assumed the STM Kconfig avoided a randconfig
>build issue, but I may be misremembering that,
>and I did not try it without that patch.
I'll queue them up, thanks for the explanation.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-04-01 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 20:46 [STABLE candidates] backport candidates from Allwinner kernels Arnd Bergmann
2019-03-27 15:59 ` Sasha Levin
2019-03-28 3:02 ` Arnd Bergmann
2019-04-01 14:34 ` Sasha Levin [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=20190401143432.GB2792@sasha-vm \
--to=sashal@kernel.org \
--cc=arnd@arndb.de \
--cc=stable@vger.kernel.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