From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: andy@greyhouse.net, netdev@vger.kernel.org
Subject: Re: [5/5][BNX2]: Update version and reldate.
Date: Mon, 04 Jun 2007 21:26:00 -0700 (PDT) [thread overview]
Message-ID: <20070604.212600.91329859.davem@davemloft.net> (raw)
In-Reply-To: <1181001678.5275.16.camel@dell>
From: "Michael Chan" <mchan@broadcom.com>
Date: Mon, 04 Jun 2007 17:01:18 -0700
> [BNX2]: Update version and reldate.
>
> Update to version 1.5.11.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Also applied.
I'd like to note in passing since I saw it in the context of this diff
that I find the RUN_AT() macro confusing.
It's name implies that the argument given to it is absolute. Instead,
the argument is relative and it's return value is absolute.
Maybe it's just me :-)
prev parent reply other threads:[~2007-06-05 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 0:01 [5/5][BNX2]: Update version and reldate Michael Chan
2007-06-05 4:26 ` David Miller [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=20070604.212600.91329859.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.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).