All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: m.chehab@samsung.com, gregkh@linuxfoundation.org,
	prabhakar.csengg@gmail.com, yongjun_wei@trendmicro.com.cn,
	sakari.ailus@iki.fi, hans.verkuil@cisco.com,
	linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RESEND] [media] davinci: vpfe: remove deprecated IRQF_DISABLED
Date: Thu, 20 Feb 2014 14:17:09 +0100	[thread overview]
Message-ID: <53060055.2010408@free-electrons.com> (raw)
In-Reply-To: <4210530.AR5GZgidVz@avalon>

Hi Laurent,

On 02/20/2014 12:36 PM, Laurent Pinchart wrote:
> Hi Michael,
>
> What's the status of this patch ? Do expect Prabhakar to pick it up, or do you 
> plan to push all your IRQF_DISABLED removal patches in one go ?
It's true a good number of my patches haven't been picked up yet, even
after multiple resends.

I was planning to ask the community tomorrow about what to do to finally
get rid of IRQF_DISABLED. Effectively, pushing all the remaining changes
in one go (or removing the definition of IRQF_DISABLED) may be the final
solution.

I hope to be able to answer your question by the end of the week.

Thanks for getting back to me about this!

Michael.

-- 
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098


  reply	other threads:[~2014-02-20 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06  6:23 [PATCH] [media] davinci: vpfe: remove deprecated IRQF_DISABLED Michael Opdenacker
2013-10-07  6:12 ` Prabhakar Lad
2013-12-09 10:16   ` [PATCH][RESEND] " Michael Opdenacker
2014-02-20 11:36     ` Laurent Pinchart
2014-02-20 13:17       ` Michael Opdenacker [this message]
2014-02-20 13:30         ` Laurent Pinchart
2014-02-24  5:31         ` Prabhakar Lad
2014-02-25  6:02           ` Prabhakar Lad
2014-02-25  7:58             ` Michael Opdenacker

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=53060055.2010408@free-electrons.com \
    --to=michael.opdenacker@free-electrons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hans.verkuil@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=sakari.ailus@iki.fi \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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.