From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Joachim Eastwood <manabian@gmail.com>,
dinguyen@kernel.org, Will Deacon <will.deacon@arm.com>,
"xuwei (O)" <xuwei5@hisilicon.com>
Subject: Re: [PATCH 1/6] mmc: dw_mmc: remove the deprecated "clock-freq-min-max" property
Date: Fri, 23 Feb 2018 15:27:06 +0200 [thread overview]
Message-ID: <CAHp75Vd27mFnSJTOta0ZWhfOGz1WA8ETNgU_GpuxEJ9nnhsR-g@mail.gmail.com> (raw)
In-Reply-To: <20180223064138.18401-1-jh80.chung@samsung.com>
On Fri, Feb 23, 2018 at 8:41 AM, Jaehoon Chung <jh80.chung@samsung.com> wrote:
> 'clock-freq-min-max' property had already deprecated.
> Remove the 'clock-freq-min-max' property that is kept to maintain
> the compatibility.
Removing a property without telling the user what to expect is a bad
idea and ABI breakage.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-02-23 13:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180223064140epcas2p104fe6cca431ec24f2b09a6f5a45ed342@epcas2p1.samsung.com>
2018-02-23 6:41 ` [PATCH 1/6] mmc: dw_mmc: remove the deprecated "clock-freq-min-max" property Jaehoon Chung
[not found] ` <CGME20180223064140epcas2p41a734737c3fe7373329a94f485c21fd4@epcas2p4.samsung.com>
2018-02-23 6:41 ` [PATCH 2/6] mmc: dw_mmc: remove the deprecated "num-slots" Jaehoon Chung
2018-03-02 15:25 ` Rob Herring
2018-03-15 10:22 ` Ulf Hansson
[not found] ` <CGME20180223064140epcas2p2145faef6a2c44d7d20bb3d6099f12d18@epcas2p2.samsung.com>
2018-02-23 6:41 ` [PATCH 3/6] ARM: dts: socfpga: remove 'num-slots' property for dwmmc Jaehoon Chung
2018-03-15 10:22 ` Ulf Hansson
[not found] ` <CGME20180223064140epcas2p3804fe3b7d63e4b7975d94a178e94dffb@epcas2p3.samsung.com>
2018-02-23 6:41 ` [PATCH 4/6] arm64: dts: stratix10: " Jaehoon Chung
2018-03-07 14:37 ` Dinh Nguyen
2018-03-15 10:22 ` Ulf Hansson
[not found] ` <CGME20180223064140epcas2p1bf475ebcbfa8a0c46e92402e31590891@epcas2p1.samsung.com>
2018-02-23 6:41 ` [PATCH 5/6] ARM: dts: lpc18xx: " Jaehoon Chung
2018-03-15 10:22 ` Ulf Hansson
[not found] ` <CGME20180223064140epcas2p1fcfb5920453f965d16f717931155fa2f@epcas2p1.samsung.com>
2018-02-23 6:41 ` [PATCH 6/6] arm64: dts: hi3660: " Jaehoon Chung
2018-03-15 10:23 ` Ulf Hansson
2018-02-23 13:27 ` Andy Shevchenko [this message]
2018-02-23 14:19 ` [PATCH 1/6] mmc: dw_mmc: remove the deprecated "clock-freq-min-max" property Shawn Lin
2018-02-23 16:16 ` Andy Shevchenko
2018-02-26 2:07 ` Jaehoon Chung
2018-02-26 3:26 ` [PATCH 1/6] mmc: dw_mmc: remove the deprecated "clock-freq-min-max" property -- You wokr with japanese after they fucked you thetruthbeforeus
2018-03-02 15:21 ` [PATCH 1/6] mmc: dw_mmc: remove the deprecated "clock-freq-min-max" property Rob Herring
2018-03-02 15:22 ` Rob Herring
2018-03-15 10:22 ` Ulf Hansson
2018-03-15 11:48 ` Jaehoon Chung
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=CAHp75Vd27mFnSJTOta0ZWhfOGz1WA8ETNgU_GpuxEJ9nnhsR-g@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.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.