From: Daniel Vetter <daniel@ffwll.ch>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
dri-devel@lists.freedesktop.org,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH 0/3] video: Remove in_interrupt() usage.
Date: Tue, 16 Feb 2021 10:09:36 +0100 [thread overview]
Message-ID: <YCuL0DR8CQXEKTjP@phenom.ffwll.local> (raw)
In-Reply-To: <YCuFli/TEl6gysTb@kroah.com>
On Tue, Feb 16, 2021 at 09:43:02AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Feb 16, 2021 at 09:35:00AM +0100, Sebastian Andrzej Siewior wrote:
> > On 2021-02-08 23:38:07 [+0100], To linux-fbdev@vger.kernel.org wrote:
> > > Folks,
> > >
> > > in the discussion about preempt count consistency across kernel
> > > configurations:
> > >
> > > https://lore.kernel.org/r/20200914204209.256266093@linutronix.de/
> > >
> > > it was concluded that the usage of in_interrupt() and related context
> > > checks should be removed from non-core code.
> > >
> > > In the long run, usage of 'preemptible, in_*irq etc.' should be banned from
> > > driver code completely.
> > >
> > > This series targets the video subsystem. The omap patches are a repost
> > > of [0], the amba-clcd is new after I received no feedback on my analysis
> > > [1].
> > >
> > > [0] https://lkml.kernel.org/r/20210127172902.145335-1-bigeasy@linutronix.de
> > > [1] https://lkml.kernel.org/r/20210127174408.ududpwfrbg3dhyxj@linutronix.de
> >
> > Could someone please apply the series? Video seems unmaintained.
>
> It's the merge window, no one can apply the series...
>
> Please resend once 5.12-rc1 is out.
drm trees are always open, to avoid the merge window blackout lol :-)
Reason I didn't merge anything is that I'm intentionally letting fbdev
hang in there, in the hopes someone picks up review&patch apply duties. It
already worked a few times but then people move on again ...
Anyway patches queued up in drm-misc-next for 5.13.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-fbdev@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Russell King <linux@armlinux.org.uk>,
dri-devel@lists.freedesktop.org,
Thomas Gleixner <tglx@linutronix.de>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] video: Remove in_interrupt() usage.
Date: Tue, 16 Feb 2021 10:09:36 +0100 [thread overview]
Message-ID: <YCuL0DR8CQXEKTjP@phenom.ffwll.local> (raw)
In-Reply-To: <YCuFli/TEl6gysTb@kroah.com>
On Tue, Feb 16, 2021 at 09:43:02AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Feb 16, 2021 at 09:35:00AM +0100, Sebastian Andrzej Siewior wrote:
> > On 2021-02-08 23:38:07 [+0100], To linux-fbdev@vger.kernel.org wrote:
> > > Folks,
> > >
> > > in the discussion about preempt count consistency across kernel
> > > configurations:
> > >
> > > https://lore.kernel.org/r/20200914204209.256266093@linutronix.de/
> > >
> > > it was concluded that the usage of in_interrupt() and related context
> > > checks should be removed from non-core code.
> > >
> > > In the long run, usage of 'preemptible, in_*irq etc.' should be banned from
> > > driver code completely.
> > >
> > > This series targets the video subsystem. The omap patches are a repost
> > > of [0], the amba-clcd is new after I received no feedback on my analysis
> > > [1].
> > >
> > > [0] https://lkml.kernel.org/r/20210127172902.145335-1-bigeasy@linutronix.de
> > > [1] https://lkml.kernel.org/r/20210127174408.ududpwfrbg3dhyxj@linutronix.de
> >
> > Could someone please apply the series? Video seems unmaintained.
>
> It's the merge window, no one can apply the series...
>
> Please resend once 5.12-rc1 is out.
drm trees are always open, to avoid the merge window blackout lol :-)
Reason I didn't merge anything is that I'm intentionally letting fbdev
hang in there, in the hopes someone picks up review&patch apply duties. It
already worked a few times but then people move on again ...
Anyway patches queued up in drm-misc-next for 5.13.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-02-16 9:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 22:38 [PATCH 0/3] video: Remove in_interrupt() usage Sebastian Andrzej Siewior
2021-02-08 22:38 ` Sebastian Andrzej Siewior
2021-02-08 22:38 ` [PATCH 1/3] video: omap: " Sebastian Andrzej Siewior
2021-02-08 22:38 ` Sebastian Andrzej Siewior
2021-02-08 22:38 ` [PATCH 2/3] video: omapfb: Remove WARN_ON(in_interrupt()) Sebastian Andrzej Siewior
2021-02-08 22:38 ` Sebastian Andrzej Siewior
2021-02-08 22:38 ` [PATCH 3/3] video: fbdev: amba-clcd: Always use msleep() for waiting Sebastian Andrzej Siewior
2021-02-08 22:38 ` Sebastian Andrzej Siewior
2021-02-16 8:35 ` [PATCH 0/3] video: Remove in_interrupt() usage Sebastian Andrzej Siewior
2021-02-16 8:35 ` Sebastian Andrzej Siewior
2021-02-16 8:43 ` Greg Kroah-Hartman
2021-02-16 8:43 ` Greg Kroah-Hartman
2021-02-16 9:09 ` Daniel Vetter [this message]
2021-02-16 9:09 ` Daniel Vetter
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=YCuL0DR8CQXEKTjP@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=bigeasy@linutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.