From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH net-next-2.6 2/5] sfc: Implement message level control
Date: Thu, 24 Jun 2010 14:33:32 -0700 (PDT) [thread overview]
Message-ID: <20100624.143332.179939286.davem@davemloft.net> (raw)
In-Reply-To: <1277349138.26161.144.camel@localhost>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Thu, 24 Jun 2010 04:12:18 +0100
> I'm hoping you're going to apply
> <http://patchwork.ozlabs.org/patch/56308> first.
I'm hoping that you will always tell me about such dependencies
in the future.
I always work my queue out of order. If I'm heavily backlogged like
I am now, I'll sometimes apply much "simpler" to review patch
sets before more difficult ones, even if the "difficult" ones are
older.
Never assume anything, always state explicitly what tree something
is for and whether dependencies exist for things as-yet not applied.
Your style of assuming things makes life real difficult for me.
next prev parent reply other threads:[~2010-06-24 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 21:27 [PATCH net-next-2.6 0/5] sfc changes for 2.6.36 Ben Hutchings
2010-06-23 21:29 ` [PATCH net-next-2.6 1/5] sfc: Log MTD errors using partition name, not just net device name Ben Hutchings
2010-06-23 21:30 ` [PATCH net-next-2.6 2/5] sfc: Implement message level control Ben Hutchings
2010-06-24 1:29 ` David Miller
2010-06-24 3:12 ` Ben Hutchings
2010-06-24 21:33 ` David Miller [this message]
2010-06-23 21:30 ` [PATCH net-next-2.6 3/5] sfc: Replace EFX_DRIVER_NAME with KBUILD_MODNAME Ben Hutchings
2010-06-23 21:30 ` [PATCH net-next-2.6 4/5] sfc: Disable setting feature flags that are not implemented Ben Hutchings
2010-06-23 21:31 ` [PATCH net-next-2.6 5/5] sfc: Record hardware RX hash on each skb where possible Ben Hutchings
2010-06-24 15:18 ` 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=20100624.143332.179939286.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).