i2c: Enable Cadence driver for ARM64

This IP is available on Xilinx ZynqMP.

Signed-off-by: Michal Simek <michal.simek@xilinx.com>
---

 drivers/i2c/busses/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Regarding your address list -- it's too big.  Most of your addressees
don't care about this patch.  Please be more selective when sending
patches to people, most of us have enough (relevant) mail as it is.

> This IP is available on Xilinx ZynqMP.
> 
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> 
>  drivers/i2c/busses/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index 08b86178e8fb..d54c0e6d65d8 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -422,7 +422,7 @@ config I2C_BLACKFIN_TWI_CLK_KHZ
>  
>  config I2C_CADENCE
>  	tristate "Cadence I2C Controller"
> -	depends on ARCH_ZYNQ
> +	depends on ARCH_ZYNQ || ARM64
>  	help
>  	  Say yes here to select Cadence I2C Host Controller. This controller is
>  	  e.g. used by Xilinx Zynq.

Hi,

On 10/26/2015 03:32 PM, Lee Jones wrote:
> Regarding your address list -- it's too big.  Most of your addressees
> don't care about this patch.  Please be more selective when sending
> patches to people, most of us have enough (relevant) mail as it is.

This is just what get_maintainer.pl is returning you. And I do use
patman (uboot tools) for ages and none has any problem with it. That's
why I am curious why you have the problem with it.

Thanks,
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Mon, Oct 26, 2015 at 02:32:36PM +0000, Lee Jones wrote:
> Regarding your address list -- it's too big.  Most of your addressees
> don't care about this patch.  Please be more selective when sending
> patches to people, most of us have enough (relevant) mail as it is.

Probably more effective than to write every user of get_maintainer.pl:
Patch it to not use git history by default and win the fight ;)

On Mon, Oct 26, 2015 at 03:09:53PM +0100, Michal Simek wrote:
> This IP is available on Xilinx ZynqMP.
> 
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>

Applied to for-next, thanks!

On Mon, 26 Oct 2015, Michal Simek wrote:
> On 10/26/2015 03:32 PM, Lee Jones wrote:
> > Regarding your address list -- it's too big.  Most of your addressees
> > don't care about this patch.  Please be more selective when sending
> > patches to people, most of us have enough (relevant) mail as it is.
> 
> This is just what get_maintainer.pl is returning you. And I do use
> patman (uboot tools) for ages and none has any problem with it. That's
> why I am curious why you have the problem with it.

git_maintainer.pl is best used with the --no-git-fallback flag.  If
you don't it tells you about everyone who adapted, looked at, opened,
and/or breathed on the file.  The only people that are likely to care
about your change is either the original author of the specific hunk
you are changing and the Maintainers/Supporters.  To everyone else
these emails are spam.

On Mon, 26 Oct 2015, Wolfram Sang wrote:
> On Mon, Oct 26, 2015 at 02:32:36PM +0000, Lee Jones wrote:
> > Regarding your address list -- it's too big.  Most of your addressees
> > don't care about this patch.  Please be more selective when sending
> > patches to people, most of us have enough (relevant) mail as it is.
> 
> Probably more effective than to write every user of get_maintainer.pl:
> Patch it to not use git history by default and win the fight ;)

Geert wrote to Joe today.  Let's see if he can improve things.