linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Vignesh R <vigneshr@ti.com>, Yong Li <yong.b.li@intel.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-gpio <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] gpio: pca953x: coding style fixes
Date: Fri, 9 Sep 2016 17:08:27 +0200	[thread overview]
Message-ID: <CAMpxmJXR5H12wwMTS-FxBiEFzoxQfe1d1cZw6-cfpZ9MM1NUHA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYGh2iqoY-uyoBxmgN3WoB7cKMrHYXvXqgj1K9s6U5sjg@mail.gmail.com>

2016-09-08 1:15 GMT+02:00 Linus Walleij <linus.walleij@linaro.org>:
> On Wed, Sep 7, 2016 at 11:55 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Mon, Sep 5, 2016 at 4:31 PM, Bartosz Golaszewski
>> <bgolaszewski@baylibre.com> wrote:
>>
>>> pca953x_gpio_set_multiple() has some coding style issues that make it
>>> harder to read. Tweak the code a bit.
>>>
>>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>
>> Much better like this.
>>
>> Patch applied.
>
> Ah I see there was a later version and it was moved around.
>
> OK backing this out. Let's go for latest version and also please
> rebase it onto my devel branch.
>
> Yours,
> Linus Walleij

Done. The current, rebased version is v6.

Thanks,
Bartosz

  reply	other threads:[~2016-09-09 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 14:31 [PATCH 0/5] gpio: pca953x: code refactoring Bartosz Golaszewski
2016-09-05 14:31 ` [PATCH 1/5] gpio: pca953x: coding style fixes Bartosz Golaszewski
2016-09-07 21:55   ` Linus Walleij
2016-09-07 23:15     ` Linus Walleij
2016-09-09 15:08       ` Bartosz Golaszewski [this message]
2016-09-05 14:31 ` [PATCH 2/5] gpio: pca953x: code shrink Bartosz Golaszewski
2016-09-05 14:40   ` Geert Uytterhoeven
2016-09-07 22:01   ` Linus Walleij
2016-09-05 14:31 ` [PATCH 3/5] gpio: pca953x: refactor pca953x_write_regs() Bartosz Golaszewski
2016-09-05 14:31 ` [PATCH 4/5] gpio: pca953x: remove an unused variable Bartosz Golaszewski
2016-09-05 14:31 ` [PATCH 5/5] gpio: pca953x: refactor pca953x_read_regs() Bartosz Golaszewski
2016-09-07 22:02 ` [PATCH 0/5] gpio: pca953x: code refactoring 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=CAMpxmJXR5H12wwMTS-FxBiEFzoxQfe1d1cZw6-cfpZ9MM1NUHA@mail.gmail.com \
    --to=bgolaszewski@baylibre.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=geert+renesas@glider.be \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vigneshr@ti.com \
    --cc=yong.b.li@intel.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;
as well as URLs for NNTP newsgroup(s).