From: David Miller <davem@davemloft.net>
To: alex.williams@ettus.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, mdf@kernel.org, keescook@chromium.org,
alex.williams@ni.com
Subject: Re: [PATCH net-next 1/2] net: nixge: Separate ctrl and dma resources
Date: Mon, 29 Oct 2018 16:37:38 -0700 (PDT) [thread overview]
Message-ID: <20181029.163738.2228889706351204145.davem@davemloft.net> (raw)
In-Reply-To: <20181029231447.3690-1-alex.williams@ettus.com>
The net-next tree is closed, please resubmit this when the net-next tree
opens back up.
Thank you.
prev parent reply other threads:[~2018-10-29 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 23:14 [PATCH net-next 1/2] net: nixge: Separate ctrl and dma resources alex.williams
2018-10-29 23:14 ` [PATCH net-next 2/2] net: nixge: Update device-tree bindings with v3.00 alex.williams
[not found] ` <5bea0e95.1c69fb81.88799.a282@mx.google.com>
2018-11-12 23:41 ` Alex Williams
2018-11-13 0:26 ` Rob Herring
2018-10-29 23:37 ` 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=20181029.163738.2228889706351204145.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.williams@ettus.com \
--cc=alex.williams@ni.com \
--cc=devicetree@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mdf@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).