From: Robert Baldyga <r.baldyga@samsung.com>
To: a.zummo@towertech.it
Cc: "lee.jones@linaro.org >> Lee Jones" <lee.jones@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
rtc-linux@googlegroups.com
Subject: Re: [PATCH v5 0/3] mfd: max8997: add regmap support
Date: Tue, 17 Feb 2015 09:49:24 +0100 [thread overview]
Message-ID: <54E30094.4090908@samsung.com> (raw)
In-Reply-To: <20150129180326.GB26625@dtor-ws>
Hi Alessandro,
It looks like only your Ack is missing. Could you please look at my
patches? There are very little changes in RTC subsystem but your Ack is
needed.
Thank you,
Robert Baldyga
On 01/29/2015 07:03 PM, Dmitry Torokhov wrote:
> Hi Robert,
>
> On Wed, Jan 28, 2015 at 03:20:11PM +0100, Robert Baldyga wrote:
>> Hi,
>>
>> The first version of this patchset was send to kernel list almost 9
>> months ago and still I don't have all needed Acks. The missing ones are
>> for changes in INPUT and RTC subsystems.
>>
>> Dmitry, Alessandro, could you please have a look at this patches and
>> give your Acks?
>
> Sorry, there was nothing input-specific in the change (even though it
> did touch one of the input drivers) so I did not realize you were
> waiting for an ack.
>
> Just for the record I am fine with the change.
>
> Thanks.
>
next prev parent reply other threads:[~2015-02-17 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 7:23 [PATCH v5 0/3] mfd: max8997: add regmap support Robert Baldyga
2014-11-12 7:23 ` [PATCH v5 1/3] mfd: max8997: use regmap to access registers Robert Baldyga
2014-11-12 17:01 ` Sebastian Reichel
2015-01-29 18:01 ` Dmitry Torokhov
2014-11-12 7:23 ` [PATCH v5 2/3] mfd: max8997: handle IRQs using regmap Robert Baldyga
2014-11-12 7:23 ` [PATCH v5 3/3] mfd: max8997: change irq names to upper case Robert Baldyga
2015-01-30 1:00 ` Chanwoo Choi
2015-01-28 14:20 ` [PATCH v5 0/3] mfd: max8997: add regmap support Robert Baldyga
2015-01-29 18:03 ` Dmitry Torokhov
2015-02-17 8:49 ` Robert Baldyga [this message]
2016-05-03 15:56 ` Alexandre Belloni
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=54E30094.4090908@samsung.com \
--to=r.baldyga@samsung.com \
--cc=a.zummo@towertech.it \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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