On Wed, Aug 16, 2017 at 1:47 AM, Dan Williams wrote:
> On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote:
>> On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote:
> [..]
>>>114 static const unsigned long
On Wed, Aug 16, 2017 at 1:47 AM, Dan Williams wrote:
> On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote:
>> On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote:
> [..]
>>>114 static const unsigned long *nd_pfn_supported_alignments(void)
>>>115 {
>>>116 /*
>>>117
On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote:
> On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote:
[..]
>>114 static const unsigned long *nd_pfn_supported_alignments(void)
>>115 {
>>116 /*
>>117 * This needs to be a
On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote:
> On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote:
[..]
>>114 static const unsigned long *nd_pfn_supported_alignments(void)
>>115 {
>>116 /*
>>117 * This needs to be a local variable because the *_SIZE
On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote:
> Hi Oliver,
>
> [auto build test ERROR on linux-nvdimm/libnvdimm-for-next]
> [also build test ERROR on v4.13-rc5 next-20170811]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve
On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote:
> Hi Oliver,
>
> [auto build test ERROR on linux-nvdimm/libnvdimm-for-next]
> [also build test ERROR on v4.13-rc5 next-20170811]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
>
Hi Oliver,
[auto build test ERROR on linux-nvdimm/libnvdimm-for-next]
[also build test ERROR on v4.13-rc5 next-20170811]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Oliver,
[auto build test ERROR on linux-nvdimm/libnvdimm-for-next]
[also build test ERROR on v4.13-rc5 next-20170811]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
From: Oliver O'Halloran
The alignment of a DAX and PFN regions dictates the page sizes that can
be used to map the region. Even if the hardware page sizes are known the
actual range of supported page sizes that can be used with DAX depends
on the kernel configuration. As a
From: Oliver O'Halloran
The alignment of a DAX and PFN regions dictates the page sizes that can
be used to map the region. Even if the hardware page sizes are known the
actual range of supported page sizes that can be used with DAX depends
on the kernel configuration. As a result it's best that
10 matches
Mail list logo