>Though it seems most of patch2 should have been in patch1 (except for the efi
>part).
OK. I will merge pstore part in patch2 to patch1.
>
> The only nitpick I have is the name 'is_non_blocking_path'. I don't know
> why, but the name doesn't seem exactly right to me. I was
> thinking
Though it seems most of patch2 should have been in patch1 (except for the efi
part).
OK. I will merge pstore part in patch2 to patch1.
The only nitpick I have is the name 'is_non_blocking_path'. I don't know
why, but the name doesn't seem exactly right to me. I was
thinking something
On Mon, Dec 17, 2012 at 08:56:27PM +, Seiji Aguchi wrote:
> Changelog v1 -> v2
> - Erase a logic checking the number of online cpus.
> - Create a patchset to fix deadlocking issue in both pstore filesystem and
>efi_pstore driver.
>- Introduce a function, is_non_blocking_path(), to
Changelog v1 -> v2
- Erase a logic checking the number of online cpus.
- Create a patchset to fix deadlocking issue in both pstore filesystem and
efi_pstore driver.
- Introduce a function, is_non_blocking_path(), to check if pstore
is in panic and emergency-restart paths (PATCH 1/2)
Changelog v1 - v2
- Erase a logic checking the number of online cpus.
- Create a patchset to fix deadlocking issue in both pstore filesystem and
efi_pstore driver.
- Introduce a function, is_non_blocking_path(), to check if pstore
is in panic and emergency-restart paths (PATCH 1/2)
On Mon, Dec 17, 2012 at 08:56:27PM +, Seiji Aguchi wrote:
Changelog v1 - v2
- Erase a logic checking the number of online cpus.
- Create a patchset to fix deadlocking issue in both pstore filesystem and
efi_pstore driver.
- Introduce a function, is_non_blocking_path(), to check if
6 matches
Mail list logo