From: Thomas Klein <osstklei@de.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: tklein@de.ibm.com, netdev@vger.kernel.org, themann@de.ibm.com,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2][RESEND] ehea: error handling improvement
Date: Fri, 23 Apr 2010 10:22:33 +0200 [thread overview]
Message-ID: <4BD158C9.90807@de.ibm.com> (raw)
In-Reply-To: <20100421.223620.257172362.davem@davemloft.net>
On 04/22/2010 07:36 AM, David Miller wrote:
> From: Thomas Klein<tklein@de.ibm.com>
> Date: Wed, 21 Apr 2010 11:10:55 +0200
>
>> Reset a port's resources only if they're actually in an error state
>>
>> Signed-off-by: Thomas Klein<tklein@de.ibm.com>
>> ---
>>
>> Patch created against net-2.6
>
> I thought you were sorry for wasting my time and that you were going
> to follow the directions I gave you last time, and I quote:
>
> --------------------
> 3) These are not appropriate for net-2.6 as we are deep in
> the -rcX series at this point and only the most diabolical
> bug fixes are appropriate. Therefore, please generate these
> against net-next-2.6, thanks.
> --------------------
>
> And here you are generating your patches against net-2.6. Heck, you
> even feel it's worth mentioning explicitly.
Guilty! Allows no excuse. Screwed it. Deeply sorry.
>
> Lucky for you the patches happen to apply cleanly to net-next-2.6 so
> I've put them there.
Thanks!
Thomas
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-04-23 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 9:10 [PATCH 1/2][RESEND] ehea: error handling improvement Thomas Klein
2010-04-22 5:36 ` David Miller
2010-04-23 8:22 ` Thomas Klein [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=4BD158C9.90807@de.ibm.com \
--to=osstklei@de.ibm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=themann@de.ibm.com \
--cc=tklein@de.ibm.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).