public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steve French <smfrench@gmail.com>,
	CIFS <linux-cifs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Steve French <stfrench@microsoft.com>,
	"Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Subject: Re: linux-next: manual merge of the mm-stable tree with the cifs tree
Date: Tue, 21 Feb 2023 18:42:25 +1100	[thread overview]
Message-ID: <20230221184225.0e734f0e@canb.auug.org.au> (raw)
In-Reply-To: <2351091.1676963957@warthog.procyon.org.uk>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

Hi David,

On Tue, 21 Feb 2023 07:19:17 +0000 David Howells <dhowells@redhat.com> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > in the cifs tree introduces a new usage of it in code that is used in
> > the cifs code ... so someone has to figure out what the merge
> > resolution is between the 2 trees (how to replace that new usage) and
> > let me know and then we need to test that combination for a while
> > before asking Linus to take it.  
> 
> It seems I can't fix my patch and give Steve a replacement patch because the
> new filemap_get_folios_tag() that I would need to use hasn't been added
> upstream yet.  Do we have any idea when the mm tree might land?

Andrew has already asked for it to be merged, so its up to Linus.

You could fetch it yourself and do a trial merge and send me your
resolution ..

git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-stable-2023-02-20-13-37

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-02-21  7:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  4:29 linux-next: manual merge of the mm-stable tree with the cifs tree Stephen Rothwell
2023-02-20 13:58 ` Matthew Wilcox
2023-02-20  8:01   ` Stephen Rothwell
2023-02-20 20:58     ` Matthew Wilcox
2023-02-21  6:44       ` Stephen Rothwell
2023-02-21  7:19         ` David Howells
2023-02-21  7:42           ` Stephen Rothwell [this message]
2023-02-21 14:39             ` David Howells
2023-02-21 14:55               ` Matthew Wilcox
2023-02-21 15:05                 ` David Howells
2023-02-21 15:26                   ` Matthew Wilcox
2023-02-21 15:20                 ` David Howells
2023-02-21 15:30                   ` Obsolete comment on page swizzling (written by Hugh)? David Howells
     [not found]               ` <2890066.1676993700@warthog.procyon.org.uk>
2023-02-21 22:41                 ` Hugh Dickins
2023-02-22  2:49               ` linux-next: manual merge of the mm-stable tree with the cifs tree Stephen Rothwell
2023-02-22  8:27                 ` David Howells
2023-02-22 12:13                   ` Stephen Rothwell
2023-02-20 21:00     ` Steve French
2023-02-21  6:50       ` Stephen Rothwell
2023-02-20 14:29   ` David Howells
2023-02-20 15:12     ` Matthew Wilcox
2023-02-20  8:05       ` Stephen Rothwell

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=20230221184225.0e734f0e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=stfrench@microsoft.com \
    --cc=vishal.moola@gmail.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