linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Roman Sommer <roman.sommer@fau.de>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: linux-next: manual merge of the gpio tree with the staging tree
Date: Mon, 30 Jan 2017 18:02:45 +0100	[thread overview]
Message-ID: <20170130170245.GB13895@kroah.com> (raw)
In-Reply-To: <20170130152855.7e8cb6c2@canb.auug.org.au>

On Mon, Jan 30, 2017 at 03:28:55PM +1100, Stephen Rothwell wrote:
> Hi Linus,
> 
> Today's linux-next merge of the gpio tree got a conflict in:
> 
>   drivers/staging/greybus/gpio.c
> 
> between commit:
> 
>   1d3dfbd1dd34 ("staging: greybus: fix checkpatch unsigned warnings")
> 
> from the staging tree and commit:
> 
>   2956b5d94a76 ("pinctrl / gpio: Introduce .set_config() callback for GPIO chips")
> 
> from the gpio tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc drivers/staging/greybus/gpio.c
> index 558550cfe687,51384bdde450..000000000000
> --- a/drivers/staging/greybus/gpio.c
> +++ b/drivers/staging/greybus/gpio.c
> @@@ -474,17 -474,20 +474,20 @@@ static void gb_gpio_set(struct gpio_chi
>   	gb_gpio_set_value_operation(ggc, (u8)offset, !!value);
>   }
>   
> - static int gb_gpio_set_debounce(struct gpio_chip *chip, unsigned int offset,
> - 				unsigned int debounce)
>  -static int gb_gpio_set_config(struct gpio_chip *chip, unsigned offset,
> ++static int gb_gpio_set_config(struct gpio_chip *chip, unsigned int offset,
> + 			      unsigned long config)
>   {
>   	struct gb_gpio_controller *ggc = gpio_chip_to_gb_gpio_controller(chip);
> - 	u16 usec;
> + 	u32 debounce;
>   
> + 	if (pinconf_to_config_param(config) != PIN_CONFIG_INPUT_DEBOUNCE)
> + 		return -ENOTSUPP;
> + 
> + 	debounce = pinconf_to_config_argument(config);
>   	if (debounce > U16_MAX)
>   		return -EINVAL;
> - 	usec = (u16)debounce;
>   
> - 	return gb_gpio_set_debounce_operation(ggc, (u8)offset, usec);
> + 	return gb_gpio_set_debounce_operation(ggc, (u8)offset, (u16)debounce);
>   }
>   
>   static int gb_gpio_controller_setup(struct gb_gpio_controller *ggc)


Looks good, thanks for this.

greg k-h

  reply	other threads:[~2017-01-30 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30  4:28 linux-next: manual merge of the gpio tree with the staging tree Stephen Rothwell
2017-01-30 17:02 ` Greg KH [this message]
2017-01-30 17:28 ` Linus Walleij

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=20170130170245.GB13895@kroah.com \
    --to=greg@kroah.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=roman.sommer@fau.de \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).