From: Dmitry Torokhov <dtor@vmware.com>
To: pv-drivers@vmware.com
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [Pv-drivers] [PATCH -next] vmxnet3: use dev_dbg, fix build for CONFIG_BLOCK=n
Date: Thu, 15 Oct 2009 15:53:17 -0700 [thread overview]
Message-ID: <200910151553.17203.dtor@vmware.com> (raw)
In-Reply-To: <200910151547.48247.dtor@vmware.com>
On Thursday 15 October 2009 03:47:48 pm Dmitry Torokhov wrote:
> Hi Randy,
>
> On Thursday 15 October 2009 03:42:49 pm Randy Dunlap wrote:
> > Bhavesh Davda wrote:
> > > Who ever compiles with CONFIG_BLOCK=n? Just kidding...
> >
> > or why does networking need CONFIG_BLOCK at all? ;)
> >
> > > Thanks again for making this change! Ship it!
> >
> > So could I have used adapter->netdev->dev or adapter->pdev->dev ?
> > either of them? are they the same?
>
> They are the same.
>
Hmm.. I take this back, adapter->netdev->dev.parent == adapter->pdev->dev.
--
Dmitry
next prev parent reply other threads:[~2009-10-15 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091015152538.74a1cb15.sfr@canb.auug.org.au>
2009-10-15 22:29 ` [PATCH -next] vmxnet3: use dev_dbg, fix build for CONFIG_BLOCK=n Randy Dunlap
2009-10-15 22:35 ` [Pv-drivers] " Bhavesh Davda
2009-10-15 22:42 ` Randy Dunlap
2009-10-15 22:47 ` Dmitry Torokhov
2009-10-15 22:53 ` Dmitry Torokhov [this message]
2009-10-15 22:53 ` Bhavesh Davda
2009-10-17 0:54 ` David Miller
2009-10-15 22:37 ` Shreyas Bhatewara
[not found] ` <20091015104852.GA6740@linux.vnet.ibm.com>
[not found] ` <4AD6CD940200005A00056857@sinclair.provo.novell.com>
2009-10-15 17:39 ` [BUILD-FAILURE] next-20091015 - vbus_enet driver breaks with allmodconfig Gregory Haskins
2009-10-15 18:42 ` Randy Dunlap
2009-10-15 18:54 ` Randy Dunlap
2009-10-15 22:25 ` Gregory Haskins
2009-11-06 17:38 ` Randy Dunlap
2009-11-06 19:02 ` Gregory Haskins
2009-10-16 0:29 ` Gregory Haskins
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=200910151553.17203.dtor@vmware.com \
--to=dtor@vmware.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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).