From: Jean Sacren <sakiwit@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>, <aaron.f.brown@intel.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Linux NICS <linux.nics@intel.com>
Subject: [PATCH net-next 0/2] Fix some typos and an excessive space character
Date: Sat, 2 Aug 2014 20:37:09 -0600 [thread overview]
Message-ID: <1407026820-26552-1-git-send-email-mysctp@gmail.com> (raw)
This small series fixes some typos in the kernel doc and an
excessive space character in the debug message. Both are associated
with e1000_mng_enable_host_if() of the Intel e1000e driver.
Please apply in the order as annotated.
Jean Sacren (2):
e1000e: delete excessive space character in debug message
e1000e: fix trivial kernel doc typos
drivers/net/ethernet/intel/e1000e/manage.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next reply other threads:[~2014-08-03 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 2:37 Jean Sacren [this message]
2014-08-03 2:37 ` [PATCH net-next 1/2] e1000e: fix trivial kernel doc typos Jean Sacren
2014-08-03 2:37 ` [PATCH net-next 2/2] e1000e: delete excessive space character in debug message Jean Sacren
2014-08-05 0:12 ` [PATCH net-next 0/2] Fix some typos and an excessive space character Brown, Aaron F
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=1407026820-26552-1-git-send-email-mysctp@gmail.com \
--to=sakiwit@gmail.com \
--cc=aaron.f.brown@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux.nics@intel.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).