All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Scott Wood <scottwood@freescale.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] fs_enet: Don't call phy_mii_ioctl() in atomic context.
Date: Wed, 20 Feb 2008 11:50:51 -0500	[thread overview]
Message-ID: <47BC5A6B.1030304@pobox.com> (raw)
In-Reply-To: <20080215210804.GA14468@loki.buserror.net>

Scott Wood wrote:
> The lock acquisition in fs_ioctl() does not appear to actually be necessary,
> and thus is simply removed.
> 
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> This fixes the following bug:
> http://ozlabs.org/pipermail/linuxppc-dev/2008-February/051564.html
> 
>  drivers/net/fs_enet/fs_enet-main.c |    7 +------
>  1 files changed, 1 insertions(+), 6 deletions(-)

applied

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: Scott Wood <scottwood@freescale.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Rune Torgersen <runet@innovsys.com>
Subject: Re: [PATCH] fs_enet: Don't call phy_mii_ioctl() in atomic context.
Date: Wed, 20 Feb 2008 11:50:51 -0500	[thread overview]
Message-ID: <47BC5A6B.1030304@pobox.com> (raw)
In-Reply-To: <20080215210804.GA14468@loki.buserror.net>

Scott Wood wrote:
> The lock acquisition in fs_ioctl() does not appear to actually be necessary,
> and thus is simply removed.
> 
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> This fixes the following bug:
> http://ozlabs.org/pipermail/linuxppc-dev/2008-February/051564.html
> 
>  drivers/net/fs_enet/fs_enet-main.c |    7 +------
>  1 files changed, 1 insertions(+), 6 deletions(-)

applied



  parent reply	other threads:[~2008-02-20 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 21:08 [PATCH] fs_enet: Don't call phy_mii_ioctl() in atomic context Scott Wood
2008-02-15 21:08 ` Scott Wood
2008-02-15 21:47 ` Rune Torgersen
2008-02-15 21:47   ` Rune Torgersen
2008-02-20 16:50 ` Jeff Garzik [this message]
2008-02-20 16:50   ` Jeff Garzik

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=47BC5A6B.1030304@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=scottwood@freescale.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.