linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Arminder Singh <arminders208@outlook.com>
Cc: alyssa@rosenzweig.io, darren@stevens-zone.net,
	sven@svenpeter.dev, marcan@marcan.st,
	linux-kernel@vger.kernel.org, paulus@samba.org,
	asahi@lists.linux.dev, chzigotzky@xenosoft.de,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] i2c-pasemi: PASemi I2C controller IRQ enablement
Date: Wed, 5 Oct 2022 21:04:02 +0200	[thread overview]
Message-ID: <Yz3VItDOw6mYwxak@shikoro> (raw)
In-Reply-To: <MN2PR01MB5358FB185A18D2E6C22A45FE9F589@MN2PR01MB5358.prod.exchangelabs.com>

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


> Does fixing the alignment issues and the commit description justify a v3
> of the patch or should the minor fixes go out as a "resend"? Just not sure
> in this particular case as the fixes seem to be very minor ones.

Yes, please send a v3. Since you are only fixing whitespace issues, you
can add the Tested-by tags given here for v3 already.


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

  parent reply	other threads:[~2022-10-05 19:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01 22:25 [PATCH v2] i2c/pasemi: PASemi I2C controller IRQ enablement Arminder Singh
2022-10-02 11:21 ` Sven Peter
2022-10-02 11:28   ` Wolfram Sang
2022-10-02 14:07     ` [PATCH v2] i2c-pasemi: " Arminder Singh
2022-10-02 15:02       ` Sven Peter
2022-10-04  1:27         ` Michael Ellerman
2022-10-05 19:04       ` Wolfram Sang [this message]
2022-10-02 15:28 ` [PATCH v2] i2c/pasemi: " Christian Zigotzky

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=Yz3VItDOw6mYwxak@shikoro \
    --to=wsa@kernel.org \
    --cc=alyssa@rosenzweig.io \
    --cc=arminders208@outlook.com \
    --cc=asahi@lists.linux.dev \
    --cc=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=marcan@marcan.st \
    --cc=paulus@samba.org \
    --cc=sven@svenpeter.dev \
    /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).