All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-omap@vger.kernel.org
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH 0/2] video: omap*: Remove in_interrupt() usage.
Date: Wed, 27 Jan 2021 18:29:00 +0100	[thread overview]
Message-ID: <20210127172902.145335-1-bigeasy@linutronix.de> (raw)

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.

Sebastian


WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-omap@vger.kernel.org
Cc: linux-fbdev@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	dri-devel@lists.freedesktop.org
Subject: [PATCH 0/2] video: omap*: Remove in_interrupt() usage.
Date: Wed, 27 Jan 2021 18:29:00 +0100	[thread overview]
Message-ID: <20210127172902.145335-1-bigeasy@linutronix.de> (raw)

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.

Sebastian

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2021-01-27 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 17:29 Sebastian Andrzej Siewior [this message]
2021-01-27 17:29 ` [PATCH 0/2] video: omap*: Remove in_interrupt() usage Sebastian Andrzej Siewior
2021-01-27 17:29 ` [PATCH 1/2] video: omap: " Sebastian Andrzej Siewior
2021-01-27 17:29   ` Sebastian Andrzej Siewior
2021-01-27 17:29 ` [PATCH 2/2] video: omapfb: Remove WARN_ON(in_interrupt()) Sebastian Andrzej Siewior
2021-01-27 17:29   ` Sebastian Andrzej Siewior

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=20210127172902.145335-1-bigeasy@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --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.