Andrew Morton writes:
> On Wed, 6 Apr 2016 15:45:10 +0200 Vitaly Kuznetsov
> wrote:
>
>> This patchset continues the work I started with:
>>
>> commit 31bc3858ea3ebcc3157b3f5f0e624c5962f5a7a6
>> Author: Vitaly Kuznetsov
>> Date: Tue Mar 15 14:56:48 2016 -0700
>>
>> memory-hotplug: add
David Rientjes writes:
> On Wed, 6 Apr 2016, Andrew Morton wrote:
>
>> > This patchset continues the work I started with:
>> >
>> > commit 31bc3858ea3ebcc3157b3f5f0e624c5962f5a7a6
>> > Author: Vitaly Kuznetsov
>> > Date: Tue Mar 15 14:56:48 2016 -0700
>> >
>> > memory-hotplug: add automa
On Tue, 05 Apr 2016, Laxman Dewangan wrote:
> Add device managed APIs devm_mfd_add_devices() and
> devm_mfd_remove_devices() for the APIs mfd_add_devices()
> and mfd_remove_devices().
Nit: Line wrap after "devm_mfd_remove_devices()" instead.
> This helps in reducing code in error path and someti
Hi Lee,
Thanks for review.
I will send another patch with incorporating your comments.
On Thursday 07 April 2016 04:14 PM, Lee Jones wrote:
On Tue, 05 Apr 2016, Laxman Dewangan wrote:
+ if (!ret) {
+ *ptr = dev;
+ devres_add(dev, ptr);
+ } else {
+
On Wed, Apr 06, 2016 at 07:36:49PM -0500, Thor Thayer wrote:
> Yes, nothing else changes. The rest was OK. Thanks!
Cool. The two remaining applied and pushed out.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
To unsubscribe from this list: send the line
On 2016/4/6 22:45, Alex Williamson wrote:
On Tue, 5 Apr 2016 21:46:44 +0800
Yongji Xie wrote:
This patch enables mmapping MSI-X tables if
hardware supports interrupt remapping which
can ensure that a given pci device can only
shoot the MSIs assigned for it.
Signed-off-by: Yongji Xie
---
d
On Thu, 07 Apr 2016, Laxman Dewangan wrote:
> Hi Lee,
> Thanks for review.
> I will send another patch with incorporating your comments.
>
>
> On Thursday 07 April 2016 04:14 PM, Lee Jones wrote:
> >On Tue, 05 Apr 2016, Laxman Dewangan wrote:
> >
> >+if (!ret) {
> >+*ptr = dev;
>
On Thursday 07 April 2016 05:12 PM, Lee Jones wrote:
On Thu, 07 Apr 2016, Laxman Dewangan wrote:
+ * Normally this function will not need to be called and the resource
+ * management code will ensure that the resource is freed.
Then what is the purpose of providing it? Do you have a user?
To
On Wed, Apr 6, 2016 at 2:29 PM, Yury Norov wrote:
>> We're already closer to the (future) y2038 than to the (past) introduction of
>> LP64...
>
> This is not about Y2038 at all. In fact, current version doesn't fix
> Y2038 problem, as we decided finally.
Indeed. So these legacy applications have
On Tue, Mar 29, 2016 at 02:19:12PM -0400, Stefan Berger wrote:
> This patch implements a proxy driver for supporting multiple emulated TPMs
> in a system.
>
> The driver implements a device /dev/vtpmx that is used to created
> a client device pair /dev/tpmX (e.g., /dev/tpm10) and a server side tha
On Tue, Mar 29, 2016 at 02:19:14PM -0400, Stefan Berger wrote:
> Add documentation for the tpm_vtpm device driver that implements
> support for providing TPM functionality to Linux containers.
>
> Parts of this documentation were recycled from the Xen vTPM
> device driver documentation.
>
> Updat
On Wed, 6 Apr 2016, Geert Uytterhoeven wrote:
> On Wed, Apr 6, 2016 at 12:08 AM, Yury Norov wrote:
>> v6:
>> - time_t, __kenel_off_t and other types turned to be 32-bit
>>for compatibility reasons (after v5 discussion);
Introducing a new arch today with y2038 problems is not a good idea.
Li
Hi Yongji,
On 04/07/2016 01:38 PM, Yongji Xie wrote:
> On 2016/4/6 22:45, Alex Williamson wrote:
>> On Tue, 5 Apr 2016 21:46:44 +0800
>> Yongji Xie wrote:
>>
>>> This patch enables mmapping MSI-X tables if
>>> hardware supports interrupt remapping which
>>> can ensure that a given pci device can
On 04/07/2016 08:35 AM, Jarkko Sakkinen wrote:
On Tue, Mar 29, 2016 at 02:19:12PM -0400, Stefan Berger wrote:
This patch implements a proxy driver for supporting multiple emulated TPMs
in a system.
The driver implements a device /dev/vtpmx that is used to created
a client device pair /dev/tpmX
The ARMv8.0 architecture reserves several system register
encodings for future use. These encodings should behave
as read-only and always return zero on a read. The Kryo core
errantly causes an instruction abort upon an AArch64
read attempt to the following system register encodings using
the MRS i
HI Naveen,
On 07/04/16 16:54, Naveen Kaje wrote:
> The ARMv8.0 architecture reserves several system register
> encodings for future use. These encodings should behave
> as read-only and always return zero on a read. The Kryo core
> errantly causes an instruction abort upon an AArch64
> read attem
This series add devm_ version of the APIs mfd_add_devices() and
mfd_release_devices() and get rid of call for mfd_release_devices()
some places and also remove the need of .remove callbacks as this
is not needed.
Changes from V1:
- Remove devm_mfd_remove_devices() as it is not required.
- Convert
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Tony Lindgren
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatch with --strict option and fi
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Mark Brown
CC: patc...@opensource.wolfsonmicro.com
Acked-by: Charles Keepax
---
Changes from V1:
- C
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Florian Fainelli
---
Changes from V1:
- Convert mfd to MFD.
- Fix checkpatch --strict error on patch.
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Andreas Werner
Reviewed-by: Andreas Werner
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpat
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Todd Fischer
---
Changes from V1:
- Convert mfd to MFD.
- Fix checkpatch --strict error on patch.
d
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Ingi Kim
CC: Javier Martinez Canillas
Reviewed-by: Javier Martinez Canillas
---
Changes from V1:
-
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Linus Walleij
Acked-by: Linus Walleij
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatch wi
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: John Crispin
CC: Javier Martinez Canillas
Reviewed-by: Javier Martinez Canillas
---
Changes from V1
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Gyungoh Yoo
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatch with --strict option and fix
Use devm_mfd_add_devices() for MFD devices registration and remove
the call of mfd_remove_devices() from .remove callback to remove
MFD child-devices. This is done by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Beniamino Galvani
---
Changes from V1:
- Convert mfd to MFD.
- Run
Use devm_mfd_add_devices() for MFD devices registration and remove
the call of mfd_remove_devices() from .remove callback to remove
MFD child-devices. This is done by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Tony Lindgren
---
Changes from V1:
- Convert mfd to MFD.
drivers/
Use devm_mfd_add_devices() for MFD devices registration and remove
the call of mfd_remove_devices() from .remove callback to remove
MFD child-devices. This is done by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Chris Zhong
---
Changes from V1:
- Convert mfd to MFD.
- Run checkp
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Boris Brezillon
Acked-by: Boris Brezillon
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatc
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Wenyou Yang
CC: Krzysztof Kozlowski
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatch with
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Guodong Xu
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatch with --strict option and fix w
Add resource managed API devm_mfd_add_devices() for the mfd_add_devices().
This helps in reducing code in error path as it is not required
to call mfd_remove_devices() explicitly to remove all child-devices.
In some cases, it also helps not to implement .remove() callback
which get called during d
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Guennadi Liakhovetski
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatch with --strict optio
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Matt Porter
---
Changes from V1:
- Convert mfd to MFD.
- Run checkpatch with --strict option and fix
Add devm wrappers for the mfd_add_devices() in the list of managed
interfaces.
Signed-off-by: Laxman Dewangan
---
Changes from V1:
- Reformat the commit message.
- Remove devm_ for mfd_remove_devices() as this is not used.
Documentation/driver-model/devres.txt | 3 +++
1 file changed, 3 insert
Use devm_mfd_add_devices() for MFD devices registration and get
rid of .remove callback to remove MFD child-devices. This is done
by managed device framework.
Signed-off-by: Laxman Dewangan
CC: Milo Kim
Acked-by: Milo Kim
---
Changes from V1:
- Convert mfd to MFD.
- Collected acks.
drivers/m
When the kernel crashkernel parameter is specified with just a size, we
are supposed to allocate a region from RAM to store the crashkernel.
However, ARM merely reserves physical address zero with no checking that
there is even RAM there.
Fix this by lifting similar code from x86, importing it to
On 03/28/2016 06:06 PM, Al Stone wrote:
> The ACPI 6.1 specification was recently released at the end of January
> 2016, but the arm64 kernel documentation for the use of ACPI was written
> for the 5.1 version of the spec. There were significant additions to the
> spec that had not yet been mentio
Hi Mark,
On Wed, 30 Mar 2016 14:24:10 -0700
Mark Brown wrote:
> On Wed, Mar 30, 2016 at 10:03:53PM +0200, Boris Brezillon wrote:
> > The continuous PWM voltage regulator is caching the voltage value in
> > the ->volt_uV field. While most of the time this value should reflect the
> > real voltage
On 04/07/16 at 10:03pm, Russell King wrote:
> When the kernel crashkernel parameter is specified with just a size, we
> are supposed to allocate a region from RAM to store the crashkernel.
> However, ARM merely reserves physical address zero with no checking that
> there is even RAM there.
>
> Fix
On Thu, Apr 7, 2016 at 5:18 AM, Adam Borowski wrote:
> On Wed, 6 Apr 2016, Geert Uytterhoeven wrote:
>> On Wed, Apr 6, 2016 at 12:08 AM, Yury Norov
>> wrote:
>>> v6:
>>> - time_t, __kenel_off_t and other types turned to be 32-bit
>>>for compatibility reasons (after v5 discussion);
>
> Intr
42 matches
Mail list logo
