All of lore.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.6-rc1
Date: Mon, 28 Aug 2023 14:36:20 -0600	[thread overview]
Message-ID: <ZO0FRCAhO5vdQFPA@work> (raw)

The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:

  Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 4d8cbf6dbcdaebe949461b0a933ae4c71cb53edc:

  fs: omfs: Use flexible-array member in struct omfs_extent (2023-07-31 14:55:48 -0600)

----------------------------------------------------------------
flexible-array transformations for 6.6-rc1

Hi Linus,

Please, pull the following flexible-array transformations. These patches
have been baking in linux-next for a while.

Thanks
--
Gustavo

----------------------------------------------------------------
Gustavo A. R. Silva (3):
      reiserfs: Replace one-element array with flexible-array member
      sparc: openpromio: Address -Warray-bounds warning
      fs: omfs: Use flexible-array member in struct omfs_extent

 arch/sparc/include/uapi/asm/openpromio.h |  5 ++---
 fs/omfs/file.c                           | 12 ++++++------
 fs/omfs/omfs_fs.h                        |  2 +-
 fs/reiserfs/fix_node.c                   |  5 +++--
 fs/reiserfs/reiserfs.h                   |  2 +-
 5 files changed, 13 insertions(+), 13 deletions(-)

             reply	other threads:[~2023-08-28 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 20:36 Gustavo A. R. Silva [this message]
2023-08-29 20:18 ` [GIT PULL] flexible-array transformations for 6.6-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=ZO0FRCAhO5vdQFPA@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 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.