All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Valdis.Kletnieks@vt.edu, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, Nitin Gupta <ngupta@vflare.org>
Subject: Re: mmotm 2011-02-10-16-26 uploaded (zcache')
Date: Fri, 11 Feb 2011 18:47:18 -0800	[thread overview]
Message-ID: <4D55F4B6.8040801@oracle.com> (raw)
In-Reply-To: <b4feb995-1e73-4c12-8c58-ad0c2252233c@default>

On 2/11/2011 2:09 PM, Dan Magenheimer wrote:
>> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
>> Sent: Friday, February 11, 2011 2:53 PM
>> To: akpm@linux-foundation.org; Dan Magenheimer
>> Cc: mm-commits@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
>> mm@kvack.org; linux-fsdevel@vger.kernel.org
>> Subject: Re: mmotm 2011-02-10-16-26 uploaded
>>
>> On Thu, 10 Feb 2011 16:26:36 PST, akpm@linux-foundation.org said:
>>> The mm-of-the-moment snapshot 2011-02-10-16-26 has been uploaded to
>>>
>>>     http://userweb.kernel.org/~akpm/mmotm/
>>
>> CONFIG_ZCACHE=m dies a horrid death:
>
> Thanks Valdis.  A fix for this has already been posted by
> Nitin Gupta and Randy Dunlap here:
>
> https://lkml.org/lkml/2011/2/10/383
>
> Another patch for a zcache memory leak has been posted here:
>
> https://lkml.org/lkml/2011/2/10/306
>
> I'm sorry that multiple people have run into this in
> multiple trees.
> I have to admit I am a bit baffled as to what the proper
> tree flow is for bug fixes like this, but would be happy
> to "follow the process" if I am told what it is or if
> someone can point me to a document describing it.
>
> (Clearly making sure there are no bugs at all in a
> submission is the best way to go, but I'm afraid
> I can't claim to be perfect :-)

When CONFIG_SYSFS is not enabled:

mmotm-2011-0210-1626/drivers/staging/zcache/zcache.c:1608: error: 'ret' 
undeclared (first use in this function)


WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Valdis.Kletnieks@vt.edu, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, Nitin Gupta <ngupta@vflare.org>
Subject: Re: mmotm 2011-02-10-16-26 uploaded (zcache')
Date: Fri, 11 Feb 2011 18:47:18 -0800	[thread overview]
Message-ID: <4D55F4B6.8040801@oracle.com> (raw)
In-Reply-To: <b4feb995-1e73-4c12-8c58-ad0c2252233c@default>

On 2/11/2011 2:09 PM, Dan Magenheimer wrote:
>> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
>> Sent: Friday, February 11, 2011 2:53 PM
>> To: akpm@linux-foundation.org; Dan Magenheimer
>> Cc: mm-commits@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
>> mm@kvack.org; linux-fsdevel@vger.kernel.org
>> Subject: Re: mmotm 2011-02-10-16-26 uploaded
>>
>> On Thu, 10 Feb 2011 16:26:36 PST, akpm@linux-foundation.org said:
>>> The mm-of-the-moment snapshot 2011-02-10-16-26 has been uploaded to
>>>
>>>     http://userweb.kernel.org/~akpm/mmotm/
>>
>> CONFIG_ZCACHE=m dies a horrid death:
>
> Thanks Valdis.  A fix for this has already been posted by
> Nitin Gupta and Randy Dunlap here:
>
> https://lkml.org/lkml/2011/2/10/383
>
> Another patch for a zcache memory leak has been posted here:
>
> https://lkml.org/lkml/2011/2/10/306
>
> I'm sorry that multiple people have run into this in
> multiple trees.
> I have to admit I am a bit baffled as to what the proper
> tree flow is for bug fixes like this, but would be happy
> to "follow the process" if I am told what it is or if
> someone can point me to a document describing it.
>
> (Clearly making sure there are no bugs at all in a
> submission is the best way to go, but I'm afraid
> I can't claim to be perfect :-)

When CONFIG_SYSFS is not enabled:

mmotm-2011-0210-1626/drivers/staging/zcache/zcache.c:1608: error: 'ret' 
undeclared (first use in this function)

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-02-12  2:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  0:26 mmotm 2011-02-10-16-26 uploaded akpm
2011-02-11  0:26 ` akpm
2011-02-11 21:52 ` Valdis.Kletnieks
2011-02-11 22:09   ` Dan Magenheimer
2011-02-11 22:09     ` Dan Magenheimer
2011-02-12  2:47     ` Randy Dunlap [this message]
2011-02-12  2:47       ` mmotm 2011-02-10-16-26 uploaded (zcache') Randy Dunlap
2011-02-12  6:33 ` [PATCH -next/mmotm] net/can: fix softing build errors Randy Dunlap
2011-02-12 11:15   ` Kurt Van Dijck
2011-02-12 16:02     ` Randy Dunlap
2011-02-13 13:37       ` Kurt Van Dijck
2011-02-13 16:01         ` Randy Dunlap
2011-02-13 18:38           ` David Miller
2011-02-14  7:55       ` [PATCH] net/can/softing: make CAN_SOFTING_CS depend on CAN_SOFTING Kurt Van Dijck
2011-02-14 19:44         ` David Miller

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=4D55F4B6.8040801@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ngupta@vflare.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.