From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: bodonnel@redhat.com, hch@lst.de, linux-xfs@vger.kernel.org
Subject: Re: [GIT PULL 01/11] xfsprogs: packaging fixes for 6.7
Date: Mon, 22 Apr 2024 11:56:35 +0200 [thread overview]
Message-ID: <q4hmf27phzvtywp65mszhllxedznmw7myxkqrsyxe4vrthjgw5@hgbpf6tcai6i> (raw)
In-Reply-To: <171339158311.1911630.13437553389622374759.stg-ugh@frogsfrogsfrogs>
On Wed, Apr 17, 2024 at 03:07:35PM -0700, Darrick J. Wong wrote:
> Hi Carlos,
>
> Please pull this branch with changes for xfsprogs for 6.6-rc1.
>
> As usual, I did a test-merge with the main upstream branch as of a few
> minutes ago, and didn't see any conflicts. Please let me know if you
> encounter any problems.
>
> The following changes since commit 09ba6420a1ee2ca4bfc763e498b4ee6be415b131:
>
> xfsprogs: Release v6.7.0 (2024-04-17 09:55:22 +0200)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfsprogs-dev.git tags/packaging-fixes-6.7_2024-04-17
I'm actually pulling this before 6.8 libxfs-sync, as it fixes the xfs_rtbitmap.h include mistake I
did previous sync, so I can synchronize libxfs with this already fixed.
Carlos
>
> for you to fetch changes up to d27e715c3081306e1b210e64d21775457c9f087a:
>
> libxfs: fix incorrect porting to 6.7 (2024-04-17 14:06:22 -0700)
>
> ----------------------------------------------------------------
> xfsprogs: packaging fixes for 6.7 [01/20]
>
> This series fixes some bugs that I and others have found in the
> userspace tools. At this point 6.7 is released, so these target 6.8.
>
> This has been running on the djcloud for months with no problems. Enjoy!
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
>
> ----------------------------------------------------------------
> Darrick J. Wong (2):
> debian: fix package configuration after removing platform_defs.h.in
> libxfs: fix incorrect porting to 6.7
>
> db/check.c | 1 -
> debian/rules | 6 ++++--
> include/libxfs.h | 4 ++++
> libxfs/Makefile | 1 +
> libxfs/xfs_rtbitmap.c | 2 +-
> libxfs/xfs_rtbitmap.h | 3 ---
> repair/rt.c | 1 -
> 7 files changed, 10 insertions(+), 8 deletions(-)
>
>
next prev parent reply other threads:[~2024-04-22 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 22:04 [GIT PULLBOMB] xfsprogs: catch us up to 6.8, at least Darrick J. Wong
2024-04-17 22:07 ` [GIT PULL 01/11] xfsprogs: packaging fixes for 6.7 Darrick J. Wong
2024-04-18 4:31 ` Christoph Hellwig
2024-04-22 9:56 ` Carlos Maiolino [this message]
2024-04-17 22:07 ` [GIT PULL 02/11] xfsprogs: minor " Darrick J. Wong
2024-04-17 22:08 ` [GIT PULL 03/11] xfsprogs: convert utilities to use new rt helpers Darrick J. Wong
2024-04-17 22:08 ` [GIT PULL 04/11] libxfs: sync with 6.8 Darrick J. Wong
2024-04-17 22:08 ` [GIT PULL 05/11] xfs_repair: faster btree bulkloading Darrick J. Wong
2024-04-17 22:08 ` [GIT PULL 06/11] xfsprogs: bug fixes for 6.8 Darrick J. Wong
2024-04-17 22:09 ` [GIT PULL 07/11] xfsprogs: fix log sector size detection Darrick J. Wong
2024-04-17 22:09 ` [GIT PULL 08/11] mkfs: scale shards on ssds Darrick J. Wong
2024-04-17 22:09 ` [GIT PULL 09/11] xfs_scrub: scan metadata files in parallel Darrick J. Wong
2024-04-17 22:09 ` [GIT PULL 10/11] xfs_repair: rebuild inode fork mappings Darrick J. Wong
2024-04-17 22:10 ` [GIT PULL 11/11] xfs_repair: support more than 4 billion records Darrick J. Wong
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=q4hmf27phzvtywp65mszhllxedznmw7myxkqrsyxe4vrthjgw5@hgbpf6tcai6i \
--to=cem@kernel.org \
--cc=bodonnel@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).