From: David Miller <davem@davemloft.net>
To: thomas.lendacky@amd.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1 0/2] amd-xgbe: AMD XGBE driver updates 2014-11-06
Date: Thu, 06 Nov 2014 19:00:47 -0500 (EST) [thread overview]
Message-ID: <20141106.190047.1846700868326941068.davem@davemloft.net> (raw)
In-Reply-To: <20141106230207.21973.67338.stgit@tlendack-t1.amdoffice.net>
From: Tom Lendacky <thomas.lendacky@amd.com>
Date: Thu, 6 Nov 2014 17:02:07 -0600
> The following series of patches fixes a couple of bugs that slipped
> through my last series.
>
> - Free channel structure after freeing the per channel interrupts
> - If an skb error allocation occurs during receive processing check
> whether more descriptors are associated with the packet or whether
> to start on a new packet
>
> This patch series is based on net-next.
Series applied, thanks Tom.
prev parent reply other threads:[~2014-11-07 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 23:02 [PATCH net-next v1 0/2] amd-xgbe: AMD XGBE driver updates 2014-11-06 Tom Lendacky
2014-11-06 23:02 ` [PATCH net-next v1 1/2] amd-xgbe: Free channel/ring structures later Tom Lendacky
2014-11-06 23:02 ` [PATCH net-next v1 2/2] amd-xgbe: Check for complete packet on skb allocation error Tom Lendacky
2014-11-07 0:00 ` David Miller [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=20141106.190047.1846700868326941068.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=thomas.lendacky@amd.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