All of lore.kernel.org
 help / color / mirror / Atom feed
From: Souptick Joarder <jrdr.linux@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: rppt@linux.ibm.com, Michal Hocko <mhocko@suse.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Matthew Wilcox <willy@infradead.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	vbabka@suse.cz, riel@redhat.com, Linux-MM <linux-mm@kvack.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm: Create the new vm_fault_t type
Date: Tue, 8 Jan 2019 17:23:33 +0530	[thread overview]
Message-ID: <CAFqt6zZV-9qJYbKDbCNR1AkmeCVFWrJ2i270=w0i3jNEnN_nvw@mail.gmail.com> (raw)
In-Reply-To: <20190107144411.b3e2313649f106de0776432e@linux-foundation.org>

On Tue, Jan 8, 2019 at 4:14 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 7 Jan 2019 11:47:12 +0530 Souptick Joarder <jrdr.linux@gmail.com> wrote:
>
> > > Do I need to make any further improvement for this patch ?
> >
> > If no further comment, can we get this patch in queue for 5.0-rcX ?
>
> I stopped paying attention a while ago, sorry.
>
> Please resend everything which you believe is ready to go.

Sure, I will resend. no prob :)

  reply	other threads:[~2019-01-08 11:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 12:06 [PATCH v3] mm: Create the new vm_fault_t type Souptick Joarder
2018-11-06 12:10 ` Michal Hocko
2018-11-14  5:13 ` Souptick Joarder
2018-11-14  9:59   ` William Kucharski
2018-11-15  1:47 ` Mike Rapoport
2018-11-24  4:46   ` Souptick Joarder
2018-12-14  5:05     ` Souptick Joarder
2019-01-07  6:17       ` Souptick Joarder
2019-01-07  6:17         ` Souptick Joarder
2019-01-07 22:44         ` Andrew Morton
2019-01-08 11:53           ` Souptick Joarder [this message]
2019-01-08 11:53             ` Souptick Joarder

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='CAFqt6zZV-9qJYbKDbCNR1AkmeCVFWrJ2i270=w0i3jNEnN_nvw@mail.gmail.com' \
    --to=jrdr.linux@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=riel@redhat.com \
    --cc=rppt@linux.ibm.com \
    --cc=vbabka@suse.cz \
    --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 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.