From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Olof Johansson' <olof@lixom.net>, 'Tomasz Figa' <tomasz.figa@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org,
'Mike Turquette' <mturquette@linaro.org>,
arm@kernel.org, arnd@arndb.de, khilman@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: RE: [GIT PULL 5/6] Samsung PM updates for v3.15
Date: Tue, 11 Mar 2014 10:50:03 +0900 [thread overview]
Message-ID: <01d001cf3ccc$39f339b0$add9ad10$@samsung.com> (raw)
In-Reply-To: <CAOesGMiqhVk6JYhx=4446E1ZFWy7CrQNsjp8U6jf_De8FzidFw@mail.gmail.com>
Olof Johansson wrote:
>
> >> Hi,
> >>
> >> I don't see a single cc or acked-by line from Mike Turquette here. I'll
> >> hold
> >> off until he's had a chance to take a look at these ones; I suspect
> >> they'll be
> >> fine since it's mostly code refactoring though.
> >
> >
> > I guess I should have ACKed them too, but it felt kind of strange to ACK
> my
> > own patches. ;)
> >
> > Anyway, for all samsung-clk patches:
> >
> > Acked-by: Tomasz Figa <t.figa@samsung.com>
>
> Yeah, self-acking doesn't make much sense. :)
>
> I'm mostly worried about patches touching other subsystems without the
> other maintainer being aware of it or having reviewed them. As I said,
> these mostly look like refactorings but it's still good habit.
>
OK, agreed, I think Mike knew about that though. Let's wait for Mike's
response.
BTW, should I sort out the branch again if Mike gives ack on that?
- Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/6] Samsung PM updates for v3.15
Date: Tue, 11 Mar 2014 10:50:03 +0900 [thread overview]
Message-ID: <01d001cf3ccc$39f339b0$add9ad10$@samsung.com> (raw)
In-Reply-To: <CAOesGMiqhVk6JYhx=4446E1ZFWy7CrQNsjp8U6jf_De8FzidFw@mail.gmail.com>
Olof Johansson wrote:
>
> >> Hi,
> >>
> >> I don't see a single cc or acked-by line from Mike Turquette here. I'll
> >> hold
> >> off until he's had a chance to take a look at these ones; I suspect
> >> they'll be
> >> fine since it's mostly code refactoring though.
> >
> >
> > I guess I should have ACKed them too, but it felt kind of strange to ACK
> my
> > own patches. ;)
> >
> > Anyway, for all samsung-clk patches:
> >
> > Acked-by: Tomasz Figa <t.figa@samsung.com>
>
> Yeah, self-acking doesn't make much sense. :)
>
> I'm mostly worried about patches touching other subsystems without the
> other maintainer being aware of it or having reviewed them. As I said,
> these mostly look like refactorings but it's still good habit.
>
OK, agreed, I think Mike knew about that though. Let's wait for Mike's
response.
BTW, should I sort out the branch again if Mike gives ack on that?
- Kukjin
next prev parent reply other threads:[~2014-03-11 1:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 9:56 [GIT PULL 5/6] Samsung PM updates for v3.15 Kukjin Kim
2014-03-03 9:56 ` Kukjin Kim
2014-03-09 18:35 ` Olof Johansson
2014-03-09 18:35 ` Olof Johansson
2014-03-09 23:32 ` Tomasz Figa
2014-03-09 23:32 ` Tomasz Figa
2014-03-10 0:08 ` Olof Johansson
2014-03-10 0:08 ` Olof Johansson
2014-03-11 1:50 ` Kukjin Kim [this message]
2014-03-11 1:50 ` Kukjin Kim
2014-03-11 2:52 ` Olof Johansson
2014-03-11 2:52 ` Olof Johansson
2014-03-19 4:01 ` Mike Turquette
2014-03-19 4:01 ` Mike Turquette
2014-03-20 19:39 ` Kukjin Kim
2014-03-20 19:39 ` Kukjin Kim
2014-03-28 8:52 ` Kukjin Kim
2014-03-28 8:52 ` Kukjin Kim
2014-03-29 1:47 ` Arnd Bergmann
2014-03-29 1:47 ` Arnd Bergmann
2014-03-29 12:10 ` Heiko Stübner
2014-03-29 12:10 ` Heiko Stübner
2014-04-02 4:25 ` Kukjin Kim
2014-04-02 4:25 ` Kukjin Kim
2014-04-03 7:19 ` Mike Turquette
2014-04-03 7:19 ` Mike Turquette
2014-04-03 9:24 ` Kukjin Kim
2014-04-03 9:24 ` Kukjin Kim
2014-04-03 9:58 ` Heiko Stübner
2014-04-03 9:58 ` Heiko Stübner
2014-04-03 10:03 ` Kukjin Kim
2014-04-03 10:03 ` Kukjin Kim
2014-03-17 18:09 ` Tomasz Figa
2014-03-17 18:09 ` Tomasz Figa
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='01d001cf3ccc$39f339b0$add9ad10$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=olof@lixom.net \
--cc=tomasz.figa@gmail.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 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.