From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-parisc@vger.kernel.org, Kyle McMartin <kyle@redhat.com>,
"James E.J. Bottomley" <jejb@parisc-linux.org>
Subject: Re: [patch 0/8] parisc: Convert to new irq_chip functions
Date: Mon, 07 Feb 2011 11:36:08 -0600 [thread overview]
Message-ID: <1297100168.8577.42.camel@mulgrave.site> (raw)
In-Reply-To: <alpine.LFD.2.00.1102071744590.31804@localhost6.localdomain6>
On Mon, 2011-02-07 at 17:53 +0100, Thomas Gleixner wrote:
> On Mon, 7 Feb 2011, James Bottomley wrote:
>
> > On Sun, 2011-02-06 at 20:45 +0000, Thomas Gleixner wrote:
> > > The following series converts parisc to the new irq_chip functions and
> > > sets GENERIC_HARDIRQS_NO_DEPRECATED. Compile tested only.
> >
> > You don't really need one patch per file in the irq function changes do
> > you? ... unless you're being rechristened Joe Perches ...
>
> WTF ? It's damn easier to review and make sure that you did not miss
> anything that way. That's not a 100 patches series doing spelling
> fixes or other trivial shite.
>
> Feel free to bulk apply them, I don't care. Next time I'm going to
> ignore parisc and just mark it broken, then you can fix it up yourself
> as you like.
sorry, outgoing humour filter stopped picking up .de addresses for some
reason ... I've fixed it ...
> > I can't get the last patch to apply ... it looks like there are lots of
> > other Kconfig changes besides the one liner it does; what's missing?
>
> Tested it against -next as well, had to fix up crap there and sent out
> that queue instead the one against linus.
Actually, you'll be pleased to hear this was entirely my fault: The irq
branch of the parisc tree wasn't where I thought it was (it was about a
month behind.
There's some problem in arch/parisc/kernel.c it's giving me undefined
references to irq (oh and some easily fixed compile issues). I'll see
if I can sort it out and get back to you.
> Yours grumpy,
Well, I'd like to be happy ... but I guess after the git cockup I'll
have to settle for dopey.
James
next prev parent reply other threads:[~2011-02-07 17:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 20:45 [patch 0/8] parisc: Convert to new irq_chip functions Thomas Gleixner
2011-02-06 20:45 ` [patch 1/8] parisc: Convert cpu irq_chip to new functions Thomas Gleixner
2011-02-06 20:45 ` [patch 2/8] parisc: Convert dino " Thomas Gleixner
2011-02-06 20:45 ` [patch 3/8] parisc: Convert eisa " Thomas Gleixner
2011-02-06 20:45 ` [patch 4/8] parisc: Convert gsc " Thomas Gleixner
2011-02-06 20:46 ` [patch 5/8] parisc: Convert iosapic " Thomas Gleixner
2011-02-06 20:46 ` [patch 6/8] parisc: Convert superio " Thomas Gleixner
2011-02-06 20:46 ` [patch 7/8] parisc: Prepare show_interrupts for GENERIC_HARDIRQS_NO_DEPRECATED Thomas Gleixner
2011-02-06 20:46 ` [patch 8/8] parisc: Select GENERIC_HARDIRQS_NO_DEPRECATED Thomas Gleixner
2011-02-07 16:02 ` [patch 0/8] parisc: Convert to new irq_chip functions James Bottomley
2011-02-07 16:53 ` Thomas Gleixner
2011-02-07 17:36 ` James Bottomley [this message]
2011-02-07 18:28 ` Thomas Gleixner
2011-02-07 21:26 ` James Bottomley
2011-02-08 0:32 ` James Bottomley
2011-02-08 14:25 ` Thomas Gleixner
2011-02-08 14:37 ` Thomas Gleixner
2011-02-08 16:53 ` James Bottomley
2011-02-08 17:42 ` Thomas Gleixner
2011-02-08 17:45 ` James Bottomley
2011-02-08 21:59 ` Thomas Gleixner
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=1297100168.8577.42.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=jejb@parisc-linux.org \
--cc=kyle@redhat.com \
--cc=linux-parisc@vger.kernel.org \
--cc=tglx@linutronix.de \
/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