All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/mpc52xx: Properly update irq_desc when set_type() is called.
Date: Thu, 08 Jan 2009 08:40:01 -0600	[thread overview]
Message-ID: <49661041.2010302@genesi-usa.com> (raw)
In-Reply-To: <fa686aa40901072053v7803c6afp206e0572a6c79eda@mail.gmail.com>

Grant Likely wrote:
> On Wed, Jan 7, 2009 at 8:51 PM, Matt Sealey <matt@genesi-usa.com> wrote:
>> Grant Likely wrote:
>>> From: Grant Likely <grant.likely@secretlab.ca>
>>>
>>> The MPC5200 PIC driver doesn't correctly update the .status field of
>>> the irq_desc structure when the set_type hook is called.  This patch
>>> adds the required code.
>>>
>>> Also cleans up the external IRQ typename field to be something easier
>>> to read (very minor).
>>>
>>> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
>> Hi Grant,
>>
>> What does this affect?
> 
> cat /proc/interrupts

Ah so, completely cosmetic in the end. I was worried I'd have to build a 
new kernel for a second.. :D

-- Matt

  reply	other threads:[~2009-01-08 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 19:25 [PATCH] powerpc/mpc52xx: Properly update irq_desc when set_type() is called Grant Likely
2009-01-08  3:51 ` Matt Sealey
2009-01-08  4:53   ` Grant Likely
2009-01-08 14:40     ` Matt Sealey [this message]
2009-01-09 21:02       ` Grant Likely
2009-01-10 17:19         ` Matt Sealey
     [not found]           ` <fa686aa40901101425y5ff97f9fgabaa8aa6f0e974c7@mail.gmail.com>
     [not found]             ` <496AB287.5050508@genesi-usa.com>
     [not found]               ` <fa686aa40901112156i69611682icf9ef3a7702fd862@mail.gmail.com>
     [not found]                 ` <496C907B.2060609@genesi-usa.com>
     [not found]                   ` <fa686aa40901132203p71bbd6eem2b8173dc8a4e5fc8@mail.gmail.com>
2009-01-14  6:03                     ` Fwd: " Grant Likely

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=49661041.2010302@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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.