From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Kurt Van Dijck <kurt.van.dijck@eia.be>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [PATCH v3] can: fix sja1000 pre_irq/post_irq handling
Date: Wed, 20 Nov 2013 07:33:21 +0100 [thread overview]
Message-ID: <528C57B1.8000006@hartkopp.net> (raw)
In-Reply-To: <20131118211557.GA3084@vandijck-laurijssen.be>
On 18.11.2013 22:15, Kurt Van Dijck wrote:
> Oliver,
>
> On Mon, Nov 18, 2013 at 02:01:14PM +0100, Oliver Hartkopp wrote:
>> The SJA1000 driver provides optional function pointers to handle specific
>> hardware setups at interrupt time.
>>
>> This patch fixes the issue that the sja1000_interrupt() function may have
>> returned IRQ_NONE without processing the post_irq function. Additionally
>> an introduced and documented return value from the pre_irq function is
>> checked to skip the entire interrupt handling on pre_irq function errors.
>
> You combine fixes and new features in 1 patch.
You are right. The return value is not really a fix.
> Both are tried in addressing the problem with peak_pci,
> but that doesn't make them depend on each other.
It mainly isn't related to peak_pci. It just emerged in the code review when
investigating an issue with the peak_pci driver.
I have no strong opinion about splitting up the patch.
Regards,
Oliver
next prev parent reply other threads:[~2013-11-20 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 13:01 [PATCH v3] can: fix sja1000 pre_irq/post_irq handling Oliver Hartkopp
2013-11-18 19:38 ` Wolfgang Grandegger
2013-11-18 21:15 ` Kurt Van Dijck
2013-11-20 6:33 ` Oliver Hartkopp [this message]
2013-11-20 9:28 ` Kurt Van Dijck
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=528C57B1.8000006@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=kurt.van.dijck@eia.be \
--cc=linux-can@vger.kernel.org \
--cc=wg@grandegger.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.