From: David Miller <davem@davemloft.net>
To: michal.simek@xilinx.com
Cc: netdev@vger.kernel.org, sthokal@xilinx.com,
devicetree@vger.kernel.org, monstr@monstr.eu,
John.Linn@xilinx.com, anirudh@xilinx.com,
linux-kernel@vger.kernel.org, grant.likely@linaro.org,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/14] Xilinx axi ethernet patches
Date: Wed, 12 Feb 2014 19:18:46 -0500 (EST) [thread overview]
Message-ID: <20140212.191846.1464564509609498703.davem@davemloft.net> (raw)
In-Reply-To: <cover.1392220536.git.michal.simek@xilinx.com>
From: Michal Simek <michal.simek@xilinx.com>
Date: Wed, 12 Feb 2014 16:55:34 +0100
> I have exctracted patches which I have in our
> xilinx git tree which are missing in the mainline.
>
> The first two patches fix compilation error and
> warnings. Then 5 feature patches
> and the rest is OF cleanup and with kernel-doc
> and checkpatch problems.
You should not combine bug fix and feature patches.
Rather, you should submit bug fixes against the 'net' tree. Then when
those bug fixes get applied and propagate to the 'net-next' tree you
can submit the feature patches and cleanups against the 'net-next'
tree.
next prev parent reply other threads:[~2014-02-13 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 15:55 [PATCH 0/14] Xilinx axi ethernet patches Michal Simek
2014-02-12 15:55 ` [PATCH 10/14] net: axienet: Use pdev instead of op Michal Simek
2014-02-12 15:55 ` [PATCH 12/14] net: axienet: Use of_property_* calls Michal Simek
2014-02-13 0:18 ` David Miller [this message]
2014-02-13 7:00 ` [PATCH 0/14] Xilinx axi ethernet patches Michal Simek
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=20140212.191846.1464564509609498703.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=John.Linn@xilinx.com \
--cc=anirudh@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sthokal@xilinx.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).