On Wed, 3 Dec 2014, Dave Jones wrote:
> On Wed, Dec 03, 2014 at 09:59:20PM +0100, Thomas Gleixner wrote:
>
> > Can you please provide the cpuinfo flags of that box?
>
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
From: Borislav Petkov
Use the correct function name in the kernel-doc comment above it.
Cc: Ming Lei
Cc: Greg Kroah-Hartman
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Borislav Petkov
---
drivers/base/firmware_class.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dr
We are moving to device tree support on OMAP3, but that currently
breaks ADP1653 driver. This adds device tree support, plus required
documentation.
Signed-off-by: Pavel Machek
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/i2c/adp1653.txt
@@ -0,0 +1,38 @@
+* Analog Devices ADP1653
On Wed, Dec 3, 2014 at 7:46 PM, Frank Rowand wrote:
> On 12/3/2014 7:12 AM, Grant Likely wrote:
>> On Wed, Dec 3, 2014 at 2:24 AM, Frank Rowand wrote:
>>> On 11/27/2014 9:56 AM, Leif Lindholm wrote:
Add a global binding for the chosen node.
Include a description of the stdout-path, and
Hi Darren / platform-driver-x86 list,
Peter Feuerer writes:
please apply this series of patches.
did you find time for my patchseries already?
Is there any problem with it?
--
kind regards,
--peter;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
The commit "xen/pciback: Don't deadlock when unbinding." was using
the version of pci_reset_function which would lock the device lock.
That is no good as we can dead-lock. As such we swapped to using
the lock-less version and requiring that the callers
of 'pcistub_put_pci_dev' take the device lock.
A little cleanup. No functional difference.
Reviewed-by: Boris Ostrovsky
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/pci_stub.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/xen/xen-pciback/pci_stub.c
b/drivers/xen/xen-pc
Instead of open-coding it in drivers that want to double check
that their functions are indeed holding the device lock.
Signed-off-by: Konrad Rzeszutek Wilk
Suggested-by: David Vrabel
Acked-by: Greg Kroah-Hartman
---
drivers/xen/xen-pciback/pci_stub.c | 2 +-
include/linux/device.h
Hi,
I've added blank lines after several declarations that were
previously missing them, reducing the number of warnings from
checkpatch.pl.
Regards,
Jamie Lawler
Signed-off-by: Jamie Lawler
---
drivers/staging/octeon/ethernet-rx.c | 4
drivers/staging/octeon/ethernet-tx.c | 11 ++
We had been printing it only if the device was built with
debug enabled. But this information is useful in the field
to troubleshoot.
Signed-off-by: Konrad Rzeszutek Wilk
Reviewed-by: David Vrabel
---
drivers/xen/xen-pciback/xenbus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
On 3 December 2014 at 11:37, Pravin Shelar wrote:
> On Tue, Dec 2, 2014 at 6:56 PM, Joe Stringer wrote:
>> diff --git a/net/openvswitch/datapath.c b/net/openvswitch/datapath.c
>> index 332b5a0..b2a3796 100644
>> --- a/net/openvswitch/datapath.c
>> +++ b/net/openvswitch/datapath.c
>> @@ -462,10 +4
The life-cycle of a PCI device in Xen pciback is complex
and is constrained by the PCI generic locking mechanism.
It starts with the device being binded to us - for which
we do a device function reset (and done via SysFS
so the PCI lock is held)
If the device is unbinded from us - we also do a fu
We have the pci_load_and_free_saved_state, and pci_store_saved_state
but are missing the functionality to just load the state
multiple times in the PCI device without having to free/save
the state.
This patch makes it possible to use this function.
CC: Bjorn Helgaas
Signed-off-by: Konrad Rzeszut
Since v4 (http://lists.xen.org/archives/html/xen-devel/2014-11/msg02130.html):
- Per David's review altered one of the patches.
v3 (https://lkml.org/lkml/2014/7/8/533):
- Epic discussion.
These patches fix some issues with PCI back and also add proper
bus/slot reset.
Documentation/ABI/testin
From: Jan Beulich
When a PF driver unloads, it may find it necessary to leave the VFs
around simply because of pciback having marked them as assigned to a
guest. Utilize a suitable notification to let go of the VFs, thus
allowing the PF to go back into the state it was before its driver
loaded (w
Cleanup the function a bit - also include the id of the
domain that is using the device.
Signed-off-by: Konrad Rzeszutek Wilk
Reviewed-by: David Vrabel
---
drivers/xen/xen-pciback/pci_stub.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/xen/xen-pciback/p
As commit 0a9fd0152929db372ff61b0d6c280fdd34ae8bdb
'xen/pciback: Document the entry points for 'pcistub_put_pci_dev''
explained there are four entry points in this function.
Two of them are when the user fiddles in the SysFS to
unbind a device which might be in use by a guest or not.
Both 'unbind'
On Wed, Dec 03, 2014 at 01:06:59PM -0800, Jeremiah Mahler wrote:
> Arend,
>
> On Wed, Dec 03, 2014 at 01:49:00PM +0100, Arend van Spriel wrote:
> > On 12/03/14 11:51, Jeremiah Mahler wrote:
> > >On Wed, Dec 03, 2014 at 12:36:55AM -0800, Jeremiah Mahler wrote:
> > >>all,
> > >>
> > >>On Mon, Dec 01
From: Borislav Petkov
We need the additional "k" to make it a hard-c:
https://en.wiktionary.org/wiki/panicked
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/
I'm pretty sure I did. I'd normally just say "yes I'm sure," but the
kernel folks do extremely clever things with the compiler, linker, and
basically everything else, so I'm reluctant to assume that *anything*
I know about C in userspace or C in less-cleverly-written code holds
here. To that end, I
opa362 is amplifier for video and can be connected to the tvout pads
of the OMAP3. It has one gpio control for enable/disable of the output
(high impedance).
Signed-off-by: H. Nikolaus Schaller
Signed-off-by: Marek Belisko
---
drivers/video/fbdev/omap2/displays-new/Kconfig | 6 +
drivers/
Signed-off-by: Marek Belisko
---
.../devicetree/bindings/video/ti,opa362.txt| 38 ++
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindings/video/ti,opa362.txt
diff --git a/Documentation/devicetree/bindings/video/ti,opa362.txt
b/Docume
A patch to fix the rest of the long line warnings in the dgnc_cls.h file
found by the checkpatch.pl tool
Signed-off-by: Sean Cleator
---
drivers/staging/dgnc/dgnc_cls.h | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_cls.h b/drive
Add handling for gta04 tv out chain:
venc -> opa362 -> svideo
Use invert-polarity in venc node because opa362
is doing polarity inversion also.
Signed-off-by: Marek Belisko
---
arch/arm/boot/dts/omap3-gta04.dtsi | 49 ++
1 file changed, 49 insertions(+)
diff
changes from v3:
- use GPL v2 instead GPL
- fix wrong gpios property name in doc and DT
- set gpio to NULL if invalid
- drop unnecessary header
changes from v2:
- rename amplifier-opa362.c to encoder-opa362
- drop inversion handlign from driver
- add ti,invert-polarity to venc node
I also drop de
Am 03.12.2014 um 14:56 schrieb Harald Geyer:
> Richard Weinberger writes:
>> Am 03.12.2014 um 13:58 schrieb Harald Geyer:
>>> Richard Weinberger writes:
Currently the driver uses pr_* and dev_* functions.
Change all logging functions to dev_* style to be consistent
and have the corre
thermal_unregister_governors() and class_unregister() were being called in
the wrong order.
Fixes: 80a26a5c22b9 ("Thermal: build thermal governors into thermal_sys module")
Cc: sta...@vger.kernel.org
Signed-off-by: Luis Henriques
---
drivers/thermal/thermal_core.c | 4 ++--
1 file changed, 2 ins
On Wed, Dec 3, 2014 at 12:55 PM, Thomas Gleixner wrote:
>
> But it's always negative, which means HPET is always ahead of
> TSC. That excludes pretty much the clocksource watchdog starvation
> issue which results in TSC being ahead of HPET due to a HPET
> wraparound (which takes ~300s).
Still, I'
On Wed, Dec 03, 2014 at 04:22:33AM -0500, Richard Yao wrote:
> On 12/02/2014 12:26 PM, Greg Kroah-Hartman wrote:
> > On Tue, Dec 02, 2014 at 07:22:11AM -0500, Richard Yao wrote:
> >> Assuming that this dance succeeds, the FUSE process could then make a
> >> readonly file in itself, open it read onl
On Wed, 3 Dec 2014, Andrey Ryabinin wrote:
>
> Commit ed4d4902ebdd ("mm, hugetlb: remove hugetlb_zero and hugetlb_infinity")
> replaced
> 'unsigned long hugetlb_zero' with 'int zero' leading to out-of-bounds access
> in proc_doulongvec_minmax():
>
> ===
Arend,
On Wed, Dec 03, 2014 at 01:49:00PM +0100, Arend van Spriel wrote:
> On 12/03/14 11:51, Jeremiah Mahler wrote:
> >On Wed, Dec 03, 2014 at 12:36:55AM -0800, Jeremiah Mahler wrote:
> >>all,
> >>
> >>On Mon, Dec 01, 2014 at 08:34:05AM +0100, Arend van Spriel wrote:
> >>>On 01-12-14 08:19, Steph
On Wed, Dec 03, 2014 at 09:59:20PM +0100, Thomas Gleixner wrote:
> Can you please provide the cpuinfo flags of that box?
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx pdpe1gb rdtscp lm constant
On 3 December 2014 at 11:45, Pravin Shelar wrote:
> On Wed, Dec 3, 2014 at 10:47 AM, Joe Stringer wrote:
>> I forgot to mention that this is the first post based against net-next.
>>
>> On 2 December 2014 at 18:56, Joe Stringer wrote:
>>>
>>> diff --git a/net/openvswitch/flow.h b/n
On Wed, 3 Dec 2014, Dave Jones wrote:
> On Wed, Dec 03, 2014 at 09:37:10PM +0100, Thomas Gleixner wrote:
>
> > Right, that resulted in a delta > 0. I have no idea how we could
> > create a negative delta via wrapping the HPET around, i.e. HPET being
> > 96 seconds ahead of TSC.
> >
> > This
On Wed, Dec 3, 2014 at 3:11 PM, Dave Jones wrote:
On Wed, Dec 03, 2014 at 02:59:58PM -0500, Chris Mason wrote:
> You've also mentioned a few times where messages stopped hitting
the
> console?
>
> commit 5874af2003b1053128d655710140e3187226
> Author: Jan Kara
> Date: Wed Aug 6
On 02.12.2014 20:18, Greg KH wrote:
> On Sun, Nov 30, 2014 at 11:47:20AM -0800, Linus Torvalds wrote:
>> Hmm, Greg.
>>
>> I seem to get this problem possibly more commonly at boot these days:
>>
>> usb 1-6: new full-speed USB device number 2 using xhci_hcd
>> usb 1-6: device descriptor read/64,
On Wed, 3 Dec 2014, Linus Torvalds wrote:
> On Wed, Dec 3, 2014 at 12:09 PM, Dave Jones wrote:
> >
> > fwiw, there's quite a bit of variance in the delta that seems to show up.
>
> Yeah, anything from 1 to 251 seconds. That's definitely "quite a bit
> of variance"
But it's always negative, which
On Wed, Dec 03, 2014 at 05:11:49PM +0800, rui wang wrote:
> The problem is because kdump fails to load a new kernel, and we're
> executing past crash_kexec() in panic(). And it calls
> bust_spinlocks(0) which calls into the GPU driver trying to unblank
> the screen, which eventually calls __schedul
AT91 SoCs have a memory range reserved for internal bus configuration.
Expose those registers so that drivers can make use of the matrix syscon
declared in at91 DTs.
Signed-off-by: Boris Brezillon
Acked-by: Lee Jones
---
include/linux/mfd/syscon/atmel-matrix.h | 117
The Matrix registers are provided to configure internal bus behavior on
at91 SoCs.
Some registers might be accessed by several drivers (e.g. to configure
external memory bus timings), hence we declare this register set as a
syscon device.
Signed-off-by: Boris Brezillon
Acked-by: Lee Jones
---
.
Atmel AT91 SoCs have a memory range reserved for SMC (Static Memory
Controller) configuration.
Expose those registers so that drivers can make use of the smc syscon
declared in at91 DTs.
Signed-off-by: Boris Brezillon
Acked-by: Lee Jones
---
include/linux/mfd/syscon/atmel-smc.h | 173 ++
The EBI (External Bus Interface) is used to access external peripherals
(NOR, SRAM, NAND, and other specific devices like ethernet controllers).
Each device is assigned a CS line and an address range and can have its
own configuration (timings, access mode, bus width, ...).
This driver provides a g
The SMC registers are used to configure Atmel EBI (External Bus Interface)
to interface with standard memory devices (NAND, NOR, SRAM or specialized
devices like FPGAs).
Declare this memory region as a syscon, so that different drivers can
configure the SMC interface (mostly timing configuration)
Add matrix node in sama5d3 dtsi so that it can be referenced by other
devices.
Signed-off-by: Boris Brezillon
---
arch/arm/boot/dts/sama5d3.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3.dtsi b/arch/arm/boot/dts/sama5d3.dtsi
index 9f1eed5..d49dab7 100644
The EBI (External Bus Interface) is used to access external peripherals
(NOR, SRAM, NAND, and other specific devices like ethernet controllers).
Each device is assigned a CS line and an address range and can have its
own configuration (timings, access mode, bus width, ...).
This driver provides a g
at91sam9* and sama5d* SoCs have an EBI (External Bus Interface).
Select the ATMEL_EBI driver when support for these SoCs is selected.
Signed-off-by: Boris Brezillon
---
.../bindings/memory-controllers/atmel-ebi.txt | 18 +-
arch/arm/mach-at91/Kconfig
The EBI (External Bus Interface) is used to access external peripherals
(NOR, SRAM, NAND, and other specific devices like ethernet controllers).
Each device is assigned a CS line and an address range and can have its
own configuration (timings, access mode, bus width, ...).
This driver provides a g
On Wed, Dec 3, 2014 at 3:21 PM, Jeff Layton wrote:
> On Wed, 3 Dec 2014 14:59:43 -0500
> Trond Myklebust wrote:
>
>> On Wed, Dec 3, 2014 at 2:20 PM, Jeff Layton
>> wrote:
>> > On Wed, 3 Dec 2014 14:08:01 -0500
>> > Trond Myklebust wrote:
>> >> Which workqueue are you using? Since the receive c
On Wed, Dec 03, 2014 at 09:37:10PM +0100, Thomas Gleixner wrote:
> Right, that resulted in a delta > 0. I have no idea how we could
> create a negative delta via wrapping the HPET around, i.e. HPET being
> 96 seconds ahead of TSC.
>
> This looks more like a genuine TSC wreckage. So we have
Add EBI node and EBI pin muxing.
Signed-off-by: Boris Brezillon
---
arch/arm/boot/dts/sama5d3.dtsi | 83 ++
1 file changed, 83 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3.dtsi b/arch/arm/boot/dts/sama5d3.dtsi
index d49dab7..d011ade 100644
--- a/a
Add the SMC node in sama5d3 dtsi.
Signed-off-by: Boris Brezillon
---
arch/arm/boot/dts/sama5d3.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3.dtsi b/arch/arm/boot/dts/sama5d3.dtsi
index 5f4144d..9f1eed5 100644
--- a/arch/arm/boot/dts/sama5d3.dtsi
+++ b/ar
The sama5d3 evaluation kit embeds a NOR chip which is connected through
the EBI.
Define this NOR chip in the CPU module dtsi.
Signed-off-by: Boris Brezillon
---
arch/arm/boot/dts/sama5d3xcm.dtsi | 33 +
1 file changed, 33 insertions(+)
diff --git a/arch/arm/boot/
Hey guys,
On Wed, Dec 3, 2014 at 12:19 PM, Dave Jones wrote:
> On Wed, Dec 03, 2014 at 12:06:56PM -0800, Andy Lutomirski wrote:
>
> > >> Did something in RCU change recently ?
> > >
> > > Not since -rc1, as far as I know, anyway.
> >
> > I have patches to delete this whole fscking sysret fast but not r
On Wed, 3 Dec 2014, John Stultz wrote:
> I'll look around for some other suspects though. The nohz ntp
> improvments might be high on my list there, since it was a 3.17 item.
> Will dig.
Neither the clocksource watchdog nor the timestamp of the kernel
watchdog are affected by NTP adjustments.
Tha
Dave,
One last(?) batch of fixes hoping to make 3.18...
In this episode, we have another trio of rtlwifi fixes
repairing a little more damage from the major update of the
rtlwifi-family of drivers. These editing mistakes caused some
memory corruption and missed a flag critical to proper interrup
On Wed, Dec 3, 2014 at 12:09 PM, Dave Jones wrote:
>
> fwiw, there's quite a bit of variance in the delta that seems to show up.
Yeah, anything from 1 to 251 seconds. That's definitely "quite a bit
of variance"
Linus
--
To unsubscribe from this list: send the line "unsubscribe li
On Wed, 3 Dec 2014, John Stultz wrote:
> On Wed, Dec 3, 2014 at 11:25 AM, Linus Torvalds
> wrote:
> > On Wed, Dec 3, 2014 at 11:00 AM, Dave Jones wrote:
> >>
> >> So right after sending my last mail, I rebooted, and restarted the run
> >> on the same kernel again.
> >>
> >> As I was writing this
On Wed, 3 Dec 2014, Robert Jarzmik wrote:
> Nicolas Pitre writes:
>
> > Let ktime_divns() use do_div() inline whenever the divisor is constant
> > and small enough. This will make things like ktime_to_us() and
> > ktime_to_ms() much faster.
>
> Hi Nicolas,
>
> I suppose the "small enough" is
On Tue, Dec 02, 2014 at 06:11:50PM -0500, Boris Ostrovsky wrote:
> On 11/21/2014 05:17 PM, Konrad Rzeszutek Wilk wrote:
> >The commit "xen/pciback: Don't deadlock when unbinding." was using
> >the version of pci_reset_function which would lock the device lock.
> >That is no good as we can dead-lock
Hi,
I've attached a patch that fixes the lack of blank lines after 9 declarations
within drivers/thunderbolt/ctl.c. ctl.c now passes checkpatch.pl
Regards,
Jamie Lawler
Signed-off-by: Jamie Lawler
---
drivers/thunderbolt/ctl.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/driver
On Wednesday 03 December 2014 16:03:32 Russell King - ARM Linux wrote:
> On Fri, Nov 28, 2014 at 12:11:38PM +0100, Arnd Bergmann wrote:
> > I'm fine with it either way. Russell, if you like you can merge
> > http://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung
> > v3.19-next/pm-samsu
Haojian Zhuang writes:
>
> I think that it's a kind of irq muxing, just like lots of PMIC (power
> management IC).
> We should move the lubbock board irqs to a mfd driver, and register them as
> threaded irqs.
I will have a look.
I didn't consider mfd for motherboard gates, I'll think of it, tha
Linus,
i2c has a few driver bugfixes for 3.18. Please pull.
Thanks,
Wolfram
The following changes since commit 206c5f60a3d902bc4b56dab2de3e88de5eb06108:
Linux 3.18-rc4 (2014-11-09 14:55:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ws
On Wed, 3 Dec 2014 14:59:43 -0500
Trond Myklebust wrote:
> On Wed, Dec 3, 2014 at 2:20 PM, Jeff Layton
> wrote:
> > On Wed, 3 Dec 2014 14:08:01 -0500
> > Trond Myklebust wrote:
> >> Which workqueue are you using? Since the receive code is non-blocking,
> >> I'd expect you might be able to use
On Wed, Dec 03, 2014 at 12:06:56PM -0800, Andy Lutomirski wrote:
> >> Did something in RCU change recently ?
> >
> > Not since -rc1, as far as I know, anyway.
>
> I have patches to delete this whole fscking sysret fast but not really
> fast path. I'll resend them for 3.19. In the mean t
Harald,
Am 03.12.2014 um 13:18 schrieb Harald Geyer:
> Hi Richard,
>
> thanks for all the work you put into this!
>
> Richard Weinberger writes:
>> Please see my current patches for your driver.
>> As discussed in an earlier mail I'm testing with the DHT22 sensor only.
>> With the IRQ changes I
On Wed, Dec 03, 2014 at 09:13:18PM +0100, Arnd Bergmann wrote:
> I don't think we even have to worry about the platform_data case here:
> the only platform using this hardware in Linux is arm/mach-spear, and
> it defines a device node with a binding that is similar to the one you
> document here b
Nicolas Pitre writes:
> Let ktime_divns() use do_div() inline whenever the divisor is constant
> and small enough. This will make things like ktime_to_us() and
> ktime_to_ms() much faster.
Hi Nicolas,
I suppose the "small enough" is linked to the "!(div >> 32)" in your patch. Can
I have the
Richard Weinberger schrieb am 02.12.2014 um 19:12:
> Oh, that's a very valuable information! Currently I'm evaluating some sensors
> for a private project. You can recommend a better temp/humidity sensor?
Si7013 and Si7021 look very promising to me, regarding accuracy. Both are
supported by driv
On Wednesday 03 December 2014 16:39:08 Andrew Jackson wrote:
> Convert to driver to use either platform_data or device-tree for configuration
> of the device. When using device-tree, the I2S block's configuration is read
> from the relevant registers: this reduces the amount of information require
On Wed, Dec 03, 2014 at 02:59:58PM -0500, Chris Mason wrote:
> > [ 503.692038] Switched to clocksource hpet
> > [ 524.420897] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
> > [trinity-c178:20182]
>
> Neat. We often see switching to hpet on boxes as they are diving into
> so
On Wed, Dec 03, 2014 at 11:48:55AM -0800, Linus Torvalds wrote:
> On Wed, Dec 3, 2014 at 11:25 AM, Linus Torvalds
> wrote:
> >
> > I don't know. This piece of code:
> >
> > delta = clocksource_delta(wdnow, cs->wd_last, watchdog->mask);
> >
> > makes no sense to me.
>
> Yeah, no,
This patch adds the random number generator support for AF_ALG.
A random number generator's purpose is to generate data without
requiring the caller to provide any data. Therefore, the AF_ALG
interface handler for RNGs only implements a callback handler for
recvmsg.
The following parameters provi
Enable compilation of the AEAD AF_ALG support and provide a Kconfig
option to compile the AEAD AF_ALG support.
Signed-off-by: Stephan Mueller
---
crypto/Kconfig | 9 +
crypto/Makefile | 1 +
2 files changed, 10 insertions(+)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 87bbc9c..0
This patch adds the AEAD support for AF_ALG.
The implementation is based on algif_skcipher, but contains heavy
modifications to streamline the interface for AEAD uses.
To use AEAD, the user space consumer has to use the salg_type named
"aead".
The AEAD implementation includes some overhead to ca
Enable compilation of the RNG AF_ALG support and provide a Kconfig
option to compile the RNG AF_ALG support.
Signed-off-by: Stephan Mueller
---
crypto/Kconfig | 9 +
crypto/Makefile | 1 +
2 files changed, 10 insertions(+)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 0b2affc..8e9
AEAD requires the caller to specify the following information separate
from the data stream. This information allows the AEAD interface handler
to identify the AAD, ciphertext/plaintext and the authentication tag:
* Associated authentication data of arbitrary length and
length
Hi,
This patch set adds AEAD and RNG support to the AF_ALG interface
exported by the kernel crypto API. By extending AF_ALG with AEAD and RNG
support, all cipher types the kernel crypto API allows access to are
now accessible from userspace.
Both, AEAD and RNG implementations are stand-alone and
On 12/03/14 17:21, Greg KH wrote:
On Wed, Dec 03, 2014 at 01:49:00PM +0100, Arend van Spriel wrote:
On 12/03/14 11:51, Jeremiah Mahler wrote:
On Wed, Dec 03, 2014 at 12:36:55AM -0800, Jeremiah Mahler wrote:
all,
On Mon, Dec 01, 2014 at 08:34:05AM +0100, Arend van Spriel wrote:
On 01-12-14 08
On 12/03/2014 11:29 AM, Paul E. McKenney wrote:
> On Wed, Dec 03, 2014 at 01:19:22PM -0500, Dave Jones wrote:
>> I'm not sure why this only just started complaining, because this code
>> hasn't changed in years, but I don't recall seeing this before.
>> This gets spewed during bootup since I put 3.
On Mon, Dec 01, 2014 at 04:09:33PM -0800, David E. Box wrote:
> This patch implements an I2C bus sharing mechanism between the host and
> platform
> hardware on select Intel BayTrail SoC platforms using the X-Powers AXP288
> PMIC.
>
> On these platforms access to the PMIC must be shared with pla
03 дек. 2014 г., в 22:38, Felipe Balbi написал(а):
> then handle slave interrupts :-) But handle them so that it won't race
> with a master transfer request. Moving omap_i2c_xfer() inside the IRQ
> handler isn't the best way to do it, however.
I do that with care :)
Currently, only 'resize fif
On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
> On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown wrote:
> > I would expect that the clock for the CODEC should be managed by the
> > CODEC if at all possible - that seems more logical than having the CPU
> > I2S controller request and manage
On Wednesday 03 December 2014 14:43:06 Nicolas Pitre wrote:
> At least on ARM, do_div() is optimized to turn constant divisors into
> an inline multiplication by the reciprocal value at compile time.
> However this optimization is missed entirely whenever ktime_divns() is
> used and the slow out-o
On Wed, Dec 3, 2014 at 2:00 PM, Dave Jones wrote:
On Wed, Dec 03, 2014 at 10:45:57AM -0800, Linus Torvalds wrote:
> On Wed, Dec 3, 2014 at 10:41 AM, Dave Jones
wrote:
> >
> > I've been stuck on this kernel for a few days now trying to
prove it
> > good/bad one way or the other, and I'm
On Wed, Dec 3, 2014 at 2:20 PM, Jeff Layton wrote:
> On Wed, 3 Dec 2014 14:08:01 -0500
> Trond Myklebust wrote:
>> Which workqueue are you using? Since the receive code is non-blocking,
>> I'd expect you might be able to use rpciod, for the initial socket
>> reads, but you wouldn't want to use th
Marek Szyprowski writes:
> Hello,
>
> On 2014-12-03 13:36, Geert Uytterhoeven wrote:
>> Hi Marek,
>>
>> On Wed, Dec 3, 2014 at 1:33 PM, Marek Szyprowski
>> wrote:
>>> diff --git a/Documentation/devicetree/bindings/arm/exynos/power_domain.txt
>>> b/Documentation/devicetree/bindings/arm/exynos/po
On Wed, Dec 3, 2014 at 11:25 AM, Linus Torvalds
wrote:
> On Wed, Dec 3, 2014 at 11:00 AM, Dave Jones wrote:
>>
>> So right after sending my last mail, I rebooted, and restarted the run
>> on the same kernel again.
>>
>> As I was writing this mail, this happened.
>>
>> [ 524.420897] NMI watchdog:
oom_kill.c assumes that PF_EXITING task should exit and free the memory
soon. This is wrong in many ways and one important case is the coredump.
A task can sleep in exit_mm() "forever" while the coredumping sub-thread
can need more memory.
Change the PF_EXITING checks to take SIGNAL_GROUP_COREDUMP
Andrew,
This replaces
oom-dont-assume-that-a-coredumping-thread-will-exit-soon.patch
in -mm tree.
The patch is basically the same, but as Michal pointed out
mem_cgroup_out_of_memory() can use the new helper too, it can face
the same problems.
Also, I tried to update the changelog.
Mic
On Wednesday 03 December 2014 03:02:24 Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
> selected) PM_RUNTIME is always set if PM is set, so #ifdef blocks
> depending on CONFIG_PM_RUNTIME may now be changed to depend on
On Wed, Dec 03, 2014 at 12:26:07PM +0100, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.34 release.
> There are 101 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Wed, Dec 3, 2014 at 11:25 AM, Linus Torvalds
wrote:
>
> I don't know. This piece of code:
>
> delta = clocksource_delta(wdnow, cs->wd_last, watchdog->mask);
>
> makes no sense to me.
Yeah, no, I see what's up. I missed that whole wd_last vs cs_last
pairing. I guess that part is all goo
On Wed, Dec 03, 2014 at 11:25:29AM -0800, Linus Torvalds wrote:
> On Wed, Dec 3, 2014 at 11:00 AM, Dave Jones wrote:
> >
> > So right after sending my last mail, I rebooted, and restarted the run
> > on the same kernel again.
> >
> > As I was writing this mail, this happened.
> >
> > [ 52
On 12/3/2014 7:12 AM, Grant Likely wrote:
> On Wed, Dec 3, 2014 at 2:24 AM, Frank Rowand wrote:
>> On 11/27/2014 9:56 AM, Leif Lindholm wrote:
>>> Add a global binding for the chosen node.
>>> Include a description of the stdout-path, and an explicit statement on
>>> its extra options in the conte
On Tue, Dec 2, 2014 at 6:56 PM, Joe Stringer wrote:
> Refactor the ovs_nla_fill_match() function into separate netlink
> serialization functions ovs_nla_put_{unmasked_key,masked_key,mask}().
> Modify ovs_nla_put_flow() to handle attribute nesting and expose the
> 'is_mask' parameter - all callers
On Wed, Dec 03, 2014 at 08:12:39AM -0500, nick wrote:
> No I don't. I am was wondering why they are there still if there is no reason
> for them.
> Cheers Nick
I'd rather hear this statement from a person with the hardware (such as
Geert for example).
Thanks.
>
> On 2014-12-03 12:52 AM, Dmitr
On Wed, Dec 3, 2014 at 10:47 AM, Joe Stringer wrote:
> I forgot to mention that this is the first post based against net-next.
>
> On 2 December 2014 at 18:56, Joe Stringer wrote:
>>
>> diff --git a/net/openvswitch/flow.h b/net/openvswitch/flow.h
>> index a8b30f3..7f31dbf 100644
>>
At least on ARM, do_div() is optimized to turn constant divisors into
an inline multiplication by the reciprocal value at compile time.
However this optimization is missed entirely whenever ktime_divns() is
used and the slow out-of-line division code is used all the time.
Let ktime_divns() use do
301 - 400 of 1055 matches
Mail list logo
