Hi Rafael,
2013/04/02 21:57, Rafael J. Wysocki wrote:
On Tuesday, April 02, 2013 09:12:44 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/04/02 8:48, Rafael J. Wysocki wrote:
On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
On Tuesday, April 02, 2013 09:12:44 AM Yasuaki Ishimatsu wrote:
> Hi Rafael,
>
> 2013/04/02 8:48, Rafael J. Wysocki wrote:
> > On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
> >> Hi Rafael,
> >>
> >> 2013/03/26 22:41, Rafael J. Wysocki wrote:
> >>> On Tuesday, March 26, 2013
On Tuesday, April 02, 2013 09:12:44 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/04/02 8:48, Rafael J. Wysocki wrote:
On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki
Hi Rafael,
2013/04/02 21:57, Rafael J. Wysocki wrote:
On Tuesday, April 02, 2013 09:12:44 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/04/02 8:48, Rafael J. Wysocki wrote:
On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
Hi Rafael,
2013/04/02 8:48, Rafael J. Wysocki wrote:
On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22
On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
> Hi Rafael,
>
> 2013/03/26 22:41, Rafael J. Wysocki wrote:
> > On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
> >> 2013/03/23 5:24, Toshi Kani wrote:
> >>> On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu
On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/04/02 8:48, Rafael J. Wysocki wrote:
On Thursday, March 28, 2013 08:58:03 AM Yasuaki Ishimatsu wrote:
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug.
Hi Rafael,
2013/03/26 22:41, Rafael J. Wysocki wrote:
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug.
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
> 2013/03/23 5:24, Toshi Kani wrote:
> > On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
> >> acpi_memory_info has enabled bit and failed bit for controlling memory
> >> hotplug. But we don't need to keep both bits.
> >>
>
On Tuesday, March 26, 2013 08:57:05 AM Yasuaki Ishimatsu wrote:
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug. But we don't need to keep both bits.
The patch
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug. But we don't need to keep both bits.
The patch removes acpi_memory_info->failed bit.
Signed-off-by: yasuaki ishimatsu
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug. But we don't need to keep both bits.
The patch removes acpi_memory_info-failed bit.
Signed-off-by: yasuaki ishimatsu
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
> acpi_memory_info has enabled bit and failed bit for controlling memory
> hotplug. But we don't need to keep both bits.
>
> The patch removes acpi_memory_info->failed bit.
>
> Signed-off-by: yasuaki ishimatsu
Thanks for the update.
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug. But we don't need to keep both bits.
The patch removes acpi_memory_info-failed bit.
Signed-off-by: yasuaki ishimatsu isimatu.yasu...@jp.fujitsu.com
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug. But we don't need to keep both bits.
The patch removes acpi_memory_info->failed bit.
Signed-off-by: yasuaki ishimatsu
---
v3 : Continue to memory hot remove when (!info->enabled) case.
v2 : Changed a based kernel
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug. But we don't need to keep both bits.
The patch removes acpi_memory_info-failed bit.
Signed-off-by: yasuaki ishimatsu isimatu.yasu...@jp.fujitsu.com
---
v3 : Continue to memory hot remove when (!info-enabled) case.
18 matches
Mail list logo