public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: David Sterba <dsterba@suse•cz>,
	David Howells <dhowells@redhat•com>,
	David Sterba <dsterba@suse•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the btrfs tree with the fscache tree
Date: Wed, 17 Feb 2021 15:50:13 -0800	[thread overview]
Message-ID: <20210217235013.GV3014244@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20210212140444.5d72dfcd@canb.auug.org.au>

On Fri, Feb 12, 2021 at 02:04:44PM +1100, Stephen Rothwell wrote:
> Hi Ira,
> 
> On Thu, 11 Feb 2021 17:07:41 -0800 Ira Weiny <ira.weiny@intel•com> wrote:
> >
> > On Fri, Feb 12, 2021 at 10:38:10AM +1100, Stephen Rothwell wrote:
> > > from the fscache tree and commit:
> > > 
> > >   325a835476e3 ("iov_iter: Remove memzero_page() in favor of zero_user()")  
> > 
> > I don't seem to have that commit after fetching linux-next?  Should I have it?
> 
> It has not been released yet.  Hopefully it will be available in less than 10 hours :-)

Thanks...  looking at the resulting code it looks good to me.  Thanks for
resolving this!

Ira

> 
> -- 
> Cheers,
> Stephen Rothwell



      reply	other threads:[~2021-02-17 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 23:38 linux-next: manual merge of the btrfs tree with the fscache tree Stephen Rothwell
2021-02-12  1:07 ` Ira Weiny
2021-02-12  3:04   ` Stephen Rothwell
2021-02-17 23:50     ` Ira Weiny [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=20210217235013.GV3014244@iweiny-DESK2.sc.intel.com \
    --to=ira.weiny@intel$(echo .)com \
    --cc=dhowells@redhat$(echo .)com \
    --cc=dsterba@suse$(echo .)com \
    --cc=dsterba@suse$(echo .)cz \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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