public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: [GIT PULL] flexible-array transformations for 6.3-rc1
Date: Thu, 23 Feb 2023 16:24:13 -0600	[thread overview]
Message-ID: <Y/fnjS5eHNauiUUR@work> (raw)

The following changes since commit 88603b6dc419445847923fcb7fe5080067a30f98:

  Linux 6.2-rc2 (2023-01-01 13:53:16 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git tags/flex-array-transformations-6.3-rc1

for you to fetch changes up to b942a520d9e43bc31f0808d2f2267a1ddba75518:

  bcache: Replace zero-length arrays with DECLARE_FLEX_ARRAY() helper (2023-01-05 17:48:45 -0600)

----------------------------------------------------------------
flexible-array transformations for 6.3-rc1

Hi Linus,

Please, pull the following patches that transform zero-length arrays,
in unions, into flexible arrays. These patches have been baking in
linux-next for the whole development cycle.

Thanks
--
Gustavo

----------------------------------------------------------------
Gustavo A. R. Silva (3):
      exportfs: Replace zero-length array with DECLARE_FLEX_ARRAY() helper
      mm/memremap: Replace zero-length array with DECLARE_FLEX_ARRAY() helper
      bcache: Replace zero-length arrays with DECLARE_FLEX_ARRAY() helper

 drivers/md/bcache/bcache_ondisk.h | 8 ++++----
 include/linux/exportfs.h          | 2 +-
 include/linux/memremap.h          | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

             reply	other threads:[~2023-02-23 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 22:24 Gustavo A. R. Silva [this message]
2023-02-25 21:10 ` [GIT PULL] flexible-array transformations for 6.3-rc1 pr-tracker-bot

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=Y/fnjS5eHNauiUUR@work \
    --to=gustavoars@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox