All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: LINUXKERNEL <linux-kernel@vger.kernel.org>,
	David Dajun Chen <david.chen@diasemi.com>,
	Support Opensource <support.opensource@diasemi.com>
Subject: Re: [PATCH V1] mfd: da9063: remove unused struct da9063_irq_data and define EVENTS_BUF_LEN
Date: Thu, 7 Apr 2016 14:52:43 +0100	[thread overview]
Message-ID: <20160407135243.GC3323@x1> (raw)
In-Reply-To: <20160405084947.B2E0A3FB1D@swsrvapps-01.diasemi.com>

On Tue, 05 Apr 2016, Steve Twiss wrote:

> From: Steve Twiss <stwiss.opensource@diasemi.com>
> 
> The structure da9063_irq_data and define EVENTS_BUF_LEN are not used, so
> remove the redundant entries.
> 
> Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
> 
> ---
> This patch applies against linux-next and next-20160405
> 
> Regards,
> Steve
> 
> 
>  drivers/mfd/da9063-irq.c | 6 ------
>  1 file changed, 6 deletions(-)

Applied, thanks.

> diff --git a/drivers/mfd/da9063-irq.c b/drivers/mfd/da9063-irq.c
> index 0aa760e..7e903fc 100644
> --- a/drivers/mfd/da9063-irq.c
> +++ b/drivers/mfd/da9063-irq.c
> @@ -25,12 +25,6 @@
>  #define	DA9063_REG_EVENT_B_OFFSET	1
>  #define	DA9063_REG_EVENT_C_OFFSET	2
>  #define	DA9063_REG_EVENT_D_OFFSET	3
> -#define EVENTS_BUF_LEN			4
> -
> -struct da9063_irq_data {
> -	u16 reg;
> -	u8 mask;
> -};
>  
>  static const struct regmap_irq da9063_irqs[] = {
>  	/* DA9063 event A register */

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2016-04-07 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  8:41 [PATCH V1] mfd: da9063: remove unused struct da9063_irq_data and define EVENTS_BUF_LEN Steve Twiss
2016-04-07 13:52 ` 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=20160407135243.GC3323@x1 \
    --to=lee.jones@linaro.org \
    --cc=david.chen@diasemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stwiss.opensource@diasemi.com \
    --cc=support.opensource@diasemi.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.