netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: a.heider@gmail.com
Cc: eric.dumazet@gmail.com, xiong@qca.qualcomm.com,
	netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: atl1c: DMA: Out of SW-IOMMU space
Date: Sun, 03 Mar 2013 01:45:25 -0500 (EST)	[thread overview]
Message-ID: <20130303.014525.737597234860582610.davem@davemloft.net> (raw)
In-Reply-To: <CAHsu+b_2dGk+-hkbnE8ziVxP52tKhUkL6BOek67HMA-R-2zPaw@mail.gmail.com>

From: Andre Heider <a.heider@gmail.com>
Date: Sun, 3 Mar 2013 04:21:52 +0100

> On Sun, Mar 3, 2013 at 3:52 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> On Sun, 2013-03-03 at 01:48 +0000, Huang, Xiong wrote:
>>> There is another patch follows commit ac574804d412047e52de4dd887615cc88f58aeb0, would you have a try ?
>>
>>
>> Do you mean the following ?
>>
>> commit 7cb08d7f3a5ea6131f4f243c2080530ac41cb293
>> Author: Huang, Xiong <xiong@qca.qualcomm.com>
>> Date:   Tue Feb 19 07:23:09 2013 +0000
>>
>>     atl1c: restore buffer state
>>
>>     in the previous commit : f1f220ea1dda078, the BUSY state of buffer is wrongly
>>     deleted. this patch just restore it.
>>
>>     Signed-off-by: xiong <xiong@qca.qualcomm.com>
>>     Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> Yeah, that's the only relevant commit I could find too, and indeed
> that patch fixes the problem, thanks!
> 
> Can we please apply this to 3.8.y ? atl1c is broken on 3.8 and 3.8.1,
> <= 3.7 is fine.

I've queued this up for -stable submission, thanks.

      reply	other threads:[~2013-03-03  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 17:28 atl1c: DMA: Out of SW-IOMMU space Andre Heider
2013-03-03  1:48 ` Huang, Xiong
2013-03-03  2:52   ` Eric Dumazet
2013-03-03  3:21     ` Andre Heider
2013-03-03  6:45       ` 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=20130303.014525.737597234860582610.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=a.heider@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xiong@qca.qualcomm.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).