public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
	"chirag.kantharia@hp.com" <chirag.kantharia@hp.com>
Cc: ISS StorageDev <iss_storagedev@hp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpqarray: remove deprecated IRQF_DISABLED
Date: Wed, 01 Oct 2014 12:09:12 +0200	[thread overview]
Message-ID: <542BD2C8.7030304@free-electrons.com> (raw)
In-Reply-To: <48275AD710FCA34184C2B6186B4016B32D14B4D5@G6W2491.americas.hpqcorp.net>

Hi Mike,

On 10/15/2013 12:17 AM, Miller, Mike (OS Dev) wrote:
>
>> -----Original Message-----
>> From: Michael Opdenacker [mailto:michael.opdenacker@free-
>> electrons.com]
>> Sent: Friday, October 11, 2013 11:15 PM
>> To: chirag.kantharia@hp.com
>> Cc: ISS StorageDev; linux-kernel@vger.kernel.org; Michael Opdenacker
>> Subject: [PATCH] cpqarray: remove deprecated IRQF_DISABLED
>>
>> This patch proposes to remove the use of the IRQF_DISABLED flag
>>
>> It's a NOOP since 2.6.35 and it will be removed one day.
> I plan to send a patch soon to remove cpqarray completely.
>
> -- mikem

Any news? Would you like me to take care of this patch if you don't have
time? It would be with pleasure...

Michael.


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


      parent reply	other threads:[~2014-10-01 10:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-12  4:15 [PATCH] cpqarray: remove deprecated IRQF_DISABLED Michael Opdenacker
2013-10-14 22:17 ` Miller, Mike (OS Dev)
2014-03-04 21:23   ` Michael Opdenacker
2014-10-01 10:09   ` Michael Opdenacker [this message]

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=542BD2C8.7030304@free-electrons.com \
    --to=michael.opdenacker@free-electrons.com \
    --cc=Mike.Miller@hp.com \
    --cc=chirag.kantharia@hp.com \
    --cc=iss_storagedev@hp.com \
    --cc=linux-kernel@vger.kernel.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