From: Wolfram Sang <wsa@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Peter Rosin <peda@axentia.se>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: mux: Replace zero-length array with flexible-array
Date: Wed, 13 May 2020 12:37:27 +0200 [thread overview]
Message-ID: <20200513103727.GD1043@ninjato> (raw)
In-Reply-To: <20200512231200.GL4897@embeddedor>
[-- Attachment #1: Type: text/plain, Size: 111 bytes --]
> If that's not much work for you, then it'd be great if you include
> it for 5.7. :)
No problem, done now!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-05-13 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 18:53 [PATCH] i2c: mux: Replace zero-length array with flexible-array Gustavo A. R. Silva
2020-05-07 22:45 ` Peter Rosin
2020-05-12 10:43 ` Wolfram Sang
2020-05-12 23:12 ` Gustavo A. R. Silva
2020-05-13 10:37 ` Wolfram Sang [this message]
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=20200513103727.GD1043@ninjato \
--to=wsa@kernel.org \
--cc=gustavoars@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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).