From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: robh+dt@kernel.org, lgirdwood@gmail.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree
Date: Wed, 13 Apr 2016 22:31:03 +0530 [thread overview]
Message-ID: <570E7B4F.8060507@nvidia.com> (raw)
In-Reply-To: <E1aqNXw-00083K-Oj@debutante>
On Wednesday 13 April 2016 09:51 PM, Mark Brown wrote:
> The patch
>
> regulator: max8973: add support for junction thermal warning
>
> has been applied to the regulator tree at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
>
> 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
>
> From d2d5437bdfdde20a75bdf59db1c1a77721613b22 Mon Sep 17 00:00:00 2001
> From: Laxman Dewangan <ldewangan@nvidia.com>
> Date: Wed, 13 Apr 2016 15:29:45 +0530
> Subject: [PATCH] regulator: max8973: add support for junction thermal warning
>
Thank you very much for accepting patch. Hope at this time, it will pass
the build test robot.
Unfortunately, it was reverted 2 times due to build issue on random config.
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: <robh+dt@kernel.org>, <lgirdwood@gmail.com>,
<mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree
Date: Wed, 13 Apr 2016 22:31:03 +0530 [thread overview]
Message-ID: <570E7B4F.8060507@nvidia.com> (raw)
In-Reply-To: <E1aqNXw-00083K-Oj@debutante>
On Wednesday 13 April 2016 09:51 PM, Mark Brown wrote:
> The patch
>
> regulator: max8973: add support for junction thermal warning
>
> has been applied to the regulator tree at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
>
> 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
>
> From d2d5437bdfdde20a75bdf59db1c1a77721613b22 Mon Sep 17 00:00:00 2001
> From: Laxman Dewangan <ldewangan@nvidia.com>
> Date: Wed, 13 Apr 2016 15:29:45 +0530
> Subject: [PATCH] regulator: max8973: add support for junction thermal warning
>
Thank you very much for accepting patch. Hope at this time, it will pass
the build test robot.
Unfortunately, it was reverted 2 times due to build issue on random config.
next prev parent reply other threads:[~2016-04-13 17:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 9:59 [PATCH V3 1/2] regulator: max8973: add DT binding details for junction warn temp Laxman Dewangan
2016-04-13 9:59 ` Laxman Dewangan
2016-04-13 9:59 ` [PATCH V3 2/2] regulator: max8973: add support for junction thermal warning Laxman Dewangan
2016-04-13 9:59 ` Laxman Dewangan
[not found] ` <1460541585-28432-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-04-13 16:21 ` Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree Mark Brown
2016-04-13 16:21 ` Mark Brown
2016-04-13 17:01 ` Laxman Dewangan [this message]
2016-04-13 17:01 ` Laxman Dewangan
-- strict thread matches above, loose matches on Subject: below --
2016-03-05 12:25 Mark Brown
2016-03-06 2:35 ` Mark Brown
2016-03-06 7:47 ` Laxman Dewangan
2016-03-06 11:35 ` Mark Brown
2016-03-07 6:36 ` Laxman Dewangan
2016-03-07 7:44 ` Mark Brown
2016-03-07 10:54 ` Laxman Dewangan
2016-03-08 2:22 ` Mark Brown
2016-01-06 16:07 [PATCH V2] regulator: max8973: add support for junction thermal warning Laxman Dewangan
2016-01-06 18:12 ` Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree Mark Brown
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=570E7B4F.8060507@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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.