From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: (unknown)
Date: Sun, 25 Sep 2016 08:51:33 -0400 (EDT)
Message-ID: <20160925.085133.1803530927600018260.davem@davemloft.net>
References: <20160925.060423.854801855957024790.davem@davemloft.net>
        <1474800749-2306-1-git-send-email-zenczykowski@gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: maze@google.com, netdev@vger.kernel.org, ek@google.com,
        lorenzo@google.com
To: zenczykowski@gmail.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:48264 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S966135AbcIYMvl (ORCPT
        <rfc822;netdev@vger.kernel.org>); Sun, 25 Sep 2016 08:51:41 -0400
In-Reply-To: <1474800749-2306-1-git-send-email-zenczykowski@gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>


This posting needs an actual Subject line, saying something like:

	[PATCH net-next v3 0/7] Add RFC7559 style ipv6 soliciation backoff support

This text will go into the merge commit I create should I apply
this patch series.

In any event, using a blank Subject line is never appropriate.