From: John Crispin <blogic@openwrt.org>
To: Guenter Roeck <linux@roeck-us.net>,
Paul Bolle <pebolle@tiscali.nl>,
John Crispin <blogic@openwrt.org>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Ralf Baechle <ralf@linux-mips.org>,
Valentin Rothberg <valentinrothberg@gmail.com>,
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 15:14:21 +0100 [thread overview]
Message-ID: <54D2293D.8000100@openwrt.org> (raw)
In-Reply-To: <54D225D6.6040603@roeck-us.net>
On 04/02/2015 14:59, Guenter Roeck wrote:
> On 02/04/2015 04:22 AM, Paul Bolle wrote:
>> John Crispin schreef op wo 04-02-2015 om 12:10 [+0100]:
>>> 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.
>>
>> Once code is mainlined you'll get fixes written for you, updates done
>> for you, etc. But you'll also get pointed at defects that require you to
>> fix them yourself, or see the code removed eventually.
>>
>>> @Wim, can you drop the patch please ?
>>
>> Why should Wim drop more than the
>> || SOC_MT7621
>>
>> snippet?
>>
>
> Question is if the driver works with MT7620 as advertised. Either case
> it would be odd if the driver advertises itself as MT7621 but only works
> for MT7620, so I think it should be dropped entirely for now.
>
> Wim, should I possibly ask Stephen to include my watchdog-next branch
> in his -next builds ? This would help us catching such problems earlier.
>
> Thanks,
> Guenter
>
>
>
it wont work on mt7620 but on mt7628 which is a subtype on mt7620. both
share the soc_mt7620.c inside arch/mips/ralink/ we rely on runtime
detection between the 2 and on the dts loading the correct driver.
mt7620 and mt7628 are both hidden behind the SOC_MT7620 symbol. the
depends on SOC_MT7620 part is correct and working. but i agree, just
drop it, i will simply carry it around with us in openwrt. one driver
more wont make a difference.
John
prev parent reply other threads:[~2015-02-04 14:14 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
2015-02-04 12:22 ` Paul Bolle
2015-02-04 13:59 ` Guenter Roeck
2015-02-04 14:14 ` John Crispin [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=54D2293D.8000100@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.