Re: [PATCH] i2c: octeon: Prevent error message on bus error

2018-03-02 Thread Phil Pokorny
On Fri, Mar 2, 2018 at 2:11 AM, Wolfram Sang wrote: > > On Tue, Feb 27, 2018 at 04:42:13PM +0100, Jan Glauber wrote: > > The error message: > > > > [Fri Feb 16 13:42:13 2018] i2c-thunderx :01:09.4: unhandled state: 0 > > > > is mis-leading as state 0 (bus error) is not an

Re: [PATCH] i2c: octeon: Prevent error message on bus error

2018-03-02 Thread Phil Pokorny
On Fri, Mar 2, 2018 at 2:11 AM, Wolfram Sang wrote: > > On Tue, Feb 27, 2018 at 04:42:13PM +0100, Jan Glauber wrote: > > The error message: > > > > [Fri Feb 16 13:42:13 2018] i2c-thunderx :01:09.4: unhandled state: 0 > > > > is mis-leading as state 0 (bus error) is not an unknown state. > > >

Re: [lm-sensors] [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128.

2015-10-13 Thread Phil Pokorny
On Tue, Oct 13, 2015 at 1:31 PM, Guenter Roeck wrote: > > On Mon, Oct 12, 2015 at 01:53:32PM +0200, Lukasz Odzioba wrote: > > A new limit selected arbitrarily as power of two greater than > > required minimum for Xeon Phi processor. > Why 128 instead of a more reasonable 64 ? What is the

Re: [lm-sensors] [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128.

2015-10-13 Thread Phil Pokorny
On Tue, Oct 13, 2015 at 1:31 PM, Guenter Roeck wrote: > > On Mon, Oct 12, 2015 at 01:53:32PM +0200, Lukasz Odzioba wrote: > > A new limit selected arbitrarily as power of two greater than > > required minimum for Xeon Phi processor. > Why 128 instead of a more reasonable 64 ?

Re: [Linux-nvdimm] [PATCH v2 11/20] libnd, nd_pmem: add libnd support to the pmem driver

2015-04-28 Thread Phil Pokorny
On Tue, Apr 28, 2015 at 3:58 PM, Andy Lutomirski wrote: > On Tue, Apr 28, 2015 at 3:21 PM, Phil Pokorny > wrote: >> On Tue, Apr 28, 2015 at 2:04 PM, Andy Lutomirski wrote: >>> On Tue, Apr 28, 2015 at 11:25 AM, Dan Williams >>> wrote: >>>> +config ND

Re: [Linux-nvdimm] [PATCH v2 11/20] libnd, nd_pmem: add libnd support to the pmem driver

2015-04-28 Thread Phil Pokorny
On Tue, Apr 28, 2015 at 2:04 PM, Andy Lutomirski wrote: > On Tue, Apr 28, 2015 at 11:25 AM, Dan Williams > wrote: >> +config ND_E820 >> + tristate "E820: Support the E820-type-12 PMEM convention" >> + depends on X86_PMEM_LEGACY >> + default m if X86_PMEM_LEGACY >> +

Re: [Linux-nvdimm] [PATCH v2 11/20] libnd, nd_pmem: add libnd support to the pmem driver

2015-04-28 Thread Phil Pokorny
On Tue, Apr 28, 2015 at 3:58 PM, Andy Lutomirski l...@amacapital.net wrote: On Tue, Apr 28, 2015 at 3:21 PM, Phil Pokorny ppoko...@penguincomputing.com wrote: On Tue, Apr 28, 2015 at 2:04 PM, Andy Lutomirski l...@amacapital.net wrote: On Tue, Apr 28, 2015 at 11:25 AM, Dan Williams dan.j.willi

Re: [Linux-nvdimm] [PATCH v2 11/20] libnd, nd_pmem: add libnd support to the pmem driver

2015-04-28 Thread Phil Pokorny
On Tue, Apr 28, 2015 at 2:04 PM, Andy Lutomirski l...@amacapital.net wrote: On Tue, Apr 28, 2015 at 11:25 AM, Dan Williams dan.j.willi...@intel.com wrote: +config ND_E820 + tristate E820: Support the E820-type-12 PMEM convention + depends on X86_PMEM_LEGACY + default m if

Re: [lm-sensors] [PATCH 1/4] kernel.h: add find_closest() macro

2015-02-24 Thread Phil Pokorny
On Tue, Feb 24, 2015 at 9:42 AM, Bartosz Golaszewski wrote: > > Searching for the member of an array closest to 'x' is > duplicated in several places. > > Add two macros that implement this algorithm for arrays > sorted both in ascending and descending order. I don't see the point here. You're

Re: [lm-sensors] [PATCH 1/4] kernel.h: add find_closest() macro

2015-02-24 Thread Phil Pokorny
On Tue, Feb 24, 2015 at 9:42 AM, Bartosz Golaszewski bgolaszew...@baylibre.com wrote: Searching for the member of an array closest to 'x' is duplicated in several places. Add two macros that implement this algorithm for arrays sorted both in ascending and descending order. I don't see the