From: Wolfram Sang <wsa@the-dreams.de>
To: ext-jaakko.laine@vaisala.com
Cc: linux-i2c@vger.kernel.org, michal.simek@xilinx.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] i2c: xiic: Change code alignment to 1 space only
Date: Fri, 28 Aug 2020 09:02:39 +0200 [thread overview]
Message-ID: <20200828070239.GA1343@ninjato> (raw)
In-Reply-To: <20200827144848.12107-2-ext-jaakko.laine@vaisala.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Thu, Aug 27, 2020 at 05:48:46PM +0300, ext-jaakko.laine@vaisala.com wrote:
> From: Jaakko Laine <ext-jaakko.laine@vaisala.com>
>
> Alignment removed and replaced with 1 space only to
> reduce need for future alignment changes affecting multiple
> lines, when new variables are added.
>
> Signed-off-by: Jaakko Laine <ext-jaakko.laine@vaisala.com>
> Acked-by: Michal Simek <michal.simek@xilinx.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: ext-jaakko.laine@vaisala.com
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
michal.simek@xilinx.com
Subject: Re: [PATCH 1/3] i2c: xiic: Change code alignment to 1 space only
Date: Fri, 28 Aug 2020 09:02:39 +0200 [thread overview]
Message-ID: <20200828070239.GA1343@ninjato> (raw)
In-Reply-To: <20200827144848.12107-2-ext-jaakko.laine@vaisala.com>
[-- Attachment #1.1: Type: text/plain, Size: 446 bytes --]
On Thu, Aug 27, 2020 at 05:48:46PM +0300, ext-jaakko.laine@vaisala.com wrote:
> From: Jaakko Laine <ext-jaakko.laine@vaisala.com>
>
> Alignment removed and replaced with 1 space only to
> reduce need for future alignment changes affecting multiple
> lines, when new variables are added.
>
> Signed-off-by: Jaakko Laine <ext-jaakko.laine@vaisala.com>
> Acked-by: Michal Simek <michal.simek@xilinx.com>
Applied to for-next, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-28 7:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 14:48 [PATCH 0/3] i2c: xiic: Support forcing single-master in DT ext-jaakko.laine
2020-08-27 14:48 ` ext-jaakko.laine
2020-08-27 14:48 ` [PATCH 1/3] i2c: xiic: Change code alignment to 1 space only ext-jaakko.laine
2020-08-27 14:48 ` ext-jaakko.laine
2020-08-28 7:02 ` Wolfram Sang [this message]
2020-08-28 7:02 ` Wolfram Sang
2020-08-27 14:48 ` [PATCH 2/3] i2c: xiic: Improve struct memory alignment ext-jaakko.laine
2020-08-27 14:48 ` ext-jaakko.laine
2020-08-27 15:56 ` Michal Simek
2020-08-27 15:56 ` Michal Simek
2020-08-28 7:02 ` Wolfram Sang
2020-08-28 7:02 ` Wolfram Sang
2020-08-27 14:48 ` [PATCH 3/3] i2c: xiic: Support forcing single-master in DT ext-jaakko.laine
2020-08-27 14:48 ` ext-jaakko.laine
2020-08-27 15:57 ` Michal Simek
2020-08-27 15:57 ` Michal Simek
2020-08-28 7:02 ` Wolfram Sang
2020-08-28 7:02 ` Wolfram Sang
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=20200828070239.GA1343@ninjato \
--to=wsa@the-dreams.de \
--cc=ext-jaakko.laine@vaisala.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=michal.simek@xilinx.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.