From: "John W. Linville" <linville@tuxdriver.com>
To: "Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>
Cc: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
Emmanuel Grumbach <egrumbach@gmail.com>,
Pavel Roskin <proski@gnu.org>,
Daniel Halperin <dhalperi@cs.washington.edu>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH wireless-3.1] iwlagn: sysfs couldn't find the priv pointer
Date: Mon, 8 Aug 2011 10:27:45 -0400 [thread overview]
Message-ID: <20110808142744.GA21103@tuxdriver.com> (raw)
In-Reply-To: <E9954878DD1FB34FAE5187FB88C58A350199604E03@orsmsx506.amr.corp.intel.com>
Sure, that sounds great.
On Sat, Aug 06, 2011 at 11:21:42PM -0700, Guy, Wey-Yi W wrote:
> I will like to combine the patches if it's ok for John.
>
> Wey
>
> -----Original Message-----
> From: Grumbach, Emmanuel
> Sent: Sunday, August 07, 2011 8:09 AM
> To: Grumbach, Emmanuel; Emmanuel Grumbach; Guy, Wey-Yi W
> Cc: Pavel Roskin; Daniel Halperin; linville@tuxdriver.com; linux-wireless@vger.kernel.org
> Subject: RE: [PATCH wireless-3.1] iwlagn: sysfs couldn't find the priv pointer
>
> FWIW, the patch below solved the problem on my system.
> Dan, please confirm you are happy with it.
>
> The bug was introduced by the patch that fixed the sysfs issue.
>
> Wey, John, do you think it would be better to revert my previous fix and send a combined patch that solves the sysfs issue and doesn't add the bug ? Or another patch on top of the buggy sysfs fix ?
>
> Thanks,
> Emmanuel
>
>
> > -----Original Message-----
> > From: Grumbach, Emmanuel
> > Sent: Saturday, August 06, 2011 10:46 PM
> > To: Emmanuel Grumbach; Guy, Wey-Yi W
> > Cc: Pavel Roskin; Daniel Halperin; linville@tuxdriver.com; linux-
> > wireless@vger.kernel.org
> > Subject: RE: [PATCH wireless-3.1] iwlagn: sysfs couldn't find the priv
> > pointer
> >
> > On top of my previous patch of course (which actually fixed the previous
> > bug, but added the one you are facing now...).
> >
> > Thanks,
> > Emmanuel
> >
> >
> > > -----Original Message-----
> > > From: Emmanuel Grumbach [mailto:egrumbach@gmail.com]
> > > Sent: Saturday, August 06, 2011 10:44 PM
> > > To: Guy, Wey-Yi W
> > > Cc: Pavel Roskin; Grumbach, Emmanuel; Daniel Halperin;
> > > linville@tuxdriver.com; linux-wireless@vger.kernel.org
> > > Subject: Re: [PATCH wireless-3.1] iwlagn: sysfs couldn't find the priv
> > > pointer
> > >
> > > Can you please try that one ?
> > > I don't have my machine near me, and don't want to crash it remotely, so
> > I
> > > didn't test it. I will test in on Sunday.
> > >
> > >
> > > diff --git a/drivers/net/wireless/iwlwifi/iwl-pci.c
> > > b/drivers/net/wireless/iwlwifi/iwl-pci.c
> > > index 69d4ec4..2fdbffa 100644
> > > --- a/drivers/net/wireless/iwlwifi/iwl-pci.c
> > > +++ b/drivers/net/wireless/iwlwifi/iwl-pci.c
> > > @@ -478,27 +478,22 @@ out_no_pci:
> > > return err;
> > > }
> > >
> > > -static void iwl_pci_down(struct iwl_bus *bus) -{
> > > - struct iwl_pci_bus *pci_bus = (struct iwl_pci_bus *) bus-
> > > >bus_specific;
> > > -
> > > - pci_disable_msi(pci_bus->pci_dev);
> > > - pci_iounmap(pci_bus->pci_dev, pci_bus->hw_base);
> > > - pci_release_regions(pci_bus->pci_dev);
> > > - pci_disable_device(pci_bus->pci_dev);
> > > - pci_set_drvdata(pci_bus->pci_dev, NULL);
> > > -
> > > - kfree(bus);
> > > -}
> > > -
> > > static void __devexit iwl_pci_remove(struct pci_dev *pdev) {
> > > struct iwl_priv *priv = pci_get_drvdata(pdev);
> > > - void *bus_specific = priv->bus->bus_specific;
> > > + struct iwl_bus *bus = priv->bus;
> > > + struct iwl_pci_bus *pci_bus = IWL_BUS_GET_PCI_BUS(bus);
> > > + struct pci_dev *pci_dev = IWL_BUS_GET_PCI_DEV(bus);
> > >
> > > iwl_remove(priv);
> > >
> > > - iwl_pci_down(bus_specific);
> > > + pci_disable_msi(pci_dev);
> > > + pci_iounmap(pci_dev, pci_bus->hw_base);
> > > + pci_release_regions(pci_dev);
> > > + pci_disable_device(pci_dev);
> > > + pci_set_drvdata(pci_dev, NULL);
> > > +
> > > + kfree(bus);
> > > }
> > >
> > > #ifdef CONFIG_PM
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-08-08 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 19:46 [PATCH wireless-3.1] iwlagn: sysfs couldn't find the priv pointer Wey-Yi Guy
2011-08-02 3:53 ` Daniel Halperin
2011-08-02 5:50 ` Grumbach, Emmanuel
2011-08-02 6:39 ` Daniel Halperin
2011-08-04 20:55 ` Daniel Halperin
2011-08-04 23:15 ` Guy, Wey-Yi
2011-08-06 2:50 ` Pavel Roskin
2011-08-06 18:17 ` Guy, Wey-Yi W
2011-08-06 19:43 ` Emmanuel Grumbach
2011-08-06 19:45 ` Grumbach, Emmanuel
2011-08-07 5:09 ` Grumbach, Emmanuel
2011-08-07 6:21 ` Guy, Wey-Yi W
2011-08-08 14:27 ` John W. Linville [this message]
2011-08-08 16:19 ` Grumbach, Emmanuel
2011-08-09 14:38 ` Mohammed Shafi
2011-08-09 19:23 ` Grumbach, Emmanuel
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=20110808142744.GA21103@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dhalperi@cs.washington.edu \
--cc=egrumbach@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
--cc=wey-yi.w.guy@intel.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 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).