linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jongseok Kim <ks77sj@gmail.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Jongseok Kim <ks77sj@gmail.com>
Subject: Re: [PATCH] z3fold: fix wrong handling of headless pages
Date: Thu,  8 Nov 2018 22:45:40 +0900	[thread overview]
Message-ID: <20181108134540.12756-1-ks77sj@gmail.com> (raw)
In-Reply-To: <CAMJBoFP3C5NffHf2bPaY-W2qXPLs6z+Ker+Z+Sq_3MHV5xekHQ@mail.gmail.com>

Yes, you are right.
I think that's the best way to deal it.
Thank you.

Best regards,
Jongseok

> Den tors 8 nov. 2018 kl 13:34 skrev +-eA 3/4  1/4 (R) <ks77sj@gmail.com>:
> >
> > Hi Vitaly,
> > thank you for the reply.
> >
> > I agree your a new solution is more comprehensive and drop my patch is simple way.
> > But, I think it's not fair.
> > If my previous patch was not wrong, is (my patch -> your patch) the right way?

> I could apply the new patch on top of yours but that would effectively
> revert most of your changes.
> Would it be ok for you if I add you to Signed-off-by for the new patch instead?

> ~Vitaly


> > I'm sorry I sent reply twice.
> >
> > Best regards,
> > Jongseok
> >
> >
> > > On 6/11/2018 4:48 PM, Vitaly Wool wrote:
> > > Hi Jongseok,
> >
> > > thank you for your work, we've now got a more comprehensive solution:
> > > https://lkml.org/lkml/2018/11/5/726
> >
> > > Would you please confirm that it works for you? Also, would you be
> > >okay with dropping your patch in favor of the new one?
> >
> > > ~Vitaly

  reply	other threads:[~2018-11-08 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06  5:10 [PATCH] z3fold: fix wrong handling of headless pages Jongseok Kim
2018-11-06  7:48 ` Vitaly Wool
2018-11-08 12:26   ` 김종석
2018-11-08 12:34   ` 김종석
2018-11-08 12:57     ` Vitaly Wool
2018-11-08 13:45       ` Jongseok Kim [this message]
2018-11-08 22:23         ` Andrew Morton
2018-11-08 22:33           ` Vitaly Wool

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=20181108134540.12756-1-ks77sj@gmail.com \
    --to=ks77sj@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vitalywool@gmail.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 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).