All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Toshi Kani <toshi.kani@hp.com>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Wen Congyang <wency@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-acpi@vger.kernel.org, Len Brown <len.brown@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Jiang Liu <jiang.liu@huawei.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mgorman@suse.de>,
	David Rientjes <rientjes@google.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory
Date: Fri, 16 Nov 2012 02:02:50 +0100	[thread overview]
Message-ID: <1404902.mCy2TVRL7G@vostro.rjw.lan> (raw)
In-Reply-To: <1353026459.12509.36.camel@misato.fc.hp.com>

On Thursday, November 15, 2012 05:40:59 PM Toshi Kani wrote:
> > > Well, I have tried _really_ hard to apply this patchset, but pretty much
> > > none of the patches except for [1/7] applied for me.  I have no idea what
> > > tree they are against, but I'm pretty sure it's not my tree.
> > > 
> > > I _have_ applied patches [1-4/7] and pushed them to linux-pm.git/linux-next.
> > > I needed to fix up almost all of them so that they applied, so please check
> > > if my fixups make sense (and let me know ASAP if that's not the case).
> > > 
> > > If they are OK, please rebase the rest of the series on top of
> > > linux-pm.git/linux-next and repost.  I'm not going to take any more
> > > patches that don't apply from you.
> > > 
> > > Moreover, I'm not going to take any more ACPI memory hotplug patches
> > > for v3.8 except for the [5-7/7] from this series (after they have been
> > > rebased and _if_ they apply), so please don't submit any until the v3.8
> > > merge window closes (of course, you're free to post RFCs, but I will
> > > ignore them).
> > 
> > And by the way, if someone gives a "Reviewed-by" to a patch that _obviously_
> > doesn't apply, I will ignore any "Reviewed-by" from that person going forward,
> > because that quite obviously means you haven't even compared the patch with the
> > existing code and thus your "review" is worthless.
> 
> I was able to apply all his patches on top of the Linus's tree...

Ah, that may be because of my mistake.  Sorry about that.

I'll try again and see if that works (sigh).

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Toshi Kani <toshi.kani@hp.com>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Wen Congyang <wency@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-acpi@vger.kernel.org, Len Brown <len.brown@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Jiang Liu <jiang.liu@huawei.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mgorman@suse.de>,
	David Rientjes <rientjes@google.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory
Date: Fri, 16 Nov 2012 02:02:50 +0100	[thread overview]
Message-ID: <1404902.mCy2TVRL7G@vostro.rjw.lan> (raw)
In-Reply-To: <1353026459.12509.36.camel@misato.fc.hp.com>

On Thursday, November 15, 2012 05:40:59 PM Toshi Kani wrote:
> > > Well, I have tried _really_ hard to apply this patchset, but pretty much
> > > none of the patches except for [1/7] applied for me.  I have no idea what
> > > tree they are against, but I'm pretty sure it's not my tree.
> > > 
> > > I _have_ applied patches [1-4/7] and pushed them to linux-pm.git/linux-next.
> > > I needed to fix up almost all of them so that they applied, so please check
> > > if my fixups make sense (and let me know ASAP if that's not the case).
> > > 
> > > If they are OK, please rebase the rest of the series on top of
> > > linux-pm.git/linux-next and repost.  I'm not going to take any more
> > > patches that don't apply from you.
> > > 
> > > Moreover, I'm not going to take any more ACPI memory hotplug patches
> > > for v3.8 except for the [5-7/7] from this series (after they have been
> > > rebased and _if_ they apply), so please don't submit any until the v3.8
> > > merge window closes (of course, you're free to post RFCs, but I will
> > > ignore them).
> > 
> > And by the way, if someone gives a "Reviewed-by" to a patch that _obviously_
> > doesn't apply, I will ignore any "Reviewed-by" from that person going forward,
> > because that quite obviously means you haven't even compared the patch with the
> > existing code and thus your "review" is worthless.
> 
> I was able to apply all his patches on top of the Linus's tree...

Ah, that may be because of my mistake.  Sorry about that.

I'll try again and see if that works (sigh).

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

--
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:[~2012-11-16  0:58 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15  6:59 [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory Wen Congyang
2012-11-15  6:59 ` Wen Congyang
2012-11-15  6:59 ` [Patch v5 1/7] acpi,memory-hotplug : add memory offline code to acpi_memory_device_remove() Wen Congyang
2012-11-15  6:59   ` Wen Congyang
2012-11-15 23:03   ` David Rientjes
2012-11-15 23:03     ` David Rientjes
2012-11-15  6:59 ` [Patch v5 2/7] acpi,memory-hotplug: deal with eject request in hotplug queue Wen Congyang
2012-11-15  6:59   ` Wen Congyang
2012-11-15  9:13   ` Yasuaki Ishimatsu
2012-11-15  9:13     ` Yasuaki Ishimatsu
2012-11-15 22:09   ` Toshi Kani
2012-11-15 22:09     ` Toshi Kani
2012-11-15 23:32   ` David Rientjes
2012-11-15 23:32     ` David Rientjes
2012-11-16  1:54     ` Wen Congyang
2012-11-16  1:54       ` Wen Congyang
2012-11-15  6:59 ` [Patch v5 3/7] acpi_memhotplug.c: fix memory leak when memory device is unbound from the module acpi_memhotplug Wen Congyang
2012-11-15  6:59   ` Wen Congyang
2012-11-15  9:15   ` Yasuaki Ishimatsu
2012-11-15  9:15     ` Yasuaki Ishimatsu
2012-11-15 23:34   ` David Rientjes
2012-11-15 23:34     ` David Rientjes
2012-11-15  6:59 ` [Patch v5 4/7] acpi_memhotplug.c: free memory device if acpi_memory_enable_device() failed Wen Congyang
2012-11-15  6:59   ` Wen Congyang
2012-11-15  9:17   ` Yasuaki Ishimatsu
2012-11-15  9:17     ` Yasuaki Ishimatsu
2012-11-15  9:17     ` Yasuaki Ishimatsu
2012-11-15 23:36   ` David Rientjes
2012-11-15 23:36     ` David Rientjes
2012-11-15  6:59 ` [Patch v5 5/7] acpi_memhotplug.c: don't allow to eject the memory device if it is being used Wen Congyang
2012-11-15  6:59   ` Wen Congyang
2012-11-15  9:20   ` Yasuaki Ishimatsu
2012-11-15  9:20     ` Yasuaki Ishimatsu
2012-11-15 23:39   ` David Rientjes
2012-11-15 23:39     ` David Rientjes
2012-11-29 13:15   ` andywu106建国
2012-11-29 13:15     ` andywu106建国
2012-11-15  6:59 ` [Patch v5 6/7] acpi_memhotplug.c: bind the memory device when the driver is being loaded Wen Congyang
2012-11-15  6:59   ` Wen Congyang
2012-11-15  9:22   ` Yasuaki Ishimatsu
2012-11-15  9:22     ` Yasuaki Ishimatsu
2012-11-15  9:22     ` Yasuaki Ishimatsu
2012-11-15 23:40   ` David Rientjes
2012-11-15 23:40     ` David Rientjes
2012-11-15  6:59 ` [Patch v5 7/7] acpi_memhotplug.c: auto bind the memory device which is hotplugged before the driver is loaded Wen Congyang
2012-11-15  6:59   ` Wen Congyang
2012-11-15  9:57   ` Yasuaki Ishimatsu
2012-11-15  9:57     ` Yasuaki Ishimatsu
2012-11-15 22:45   ` Toshi Kani
2012-11-15 22:45     ` Toshi Kani
2012-11-15 22:51 ` [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory David Rientjes
2012-11-15 22:51   ` David Rientjes
2012-11-15 23:22   ` Rafael J. Wysocki
2012-11-15 23:22     ` Rafael J. Wysocki
2012-11-15 23:33     ` Rafael J. Wysocki
2012-11-15 23:33       ` Rafael J. Wysocki
2012-11-16  0:28 ` Rafael J. Wysocki
2012-11-16  0:28   ` Rafael J. Wysocki
2012-11-16  0:40   ` Rafael J. Wysocki
2012-11-16  0:40     ` Rafael J. Wysocki
2012-11-16  0:40     ` Toshi Kani
2012-11-16  0:40       ` Toshi Kani
2012-11-16  1:02       ` Rafael J. Wysocki [this message]
2012-11-16  1:02         ` Rafael J. Wysocki
2012-11-16  1:07   ` Yasuaki Ishimatsu
2012-11-16  1:07     ` Yasuaki Ishimatsu
2012-11-16  1:07     ` Yasuaki Ishimatsu
2012-11-16  1:28     ` Rafael J. Wysocki
2012-11-16  1:28       ` Rafael J. Wysocki
2012-11-16  1:31       ` Yasuaki Ishimatsu
2012-11-16  1:31         ` Yasuaki Ishimatsu
2012-11-16  1:31         ` Yasuaki Ishimatsu

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=1404902.mCy2TVRL7G@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan.kim@gmail.com \
    --cc=rientjes@google.com \
    --cc=toshi.kani@hp.com \
    --cc=wency@cn.fujitsu.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.