linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 01/10] rtc: sa1100: include mach/irqs.h instead of asm/irq.h
Date: Fri, 13 Jan 2012 10:58:01 -0600	[thread overview]
Message-ID: <4F106299.8050306@gmail.com> (raw)
In-Reply-To: <20120113164336.GA1068@n2100.arm.linux.org.uk>

On 01/13/2012 10:43 AM, Russell King - ARM Linux wrote:
> On Fri, Jan 13, 2012 at 10:34:02AM -0600, Rob Herring wrote:
>> From: Rob Herring <rob.herring@calxeda.com>
>>
>> Since asm/irq.h may not include mach/irqs.h, include mach/irqs.h directly.
> 
> Rather than doing this, we should be eliminating the need for these
> old drivers to include mach/irqs.h at all.
> 
> Adding the resources to the platform device, and then using at least
> the IRQ resource(s) would be a definite step forward (and a relatively
> easy one to do.)
> 

Well, this has just happened in 3.3. So I can now drop this one I think.

Rob

>>
>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>> ---
>>  drivers/rtc/rtc-sa1100.c |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/rtc/rtc-sa1100.c b/drivers/rtc/rtc-sa1100.c
>> index 4595d3e..144fa06 100644
>> --- a/drivers/rtc/rtc-sa1100.c
>> +++ b/drivers/rtc/rtc-sa1100.c
>> @@ -33,7 +33,7 @@
>>  #include <linux/io.h>
>>  
>>  #include <mach/hardware.h>
>> -#include <asm/irq.h>
>> +#include <mach/irqs.h>
>>  
>>  #define RTC_DEF_DIVIDER		(32768 - 1)
>>  #define RTC_DEF_TRIM		0
>> -- 
>> 1.7.5.4
>>

  reply	other threads:[~2012-01-13 16:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 16:34 [RFC PATCH 00/10] Make mach/irqs.h optional Rob Herring
2012-01-13 16:34 ` [RFC PATCH 01/10] rtc: sa1100: include mach/irqs.h instead of asm/irq.h Rob Herring
2012-01-13 16:43   ` Russell King - ARM Linux
2012-01-13 16:58     ` Rob Herring [this message]
2012-01-13 20:46       ` Nicolas Pitre
2012-01-13 21:45         ` Russell King - ARM Linux
2012-01-13 22:26           ` Nicolas Pitre
2012-01-13 23:21         ` Rob Herring
2012-01-13 23:51           ` Nicolas Pitre
2012-01-13 16:34 ` [RFC PATCH 02/10] sound: pxa2xx-ac97: include mach/irqs.h directly Rob Herring
2012-01-13 16:34 ` [RFC PATCH 03/10] ARM: mc146818rtc: remove unnecessary include of mach/irqs.h Rob Herring
2012-01-13 16:52   ` Russell King - ARM Linux
2012-01-13 16:34 ` [RFC PATCH 04/10] ARM: it8152: explicitly include mach/irqs.h Rob Herring
2012-01-13 22:02   ` Rob Herring
2012-01-13 22:36     ` Nicolas Pitre
2012-01-13 16:34 ` [RFC PATCH 05/10] sh: intc: remove dependency on NR_IRQS Rob Herring
2012-01-17  1:54   ` Nobuhiro Iwamatsu
2012-01-17  2:37     ` Rob Herring
2012-01-17  5:09       ` Nobuhiro Iwamatsu
2012-01-17 16:24         ` Rob Herring
2012-01-19  3:44           ` Nobuhiro Iwamatsu
2012-01-13 16:34 ` [RFC PATCH 06/10] ARM: mmp: remove NR_IRQS Rob Herring
2012-01-13 20:30   ` Nicolas Pitre
2012-01-13 16:34 ` [RFC PATCH 07/10] ARM: pxa: " Rob Herring
2012-01-13 16:34 ` [RFC PATCH 08/10] ARM: shmobile: " Rob Herring
2012-01-13 16:34 ` [RFC PATCH 09/10] ARM: only include mach/irqs.h for !SPARSE_IRQ Rob Herring
2012-01-13 16:34 ` [RFC PATCH 10/10] ARM: highbank: select SPARSE_IRQ and remove irqs.h Rob Herring
2012-01-13 17:42 ` [RFC PATCH 00/10] Make mach/irqs.h optional Jamie Iles

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=4F106299.8050306@gmail.com \
    --to=robherring2@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).