From: "Matt Carlson" <mcarlson@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: mcarlson@broadcom.com, netdev@vger.kernel.org,
mchan@broadcom.com, benli@broadcom.com, andy@greyhouse.net
Subject: Re: [PATCH 8/8] tg3: Update version to 3.93
Date: Tue, 27 May 2008 10:58:08 -0700 [thread overview]
Message-ID: <20080527175808.GA31979@localdomain> (raw)
In-Reply-To: <20080525.235311.235732094.davem@davemloft.net>
On Sun, May 25, 2008 at 11:53:11PM -0700, David Miller wrote:
>
> Matt, don't we need a PHYLIB dependency or select statement for the
> tg3 driver option in drivers/net/Kconfig now?
Indeed, you are correct. I'll submit a follow-on patch in another
email.
next prev parent reply other threads:[~2008-05-27 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 2:57 [PATCH 8/8] tg3: Update version to 3.93 Matt Carlson
2008-05-26 6:51 ` David Miller
2008-05-26 6:53 ` David Miller
2008-05-27 17:58 ` Matt Carlson [this message]
2008-05-27 20:02 ` David Miller
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=20080527175808.GA31979@localdomain \
--to=mcarlson@broadcom.com \
--cc=andy@greyhouse.net \
--cc=benli@broadcom.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.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).