From: Ron Mercer <ron.mercer@qlogic.com>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [net-next PATCH 0/3] qlge: Size RX buffers based on MTU.
Date: Fri, 16 Oct 2009 19:22:10 -0700 [thread overview]
Message-ID: <20091017022210.GA14919@linux-ox1b.qlogic.org> (raw)
In-Reply-To: <20091016.175142.52482970.davem@davemloft.net>
On Fri, Oct 16, 2009 at 05:51:42PM -0700, David Miller wrote:
> From: Ron Mercer <ron.mercer@qlogic.com>
> Date: Fri, 16 Oct 2009 13:15:33 -0700
>
> > These patches are interdependent.
>
> No, Ron, they are absolutely not.
>
> Apply the first patch, and that breaks the build because
> you've removed LARGE_BUFFER_SIZE but it's still referenced
> in qlge_main.c, and there are tons of other breakages too.
>
> Don't send me garbage like this and then claim it's a set
> of independent patches. A trivial build test would have
> shown otherwise, but you obviously didn't do that.
>
> This is completely rediculious:
Hi Dave,
Sorry for the confusion. I said they were 'interdependent' patches, meaning
"depending on each other". I was trying to break this up to
make it easier to review. Shall I send it as a single patch?
Thanks,
Ron
next prev parent reply other threads:[~2009-10-17 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 20:15 [net-next PATCH 0/3] qlge: Size RX buffers based on MTU Ron Mercer
2009-10-16 20:15 ` [net-next PATCH 1/3] qlge: Size RX buffers based on MTU (header changes) Ron Mercer
2009-10-16 20:15 ` [net-next PATCH 2/3] qlge: Size RX buffers based on MTU (Add API) Ron Mercer
2009-10-16 20:15 ` [net-next PATCH 3/3] qlge: Size RX buffers based on MTU changes Ron Mercer
2009-10-17 0:51 ` [net-next PATCH 0/3] qlge: Size RX buffers based on MTU David Miller
2009-10-17 2:22 ` Ron Mercer [this message]
2009-10-17 22:37 ` David Miller
2009-10-19 13:29 ` Ron Mercer
2009-10-19 13:32 ` [net-next PATCH 1/1] " Ron Mercer
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=20091017022210.GA14919@linux-ox1b.qlogic.org \
--to=ron.mercer@qlogic.com \
--cc=davem@davemloft.net \
--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