From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PULL REQUEST] renesas/v3u/devel-v2 for renesas drivers
Date: Tue, 26 Jan 2021 12:04:16 +0100 [thread overview]
Message-ID: <CAMuHMdV=r79KiCAzLF-vrYkGGu7bJP66CgNo2k-UyE0JQh2gZA@mail.gmail.com> (raw)
In-Reply-To: <20210121144321.GA2101@kunai>
Hi Wolfram,
On Thu, Jan 21, 2021 at 3:43 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> here is my updated v3u devel branch for renesas-drivers. It is based on
> our agreed base, so quite some patches from the previous version are
Oops. When discussing this, I thought you were looking for a good base
for development/testing, not for submitting ;-)
> already upstream. For the remaining ones, all review comments have been
> addressed, and the patches have been resent. Most binding doc updates
> are in -next meanwhile. The watchdog patches have been reviewed by
> Guenter. The rest is mainly your realm :) There are some debugging
> patches in there which I left in place.
>
> Please pull.
>
> Kind regards,
>
> Wolfram
>
>
> The following changes since commit 748c9c1c5e7d00fe6d1e5d47140e4492d7e63719:
>
> Merge branch 'topic/r8a779a0-dt-msiof-v2' into renesas-drivers (2021-01-12 12:36:54 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/v3u/devel-v2
>
> for you to fetch changes up to 4a1e26c947d213b717ee6c845dc922b1102305ef:
>
> HACK: make hscif0 console (2021-01-21 11:41:52 +0100)
Not to be included.
> Wolfram Sang (18):
> dt-bindings: watchdog: renesas,wdt: add r8a779a0 (V3U) support
> WIP soc: v3u: allow WDT reset
This is nice to have, for now.
> arm64: proper comment formatting in reboot handler
> watchdog: renesas_wdt: don't sleep in atomic context
> watchdog: renesas_wdt: add grace period before rebooting
This is basically your "renesas/v3u/wdt-v2" branch.
> v3u: enable other I2C busses for testing
Not to be included.
Due to the amount of conflicts between the old versions in your base,
and the newer accepted versions, and due to the unwanted commits, I'm
cherry-picking the top 5 commits of your "renesas/v3u/wdt-v2" branch
instead.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2021-01-26 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 14:43 [PULL REQUEST] renesas/v3u/devel-v2 for renesas drivers Wolfram Sang
2021-01-26 11:04 ` Geert Uytterhoeven [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='CAMuHMdV=r79KiCAzLF-vrYkGGu7bJP66CgNo2k-UyE0JQh2gZA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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).