From: David Miller <davem@davemloft.net>
To: zajec5@gmail.com
Cc: netdev@vger.kernel.org, hauke@hauke-m.de
Subject: Re: [PATCH] bgmac: support Ethernet device on BCM47094 SoC
Date: Fri, 19 Feb 2016 19:56:47 -0500 (EST) [thread overview]
Message-ID: <20160219.195647.2084670596178428477.davem@davemloft.net> (raw)
In-Reply-To: <CACna6rzGWQBu7ZncdsiHgrnfhgF9bEqZVdX2xiMcAYX7LZ5gbg@mail.gmail.com>
From: Rafał Miłecki <zajec5@gmail.com>
Date: Fri, 19 Feb 2016 22:26:48 +0100
> Are you applying it to net-next? It way my intention, sorry if I was
> supposed to make it more clear.
You are always supposed to specify this explicitly, in the
Subject line, after PATCH, like "[PATCH net-next] bgmac: ..."
prev parent reply other threads:[~2016-02-20 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 6:48 [PATCH] bgmac: support Ethernet device on BCM47094 SoC Rafał Miłecki
2016-02-19 20:37 ` David Miller
2016-02-19 21:26 ` Rafał Miłecki
2016-02-20 0:56 ` 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=20160219.195647.2084670596178428477.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hauke@hauke-m.de \
--cc=netdev@vger.kernel.org \
--cc=zajec5@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).