From: torvalds@linux-foundation.org (Linus Torvalds)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: SoC fixes
Date: Wed, 7 Nov 2018 09:17:26 -0800 [thread overview]
Message-ID: <CAHk-=whF7kBo49-BFTUc-by+HB_0qNw_=+d24TydO2mYwwsWMQ@mail.gmail.com> (raw)
In-Reply-To: <20181107171023.zoo6qox5eewy3pmk@localhost>
On Wed, Nov 7, 2018 at 9:10 AM Olof Johansson <olof@lixom.net> wrote:
>
> ARM: SoC fixes
Pulled.
> I was a bit too trigger happy to enable PREEMPT on multi_v7_defconfig,
> and it ended up regressing at least BeagleBone XM boards.
Odd. Did it hit some "may_sleep()" test in a driver that is hidden by
preempt being off? Otherwise I don't see how/why preempt should fail
in a board-specific manner..
Linus
next prev parent reply other threads:[~2018-11-07 17:17 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:10 [GIT PULL] ARM: SoC fixes Olof Johansson
2018-11-07 17:17 ` Linus Torvalds [this message]
2018-11-07 17:28 ` Olof Johansson
2018-11-08 15:49 ` Tony Lindgren
2018-11-10 18:09 ` Olof Johansson
2018-11-12 6:13 ` Corentin Labbe
2018-11-12 17:33 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2020-09-13 18:07 Olof Johansson
2020-09-13 21:57 ` pr-tracker-bot
2020-04-23 15:17 [GIT PULL] ARM: soc fixes Arnd Bergmann
2020-04-23 16:45 ` pr-tracker-bot
2020-03-08 23:58 [GIT PULL] ARM: SoC fixes Olof Johansson
2020-03-09 0:50 ` pr-tracker-bot
2020-02-15 19:49 Olof Johansson
2020-02-15 21:25 ` pr-tracker-bot
2020-01-25 21:37 Olof Johansson
2020-01-25 22:15 ` pr-tracker-bot
2020-01-17 3:00 Olof Johansson
2020-01-17 3:50 ` pr-tracker-bot
2019-12-16 21:53 Olof Johansson
2019-12-17 0:55 ` pr-tracker-bot
2019-12-06 20:53 Olof Johansson
2019-12-06 22:25 ` pr-tracker-bot
2019-11-10 18:25 Olof Johansson
2019-11-10 21:45 ` pr-tracker-bot
2019-10-25 15:38 Olof Johansson
2019-10-25 21:35 ` pr-tracker-bot
2019-10-05 22:41 Olof Johansson
2019-10-06 0:40 ` pr-tracker-bot
2019-09-29 18:34 Olof Johansson
2019-09-30 17:30 ` pr-tracker-bot
2019-07-28 6:37 Olof Johansson
2019-07-28 17:30 ` pr-tracker-bot
2019-07-05 0:22 Olof Johansson
2019-07-05 2:55 ` pr-tracker-bot
2019-06-27 2:45 Olof Johansson
2019-06-28 0:45 ` pr-tracker-bot
2019-06-18 13:52 Olof Johansson
2019-06-18 18:05 ` pr-tracker-bot
2019-04-07 22:50 Olof Johansson
2019-04-07 22:54 ` Olof Johansson
2019-04-08 0:10 ` pr-tracker-bot
2019-01-13 18:48 Olof Johansson
2019-01-13 22:50 ` pr-tracker-bot
2018-12-10 1:23 Olof Johansson
2018-12-10 20:20 ` pr-tracker-bot
2018-12-02 19:23 Olof Johansson
2018-12-02 20:30 ` pr-tracker-bot
2018-11-03 18:45 Olof Johansson
2018-11-03 19:15 ` Linus Torvalds
2018-09-30 19:23 Olof Johansson
2018-10-02 0:53 ` Greg KH
2018-09-08 17:15 Olof Johansson
2018-09-02 2:36 Olof Johansson
2018-07-21 21:13 Olof Johansson
2018-07-15 6:00 Olof Johansson
2018-07-08 16:32 Olof Johansson
2018-06-30 19:32 Olof Johansson
2018-06-27 14:38 Olof Johansson
2018-05-26 21:01 Olof Johansson
2018-05-20 1:23 Olof Johansson
2017-12-10 5:11 Olof Johansson
2017-10-04 23:05 Olof Johansson
2017-06-19 6:40 Olof Johansson
2017-06-07 4:18 Olof Johansson
2017-04-16 19:00 Olof Johansson
2017-02-08 17:07 Arnd Bergmann
2017-01-20 0:35 Olof Johansson
2016-12-09 18:01 Olof Johansson
2016-11-20 2:37 Olof Johansson
2016-11-20 2:22 Olof Johansson
2016-11-20 2:26 ` Linus Torvalds
2016-11-20 2:36 ` Olof Johansson
2016-10-29 18:54 Olof Johansson
2016-09-08 4:57 Olof Johansson
2016-08-11 21:06 Arnd Bergmann
2016-07-17 4:56 Olof Johansson
2016-04-12 23:52 Olof Johansson
2015-08-02 7:29 Olof Johansson
2015-07-19 4:16 Olof Johansson
2015-03-29 21:12 Olof Johansson
2015-02-01 17:19 Olof Johansson
2015-01-24 23:19 Olof Johansson
2015-01-18 5:57 Olof Johansson
2014-08-10 5:14 Olof Johansson
2012-10-10 21:48 Olof Johansson
2012-07-27 1:56 Olof Johansson
2012-06-30 22:51 Olof Johansson
2012-06-23 23:40 Olof Johansson
2012-06-17 5:33 Olof Johansson
2012-04-06 4:46 Olof Johansson
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-=whF7kBo49-BFTUc-by+HB_0qNw_=+d24TydO2mYwwsWMQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.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).