From: Kukjin Kim <kgene.kim@samsung.com>
To: Olof Johansson <olof@lixom.net>
Cc: Kukjin Kim <kgene.kim@samsung.com>, Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [GIT PULL] Samsung fixes-2 for v3.4
Date: Tue, 24 Apr 2012 17:32:37 -0700 [thread overview]
Message-ID: <4F974625.1030607@samsung.com> (raw)
In-Reply-To: <CAOesGMhp48Kh+tJ1534G=ze0CEcVBpaPQxVKs8A31difVw9h9Q@mail.gmail.com>
Olof Johansson wrote:
> Hi,
[...]
(Cc'ed Marek Szyprowsk)
> Looking at your current fixes-3 branch, it's unclear at a quick glance
> why the clk_type patch is a bugfix, and especially why it is a
> regression fix -- it looks like a cleanup. We're very close to 3.4-rc3
I agree that the removing clk_type member in sdhci platform data should
be included in cleanup stuff, it is useless in current mainline though.
Marek, is this ok to you?
> now, so we should only be merging fixes (and ideally only regressions
> since 3.3).
>
> So, if you do need it to go into 3.4 please motivate it when you send
> the pull request.
>
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
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] Samsung fixes-2 for v3.4
Date: Tue, 24 Apr 2012 17:32:37 -0700 [thread overview]
Message-ID: <4F974625.1030607@samsung.com> (raw)
In-Reply-To: <CAOesGMhp48Kh+tJ1534G=ze0CEcVBpaPQxVKs8A31difVw9h9Q@mail.gmail.com>
Olof Johansson wrote:
> Hi,
[...]
(Cc'ed Marek Szyprowsk)
> Looking at your current fixes-3 branch, it's unclear at a quick glance
> why the clk_type patch is a bugfix, and especially why it is a
> regression fix -- it looks like a cleanup. We're very close to 3.4-rc3
I agree that the removing clk_type member in sdhci platform data should
be included in cleanup stuff, it is useless in current mainline though.
Marek, is this ok to you?
> now, so we should only be merging fixes (and ideally only regressions
> since 3.3).
>
> So, if you do need it to go into 3.4 please motivate it when you send
> the pull request.
>
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2012-04-25 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 16:07 [GIT PULL] Samsung fixes-2 for v3.4 Kukjin Kim
2012-04-14 16:07 ` Kukjin Kim
2012-04-15 1:04 ` Olof Johansson
2012-04-15 1:04 ` Olof Johansson
2012-04-25 0:32 ` Kukjin Kim [this message]
2012-04-25 0:32 ` Kukjin Kim
2012-04-25 5:59 ` Marek Szyprowski
2012-04-25 5:59 ` Marek Szyprowski
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=4F974625.1030607@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=olof@lixom.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.