From: John Crispin <blogic@openwrt.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Ralf Baechle <ralf@linux-mips.org>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org
Subject: Re: watchdog: SOC_MT7621?
Date: Wed, 04 Feb 2015 12:10:07 +0100 [thread overview]
Message-ID: <54D1FE0F.3030308@openwrt.org> (raw)
In-Reply-To: <1423047893.23022.13.camel@x220>
On 04/02/2015 12:04, Paul Bolle wrote:
> On Wed, 2015-02-04 at 11:19 +0100, John Crispin wrote:
>> On 04/02/2015 11:13, Paul Bolle wrote:
>>> Is SOC_MT7621 still being worked on?
>>
>> yes we dropped the series as it collided with the gic rework that
>> chromiun.org was working on. i hope to push it during the next merge
>> window. the 1004k support has just been flaky till now as there was
>> never any real silicon to test it on. the chromium people really did a
>> good job at making the gic code nicer.
>
> Thanks for explaining this. Unless SOC_MT7621 takes a long time to land
> in linux-next I won't be bothering you again about this. (I think I'll
> use "by the end of the v3.20 series" as a definition of a long time.)
>
>> quite an impressive Cc list you have there
>
> Yes, that's the way it works with problems that span two (or more)
> subsystems (in this case watchdog and MIPS). Actually, much longer CC
> lists are used regularly on lkml.
>
> Thanks!
>
>
> Paul Bolle
>
i think wim should just drop it and we leave it in openwrt with the
other 1/2 million patches that we have. i prefer to upstream the stuff
without feeling pressured to hurry up, that kills the fun.
@Wim, can you drop the patch please ?
John
next prev parent reply other threads:[~2015-02-04 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 10:13 watchdog: SOC_MT7621? Paul Bolle
2015-02-04 10:19 ` John Crispin
2015-02-04 11:04 ` Paul Bolle
2015-02-04 11:10 ` John Crispin [this message]
2015-02-04 12:22 ` Paul Bolle
2015-02-04 13:59 ` Guenter Roeck
2015-02-04 14:14 ` John Crispin
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=54D1FE0F.3030308@openwrt.org \
--to=blogic@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pebolle@tiscali.nl \
--cc=ralf@linux-mips.org \
--cc=valentinrothberg@gmail.com \
--cc=wim@iguana.be \
/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