investicni

Ahoj, Jsem zastupujici investicni zajem ze strany Dubaji, pro ktere se snazime svou ucast jako v zamori zastupce. Odpoved na e-mailu nize v pripade zajmu. E-mail: philp...@gmail.com

investicni

Ahoj, Jsem zastupujici investicni zajem ze strany Dubaji, pro ktere se snazime svou ucast jako v zamori zastupce. Odpoved na e-mailu nize v pripade zajmu. E-mail: philp...@gmail.com

Re: [PATCH v2 05/11] dt-bindings: Add bindings for phy-da8xx-usb

On 03/23/2016 12:06 PM, Sekhar Nori wrote: On Thursday 17 March 2016 07:56 AM, David Lechner wrote: Device tree binding for new phy-da8xx-usb driver. Signed-off-by: David Lechner --- v2 changes: This is new patch in v2. .../devicetree/bindings/phy/phy-da8xx-usb.txt

Re: [PATCH v2 05/11] dt-bindings: Add bindings for phy-da8xx-usb

On 03/23/2016 12:06 PM, Sekhar Nori wrote: On Thursday 17 March 2016 07:56 AM, David Lechner wrote: Device tree binding for new phy-da8xx-usb driver. Signed-off-by: David Lechner --- v2 changes: This is new patch in v2. .../devicetree/bindings/phy/phy-da8xx-usb.txt | 34

Re: [PATCH v2 04/11] ARM: davinci: da8xx: add usb phy clocks

On Wednesday 23 March 2016 11:15 PM, David Lechner wrote: > On 03/23/2016 11:56 AM, Sekhar Nori wrote: >>> >>> +static struct clk usb_ref_clk = { >>> +.name= "usb_ref_clk", >>> +.rate= 4800, >>> +.set_rate= davinci_simple_set_rate, >>> +}; >> >> can we call this

Re: [PATCH v2 04/11] ARM: davinci: da8xx: add usb phy clocks

On Wednesday 23 March 2016 11:15 PM, David Lechner wrote: > On 03/23/2016 11:56 AM, Sekhar Nori wrote: >>> >>> +static struct clk usb_ref_clk = { >>> +.name= "usb_ref_clk", >>> +.rate= 4800, >>> +.set_rate= davinci_simple_set_rate, >>> +}; >> >> can we call this

RE: [PATCH] staging: comedi: drivers: remove bogus ni_mio_c_common.c

On Wednesday, March 23, 2016 3:55 AM, Ian Abbott wrote: > The zero-length file "ni_mio_c_common.c" was inadvertantly created by > commit e563637b5fef ("staging: comedi: Use ARRAY_SIZE for sizes of > arrays"). Remove it. > > Signed-off-by: Ian Abbott > --- >

RE: [PATCH] staging: comedi: drivers: remove bogus ni_mio_c_common.c

On Wednesday, March 23, 2016 3:55 AM, Ian Abbott wrote: > The zero-length file "ni_mio_c_common.c" was inadvertantly created by > commit e563637b5fef ("staging: comedi: Use ARRAY_SIZE for sizes of > arrays"). Remove it. > > Signed-off-by: Ian Abbott > --- >

Re: [PATCH 2/5] perf core: Set event's default overflow_handler

