From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL 1/2] ti-sysc driver changes for v5.3
Date: Wed, 4 Sep 2019 09:36:27 -0700 [thread overview]
Message-ID: <20190904163627.GS52127@atomide.com> (raw)
In-Reply-To: <CAK8P3a1Hh8nFe7h0Jr7tf_aoarvwr3utD7LrFf9rV_OePL-+Zg@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> [190904 15:27]:
> On Sat, Aug 24, 2019 at 12:24 AM Tony Lindgren <tony@atomide.com> wrote:
> > Driver changes for ti-sysc for v5.4
> >
> > Few changes to prepare for using a reset driver for PRM rstctrl mostly
> > to deal with the clocks for reset. Then few minor clean-up patches and
> > SPDX license identifier changes, and add a MAINTAINERs file entry.
>
> Pulled this one into an arm/late branch, together with the three
> other pull requests that depend on this one.
>
> Don't worry about the arm/late name, I expect to send this off
> together with the other branches, it's just easier for me to
> describe what's in each of the top-level branches this way.
OK sure thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL 1/2] ti-sysc driver changes for v5.3
Date: Wed, 4 Sep 2019 09:36:27 -0700 [thread overview]
Message-ID: <20190904163627.GS52127@atomide.com> (raw)
In-Reply-To: <CAK8P3a1Hh8nFe7h0Jr7tf_aoarvwr3utD7LrFf9rV_OePL-+Zg@mail.gmail.com>
* Arnd Bergmann <arnd@arndb.de> [190904 15:27]:
> On Sat, Aug 24, 2019 at 12:24 AM Tony Lindgren <tony@atomide.com> wrote:
> > Driver changes for ti-sysc for v5.4
> >
> > Few changes to prepare for using a reset driver for PRM rstctrl mostly
> > to deal with the clocks for reset. Then few minor clean-up patches and
> > SPDX license identifier changes, and add a MAINTAINERs file entry.
>
> Pulled this one into an arm/late branch, together with the three
> other pull requests that depend on this one.
>
> Don't worry about the arm/late name, I expect to send this off
> together with the other branches, it's just easier for me to
> describe what's in each of the top-level branches this way.
OK sure thanks.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-04 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 22:24 [GIT PULL 1/2] ti-sysc driver changes for v5.3 Tony Lindgren
2019-08-23 22:24 ` Tony Lindgren
2019-08-23 22:24 ` [GIT PULL 2/2] dts changes for omap variants for v5.4 Tony Lindgren
2019-08-23 22:24 ` Tony Lindgren
2019-09-03 14:01 ` Arnd Bergmann
2019-09-03 14:01 ` Arnd Bergmann
2019-09-04 15:26 ` [GIT PULL 1/2] ti-sysc driver changes for v5.3 Arnd Bergmann
2019-09-04 15:26 ` Arnd Bergmann
2019-09-04 16:36 ` Tony Lindgren [this message]
2019-09-04 16:36 ` Tony Lindgren
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=20190904163627.GS52127@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@kernel.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 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.