From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH 00/12] sfc changes for 2.6.36
Date: Wed, 02 Jun 2010 06:57:11 -0700 (PDT) [thread overview]
Message-ID: <20100602.065711.191161830.davem@davemloft.net> (raw)
In-Reply-To: <1275486746.2870.31.camel@localhost>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 02 Jun 2010 14:52:26 +0100
> Did you apply patch 12 "sfc: Get port number from CS_PORT_NUM, not PCI
> function number" to net-2.6?
When you mix bug fixes and cleanups, I'm going to apply it all to
net-next-2.6 You didn't even specify an intended destination in your
subject lines, so you leave it entirely open for interpretation and
my choice.
So, if you want a bug fix added to net-2.6, tossing it into a series
which is not wholly appropriate for net-next-2.6 is not that way to
accomplish that.
The way to do it is:
1) Submit the bug fix, explicitly state "[PATCH net-2.6 xxx] "
in your subject line.
2) Prepare your net-next-2.6 changes on top of that, and do one
of two things:
a) Explicitly state in your patch series in the "[PATCH net-next-2.6 0/xxx] "
posting "this depends upon the bug fixes posted in the series
XXX posted earlier.
b) Wait for the bug fix to reach net-next-2.6 when I do a merge,
then post your series.
Otherwise you make life way to miserable and complicated for me,
the one who has to review and integrate all of your work.
Thanks.
next prev parent reply other threads:[~2010-06-02 13:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 21:16 [PATCH 00/12] sfc changes for 2.6.36 Ben Hutchings
2010-06-01 21:17 ` [PATCH 01/12] sfc: Rename struct efx_mcdi_phy_cfg to efx_mcdi_phy_data Ben Hutchings
2010-06-01 21:17 ` [PATCH 02/12] sfc: Reschedule any resets scheduled inside efx_pm_freeze() Ben Hutchings
2010-06-01 21:17 ` [PATCH 03/12] sfc: Workaround flush failures on Falcon B0 Ben Hutchings
2010-06-01 21:18 ` [PATCH 04/12] sfc: Synchronise link_advertising and wanted_fc on Siena Ben Hutchings
2010-06-01 21:18 ` [PATCH 05/12] sfc: Wait for the link to stay up before running loopback selftest Ben Hutchings
2010-06-01 21:19 ` [PATCH 06/12] sfc: Allow DRV_GEN events to be used outside of selftests Ben Hutchings
2010-06-01 21:19 ` [PATCH 07/12] sfc: Remove efx_rx_queue::add_lock Ben Hutchings
2010-06-01 21:20 ` [PATCH 09/12] sfc: Recycle discarded rx buffers back onto the queue Ben Hutchings
2010-06-01 21:20 ` [PATCH 10/12] sfc: Allow shared pages to be recycled Ben Hutchings
2010-06-01 21:21 ` [PATCH 11/12] sfc: Only count bad packets in rx_errors Ben Hutchings
2010-06-08 9:20 ` Dmitry Kravkov
2010-06-08 18:09 ` Ben Hutchings
2010-06-01 21:32 ` [PATCH 12/12] sfc: Get port number from CS_PORT_NUM, not PCI function number Ben Hutchings
2010-06-01 21:33 ` [PATCH 08/12] sfc: Support only two rx buffers per page Ben Hutchings
2010-06-02 9:21 ` [PATCH 00/12] sfc changes for 2.6.36 David Miller
2010-06-02 13:52 ` Ben Hutchings
2010-06-02 13:57 ` David Miller [this message]
2010-06-02 15:04 ` Ben Hutchings
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=20100602.065711.191161830.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.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).