netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Sebastian Siewior <bigeasy@linutronix.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	netdev@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH 0/5] fixup locking on m68knommu fec
Date: Thu, 03 Apr 2008 16:54:06 +1000	[thread overview]
Message-ID: <47F47F0E.9030803@snapgear.com> (raw)
In-Reply-To: <20080402204417.597098190@linutronix.de>

Hi Sebastian,

Sebastian Siewior wrote:
> This series basically fixes my locking problem. We have here:
> #1 the old one which removes some undefined vars.
> #2 cleans the file with lident. I had trouble reading the code...
> #3 type def a function pointer so we don't have the long defines
>    and move the callback after releasing the lock.
> #4 This one fixes the locking I guess. My mcf5235 did not race anymore
>    after that one. I saw 0a504779d while forming the patch so I guess
>    we could revert that one, Greg?

Yes, certainly we can.
I'd like to do some testing on this as well :-)


> #5 removes the registration of interrupt handlers & enabling interrupt
>    sources that are not handled. I stepped into this after I thought that
>    it is over :) Greg, Should we also remove that part where we enable
>    the irq controller (I though request_irq() is doing that).

Currently it doesn't. The main sticking point is what to do
with the hardware based priority setting logic. We don't really
rely on it, but they need to be set to sane values.

Need to expand the interrupt controller setup code some more
before we can take that out.

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
Secure Computing Corporation                PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  parent reply	other threads:[~2008-04-03  6:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 20:58 [PATCH 0/5] fixup locking on m68knommu fec Sebastian Siewior
2008-04-02 20:58 ` [PATCH 3/5] m68knommu: fec typedef a function Sebastian Siewior
2008-04-02 20:58 ` [PATCH 5/5] m68knommu: dont allocate unused interrupts Sebastian Siewior
2008-04-03  6:47   ` Greg Ungerer
2008-04-03  7:43     ` Sebastian Siewior
2008-04-03  9:34       ` Greg Ungerer
2008-04-02 20:58 ` [PATCH 2/5] m68knommu: fec: small coding style cleanup Sebastian Siewior
2008-04-02 20:58 ` [PATCH 4/5] m68knommu: fec fixup locking Sebastian Siewior
2008-04-02 20:58 ` [PATCH 1/5] fec: kill warnings Sebastian Siewior
2008-04-03  6:30   ` Greg Ungerer
2008-04-03  7:44     ` Sebastian Siewior
2008-04-03  9:30       ` Greg Ungerer
2008-04-03  6:54 ` Greg Ungerer [this message]
2008-04-03  7:52   ` [PATCH 0/5] fixup locking on m68knommu fec Sebastian Siewior

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=47F47F0E.9030803@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=bigeasy@linutronix.de \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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).