From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] mfd: arizona: Remove some duplicate defines
Date: Wed, 15 Jun 2016 16:43:25 +0100 [thread overview]
Message-ID: <20160615154325.GO4948@dell> (raw)
In-Reply-To: <1465821471-28806-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Mon, 13 Jun 2016, Charles Keepax wrote:
> Some duplicate defines seem to have snuck into the registers file, this
> patch simply removes them.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> include/linux/mfd/arizona/registers.h | 6 ------
> 1 file changed, 6 deletions(-)
Applied, thanks.
> diff --git a/include/linux/mfd/arizona/registers.h b/include/linux/mfd/arizona/registers.h
> index cd7e78e..0d06c5d 100644
> --- a/include/linux/mfd/arizona/registers.h
> +++ b/include/linux/mfd/arizona/registers.h
> @@ -856,12 +856,6 @@
> #define ARIZONA_ISRC1INT4MIX_INPUT_1_SOURCE 0xB38
> #define ARIZONA_ISRC2DEC1MIX_INPUT_1_SOURCE 0xB40
> #define ARIZONA_ISRC2DEC2MIX_INPUT_1_SOURCE 0xB48
> -#define ARIZONA_ISRC2INT1MIX_INPUT_1_SOURCE 0xB60
> -#define ARIZONA_ISRC2INT2MIX_INPUT_1_SOURCE 0xB68
> -#define ARIZONA_ISRC1INT3MIX_INPUT_1_SOURCE 0xB30
> -#define ARIZONA_ISRC1INT4MIX_INPUT_1_SOURCE 0xB38
> -#define ARIZONA_ISRC2DEC1MIX_INPUT_1_SOURCE 0xB40
> -#define ARIZONA_ISRC2DEC2MIX_INPUT_1_SOURCE 0xB48
> #define ARIZONA_ISRC2DEC3MIX_INPUT_1_SOURCE 0xB50
> #define ARIZONA_ISRC2DEC4MIX_INPUT_1_SOURCE 0xB58
> #define ARIZONA_ISRC2INT1MIX_INPUT_1_SOURCE 0xB60
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2016-06-15 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 12:37 [PATCH] mfd: arizona: Remove some duplicate defines Charles Keepax
2016-06-15 15:43 ` Lee Jones [this message]
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=20160615154325.GO4948@dell \
--to=lee.jones@linaro.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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