From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Masanari Iida <standby24x7@gmail.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [E1000-devel] [PATCH] [trivial] ixgbe : Fix typo in ixgbe_common.h
Date: Sun, 22 Jan 2012 20:00:30 -0800 [thread overview]
Message-ID: <1327291230.2412.2.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1327153774-2092-1-git-send-email-standby24x7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Sat, 2012-01-21 at 22:49 +0900, Masanari Iida wrote:
> Correct spelling "packtetbuf_num" to "packetbuf_num" in
> drivers/net/ethernet/intel/ixgbe/ixgbe_common.h
>
> Signed-off-by: Masanari Iida<standby24x7@gmail.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_common.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_common.h b/drivers/net/ethernet/intel/ixgbe/ixgbe_common.h
> index 863f9c1..4c9a4c8 100644
> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_common.h
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_common.h
> @@ -75,7 +75,7 @@ s32 ixgbe_update_mc_addr_list_generic(struct ixgbe_hw *hw,
> s32 ixgbe_enable_mc_generic(struct ixgbe_hw *hw);
> s32 ixgbe_disable_mc_generic(struct ixgbe_hw *hw);
> s32 ixgbe_enable_rx_dma_generic(struct ixgbe_hw *hw, u32 regval);
> -s32 ixgbe_fc_enable_generic(struct ixgbe_hw *hw, s32 packtetbuf_num);
> +s32 ixgbe_fc_enable_generic(struct ixgbe_hw *hw, s32 packetbuf_num);
> s32 ixgbe_fc_autoneg(struct ixgbe_hw *hw);
>
> s32 ixgbe_validate_mac_addr(u8 *mac_addr);
Thanks! I have added the patch to my queue.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-23 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 13:49 [PATCH] [trivial] ixgbe : Fix typo in ixgbe_common.h Masanari Iida
2012-01-23 4:00 ` Jeff Kirsher [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=1327291230.2412.2.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=standby24x7@gmail.com \
--cc=trivial@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).