All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anup Patel <anup@brainfault.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-riscv@lists.infradead.org,
	Mike Rapoport <rppt@linux.ibm.com>,
	JaeJoon Jung <rgbi3307@gmail.com>,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH] riscv: using page table index in setup_vm()
Date: Fri, 28 Jun 2019 13:41:29 +0530	[thread overview]
Message-ID: <CAAhSdy21+qPp5NGrAsxEV_pzA65qe4ER=rQZfz2RNQrs6piG5Q@mail.gmail.com> (raw)
In-Reply-To: <20190628061138.GB9834@infradead.org>

On Fri, Jun 28, 2019 at 11:41 AM Christoph Hellwig <hch@infradead.org> wrote:
>
> On Thu, Jun 27, 2019 at 11:04:56PM -0700, Paul Walmsley wrote:
> > Hi
> >
> > On Thu, 23 May 2019, JaeJoon Jung wrote:
> >
> > > Thanks for your professional advice.
> > > I'd like to take your appropriate suggestion.
> >
> > Are you planning to repost this patch with the new patch description?
>
> Note that this is going to confict with Anups bigger rework of the
> area.

Yes, it does conflict. Thanks for catching.

Refer,
https://patchwork.kernel.org/patch/10980791/

Regards,
Anup

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-06-28  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  8:48 [PATCH] riscv: using page table index in setup_vm() JaeJoon Jung
2019-05-23  9:52 ` Mike Rapoport
2019-05-23 10:12   ` JaeJoon Jung
2019-06-28  6:04     ` Paul Walmsley
2019-06-28  6:11       ` Christoph Hellwig
2019-06-28  8:11         ` Anup Patel [this message]
2019-06-28 10:38           ` JaeJoon Jung

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='CAAhSdy21+qPp5NGrAsxEV_pzA65qe4ER=rQZfz2RNQrs6piG5Q@mail.gmail.com' \
    --to=anup@brainfault.org \
    --cc=hch@infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.com \
    --cc=rgbi3307@gmail.com \
    --cc=rppt@linux.ibm.com \
    /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.