From: "Matt Carlson" <mcarlson@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Michael Chan" <mchan@broadcom.com>,
"Benjamin Li" <benli@broadcom.com>,
"andy@greyhouse.net" <andy@greyhouse.net>
Subject: Re: [PATCH 1/8] tg3: Fix SEEPROM accesses
Date: Mon, 20 Apr 2009 15:02:10 -0700 [thread overview]
Message-ID: <20090420220210.GB7358@xw6200.broadcom.net> (raw)
In-Reply-To: <20090420.145328.227301985.davem@davemloft.net>
On Mon, Apr 20, 2009 at 02:53:28PM -0700, David Miller wrote:
> From: "Matt Carlson" <mcarlson@broadcom.com>
> Date: Mon, 20 Apr 2009 09:52:49 -0700
>
> > The recent NVRAM patches sanitized how the driver deals with NVRAM
> > data, but they failed to bring the SEEPROM interfaces inline with
> > the new strategy. This patch brings the SEEPROM interfaces up to date.
> > This patch also reverts commit 0d489ffb76de0fe804cf06a9d4d11fa7342d74b9.
> >
> > Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
> > Signed-off-by: Michael Chan <mchan@broadcom.com>
> > Tested-by: Robin Holt <holt@sgi.com>
> > Tested-by: James Bottomley <james.bottomley@HansenPartnership.com>
>
> Applied, thanks.
>
> But please provide a text string header line from the commit message
> of commits you reference by SHA1 ID, I think I've told you guys to
> do this more than once.
Yes. I forgot about that. My apologies.
prev parent reply other threads:[~2009-04-20 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 16:52 [PATCH 1/8] tg3: Fix SEEPROM accesses Matt Carlson
2009-04-20 21:53 ` David Miller
2009-04-20 22:02 ` Matt Carlson [this message]
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=20090420220210.GB7358@xw6200.broadcom.net \
--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).