linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
	od@zcrc.me, linux-watchdog@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] watchdog: jz4740: Driver update
Date: Fri, 09 Aug 2019 19:34:49 +0200	[thread overview]
Message-ID: <1565372089.2091.4@crapouillou.net> (raw)
In-Reply-To: <20190809172906.GA21450@roeck-us.net>



Le ven. 9 août 2019 à 19:29, Guenter Roeck <linux@roeck-us.net> a 
écrit :
> On Fri, Aug 09, 2019 at 06:55:26PM +0200, Paul Cercueil wrote:
>>  Hi Guenter,
>> 
>> 
>>  Le ven. 9 août 2019 à 18:52, Guenter Roeck <linux@roeck-us.net> a 
>> écrit :
>>  >On Fri, Aug 09, 2019 at 01:59:27PM +0200, Paul Cercueil wrote:
>>  >> Hi,
>>  >>
>>  >> This patchset comes from a bigger patchset that was cut in 
>> smaller
>>  >> pieces for easier integration to mainline.
>>  >> (The patchset was https://lkml.org/lkml/2019/3/27/1837)
>>  >>
>>  >> The reviews were kept since the code mostly didn't change. The
>>  >>exception
>>  >> is the use of device_node_to_regmap() in patch 2/3. This 
>> function was
>>  >> added in a prior patch, now merged in the MIPS tree.
>>  >>
>>  >> For that reason this patchset is based on the ingenic-tcu-v5.4 
>> branch
>>  >>of
>>  >> the MIPS tree
>>  >> (git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git).
>>  >>
>>  >
>>  >What is the expectation here ? Should the series be sent upstream
>>  >through the watchdog tree, or through some other tree ?
>> 
>>  You can get it through the watchdog tree if you merge the 
>> ingenic-tcu-v5.4
>>  branch from the MIPS tree. If you'd rather not do that, I can get 
>> it merged
>>  through the MIPS tree.
>> 
> I would prefer a merge through the mips tree.
> 
> Guenter

Ok; Can I get some signatures then? ;)

Thanks,
-Paul



  reply	other threads:[~2019-08-09 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 11:59 [PATCH 0/3] watchdog: jz4740: Driver update Paul Cercueil
2019-08-09 11:59 ` [PATCH 1/3] watchdog: jz4740: Use WDT clock provided by TCU driver Paul Cercueil
2019-08-09 17:58   ` Guenter Roeck
2019-08-09 11:59 ` [PATCH 2/3] watchdog: jz4740: Use regmap " Paul Cercueil
2019-08-09 17:58   ` Guenter Roeck
2019-08-09 11:59 ` [PATCH 3/3] watchdog: jz4740: Drop dependency on MACH_JZ47xx Paul Cercueil
2019-08-09 17:59   ` Guenter Roeck
2019-08-09 16:52 ` [PATCH 0/3] watchdog: jz4740: Driver update Guenter Roeck
2019-08-09 16:55   ` Paul Cercueil
2019-08-09 17:29     ` Guenter Roeck
2019-08-09 17:34       ` Paul Cercueil [this message]
2019-08-09 17:57         ` Guenter Roeck

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=1565372089.2091.4@crapouillou.net \
    --to=paul@crapouillou.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=od@zcrc.me \
    --cc=wim@linux-watchdog.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).