Message ID | 20201215130512.8753-1-peter.ujfalusi@ti.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: ti: Maintainer mail address change | expand |
Hi, On 15/12/2020 15.05, Peter Ujfalusi wrote: > Hi, > > My TI address is going to bounce after Friday (18.12.2020), switch my email > address to my private one for now. Obviously I forgot to 'TO' the private myself... Doing that now. > > Regards, > Peter > --- > Peter Ujfalusi (2): > MAINTAINERS: Update email address for TI ASoC and twl4030 codec > drivers > ASoC: dt-bindings: ti,j721e: Update maintainer and author information > > .../devicetree/bindings/sound/ti,j721e-cpb-audio.yaml | 4 +++- > .../devicetree/bindings/sound/ti,j721e-cpb-ivi-audio.yaml | 4 +++- > MAINTAINERS | 6 +++--- > 3 files changed, 9 insertions(+), 5 deletions(-) > - Péter Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On Tue, 15 Dec 2020 15:05:10 +0200, Peter Ujfalusi wrote: > My TI address is going to bounce after Friday (18.12.2020), switch my email > address to my private one for now. > > Regards, > Peter Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/2] MAINTAINERS: Update email address for TI ASoC and twl4030 codec drivers commit: fe6ce6c394fb1ef1d8a6384c5180e70893157f22 [2/2] ASoC: dt-bindings: ti, j721e: Update maintainer and author information commit: 61fc03b6512b18f27a25002426d595f5a36645ed All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark