All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip driver changes for 5.19 #2
Date: Fri, 27 May 2022 20:26:08 +0200	[thread overview]
Message-ID: <6492509.1IzOArtZ34@phil> (raw)
In-Reply-To: <6613768.ejJDZkT8p0@phil>

Am Dienstag, 17. Mai 2022, 21:35:07 CEST schrieb Heiko Stuebner:
> Hi Arnd, Kevin, Olof,
> 
> some additional things turned up (fixes) or got ready since the first round
> of pull requests for drivers and both flavors of devicetrees.
> 
> So depending on the schedule it would be nice to have them still in 5.19.
> But if it's to late for some, that's also no problem and I would then simply
> move them to 5.20.
> 
> All new tags (here + following mails) of course go on top of the
> previous tags.
> 
> So if timing allow, please pull.
> 
> Thanks
> Heiko
> 
> 
> The following changes since commit add9f6f30e54b5c07e7a0260cda459ef1d9646b7:
> 
>   soc: rockchip: Fix compile-testing SoC drivers (2022-04-30 15:06:14 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.19-rockchip-drivers2
> 
> for you to fetch changes up to 9b59588d8be91c96bfb0371e912ceb4f16315dbf:
> 
>   soc: rockchip: Fix refcount leak in rockchip_grf_init (2022-05-17 10:49:37 +0200)
> 
> ----------------------------------------------------------------
> Refcount leak for a used of-node in the grf-init.

superseeded by v2.




_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip driver changes for 5.19 #2
Date: Fri, 27 May 2022 20:26:08 +0200	[thread overview]
Message-ID: <6492509.1IzOArtZ34@phil> (raw)
In-Reply-To: <6613768.ejJDZkT8p0@phil>

Am Dienstag, 17. Mai 2022, 21:35:07 CEST schrieb Heiko Stuebner:
> Hi Arnd, Kevin, Olof,
> 
> some additional things turned up (fixes) or got ready since the first round
> of pull requests for drivers and both flavors of devicetrees.
> 
> So depending on the schedule it would be nice to have them still in 5.19.
> But if it's to late for some, that's also no problem and I would then simply
> move them to 5.20.
> 
> All new tags (here + following mails) of course go on top of the
> previous tags.
> 
> So if timing allow, please pull.
> 
> Thanks
> Heiko
> 
> 
> The following changes since commit add9f6f30e54b5c07e7a0260cda459ef1d9646b7:
> 
>   soc: rockchip: Fix compile-testing SoC drivers (2022-04-30 15:06:14 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.19-rockchip-drivers2
> 
> for you to fetch changes up to 9b59588d8be91c96bfb0371e912ceb4f16315dbf:
> 
>   soc: rockchip: Fix refcount leak in rockchip_grf_init (2022-05-17 10:49:37 +0200)
> 
> ----------------------------------------------------------------
> Refcount leak for a used of-node in the grf-init.

superseeded by v2.




WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip driver changes for 5.19 #2
Date: Fri, 27 May 2022 20:26:08 +0200	[thread overview]
Message-ID: <6492509.1IzOArtZ34@phil> (raw)
In-Reply-To: <6613768.ejJDZkT8p0@phil>

Am Dienstag, 17. Mai 2022, 21:35:07 CEST schrieb Heiko Stuebner:
> Hi Arnd, Kevin, Olof,
> 
> some additional things turned up (fixes) or got ready since the first round
> of pull requests for drivers and both flavors of devicetrees.
> 
> So depending on the schedule it would be nice to have them still in 5.19.
> But if it's to late for some, that's also no problem and I would then simply
> move them to 5.20.
> 
> All new tags (here + following mails) of course go on top of the
> previous tags.
> 
> So if timing allow, please pull.
> 
> Thanks
> Heiko
> 
> 
> The following changes since commit add9f6f30e54b5c07e7a0260cda459ef1d9646b7:
> 
>   soc: rockchip: Fix compile-testing SoC drivers (2022-04-30 15:06:14 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.19-rockchip-drivers2
> 
> for you to fetch changes up to 9b59588d8be91c96bfb0371e912ceb4f16315dbf:
> 
>   soc: rockchip: Fix refcount leak in rockchip_grf_init (2022-05-17 10:49:37 +0200)
> 
> ----------------------------------------------------------------
> Refcount leak for a used of-node in the grf-init.

superseeded by v2.




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-27 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 19:35 [GIT PULL] Rockchip driver changes for 5.19 #2 Heiko Stuebner
2022-05-17 19:35 ` Heiko Stuebner
2022-05-17 19:35 ` Heiko Stuebner
2022-05-27 18:26 ` Heiko Stuebner [this message]
2022-05-27 18:26   ` Heiko Stuebner
2022-05-27 18:26   ` Heiko Stuebner

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=6492509.1IzOArtZ34@phil \
    --to=heiko@sntech.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.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.