From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: ysato@users.sourceforge.jp, dalias@libc.org,
linux-sh@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Ether fixes for the SolutionEngine771x boards
Date: Tue, 09 Jan 2018 16:39:15 +0000 [thread overview]
Message-ID: <20180109.113915.2115013830186148164.davem@davemloft.net> (raw)
In-Reply-To: <ea8a7603-abc6-17e4-8ccb-388ade2a0a77@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Sat, 6 Jan 2018 22:31:53 +0300
> On 01/05/2018 06:54 PM, David Miller wrote:
>
>>> Here's the series of 2 patches against Linus' repo. This series should
>>> (hoplefully) fix the Ether support on the SolutionEngine771x boards...
>>>
>>> [1/2] SolutionEngine771x: fix Ether platform data
>>> [2/2] SolutionEngine771x: add Ether TSU resource
>> Looks like this doesn't go through my tree.
>
> Yeah, we have the SH kernel maintained now... but I have a bad feeling
> looking at their patchwork: it shows no recently applied patches. :-/
>
>> Let me know if it should.
>
> We'll wait and see, I think...
So, any update on this?
next prev parent reply other threads:[~2018-01-09 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 20:08 [PATCH 0/2] Ether fixes for the SolutionEngine771x boards Sergei Shtylyov
2018-01-03 20:57 ` Sergei Shtylyov
2018-01-05 15:54 ` David Miller
2018-01-06 19:31 ` Sergei Shtylyov
2018-01-09 16:39 ` David Miller [this message]
2018-01-09 17:06 ` Sergei Shtylyov
2018-01-06 18:53 ` Sergei Shtylyov
2018-01-06 18:56 ` Sergei Shtylyov
2018-01-09 17:21 ` David Miller
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=20180109.113915.2115013830186148164.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dalias@libc.org \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=ysato@users.sourceforge.jp \
/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).