Skip to content

Upstream: Patch 5/14: check if we need to use spin_lock_irqsave #422

Closed
Closed
Upstream: Patch 5/14: check if we need to use spin_lock_irqsave#422
Assignees
RanderWang

Description

@plbossart
plbossart
opened on Dec 12, 2018

We need clear explanations as to why we are using spin_lock_irqsave(). Takashi mentions in his feedback we can use spin_lock_irq().
I've asked for this multiple times, now it's a higher power asking...

Activity

  1. plbossart
    assigned
    ranj063
    ,
    keyonjie
    ,
    lgirdwood
    ,
    xiulipan
    and
    RanderWang
    on Dec 12, 2018
  2. jocelyn-li
    unassigned
    ranj063
    ,
    keyonjie
    ,
    lgirdwood
    and
    xiulipan
    on Dec 13, 2018

  3. RanderWang commented on Dec 13, 2018

    @RanderWang
    RanderWang
    on Dec 13, 2018

    it is a fix: #434

    We discussed this issue before and got a conclusion: spin_lock_irq should be applied(#279)

  4. plbossart
    closed this as completedon Dec 18, 2018
  5. fredoh9
    added a commit that references this issue on Jun 17, 2019

    drm/i915/gvt: Check if cur_pt_type is valid

    27348cc
  6. oder-chiou
    added a commit that references this issue on May 5, 2026

    xfs: fix BUG_ON in xfs_getbmap()

    8ee81ed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions