From: Baruch Siach <baruch@tkos.co.il>
To: Kelly Anderson <kelly@xilka.com>
Cc: Christoph Mattheis <christoph.mattheis@arcor.de>,
acmattheis@gmx.net,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Michael Walle <michael@walle.cc>,
Matus Ujhelyi <ujhelyi.m@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: AW: Re: Broken ethernet on SolidRun cubox-i // plaintext re-send
Date: Thu, 28 Jan 2021 21:56:09 +0200 [thread overview]
Message-ID: <871re4ygx2.fsf@tarshish> (raw)
In-Reply-To: <2635221.mvXUDI8C0e@dooley.internal>
Hi Kelly,
On Thu, Jan 28 2021, Kelly Anderson wrote:
> On Wednesday, January 27, 2021 1:53:04 PM MST Russell King - ARM Linux admin
> wrote:
>> On Wed, Jan 27, 2021 at 09:46:02PM +0100, Christoph Mattheis wrote:
>> > Dear all, justed wanted to check if my email from 12.Jan 2021 has been
>> > received as I never got any reply - or did I said anything in that email
>> > that offended anybody? - if so, I'm sorry, pls accept my sincere
>> > apologies BR Chris
>> The fix has been submitted, Shawn Guo applied it, it should
>> eventually end up in mainline soon and backported to stable
>> kernels.
>
> Could you please add a link to that patch?
The patch is now here:
https://git.kernel.org/linus/2cc0bfc9c12784188482a8f3d751d44af45b0d97
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
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:[~2021-01-28 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0df492b6ea6b4999ae3d5c16b6ad52ef@arcor.de>
2021-01-27 20:46 ` AW: AW: Re: Broken ethernet on SolidRun cubox-i // plaintext re-send Christoph Mattheis
2021-01-27 20:53 ` Russell King - ARM Linux admin
2021-01-28 7:45 ` Kelly Anderson
2021-01-28 19:56 ` Baruch Siach [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=871re4ygx2.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=acmattheis@gmx.net \
--cc=christoph.mattheis@arcor.de \
--cc=kelly@xilka.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=ujhelyi.m@gmail.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).