On Mon, Mar 14, 2016 at 09:59:42AM +, Wang Nan wrote: > +++ b/arch/arm/kernel/hw_breakpoint.c > @@ -631,7 +631,7 @@ int arch_validate_hwbkpt_settings(struct perf_event *bp) > info->address &= ~alignment_mask; > info->ctrl.len <<= offset; > > - if (!bp->overflow_handler) { > +

Re: [PATCH 2/5] perf core: Set event's default overflow_handler

On Mon, Mar 14, 2016 at 09:59:42AM +, Wang Nan wrote: > +++ b/arch/arm/kernel/hw_breakpoint.c > @@ -631,7 +631,7 @@ int arch_validate_hwbkpt_settings(struct perf_event *bp) > info->address &= ~alignment_mask; > info->ctrl.len <<= offset; > > - if (!bp->overflow_handler) { > +

RE: [NEW DRIVER V6 0/7] DA9058 PMIC - please comment on this new driver

> On 23 March 2016, Alexandre Belloni wrote: > > Subject: Re: [NEW DRIVER V6 0/7] DA9058 PMIC - please comment on this new > > driver > > > > Hi Anthony, Steve, > > > > This driver has been submitted a while ago and reached v6 but still had > > a few comments. Do you still have some interest in

RE: [NEW DRIVER V6 0/7] DA9058 PMIC - please comment on this new driver

> On 23 March 2016, Alexandre Belloni wrote: > > Subject: Re: [NEW DRIVER V6 0/7] DA9058 PMIC - please comment on this new > > driver > > > > Hi Anthony, Steve, > > > > This driver has been submitted a while ago and reached v6 but still had > > a few comments. Do you still have some interest in

Re: [PATCH v2 04/11] ARM: davinci: da8xx: add usb phy clocks

On 03/23/2016 11:56 AM, Sekhar Nori wrote: +static struct clk usb_ref_clk = { + .name = "usb_ref_clk", + .rate = 4800, + .set_rate = davinci_simple_set_rate, +}; can we call this usb_refclkin so it matches the TRM name? Also, should this node be

Re: [PATCH v2 04/11] ARM: davinci: da8xx: add usb phy clocks

On 03/23/2016 11:56 AM, Sekhar Nori wrote: +static struct clk usb_ref_clk = { + .name = "usb_ref_clk", + .rate = 4800, + .set_rate = davinci_simple_set_rate, +}; can we call this usb_refclkin so it matches the TRM name? Also, should this node be

Re: [PATCH 1/2] net: ethernet: dlink: dl2k: fix code style

Such cleanups and tidies are not appropriate to be submitted at this time. Only bug fixes should be going into the tree right now.

Re: [PATCH 1/2] net: ethernet: dlink: dl2k: fix code style

Such cleanups and tidies are not appropriate to be submitted at this time. Only bug fixes should be going into the tree right now.

Re: [PATCH] net: phy: at803x: Request 'reset' GPIO only for AT8030 PHY

From: Sebastian Frias Date: Wed, 23 Mar 2016 11:49:09 +0100 > This removes the dependency on GPIOLIB for non faulty PHYs. > > Indeed, without this patch, if GPIOLIB is not selected > devm_gpiod_get_optional() will return -ENOSYS and the driver probe > call will fail,

Re: Nonterministic hang during bootconsole/console handover on ath79

On 03/22/2016 04:38 PM, Peter Hurley wrote: > On 03/22/2016 06:07 AM, Matthias Schiffer wrote: >> I've tried your patch and I can't reproduce the issue anymore with it; I >> have no idea if this actually has to do something with the issue, or the >> change of the code path just hid the bug again.

Re: [PATCH] net: phy: at803x: Request 'reset' GPIO only for AT8030 PHY

From: Sebastian Frias Date: Wed, 23 Mar 2016 11:49:09 +0100 > This removes the dependency on GPIOLIB for non faulty PHYs. > > Indeed, without this patch, if GPIOLIB is not selected > devm_gpiod_get_optional() will return -ENOSYS and the driver probe > call will fail, regardless of the actual

Re: Nonterministic hang during bootconsole/console handover on ath79

On 03/22/2016 04:38 PM, Peter Hurley wrote: > On 03/22/2016 06:07 AM, Matthias Schiffer wrote: >> I've tried your patch and I can't reproduce the issue anymore with it; I >> have no idea if this actually has to do something with the issue, or the >> change of the code path just hid the bug again.

Re: net/sctp: stack-out-of-bounds in sctp_getsockopt

On Thu, Mar 24, 2016 at 12:42:43AM +0800, Baozeng wrote: > 2016-03-22 23:27 GMT+08:00 Eric Dumazet : > > Untested patch would be : > > > > diff --git a/net/bridge/netfilter/ebtables.c > > b/net/bridge/netfilter/ebtables.c > > index 67b2e27999aa..fceb7354d169 100644 > > ---

Re: net/sctp: stack-out-of-bounds in sctp_getsockopt

On Thu, Mar 24, 2016 at 12:42:43AM +0800, Baozeng wrote: > 2016-03-22 23:27 GMT+08:00 Eric Dumazet : > > Untested patch would be : > > > > diff --git a/net/bridge/netfilter/ebtables.c > > b/net/bridge/netfilter/ebtables.c > > index 67b2e27999aa..fceb7354d169 100644 > > ---

Re: [PATCH 2/2] drivers: net: ethernet: dlink: dl2k: fix indent

If dl2k is modified at all, maybe convert the printks to netdev_ too so that the logging output is more like other networking drivers. Something like: ---  drivers/net/ethernet/dlink/dl2k.c | 181 +-  1 file changed, 100 insertions(+), 81 deletions(-) diff

Re: [PATCH 2/2] drivers: net: ethernet: dlink: dl2k: fix indent

If dl2k is modified at all, maybe convert the printks to netdev_ too so that the logging output is more like other networking drivers. Something like: ---  drivers/net/ethernet/dlink/dl2k.c | 181 +-  1 file changed, 100 insertions(+), 81 deletions(-) diff

Re: [PATCH] x86/mce: Avoid using object after free in genpool.

On Wed, Mar 23, 2016 at 09:14:40AM -0700, Tony Luck wrote: > When we loop over all queued machine check error records to pass > them to the registered notifiers we use llist_for_each_entry(). > But the loop calls gen_pool_free() for the entry in the body of > the loop - and then the iterator looks

Re: [PATCH] x86/mce: Avoid using object after free in genpool.

On Wed, Mar 23, 2016 at 09:14:40AM -0700, Tony Luck wrote: > When we loop over all queued machine check error records to pass > them to the registered notifiers we use llist_for_each_entry(). > But the loop calls gen_pool_free() for the entry in the body of > the loop - and then the iterator looks

[PATCH 2/2] HID: corsair: Add K40 support

The Corsair K40 uses the same usage codes as the K90 for its special keys (although it has only 6 G-keys). Signed-off-by: Clément Vuchener --- drivers/hid/hid-core.c| 1 + drivers/hid/hid-corsair.c | 1 + drivers/hid/hid-ids.h | 1 + 3 files changed, 3

[PATCH 1/2] HID: corsair: Remove all features using the USB protocol

Remove every use of USB control requests since it can be more easily done in user space. This removes the dependency on USB and LED subsystems. The simplyfied driver now only remaps Corsair usage codes. Signed-off-by: Clément Vuchener ---

[PATCH 2/2] HID: corsair: Add K40 support

The Corsair K40 uses the same usage codes as the K90 for its special keys (although it has only 6 G-keys). Signed-off-by: Clément Vuchener --- drivers/hid/hid-core.c| 1 + drivers/hid/hid-corsair.c | 1 + drivers/hid/hid-ids.h | 1 + 3 files changed, 3 insertions(+) diff --git

[PATCH 1/2] HID: corsair: Remove all features using the USB protocol

Remove every use of USB control requests since it can be more easily done in user space. This removes the dependency on USB and LED subsystems. The simplyfied driver now only remaps Corsair usage codes. Signed-off-by: Clément Vuchener --- Documentation/ABI/testing/sysfs-driver-hid-corsair |

[PATCH 0/2] hid: corsair: Driver simplification and new supported device

I tried to add support for the K40 some time ago, but the vendor specific USB protocol became over-complicated because of a lot of small differences between the K90 and the K40. Also, since I wrote the first version of this driver, I learned that USB control transfers could be done from

[PATCH 0/2] hid: corsair: Driver simplification and new supported device

I tried to add support for the K40 some time ago, but the vendor specific USB protocol became over-complicated because of a lot of small differences between the K90 and the K40. Also, since I wrote the first version of this driver, I learned that USB control transfers could be done from

Re: [PATCH v2 03/11] ARM: davinci: da850: use clk->set_parent for async3

On Wednesday 23 March 2016 10:50 PM, David Lechner wrote: > On 03/23/2016 10:56 AM, Sekhar Nori wrote: >> On Thursday 17 March 2016 07:56 AM, David Lechner wrote: >>> The da850 family of processors has an async3 clock domain that can be >>> muxed to either pll0_sysclk2 or pll1_sysclk2. Now that

Re: [PATCH v2 03/11] ARM: davinci: da850: use clk->set_parent for async3

On Wednesday 23 March 2016 10:50 PM, David Lechner wrote: > On 03/23/2016 10:56 AM, Sekhar Nori wrote: >> On Thursday 17 March 2016 07:56 AM, David Lechner wrote: >>> The da850 family of processors has an async3 clock domain that can be >>> muxed to either pll0_sysclk2 or pll1_sysclk2. Now that

Re: [PATCH] i2c: Prevent endless uevent loop with dev_dbg

On Wed, Mar 23, 2016 at 05:50:33PM +0100, Wolfram Sang wrote: > On Wed, Mar 23, 2016 at 04:50:47PM +0100, Jan Glauber wrote: > > After enabling CONFIG_I2C_DEBUG_CORE my system was broken > > (no network, console login not possible). System log was > > flooded with the this message: > > > > ... >

Re: [PATCH] i2c: Prevent endless uevent loop with dev_dbg

On Wed, Mar 23, 2016 at 05:50:33PM +0100, Wolfram Sang wrote: > On Wed, Mar 23, 2016 at 04:50:47PM +0100, Jan Glauber wrote: > > After enabling CONFIG_I2C_DEBUG_CORE my system was broken > > (no network, console login not possible). System log was > > flooded with the this message: > > > > ... >

Re: [PATCH v2 00/11] da8xx USB clocks

Hi David, On Thursday 17 March 2016 07:09 PM, Sergei Shtylyov wrote: > On 3/17/2016 5:26 AM, David Lechner wrote: > >> OK, ready for round two. > >You're quick... :-) > >> I've added a new callback in the davinci clocks so that they can properly >> handle clock muxing. The clock functions

Re: [PATCH v2 00/11] da8xx USB clocks

Hi David, On Thursday 17 March 2016 07:09 PM, Sergei Shtylyov wrote: > On 3/17/2016 5:26 AM, David Lechner wrote: > >> OK, ready for round two. > >You're quick... :-) > >> I've added a new callback in the davinci clocks so that they can properly >> handle clock muxing. The clock functions

Re: linux-next: Tree for Mar 23 (infiniband: mlx5)

On 03/22/16 19:22, Stephen Rothwell wrote: > Hi all, > > Please do not add any v4.7 related material to your linux-next included > trees until after v4.6-rc1 is released. > > Changes since 20160322: > on i386 or x86_64: ../drivers/infiniband/hw/mlx5/main.c: In function 'mlx5_ib_add':

Re: linux-next: Tree for Mar 23 (infiniband: mlx5)

On 03/22/16 19:22, Stephen Rothwell wrote: > Hi all, > > Please do not add any v4.7 related material to your linux-next included > trees until after v4.6-rc1 is released. > > Changes since 20160322: > on i386 or x86_64: ../drivers/infiniband/hw/mlx5/main.c: In function 'mlx5_ib_add':

Re: [PATCH 1/2] Disable UV BAU by default

On Wed, Mar 23, 2016 at 06:20:26PM +0100, Thomas Gleixner wrote: > On Wed, 23 Mar 2016, Alex Thorlton wrote: > > This was actually what I initially wrote, but we decided to go with the > > on/off switch instead, because, in the UV4 time-frame, we're hoping to > > get a few things changed so that

Re: [PATCH 1/2] Disable UV BAU by default

On Wed, Mar 23, 2016 at 06:20:26PM +0100, Thomas Gleixner wrote: > On Wed, 23 Mar 2016, Alex Thorlton wrote: > > This was actually what I initially wrote, but we decided to go with the > > on/off switch instead, because, in the UV4 time-frame, we're hoping to > > get a few things changed so that

Re: [PATCH v2 06/11] phy: da8xx-usb: new driver for DA8XX SoC USB PHY

On Thursday 17 March 2016 07:56 AM, David Lechner wrote: > This is a new phy driver for the SoC USB controllers on the TI DA8XX > family of microcontrollers. The USB 1.1 PHY is just a simple on/off. > The USB 2.0 PHY also allows overriding the VBUS and ID pins. > > Signed-off-by: David Lechner

Re: [PATCH v2 06/11] phy: da8xx-usb: new driver for DA8XX SoC USB PHY

On Thursday 17 March 2016 07:56 AM, David Lechner wrote: > This is a new phy driver for the SoC USB controllers on the TI DA8XX > family of microcontrollers. The USB 1.1 PHY is just a simple on/off. > The USB 2.0 PHY also allows overriding the VBUS and ID pins. > > Signed-off-by: David Lechner

Re: [PATCH 1/2] Disable UV BAU by default

On Wed, 23 Mar 2016, Alex Thorlton wrote: > This was actually what I initially wrote, but we decided to go with the > on/off switch instead, because, in the UV4 time-frame, we're hoping to > get a few things changed so that we can default to having the bau *on* > for the new UV4 systems. > > I

Re: [PATCH 1/2] Disable UV BAU by default

On Wed, 23 Mar 2016, Alex Thorlton wrote: > This was actually what I initially wrote, but we decided to go with the > on/off switch instead, because, in the UV4 time-frame, we're hoping to > get a few things changed so that we can default to having the bau *on* > for the new UV4 systems. > > I

Re: [PATCH v2 03/11] ARM: davinci: da850: use clk->set_parent for async3

On 03/23/2016 10:56 AM, Sekhar Nori wrote: On Thursday 17 March 2016 07:56 AM, David Lechner wrote: The da850 family of processors has an async3 clock domain that can be muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the davinci clocks have a set_parent callback, we can use this to

Re: [PATCH v2 03/11] ARM: davinci: da850: use clk->set_parent for async3

On 03/23/2016 10:56 AM, Sekhar Nori wrote: On Thursday 17 March 2016 07:56 AM, David Lechner wrote: The da850 family of processors has an async3 clock domain that can be muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the davinci clocks have a set_parent callback, we can use this to

[GIT PULL] platform-drivers-x86 for 4.6-1

Hi Linus, The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at: git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git tags/platform-drivers-x86-v4.6-1 for you to fetch

[GIT PULL] platform-drivers-x86 for 4.6-1

Hi Linus, The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at: git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git tags/platform-drivers-x86-v4.6-1 for you to fetch

Re: [PATCH] net: Fix typos and whitespace.

On 03/23/2016 03:55 PM, Bjorn Helgaas wrote: [+cc Vlad] On Wed, Mar 23, 2016 at 08:45:30AM -0500, Bjorn Helgaas wrote: Fix typos. Capitalize CPU, NAPI, RCU consistently. Align structure indentation. No functional change intended; only comment and whitespace changes. Signed-off-by: Bjorn

Re: [PATCH] net: Fix typos and whitespace.

On 03/23/2016 03:55 PM, Bjorn Helgaas wrote: [+cc Vlad] On Wed, Mar 23, 2016 at 08:45:30AM -0500, Bjorn Helgaas wrote: Fix typos. Capitalize CPU, NAPI, RCU consistently. Align structure indentation. No functional change intended; only comment and whitespace changes. Signed-off-by: Bjorn

RE: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17

Hi Paul, On 2016-03-22, Paul E. McKenney wrote: > On Tue, Mar 22, 2016 at 09:04:47PM +, Chatre, Reinette wrote: >> On 2016-03-22, Paul E. McKenney wrote: >>> You set CONFIG_RCU_CPU_STALL_TIMEOUT=60, which matches the 60004 >>> jiffies above. Is that value due to a distro setting or

RE: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17

Hi Paul, On 2016-03-22, Paul E. McKenney wrote: > On Tue, Mar 22, 2016 at 09:04:47PM +, Chatre, Reinette wrote: >> On 2016-03-22, Paul E. McKenney wrote: >>> You set CONFIG_RCU_CPU_STALL_TIMEOUT=60, which matches the 60004 >>> jiffies above. Is that value due to a distro setting or

Re: net/sctp: stack-out-of-bounds in sctp_getsockopt

On Thu, 2016-03-24 at 00:42 +0800, Baozeng wrote: > Thanks for your quick patch. I tested it but it still reproduce the > bug. We should limit the length of the name, > not the prefix. The following patch fixs it. > > diff --git a/net/bridge/netfilter/ebtables.c b/net/bridge/netfilter/ebtables.c

Re: net/sctp: stack-out-of-bounds in sctp_getsockopt

On Thu, 2016-03-24 at 00:42 +0800, Baozeng wrote: > Thanks for your quick patch. I tested it but it still reproduce the > bug. We should limit the length of the name, > not the prefix. The following patch fixs it. > > diff --git a/net/bridge/netfilter/ebtables.c b/net/bridge/netfilter/ebtables.c

Re: [PATCH v2 05/11] dt-bindings: Add bindings for phy-da8xx-usb

On Thursday 17 March 2016 07:56 AM, David Lechner wrote: > Device tree binding for new phy-da8xx-usb driver. > > Signed-off-by: David Lechner > --- > > v2 changes: This is new patch in v2. > > > .../devicetree/bindings/phy/phy-da8xx-usb.txt | 34 >

Re: [PATCH v2 05/11] dt-bindings: Add bindings for phy-da8xx-usb

On Thursday 17 March 2016 07:56 AM, David Lechner wrote: > Device tree binding for new phy-da8xx-usb driver. > > Signed-off-by: David Lechner > --- > > v2 changes: This is new patch in v2. > > > .../devicetree/bindings/phy/phy-da8xx-usb.txt | 34 > ++ > 1 file

[PATCH v2] usb: gadget: f_midi: fixed a bug when buflen was smaller than wMaxPacketSize

buflen by default (256) is smaller than wMaxPacketSize (512) in high-speed devices. That caused the OUT endpoint to freeze if the host send any data packet of length greater than 256 bytes. This is an example dump of what happended on that enpoint: HOST: [DATA][Length=260][...] DEVICE: [NAK]

[PATCH v2] usb: gadget: f_midi: fixed a bug when buflen was smaller than wMaxPacketSize

buflen by default (256) is smaller than wMaxPacketSize (512) in high-speed devices. That caused the OUT endpoint to freeze if the host send any data packet of length greater than 256 bytes. This is an example dump of what happended on that enpoint: HOST: [DATA][Length=260][...] DEVICE: [NAK]

Be a Mystery Shopper and Earn

Hello, Our Organization is out to seek people who are Ready to Evaluate Businesses on our behalf and earn money at the time. To be part of this Mystery Shopping fill the form below: 1. Names 2.Address 3.Occupation 4.Phone/Cell 5.Age 6.E-mail address Thanks as you respond accordingly.

Be a Mystery Shopper and Earn

Hello, Our Organization is out to seek people who are Ready to Evaluate Businesses on our behalf and earn money at the time. To be part of this Mystery Shopping fill the form below: 1. Names 2.Address 3.Occupation 4.Phone/Cell 5.Age 6.E-mail address Thanks as you respond accordingly.

[PATCH 1/1] gpio: mcp23s08: Add support for level triggered interrupts

The interrupt for the corresponding pin is configured to trigger when the pin state changes compared to a preconfigured state (Bit set in INTCON). This state is set by setting/clearing the bit in DEFVAL. In the interrupt handler we need also to check if the bit in INTCON is set for level triggered

[PATCH 1/1] gpio: mcp23s08: Add support for level triggered interrupts

The interrupt for the corresponding pin is configured to trigger when the pin state changes compared to a preconfigured state (Bit set in INTCON). This state is set by setting/clearing the bit in DEFVAL. In the interrupt handler we need also to check if the bit in INTCON is set for level triggered

Re: [PATCH v2 04/11] ARM: davinci: da8xx: add usb phy clocks

On Thursday 17 March 2016 07:56 AM, David Lechner wrote: > Up to this point, the USB phy clock configuration was handled manually in > the board files and in the usb drivers. This adds proper clocks so that > the usb drivers can use clk_get and clk_enable and not have to worry about > the details.

Re: [PATCH v2 04/11] ARM: davinci: da8xx: add usb phy clocks

On Thursday 17 March 2016 07:56 AM, David Lechner wrote: > Up to this point, the USB phy clock configuration was handled manually in > the board files and in the usb drivers. This adds proper clocks so that > the usb drivers can use clk_get and clk_enable and not have to worry about > the details.

Re: [PATCH] tpm: drop the field 'time_expired' from struct tpm_chip

On Wed, Mar 23, 2016 at 08:23:39AM +0200, Jarkko Sakkinen wrote: > Removed the field because it is not used for anything. Reviewed-by: Jason Gunthorpe Jason

Re: [PATCH] tpm: drop the field 'time_expired' from struct tpm_chip

On Wed, Mar 23, 2016 at 08:23:39AM +0200, Jarkko Sakkinen wrote: > Removed the field because it is not used for anything. Reviewed-by: Jason Gunthorpe Jason

[PATCH] x86/mce: Avoid using object after free in genpool.

When we loop over all queued machine check error records to pass them to the registered notifiers we use llist_for_each_entry(). But the loop calls gen_pool_free() for the entry in the body of the loop - and then the iterator looks at node->next after the free. Use llist_for_each_entry_safe()

[PATCH] x86/mce: Avoid using object after free in genpool.

When we loop over all queued machine check error records to pass them to the registered notifiers we use llist_for_each_entry(). But the loop calls gen_pool_free() for the entry in the body of the loop - and then the iterator looks at node->next after the free. Use llist_for_each_entry_safe()

Re: [PATCH] net: mlxsw: avoid unused variable warnings

On Wed, Mar 23, 2016 at 05:37:38PM +0100, Arnd Bergmann wrote: > dev_dbg_ratelimited() is a macro that ignores its arguments when DEBUG is > not set, which can lead to unused variable warnings: > > ethernet/mellanox/mlxsw/pci.c: In function 'mlxsw_pci_cqe_sdq_handle': >

Re: [PATCH] net: mlxsw: avoid unused variable warnings

On Wed, Mar 23, 2016 at 05:37:38PM +0100, Arnd Bergmann wrote: > dev_dbg_ratelimited() is a macro that ignores its arguments when DEBUG is > not set, which can lead to unused variable warnings: > > ethernet/mellanox/mlxsw/pci.c: In function 'mlxsw_pci_cqe_sdq_handle': >

[PATCH v3 08/19] ARM: sun5i: Add DRAM gates

The DRAM gates control whether the image / display devices on the SoC have access to the DRAM clock or not. Enable it. Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun5i-a13.dtsi | 22 +- arch/arm/boot/dts/sun5i-r8.dtsi | 2 +- 2

[PATCH v3 08/19] ARM: sun5i: Add DRAM gates

The DRAM gates control whether the image / display devices on the SoC have access to the DRAM clock or not. Enable it. Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun5i-a13.dtsi | 22 +- arch/arm/boot/dts/sun5i-r8.dtsi | 2 +- 2 files changed, 22 insertions(+), 2

Re: [PATCH] i2c: Prevent endless uevent loop with dev_dbg

On Wed, Mar 23, 2016 at 04:50:47PM +0100, Jan Glauber wrote: > After enabling CONFIG_I2C_DEBUG_CORE my system was broken > (no network, console login not possible). System log was > flooded with the this message: > > ... > [ 608.052077] rtc-ds1307 0-0068: uevent > [ 608.052500] rtc-ds1307

Re: [PATCH] i2c: Prevent endless uevent loop with dev_dbg

On Wed, Mar 23, 2016 at 04:50:47PM +0100, Jan Glauber wrote: > After enabling CONFIG_I2C_DEBUG_CORE my system was broken > (no network, console login not possible). System log was > flooded with the this message: > > ... > [ 608.052077] rtc-ds1307 0-0068: uevent > [ 608.052500] rtc-ds1307

[PATCH] usb: rework CONFIG_USB_COMMON logic

The phy-am335x driver selects 'USB_COMMON', but all other drivers use 'depends on' for that symbol, and it depends on USB || USB_GADGET itself, which causes a Kconfig warning: warning: (AM335X_PHY_USB) selects USB_COMMON which has unmet direct dependencies (USB_SUPPORT && (USB || USB_GADGET))

[PATCH] usb: rework CONFIG_USB_COMMON logic

The phy-am335x driver selects 'USB_COMMON', but all other drivers use 'depends on' for that symbol, and it depends on USB || USB_GADGET itself, which causes a Kconfig warning: warning: (AM335X_PHY_USB) selects USB_COMMON which has unmet direct dependencies (USB_SUPPORT && (USB || USB_GADGET))

[PATCH v3 18/19] ARM: sun5i: r8: Add display blocks to the DTSI

The TCON, tv-encoder and display engine backends and frontends are combined to create our display pipeline. Add them to the R8 DTSI. It's supposed to be perfectly compatible with the A10s and A13, but since we haven't tested it on them yet, it's safer to just enable it on the R8. Eventually, it

[PATCH v3 19/19] ARM: sun5i: chip: Enable the TV Encoder

The CHIP has a composite output available muxed with the microphone in the micro-jack plug. Enable the composite output in its DTS. Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun5i-r8-chip.dts | 12 1 file changed, 12 insertions(+) diff

[PATCH v3 18/19] ARM: sun5i: r8: Add display blocks to the DTSI

The TCON, tv-encoder and display engine backends and frontends are combined to create our display pipeline. Add them to the R8 DTSI. It's supposed to be perfectly compatible with the A10s and A13, but since we haven't tested it on them yet, it's safer to just enable it on the R8. Eventually, it

[PATCH v3 19/19] ARM: sun5i: chip: Enable the TV Encoder

The CHIP has a composite output available muxed with the microphone in the micro-jack plug. Enable the composite output in its DTS. Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun5i-r8-chip.dts | 12 1 file changed, 12 insertions(+) diff --git

[PATCH v3 02/19] clk: sunxi: Add display and TCON0 clocks driver

The A10 SoCs and its relatives has a special clock controller to drive the display engines (both frontend and backend), that have a lot in common with the clock to drive the first TCON channel. Add a driver to support both. Signed-off-by: Maxime Ripard

[PATCH v3 17/19] drm: sun4i: tv: Add NTSC output standard

Add the settings to support the NTSC standard. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/sun4i/sun4i_tv.c | 45 1 file changed, 45 insertions(+) diff --git a/drivers/gpu/drm/sun4i/sun4i_tv.c

[PATCH v3 02/19] clk: sunxi: Add display and TCON0 clocks driver

The A10 SoCs and its relatives has a special clock controller to drive the display engines (both frontend and backend), that have a lot in common with the clock to drive the first TCON channel. Add a driver to support both. Signed-off-by: Maxime Ripard Acked-by: Rob Herring ---

[PATCH v3 17/19] drm: sun4i: tv: Add NTSC output standard

Add the settings to support the NTSC standard. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/sun4i/sun4i_tv.c | 45 1 file changed, 45 insertions(+) diff --git a/drivers/gpu/drm/sun4i/sun4i_tv.c b/drivers/gpu/drm/sun4i/sun4i_tv.c index

[PATCH v3 00/19] drm: Add Allwinner A10 display engine support

Hi everyone, The Allwinner SoCs (except for the very latest ones) all share the same set of controllers, loosely coupled together to form the display pipeline. Depending on the SoC, the number of instances of the controller will change (2 instances of each in the A10, only one in the A13, for

Re: [PATCH] tpm: drop 'base' from struct tpm_vendor_specific

On Wed, Mar 23, 2016 at 08:16:09AM +0200, Jarkko Sakkinen wrote: > Dropped the field 'base' from struct tpm_vendor_specific and migrated > it to the private structures of tpm_atmel and tpm_nsc. > > Signed-off-by: Jarkko Sakkinen > +#define atmel_get_priv(chip)

[PATCH v3 00/19] drm: Add Allwinner A10 display engine support

Hi everyone, The Allwinner SoCs (except for the very latest ones) all share the same set of controllers, loosely coupled together to form the display pipeline. Depending on the SoC, the number of instances of the controller will change (2 instances of each in the A10, only one in the A13, for

Re: [PATCH] tpm: drop 'base' from struct tpm_vendor_specific

On Wed, Mar 23, 2016 at 08:16:09AM +0200, Jarkko Sakkinen wrote: > Dropped the field 'base' from struct tpm_vendor_specific and migrated > it to the private structures of tpm_atmel and tpm_nsc. > > Signed-off-by: Jarkko Sakkinen > +#define atmel_get_priv(chip) ((struct tpm_atmel_priv *)

Re: [PATCH] tpm_tis: drop manufacturer_id from struct tpm_vendor_specific

On Wed, Mar 23, 2016 at 07:31:56AM +0200, Jarkko Sakkinen wrote: > Dropped manufacturer_id from struct tpm_vendor_specific and redeclared > it in the private struct priv_data that tpm_tis uses because the field > is only used tpm_tis. Reviewed-by: Jason Gunthorpe

Re: [PATCH] tpm_tis: drop manufacturer_id from struct tpm_vendor_specific

On Wed, Mar 23, 2016 at 07:31:56AM +0200, Jarkko Sakkinen wrote: > Dropped manufacturer_id from struct tpm_vendor_specific and redeclared > it in the private struct priv_data that tpm_tis uses because the field > is only used tpm_tis. Reviewed-by: Jason Gunthorpe Jason

Re: [PATCH v6] acpi: Issue _OSC call for native thermal interrupt handling

I raised a general concern on a previous patch so I found a 1P server with Skylake and HWP to try. This doesn't qualify as a tested-by since all I did was apply the patch and boot the server but hey, it booted. I do have a question below... On 3/23/2016 12:07 AM, Srinivas Pandruvada wrote: >

Re: [PATCH v6] acpi: Issue _OSC call for native thermal interrupt handling

I raised a general concern on a previous patch so I found a 1P server with Skylake and HWP to try. This doesn't qualify as a tested-by since all I did was apply the patch and boot the server but hey, it booted. I do have a question below... On 3/23/2016 12:07 AM, Srinivas Pandruvada wrote: >

[PATCH v3 10/19] drm: fb: Add seq_file definition

Otherwise, building with DEBUG_FS enabled will trigger a build warning because we're using a structure that has not been declared. Signed-off-by: Maxime Ripard --- include/drm/drm_fb_cma_helper.h | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: net/sctp: stack-out-of-bounds in sctp_getsockopt

2016-03-22 23:27 GMT+08:00 Eric Dumazet : > > On Tue, 2016-03-22 at 08:21 -0700, Eric Dumazet wrote: > > On Tue, 2016-03-22 at 23:08 +0800, Baozeng Ding wrote: > > > Hi all, > > > > > > The following program triggers an out-of-bounds bug in > > > sctp_getsockopt. The kernel

[PATCH v3 10/19] drm: fb: Add seq_file definition

Otherwise, building with DEBUG_FS enabled will trigger a build warning because we're using a structure that has not been declared. Signed-off-by: Maxime Ripard --- include/drm/drm_fb_cma_helper.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/drm/drm_fb_cma_helper.h

Re: net/sctp: stack-out-of-bounds in sctp_getsockopt

2016-03-22 23:27 GMT+08:00 Eric Dumazet : > > On Tue, 2016-03-22 at 08:21 -0700, Eric Dumazet wrote: > > On Tue, 2016-03-22 at 23:08 +0800, Baozeng Ding wrote: > > > Hi all, > > > > > > The following program triggers an out-of-bounds bug in > > > sctp_getsockopt. The kernel version is 4.5 (on Mar

Re: [PATCH] tpm_atmel: drop tpm_atmel specific fields from tpm_vendor_specific

On Wed, Mar 23, 2016 at 07:10:22AM +0200, Jarkko Sakkinen wrote: > Introduced a private struct tpm_atmel_priv that contains the variables > have_region and region_size that were previously located in struct > tpm_vendor_specific. These fields were only used by tpm_atmel. This seems fine to me

Re: [PATCH] tpm_atmel: drop tpm_atmel specific fields from tpm_vendor_specific

On Wed, Mar 23, 2016 at 07:10:22AM +0200, Jarkko Sakkinen wrote: > Introduced a private struct tpm_atmel_priv that contains the variables > have_region and region_size that were previously located in struct > tpm_vendor_specific. These fields were only used by tpm_atmel. This seems fine to me

<    3   4   5   6   7   8   9   10   11   12   >