From: Olof Johansson <olof@lixom.net>
To: Li Yang <leoyang.li@nxp.com>
Cc: soc@kernel.org, arm@kernel.org, Shawn Guo <shawnguo@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] soc/fsl drivers changes for next(v5.6)
Date: Thu, 16 Jan 2020 12:47:43 -0800 [thread overview]
Message-ID: <20200116204743.uwyo2mjvhj46vgxq@localhost> (raw)
In-Reply-To: <CADRPPNQm2ZK+trtKCo2Mjr+ga2vKCR4hWMoFXd3AMMxRQZ_4ZA@mail.gmail.com>
On Thu, Jan 16, 2020 at 01:14:07PM -0600, Li Yang wrote:
> On Thu, Jan 16, 2020 at 12:41 PM Olof Johansson <olof@lixom.net> wrote:
> >
> > Hi,
> >
> > On Thu, Jan 09, 2020 at 04:19:11PM -0600, Li Yang wrote:
> > > Hi soc maintainers,
> > >
> > > Please merge the following new changes for soc/fsl drivers.
> > >
> > > Regards,
> > > Leo
> > >
> > >
> > > The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
> > >
> > > Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git tags/soc-fsl-next-v5.6
> > >
> > > for you to fetch changes up to 6e62bd36e9ad85a22d92b1adce6a0336ea549733:
> > >
> > > soc: fsl: qe: remove set but not used variable 'mm_gc' (2020-01-08 16:02:48 -0600)
> > >
> > > ----------------------------------------------------------------
> > > NXP/FSL SoC driver updates for v5.6
> > >
> > > QUICC Engine drivers
> > > - Improve the QE drivers to be compatible with ARM/ARM64/PPC64
> > > architectures
> > > - Various cleanups to the QE drivers
> >
> > This branch contains a cross-section of drivers, including those who are
> > normally sent to other maintainers/subsystems. I don't see dependencies that
> > make them a requirement/easier to merge through the SoC tree at this time --
> > for example the ucc_uart driver updates are mostly independent cleanups.
> >
> > Am I missing some aspect here, or should those just be merged through
> > drivers/tty as other driver changes there? At the very least, we expect drivers
> > that aren't merged through the normal path to have acks from those maintainers.
> >
> > Mind following up on that? Thanks!
>
> Hi Olof,
>
> Some of the driver cleanups are dependent to core QE changes. Some
> maybe not but could have contextual dependency with other patches. I
> will be easier to have them all go in from the same place. We have
> collected the ack and confirmation from all the related maintainers.
> For the ucc_uart it is not a formal ack. Quoted the confirmation from
> Greg below:
Ok, getting that in the pull request (tag) would be useful for future cases.
Merging. Thanks!
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-16 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 22:19 [GIT PULL] soc/fsl drivers changes for next(v5.6) Li Yang
2020-01-16 18:39 ` Olof Johansson
2020-01-16 19:14 ` Li Yang
2020-01-16 20:47 ` Olof Johansson [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=20200116204743.uwyo2mjvhj46vgxq@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox