From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Alex A. Mihaylov" <minimumlaw@rambler.ru>
Cc: Mark Brown <broonie@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
Evgeniy Polyakov <zbr@ioremap.net>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/4] Introduce regmap infrastructure over Maxim/Dalas OneWire (W1) bus
Date: Thu, 25 May 2017 20:51:36 +0200 [thread overview]
Message-ID: <20170525185136.GA17588@kroah.com> (raw)
In-Reply-To: <20170525174639.3191-2-minimumlaw@rambler.ru>
On Thu, May 25, 2017 at 08:46:36PM +0300, Alex A. Mihaylov wrote:
> Signed-off-by: Alex A. Mihaylov <minimumlaw@rambler.ru>
I just said I can ont take patches without any changelog text. Why did
you resend these without fixing that up?
greg k-h
next prev parent reply other threads:[~2017-05-25 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 17:46 [PATCH 0/4] Maxim Semiconductor MAX1721x power_supply driver Alex A. Mihaylov
2017-05-25 17:46 ` [PATCH 1/4] Introduce regmap infrastructure over Maxim/Dalas OneWire (W1) bus Alex A. Mihaylov
2017-05-25 18:51 ` Greg Kroah-Hartman [this message]
2017-05-26 9:56 ` Mark Brown
2017-05-26 10:21 ` Mark Brown
2017-05-26 15:50 ` Alex A. Mihaylov
[not found] ` <404871495743279@web24o.yandex.ru>
2017-05-26 11:06 ` Mark Brown
[not found] ` <3411811495806312@web49j.yandex.ru>
2017-05-26 16:17 ` Alex A. Mihaylov
2017-05-26 17:18 ` Mark Brown
[not found] ` <4265821495830391@web12o.yandex.ru>
2017-06-28 19:37 ` Mark Brown
[not found] ` <939401499441188@web18j.yandex.ru>
2017-07-07 17:11 ` Mark Brown
2017-05-25 17:46 ` [PATCH 2/4] Introduce new OneWire (W1) family 0x26 with slave device Maxim Semconductor MAX17211/MAX17215 Fuel Gauge IC Alex A. Mihaylov
2017-05-25 17:46 ` [PATCH 3/4] Introduce Maxim Semiconductor MAX17211/MAX17215 Standalone Fuel Gauge IC support for power_supply class driver Alex A. Mihaylov
2017-05-25 17:47 ` [PATCH 4/4] Fix W1 slave exchange with second device on probe step Alex A. Mihaylov
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=20170525185136.GA17588@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=minimumlaw@rambler.ru \
--cc=sre@kernel.org \
--cc=zbr@ioremap.net \
/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.