All of lore.kernel.org
 help / color / mirror / Atom feed
From: "andriy.shevchenko@linux.intel.com"  <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	"Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	"andrew@aj.id.au" <andrew@aj.id.au>,
	"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v2 0/2] Add definition for GPIO direction
Date: Thu, 7 Nov 2019 10:52:29 +0200	[thread overview]
Message-ID: <20191107085229.GU32742@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdZ2F3zR2bdHgUV9GJX8iSojiM34BTWizTV_z+j7sS4jtw@mail.gmail.com>

On Thu, Nov 07, 2019 at 09:26:43AM +0100, Linus Walleij wrote:
> On Wed, Nov 6, 2019 at 3:25 PM andriy.shevchenko@linux.intel.com
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Wed, Nov 06, 2019 at 12:25:18PM +0000, Vaittinen, Matti wrote:

> > For pin control Intel, since we send PR to Linus and it won't be different to
> > him, we would like to see patch per driver.
> 
> It is generally good to bundle these changes because so many
> driver maintainers are passive. (Not Intel!)
> 
> If you are concerned, what about we just make a separate patch
> for the drivers under drivers/pinctrl/intel and bundle the rest?

Fine with me!

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	"andrew@aj.id.au" <andrew@aj.id.au>,
	"Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] Add definition for GPIO direction
Date: Thu, 7 Nov 2019 10:52:29 +0200	[thread overview]
Message-ID: <20191107085229.GU32742@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdZ2F3zR2bdHgUV9GJX8iSojiM34BTWizTV_z+j7sS4jtw@mail.gmail.com>

On Thu, Nov 07, 2019 at 09:26:43AM +0100, Linus Walleij wrote:
> On Wed, Nov 6, 2019 at 3:25 PM andriy.shevchenko@linux.intel.com
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Wed, Nov 06, 2019 at 12:25:18PM +0000, Vaittinen, Matti wrote:

> > For pin control Intel, since we send PR to Linus and it won't be different to
> > him, we would like to see patch per driver.
> 
> It is generally good to bundle these changes because so many
> driver maintainers are passive. (Not Intel!)
> 
> If you are concerned, what about we just make a separate patch
> for the drivers under drivers/pinctrl/intel and bundle the rest?

Fine with me!

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-11-07  8:52 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  8:51 [PATCH v2 0/2] Add definition for GPIO direction Matti Vaittinen
2019-11-06  8:51 ` Matti Vaittinen
2019-11-06  8:51 ` [alsa-devel] " Matti Vaittinen
2019-11-06  8:51 ` [PATCH v2 1/2] gpio: " Matti Vaittinen
2019-11-06  8:51   ` Matti Vaittinen
2019-11-06  8:51   ` [alsa-devel] " Matti Vaittinen
2019-11-07  8:20   ` Linus Walleij
2019-11-07  8:20     ` Linus Walleij
2019-11-07  8:20     ` [alsa-devel] " Linus Walleij
2019-11-06  8:54 ` [PATCH v2 2/2] gpio: Use new GPIO_LINE_DIRECTION Matti Vaittinen
2019-11-06  8:54   ` Matti Vaittinen
2019-11-06  8:54   ` [alsa-devel] " Matti Vaittinen
2019-11-06 14:22   ` Andy Shevchenko
2019-11-06 14:22     ` Andy Shevchenko
2019-11-06 14:22     ` [alsa-devel] " Andy Shevchenko
2019-11-06 14:43   ` William Breathitt Gray
2019-11-06 14:43     ` William Breathitt Gray
2019-11-06 14:43     ` [alsa-devel] " William Breathitt Gray
2019-11-06 17:35   ` Kuppuswamy Sathyanarayanan
2019-11-06 17:35     ` Kuppuswamy Sathyanarayanan
2019-11-06 17:35     ` [alsa-devel] " Kuppuswamy Sathyanarayanan
2019-11-07  8:33   ` Linus Walleij
2019-11-06 12:08 ` [PATCH v2 0/2] Add definition for GPIO direction Sebastian Reichel
2019-11-06 12:08   ` Sebastian Reichel
2019-11-06 12:08   ` [alsa-devel] " Sebastian Reichel
2019-11-06 12:25   ` Vaittinen, Matti
2019-11-06 12:25     ` Vaittinen, Matti
2019-11-06 12:25     ` [alsa-devel] " Vaittinen, Matti
2019-11-06 14:24     ` andriy.shevchenko
2019-11-06 14:24       ` andriy.shevchenko
2019-11-06 14:24       ` [alsa-devel] " andriy.shevchenko
2019-11-07  8:26       ` Linus Walleij
2019-11-07  8:26         ` Linus Walleij
2019-11-07  8:32         ` Geert Uytterhoeven
2019-11-07  8:32           ` Geert Uytterhoeven
2019-11-07  8:52         ` Vaittinen, Matti
2019-11-07  8:52           ` Vaittinen, Matti
2019-11-07 12:08           ` Sebastian Reichel
2019-11-07 12:08             ` Sebastian Reichel
2019-11-08  7:46             ` Nandor Han
2019-11-08  7:46               ` Nandor Han
2019-11-07  8:52         ` andriy.shevchenko [this message]
2019-11-07  8:52           ` andriy.shevchenko
2019-11-07  8:22     ` Linus Walleij
2019-11-07  8:22       ` Linus Walleij
2019-11-07  8:22       ` [alsa-devel] " Linus Walleij
2019-11-06 14:39 ` William Breathitt Gray
2019-11-06 14:39   ` William Breathitt Gray
2019-11-06 14:39   ` [alsa-devel] " William Breathitt Gray
2019-11-06 17:28   ` Vaittinen, Matti
2019-11-06 17:28     ` Vaittinen, Matti
2019-11-06 17:28     ` [alsa-devel] " Vaittinen, Matti

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=20191107085229.GU32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Matti.Vaittinen@fi.rohmeurope.com \
    --cc=andrew@aj.id.au \
    --cc=bgolaszewski@baylibre.com \
    --cc=geert+renesas@glider.be \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    /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.