From: Jeff Garzik <jeff@garzik.org>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: netdev@vger.kernel.org, shemminger@linux-foundation.org
Subject: Re: [PATCH 4/4] ixgbe: minor sparse fixes
Date: Tue, 30 Oct 2007 14:33:05 -0400 [thread overview]
Message-ID: <472778E1.4060101@garzik.org> (raw)
In-Reply-To: <20071029174624.25245.22619.stgit@localhost.localdomain>
Auke Kok wrote:
> From: Stephen Hemminger <shemminger@linux-foundation.org>
>
> Make strings const if possible, and fix includes so forward definitions
> are seen.
>
> Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
> ---
>
> drivers/net/ixgbe/ixgbe.h | 2 +-
> drivers/net/ixgbe/ixgbe_82598.c | 3 +--
> drivers/net/ixgbe/ixgbe_main.c | 9 +++++----
> 3 files changed, 7 insertions(+), 7 deletions(-)
applied 1-4
prev parent reply other threads:[~2007-10-30 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 17:46 [PATCH 1/4] e1000e: fix sparse warnings Auke Kok
2007-10-29 17:46 ` [PATCH 2/4] ixgb: " Auke Kok
2007-10-29 17:46 ` [PATCH 3/4] e1000: sparse warnings fixes Auke Kok
2007-10-29 17:46 ` [PATCH 4/4] ixgbe: minor sparse fixes Auke Kok
2007-10-30 18:33 ` Jeff Garzik [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=472778E1.4060101@garzik.org \
--to=jeff@garzik.org \
--cc=auke-jan.h.kok@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).