LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: mingo@redhat.com, acme@kernel.org, linux-kernel@vger.kernel.org,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] kernel: event: core: Change return type to vm_fault_t
Date: Thu, 17 May 2018 16:27:31 +0200	[thread overview]
Message-ID: <20180517142731.GV12217@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFqt6zaT=c87sSEU5dNs3AyWHthoe5c5iwkFGN1O1HrMsG=5_A@mail.gmail.com>

On Thu, May 17, 2018 at 07:55:13PM +0530, Souptick Joarder wrote:
> On Thu, May 10, 2018 at 7:54 PM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
> > On Fri, Apr 20, 2018 at 5:18 PM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
> >>> I'm fine with the patch, but shouldn't this be part of a larger series /
> >>> cocinelle script?
> >>>
> >>
> >> This one is trivial but many others are not.
> >> As part of this clean up we have fixed many
> >> existing bugs in fault handlers of drivers/
> >> file systems. Also we are replacing existing
> >> vm_insert_foo() with new vmf_insert_foo()
> >> in fault handlers (wherever applicable).
> >> Refer - 1c8f422059ae5da07db7406ab916203f9417e396
> >> in 4.17-rc1
> >
> > Any further comment on this patch ?
> 
> Peter, if no further comment, we would like to get this patch
> in queue for 4.18.

Nah, I still think you're doing this wrong by trickling single patches,
but have at.

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

      reply	other threads:[~2018-05-17 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14 20:28 Souptick Joarder
2018-04-20  8:28 ` Peter Zijlstra
2018-04-20 11:48   ` Souptick Joarder
2018-05-10 14:24     ` Souptick Joarder
2018-05-17 14:25       ` Souptick Joarder
2018-05-17 14:27         ` Peter Zijlstra [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=20180517142731.GV12217@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=jrdr.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=willy@infradead.org \
    --subject='Re: [PATCH] kernel: event: core: Change return type to vm_fault_t' \
    /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

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 NNTP newsgroup(s).