From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux_omap_open_source <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: Convert irq flags SA_* to IRQF_*
Date: Wed, 31 Jan 2007 11:16:19 -0800 [thread overview]
Message-ID: <20070131191619.GN27224@atomide.com> (raw)
In-Reply-To: <45BDEC2B.3000601@googlemail.com>
Hi,
* Dirk Behme <dirk.behme@googlemail.com> [070129 04:45]:
> Convert remaining interrupt flags SA_* to IRQF_* style.
>
> Documentation/feature-removal-schedule.txt tells us:
>
> What: Interrupt only SA_* flags
> When: Januar 2007
> Why: The interrupt related SA_* flags are replaced by
> IRQF_* to move them
> out of the signal namespace.
>
> and in linux/interrupt.h regarding SA_* we find
>
> "Migration helpers. Scheduled for removal in 1/2007 Do not
> use for new code !"
>
> Current -rt patches remove SA_* already, so seems to be time
> to convert all OMAP stuff.
>
> In attachment there are 12 patches for this (feel free to
> regroup them):
>
> 01 plat-omap directory conversion
> 02 mach-omap1 directory conversion
> (Note: mach-omap2 has no SA_*)
> 03 ads7846 conversion
> 04 omap-ts directory conversion
> 05 i2c-chips directory conversion
> 06 rtc-omap conversion
> 07 tsc2102 conversion
> 08 musbhsdma conversion
> 09 tahvo-usb conversion
> 10 omap-rtc conversion
> 11 innovator-ps2 conversion
> 12 omap16xxcam conversion
Thanks, I've pushed them in two parts and added the omap core changes to
the linux-omap-upstream tree too.
Regards,
Tony
prev parent reply other threads:[~2007-01-31 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 12:44 [PATCH] ARM: OMAP: Convert irq flags SA_* to IRQF_* Dirk Behme
2007-01-31 19:16 ` Tony Lindgren [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=20070131191619.GN27224@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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.