From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [ARM] Kirkwood: Prevent kernel from crashing if PCIe bridge is present
Date: Fri, 13 Nov 2009 08:50:09 +0100 [thread overview]
Message-ID: <200911130850.09903.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <20091112205528.GA11304@n2100.arm.linux.org.uk>
Am Donnerstag 12 November 2009 21:55:28 schrieb Russell King - ARM Linux:
> On Thu, Nov 12, 2009 at 03:19:42PM +0100, Dieter Kiermaier wrote:
> > diff --git a/arch/arm/mach-kirkwood/openrd_base-setup.c b/arch/arm/mach-kirkwood/openrd_base-setup.c
> > index 77617c7..9e57326 100644
> > --- a/arch/arm/mach-kirkwood/openrd_base-setup.c
> > +++ b/arch/arm/mach-kirkwood/openrd_base-setup.c
> > @@ -14,6 +14,7 @@
> > #include <linux/mtd/partitions.h>
> > #include <linux/ata_platform.h>
> > #include <linux/mv643xx_eth.h>
> > +#include <asm/io.h>
>
> linux/io.h please (and please ensure future patches similarly use that
> header rather than asm/io.h). checkpatch will tell you this.
Sorry for my stupid question but was is the difference?
Is it that asm/* provides "architecture specific headers and linux/*
abstract this on level more from the hardware?
I've taken it form LDD (thanks Alessandro!) but never thought about it.
>
> > #include <asm/mach-types.h>
> > #include <asm/mach/arch.h>
> > #include <mach/kirkwood.h>
> > @@ -76,9 +77,19 @@ static void __init openrd_base_init(void)
> >
> > static int __init openrd_base_pci_init(void)
> > {
> > + u32 cpu_config_reg;
> > + void __iomem *base;
> > + base = ioremap(0xf1020100, 4);
> > + if (base)
> > + {
>
> checkpatch will also tell you to put the opening brace on the previous line.
>
Something new I learned. I've read much docs but everyday there is something new
like checkpatch.pl - sorry for missing that.
Many thanks for commenting,
Dieter
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2009-11-13 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 14:19 [PATCH] [ARM] Kirkwood: Prevent kernel from crashing if PCIe bridge is present Dieter Kiermaier
2009-11-12 15:42 ` [PATCH] [ARM] Kirkwood: Prevent kernel from crashing if PCIe bridge?is present Alexander Clouter
2009-11-12 17:02 ` Dieter Kiermaier
2009-11-12 18:52 ` [PATCH] [ARM] Kirkwood: Prevent kernel from crashing if PCIe?bridge?is present Alexander Clouter
2009-11-13 7:50 ` [PATCH] [ARM] Kirkwood: Prevent kernel from crashing if PCIe bridge?is present Simon Kagstrom
2009-11-12 19:37 ` [PATCH] [ARM] Kirkwood: Prevent kernel from crashing if PCIe bridge is present Lennert Buytenhek
2009-11-13 7:26 ` Dieter Kiermaier
2009-11-12 20:55 ` Russell King - ARM Linux
2009-11-13 7:50 ` Dieter Kiermaier [this message]
2009-11-13 23:19 ` Russell King - ARM Linux
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=200911130850.09903.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.de \
--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 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.