From: David Miller <davem@davemloft.net>
To: bhavesh@vmware.com
Cc: randy.dunlap@oracle.com, sfr@canb.auug.org.au,
pv-drivers@vmware.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [Pv-drivers] [PATCH -next] vmxnet3: use dev_dbg, fix build for CONFIG_BLOCK=n
Date: Fri, 16 Oct 2009 17:54:13 -0700 (PDT) [thread overview]
Message-ID: <20091016.175413.236830274.davem@davemloft.net> (raw)
In-Reply-To: <8B1F619C9F5F454E81D90D3C161698D7017DD56435@EXCH-MBX-3.vmware.com>
From: Bhavesh Davda <bhavesh@vmware.com>
Date: Thu, 15 Oct 2009 15:35:02 -0700
> Who ever compiles with CONFIG_BLOCK=n? Just kidding...
Who ever uses block layer debugging facilities in a networking
driver?
> Thanks again for making this change! Ship it!
>
> Signed-off-by: Bhavesh Davda <bhavesh@vmware.com>
Applied, thanks everyone.
next prev parent reply other threads:[~2009-10-17 0:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 4:25 linux-next: Tree for October 15 Stephen Rothwell
2009-10-15 10:48 ` [BUILD-FAILURE] next-20091015 - vbus_enet driver breaks with allmodconfig Kamalesh Babulal
2009-10-15 11:21 ` Gregory Haskins
2009-10-15 11:21 ` Gregory Haskins
2009-10-15 17:39 ` 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-11-06 19:02 ` Gregory Haskins
2009-10-16 0:29 ` Gregory Haskins
2009-10-15 19:17 ` linux-next: Tree for October 15 (i7core_edac) Randy Dunlap
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
2009-10-15 22:53 ` Dmitry Torokhov
2009-10-15 22:53 ` Bhavesh Davda
2009-10-17 0:54 ` David Miller [this message]
2009-10-15 22:37 ` Shreyas Bhatewara
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=20091016.175413.236830274.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhavesh@vmware.com \
--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 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.