All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-i2c <linux-i2c@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: [PATCH][next] i2c: designware: Use fallthrough pseudo-keyword
Date: Thu, 23 Jul 2020 22:07:04 +0200	[thread overview]
Message-ID: <20200723200704.GB908@ninjato> (raw)
In-Reply-To: <20200722144848.GC22267@embeddedor>

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]


> > If you want to resend, please only one patch for all I2C drivers. The
> > change is "cosmetic" enough to do that IMO.
> > 
> 
> The reason why I'm sending separate patches for this is because
> the drivers have different maintainers.

I see. Still, people can ack parts of a patch they are responsible for.
I ack this way every now and then for cleanup patches, too.

That being said. All v2 and newer patches squashed into one and applied
to for-next.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-07-23 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 23:38 [PATCH][next] i2c: designware: Use fallthrough pseudo-keyword Gustavo A. R. Silva
2020-07-22  8:52 ` Andy Shevchenko
2020-07-22 14:37   ` Gustavo A. R. Silva
2020-07-22 14:38     ` Wolfram Sang
2020-07-22 14:48       ` Gustavo A. R. Silva
2020-07-23 20:07         ` Wolfram Sang [this message]
2020-07-23 20:53           ` Gustavo A. R. Silva

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=20200723200704.GB908@ninjato \
    --to=wsa@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gustavo@embeddedor.com \
    --cc=gustavoars@kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.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 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.