From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Esben Haabendal <esben@geanix.com>
To: netdev@vger.kernel.org
Cc: , stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/8] net: ll_temac: Fix race condition causing TX hang
Date: Thu, 20 Feb 2020 12:49:33 +0000 [thread overview]
Message-ID: <20200220124934.5344D24673@mail.kernel.org> (raw)
In-Reply-To: <20200218082619.7119-1-esben@geanix.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.5.4, v5.4.20, v4.19.104, v4.14.171, v4.9.214, v4.4.214.
v5.5.4: Build OK!
v5.4.20: Build OK!
v4.19.104: Failed to apply! Possible dependencies:
2c9938e738a2 ("net: ll_temac: Fix bug causing buffer descriptor overrun")
v4.14.171: Failed to apply! Possible dependencies:
2c9938e738a2 ("net: ll_temac: Fix bug causing buffer descriptor overrun")
v4.9.214: Failed to apply! Possible dependencies:
2c9938e738a2 ("net: ll_temac: Fix bug causing buffer descriptor overrun")
v4.4.214: Failed to apply! Possible dependencies:
2c9938e738a2 ("net: ll_temac: Fix bug causing buffer descriptor overrun")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-02-20 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 8:26 [PATCH 1/8] net: ll_temac: Fix race condition causing TX hang Esben Haabendal
2020-02-20 12:49 ` Sasha Levin [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=20200220124934.5344D24673@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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).