Linux filesystem development
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: akiyks@gmail.com, cmaiolino@redhat.com, corbet@lwn.net,
	dan.carpenter@linaro.org, dan.j.williams@intel.com,
	dchinner@redhat.com, djwong@kernel.org, hch@lst.de,
	hughd@google.com, kch@nvidia.com, kent.overstreet@linux.dev,
	leo.lilong@huawei.com, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org, longman@redhat.com,
	mchehab@kernel.org, peterz@infradead.org,
	ruansy.fnst@fujitsu.com, sfr@canb.auug.org.au,
	sshegde@linux.ibm.com
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to 601f8bc2440a
Date: Thu, 29 Feb 2024 10:39:16 +0530	[thread overview]
Message-ID: <87msrjn8ob.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <ZeAP01ULpmV0u9Ba@casper.infradead.org>

On Thu, Feb 29, 2024 at 05:02:11 AM +0000, Matthew Wilcox wrote:
> On Thu, Feb 29, 2024 at 10:23:45AM +0530, Chandan Babu R wrote:
>> Hi folks,
>> 
>> The for-next branch of the xfs-linux repository at:
>> 
>> 	https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
>> 
>> has just been updated.
>> 
>> Patches often get missed, so please check if your outstanding patches
>> were in this update. If they have not been in this update, please
>> resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
>> the next update.
>> 
>> The new head of the for-next branch is commit:
>> 
>> 601f8bc2440a Merge tag 'xfs-6.8-fixes-4' into xfs-for-next
>
> Some kind of merge snafu?  It looks like you merged all of 6.8-rc6 into
> for-next:
>
> https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/commit/?h=for-next

Apart from the patches destined for v6.9 cycle, The for-next branch has one
patch (i.e. xfs: drop experimental warning for FSDAX) that needs to be pulled
into v6.8-rc7. This patch is committed on v6.8-rc6. Hence, commits from
v6.8-rc6 got pulled into tree.

This issue will go away after I send a pull request for v6.8-rc7 to Linus and
drop the v6.8-* stuff from for-next.

-- 
Chandan

      reply	other threads:[~2024-02-29  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  4:53 [ANNOUNCE] xfs-linux: for-next updated to 601f8bc2440a Chandan Babu R
2024-02-29  5:02 ` Matthew Wilcox
2024-02-29  5:09   ` Chandan Babu R [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=87msrjn8ob.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=cmaiolino@redhat.com \
    --cc=corbet@lwn.net \
    --cc=dan.carpenter@linaro.org \
    --cc=dan.j.williams@intel.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=hughd@google.com \
    --cc=kch@nvidia.com \
    --cc=kent.overstreet@linux.dev \
    --cc=leo.lilong@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mchehab@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ruansy.fnst@fujitsu.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sshegde@linux.ibm.com \
    --cc=willy@infradead.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