linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Ganesh Mahendran <opensource.ganesh@gmail.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 210/397] mm/zsmalloc.c:1021:11: error: 'ZS_SIZE_CLASSES' undeclared
Date: Mon, 1 Dec 2014 09:27:03 +0900	[thread overview]
Message-ID: <20141201002703.GB11340@bbox> (raw)
In-Reply-To: <CADAEsF-FBqDFp4LjeYoTC5=nPOh7qsdb6h9kOdt2sVPhFE=z9w@mail.gmail.com>

Hello,

On Thu, Nov 27, 2014 at 10:12:49PM +0800, Ganesh Mahendran wrote:
> Hello:
> 
> I know why the build failed.
> 
> I sent patch 1 [mm/zsmalloc: avoid duplicate assignment of prev_class]
> firstly.  It was accept.
> And then I sent patch 2 [mm/zsmalloc: support allocating obj with size
> of ZS_MAX_ALLOC_SIZE]. I was accept.
> 
> But Dan Streetman <ddstreet@ieee.org> found an issue in patch 1
> [mm/zsmalloc: avoid duplicate assignment of prev_class].
> Then the first patch 1 was dropped. But the second patch was *based*
> on the first patch. So the build is failed on:
> commit: 304e521b912aa95514a5b66f7d6795d096f15535 [210/397]
> mm/zsmalloc: support allocating obj with size of ZS_MAX_ALLOC_SIZE
> which was based on patch 1.
> 
> But it is ok after the patch [mm/zsmalloc: avoid duplicate assignment
> of prev_class].
> 
> So what should I do now?

Normally, Andrew Morton is one of kind maintainers who fixes such
trivial problem by themselves but it doesn't mean we should wait
on him so what we can do is just make a fix and describe the problem
and send it to him. Other than that, he will handle.

Thanks.

- 
Kind regards,
Minchan Kim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2014-12-01  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  3:49 kbuild test robot
2014-11-27 13:13 ` Ganesh Mahendran
2014-11-27 14:12   ` Ganesh Mahendran
2014-12-01  0:27     ` Minchan Kim [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=20141201002703.GB11340@bbox \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=opensource.ganesh@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