netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sakiwit@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] Fix duplicate #include headers
Date: Mon, 07 Apr 2014 13:19:02 -0400 (EDT)	[thread overview]
Message-ID: <20140407.131902.31160920821686929.davem@davemloft.net> (raw)
In-Reply-To: <1396679341-23502-1-git-send-email-sakiwit@gmail.com>

From: Jean Sacren <sakiwit@gmail.com>
Date: Sat,  5 Apr 2014 00:28:59 -0600

> This tiny series fixes the same issue of duplicate #include headers.
> 
> Jean Sacren (2):
>   sxgbe: fix duplicate #include headers
>   mac802154: fix duplicate #include headers

Both applied, thanks.

      parent reply	other threads:[~2014-04-07 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05  6:28 [PATCH net 0/2] Fix duplicate #include headers Jean Sacren
2014-04-05  6:29 ` [PATCH net 1/2] sxgbe: fix " Jean Sacren
2014-04-07  9:46   ` Byungho An
2014-04-05  6:29 ` [PATCH net 2/2] mac802154: " Jean Sacren
2014-04-07 17:19 ` 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=20140407.131902.31160920821686929.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sakiwit@gmail.com \
    /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).