From: Stephen Hemminger <stephen@networkplumber.org>
To: "Tobin C. Harding" <tobin@kernel.org>
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
bridge@lists.linux-foundation.org,
Tyler Hicks <tyhicks@canonical.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH v2] bridge: Fix error path for kobject_init_and_add()
Date: Thu, 9 May 2019 20:35:01 -0700 [thread overview]
Message-ID: <20190509203501.310a477c@hermes.lan> (raw)
In-Reply-To: <20190510025702.GA10709@eros.localdomain>
On Fri, 10 May 2019 12:57:02 +1000
"Tobin C. Harding" <tobin@kernel.org> wrote:
> On Fri, May 10, 2019 at 12:52:12PM +1000, Tobin C. Harding wrote:
>
> Please ignore - I forgot about netdev procedure and the merge window.
> My bad.
>
> Will re-send when you are open.
>
> thanks,
> Tobin.
That only applies to new features, bug fixes are allowed all the time.
Also please dont send networking stuff to the greater linux-kernel mailing list.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Tobin C. Harding" <tobin@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
Tyler Hicks <tyhicks@canonical.com>,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] bridge: Fix error path for kobject_init_and_add()
Date: Thu, 9 May 2019 20:35:01 -0700 [thread overview]
Message-ID: <20190509203501.310a477c@hermes.lan> (raw)
In-Reply-To: <20190510025702.GA10709@eros.localdomain>
On Fri, 10 May 2019 12:57:02 +1000
"Tobin C. Harding" <tobin@kernel.org> wrote:
> On Fri, May 10, 2019 at 12:52:12PM +1000, Tobin C. Harding wrote:
>
> Please ignore - I forgot about netdev procedure and the merge window.
> My bad.
>
> Will re-send when you are open.
>
> thanks,
> Tobin.
That only applies to new features, bug fixes are allowed all the time.
Also please dont send networking stuff to the greater linux-kernel mailing list.
next prev parent reply other threads:[~2019-05-10 3:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 2:52 [Bridge] [PATCH v2] bridge: Fix error path for kobject_init_and_add() Tobin C. Harding
2019-05-10 2:52 ` Tobin C. Harding
2019-05-10 2:57 ` [Bridge] " Tobin C. Harding
2019-05-10 2:57 ` Tobin C. Harding
2019-05-10 3:35 ` Stephen Hemminger [this message]
2019-05-10 3:35 ` Stephen Hemminger
2019-05-10 3:59 ` [Bridge] " Tobin C. Harding
2019-05-10 3:59 ` Tobin C. Harding
2019-05-10 22:06 ` [Bridge] " David Miller
2019-05-10 22:06 ` David Miller
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=20190509203501.310a477c@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=tobin@kernel.org \
--cc=tyhicks@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.