On Sun, May 21, 2017 at 02:43:47AM +0800, Rui Teng wrote:
> This is a patch to the spk_ttyio.c file which fixes up the problems
> reported by the checkpatch.pl tool.
"the problems reported" is very very very vague.
Please read my last email to you...
On Mon, May 22, 2017 at 04:36:00PM +0300, Mike Rapoport wrote:
> On Mon, May 22, 2017 at 02:42:43PM +0300, Kirill A. Shutemov wrote:
> > On Mon, May 22, 2017 at 09:12:42AM +0300, Mike Rapoport wrote:
> > > Currently applications can explicitly enable or disable THP for a memory
> > > region using
>>> On 22.05.17 at 10:57, wrote:
> --- a/include/xen/xen.h
> +++ b/include/xen/xen.h
> @@ -9,8 +9,10 @@ enum xen_domain_type {
>
> #ifdef CONFIG_XEN
> extern enum xen_domain_type xen_domain_type;
> +extern char *xen_guest_type;
const char * ?
Jan
When __hci_cmd_sync() fails, download_firmware() should also fail, and
the same error value should be returned as PTR_ERR(skb).
Without this fix, download_firmware() will return a success when it actually
failed in __hci_cmd_sync().
Fixes: 371805522f87 ("bluetooth: hci_uart: add LL protocol
On Sat, 2017-05-20 at 13:39 +0200, Christian König wrote:
> Am 20.05.2017 um 01:48 schrieb Lyude:
> > This is the first part of me going through and cleaning up the IRQ
> > handling
> > code for radeon, since after taking a look at it the other day
> > while trying to
> > debug something I
On 05/19/2017 04:53 AM, Joonsoo Kim wrote:
> On Wed, May 17, 2017 at 03:17:13PM +0300, Andrey Ryabinin wrote:
>> On 05/16/2017 04:16 AM, js1...@gmail.com wrote:
>>> From: Joonsoo Kim
>>>
>>> Hello, all.
>>>
>>> This is an attempt to recude memory consumption of KASAN.
Hi Andrew
On 22/05/2017 15:57, Andrew Lunn wrote:
> On Mon, May 22, 2017 at 11:15:17AM +0200, Quentin Schulz wrote:
>> Some PHY require to wait for a bit after the reset GPIO has been
>> toggled. This adds support for the DT property `phy-reset-post-delay`
>> which gives the delay in milliseconds
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
On Mon, May 22, 2017 at 03:38:33PM +0300, Dan Carpenter wrote:
> On Mon, May 22, 2017 at 12:23:20PM +0100, Stefan Hajnoczi wrote:
> > I'm not sure if kmalloc() and friends guarantee to show
> > a message (not just the first time, but for every failed allocation)?
> >
>
> It prints multiple times,
On Mon, May 22, 2017 at 04:12:15PM +0300, Kirill A. Shutemov wrote:
> On Fri, May 19, 2017 at 02:01:26PM -0400, Jérôme Glisse wrote:
> > After memory hot remove it seems we do not synchronize pgds for kernel
> > virtual memory range (on vmemmap_free()). This seems bogus to me as it
> > means we
From: Markus Elfring
Date: Mon, 22 May 2017 15:34:28 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Link:
From: Markus Elfring
Date: Mon, 22 May 2017 15:40:21 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
On Mon, May 22, 2017 at 03:33:43AM -0700, Joe Perches wrote:
> vhost logging uses of vq_err has a few defects and style inconsistencies.
>
> o pr_debug already uses pr_fmt so its use in vq_err is defective
> however no #defines of pr_fmt exist in this code so no actual
> defects exist
> o
On 22/05/17 15:17, Boris Ostrovsky wrote:
>
>> diff --git a/Documentation/ABI/testing/sysfs-hypervisor
>> b/Documentation/ABI/testing/sysfs-hypervisor
>> index 443196f0aa1c..06850f74ebd4 100644
>> --- a/Documentation/ABI/testing/sysfs-hypervisor
>> +++
On (05/22/17 16:13), SF Markus Elfring wrote:
>
> Omit an extra message for a memory allocation failure in this function.
The change itself is harmless, but I'm curious about the "extra"
part: "extra" from what? If this happens, hopefully this will be logged
somewhere? Note that this type of
On Sun, May 21, 2017 at 10:42 PM, Wolfram Sang wrote:
> include/linux/i2c is not for client devices. Move the header file to a
> more appropriate location.
>
> Signed-off-by: Wolfram Sang
> ---
> drivers/misc/apds990x.c | 2 +-
>
On 05/20/2017 08:40 AM, Jarkko Sakkinen wrote:
On Mon, May 15, 2017 at 12:51:45PM -0400, Stefan Berger wrote:
Implement the request_locality function. To set the locality on the
backend we define vendor-specific TPM 1.2 and TPM 2 ordinals and send
a command to the backend to set the locality
On Mon, May 22, 2017 at 03:55:48PM +0200, Michal Hocko wrote:
> On Mon 22-05-17 16:36:00, Mike Rapoport wrote:
> > On Mon, May 22, 2017 at 02:42:43PM +0300, Kirill A. Shutemov wrote:
> > > On Mon, May 22, 2017 at 09:12:42AM +0300, Mike Rapoport wrote:
> > > > Currently applications can explicitly
From: Kalle Valo
Date: Mon, 22 May 2017 12:28:20 +0300
> Sebastian Reichel writes:
>
>> Motorola Droid 4 uses a WL1285C. With differences between the
>> chips not being public let's add explicit binding for wl1285
>> instead of relying
On 05/22/2017 09:33 AM, Andrew Cooper wrote:
> On 22/05/17 09:57, Juergen Gross wrote:
>> Currently there is no reliable user interface inside a Xen guest to
>> determine its type (e.g. HVM, PV or PVH). Instead of letting user mode
>> try to determine this by various rather hacky mechanisms
> -Original Message-
> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On
> Behalf Of Vitaly Kuznetsov
> Sent: Monday, May 22, 2017 3:44 AM
> To: Andy Lutomirski
> Cc: Stephen Hemminger ; Jork Loeser
>
On Mon, May 22, 2017 at 4:34 AM, Jiri Kosina wrote:
> On Sat, 20 May 2017, H.J. Lu wrote:
>
>> pushq %whatever
>> .cfi_adjust_sp -8
>> ...
>> popq %whatever
>> .cfi_adjust_sp 8
>>
>> >>
>> >> Np. Compiler needs to generate this.
>> >>
>> >
>> > How
From: Vivien Didelot
Date: Fri, 19 May 2017 17:00:35 -0400
> DSA is by nature the support for a switch fabric, which can be composed
> of a single, or multiple interconnected Ethernet switch chips.
>
> The current DSA core behavior is to identify the slave
> Do you find information from a Linux allocation failure report sufficient
> for such an use case?
yes, I suppose that would cover the needed cases.
Your change looks good to me.
Acked-by: Sowmini Varadhan
On Sun, May 21, 2017 at 02:48:56PM +0200, Ralph Sennhauser wrote:
> The new ones work so there is little reason to keep the legacy bindings.
> Use the rework as the oportunity to drop the legacy node.
>
> Signed-off-by: Ralph Sennhauser
Reviewed-by: Andrew Lunn
On Sun, May 21, 2017 at 02:48:55PM +0200, Ralph Sennhauser wrote:
> Now that we use the reference for the USB3.0 port update the node name
> and labels for the phy and vbus to match the label used by
> armada-38x.dtsi.
>
> Signed-off-by: Ralph Sennhauser
>
> ---
>
>
On 5/22/2017 4:07 PM, Sricharan R wrote:
Hi,
On 5/22/2017 3:03 PM, Dwivedi, Avaneesh Kumar (avani) wrote:
On 5/20/2017 8:25 AM, Sricharan R wrote:
Hi Bjorn/Avaneesh,
On 5/16/2017 11:32 PM, Avaneesh Kumar Dwivedi wrote:
This patch refactor code to first load all firmware blobs
and then
On Sun, May 21, 2017 at 7:13 PM, Thomas Gleixner wrote:
> On Tue, 16 May 2017, Arnd Bergmann wrote:
>> On Tue, May 16, 2017 at 5:51 PM, Christoph Hellwig wrote:
>> > Yes, that sounds useful to me as well. As you said it's an independent
>> > but somewhat related
On Mon, May 22, 2017 at 04:28:24PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> On Monday 22 May 2017 03:56 PM, Greg Kroah-Hartman wrote:
> > On Fri, May 19, 2017 at 08:13:27PM +0530, Kishon Vijay Abraham I wrote:
> >> Hi Greg,
> >>
> >> Please find the pull request for 4.12 -rc below.
>
On Mon 22-05-17 09:18:58, Pasha Tatashin wrote:
> >
> >I have only noticed this email today because my incoming emails stopped
> >syncing since Friday. But this is _definitely_ not the right approachh.
> >64G for 32b systems is _way_ off. We have only ~1G for the kernel. I've
> >already proposed
The newly added meson_uart_enable_tx_engine function is only called
from the console setup, not the runtime uart, which has an open-coded
version of the same register access. This produces a harmless warning
when the console code is disabled:
drivers/tty/serial/meson_uart.c:127:13: error:
On Mon, May 22, 2017 at 05:41:31PM +0530, Richa Jha wrote:
> Changes :
>
> ulActualMxClk ---> ul_actual_max_clk
> pInitParam---> p_init_param
I can see that from the patch, but _why_ are you doing this?
And please fix up your subject to match others for this driver, you can
find that in
On Mon, 2017-05-22 at 15:38 +0200, Jan Kara wrote:
> On Fri 19-05-17 15:20:52, Jeff Layton wrote:
> > On Mon, 2017-05-15 at 12:42 +0200, Jan Kara wrote:
> > > On Tue 09-05-17 11:49:18, Jeff Layton wrote:
> > > > Now that we have a better way to store and report errors that occur
> > > > during
On Mon 22-05-17 16:36:00, Mike Rapoport wrote:
> On Mon, May 22, 2017 at 02:42:43PM +0300, Kirill A. Shutemov wrote:
> > On Mon, May 22, 2017 at 09:12:42AM +0300, Mike Rapoport wrote:
> > > Currently applications can explicitly enable or disable THP for a memory
> > > region using MADV_HUGEPAGE or
On Mon, May 22, 2017 at 3:36 PM, Punit Agrawal wrote:
> diff --git a/include/asm-generic/hugetlb.h b/include/asm-generic/hugetlb.h
> index 99b490b4d05a..3138e126f43b 100644
> --- a/include/asm-generic/hugetlb.h
> +++ b/include/asm-generic/hugetlb.h
> @@ -31,10 +31,7 @@
On 22/05/17 14:34, Leo Yan wrote:
> Hi Sudeep,
>
> On Mon, May 22, 2017 at 02:02:12PM +0100, Sudeep Holla wrote:
>
> [...]
>
>> On 19/05/17 17:45, Daniel Lezcano wrote:
>>> Some hardware have clusters with different idle states. The current
>>> code does
>>> not support this
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
From: gabriele paoloni
Currently the MSI/MSIx vectors for the root port services are
allocated calling pcie_init_service_irqs(). At the moment these
vectors are only allocated for AER, PME, HP.
This patch allocate an MSI/MSIx vector also for DPC.
Signed-off-by:
Execution cannot reach NET_IP_ALIGN inside the following statement:
ip_align = strict ? 2 : NET_IP_ALIGN
Addresses-Coverity-ID: 1409762
Signed-off-by: Gustavo A. R. Silva
---
NOTE: variable ip_align could also be removed and use value 2 directly.
kernel/bpf/verifier.c
From: gabriele paoloni
This patchset:
1) adds support for MSI interrupt vectors to be used for Roor Port services
2) adds support for DPC Root Port service interrupt
The patchset has been tested on Hisilicon Hip08 Chipset
Changes from v3:
- removed 2 extra lines at
From: Markus Elfring
Date: Mon, 22 May 2017 15:45:31 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Link:
This will be useful when the condition becomes slightly more
complicated in the next patch.
Signed-off-by: Rasmus Villemoes
---
drivers/watchdog/watchdog_dev.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git
This allows setting a default value for the watchdog.open_timeout
commandline parameter via Kconfig.
Signed-off-by: Rasmus Villemoes
---
Documentation/watchdog/watchdog-parameters.txt | 9 +
drivers/watchdog/Kconfig | 9 +
From: Stephen Rothwell
Date: Mon, 22 May 2017 13:43:00 +1000
> Hi Dave,
>
> On Sun, 21 May 2017 23:14:10 -0400 (EDT) David Miller
> wrote:
>>
>> From: Stephen Rothwell
>> Date: Mon, 22 May 2017 11:16:05 +1000
>>
>> > After
> No objection from me but please make sure to keep vq_err().
How long should I wait before I may dare to send another variant for the
discussed update suggestion?
Which commit message would be acceptable then for this update step?
Regards,
Markus
>> Omit an extra message for a memory allocation failure in this function.
>
> The change itself is harmless, but I'm curious about the "extra"
> part: "extra" from what? If this happens, hopefully this will be logged
> somewhere? Note that this type of (infrequent) logging noise is useful
> in
This patch series add hardware CRC32 ("Ethernet") calculation support
for STMicroelectronics STM32F429.
Polynomial and key setting are not supported, key is fixed as 0x4C11DB7
and poly is 0x.
Module is tested on STM32F429-disco board with crypto testmgr using
cases within the key
From: "Gustavo A. R. Silva"
Date: Mon, 22 May 2017 09:07:46 -0500
> Execution cannot reach NET_IP_ALIGN inside the following statement:
> ip_align = strict ? 2 : NET_IP_ALIGN
>
> Addresses-Coverity-ID: 1409762
> Signed-off-by: Gustavo A. R. Silva
On Thu 18-05-17 15:29:39, Ross Zwisler wrote:
> On Thu, May 18, 2017 at 09:50:37AM +0200, Jan Kara wrote:
> > On Wed 17-05-17 11:16:39, Ross Zwisler wrote:
> > > We currently have two related PMD vs PTE races in the DAX code. These can
> > > both be easily triggered by having two threads reading
On 22/05/17 15:35, Boris Ostrovsky wrote:
> On 05/22/2017 09:33 AM, Andrew Cooper wrote:
>> On 22/05/17 09:57, Juergen Gross wrote:
>>> Currently there is no reliable user interface inside a Xen guest to
>>> determine its type (e.g. HVM, PV or PVH). Instead of letting user mode
>>> try to
On Mon, May 22, 2017 at 04:00:47PM +0200, Quentin Schulz wrote:
> Hi Andrew
>
> On 22/05/2017 15:57, Andrew Lunn wrote:
> > On Mon, May 22, 2017 at 11:15:17AM +0200, Quentin Schulz wrote:
> >> Some PHY require to wait for a bit after the reset GPIO has been
> >> toggled. This adds support for the
On Sun, May 21, 2017 at 02:48:51PM +0200, Ralph Sennhauser wrote:
> Add labels to nodes used by dependants. Also rename node gpio_keys to
> gpio-keys to mach the style of the rest of the file as well as the
s/mach/match
> documented example.
>
> Signed-off-by: Ralph Sennhauser
On Mon, May 22, 2017 at 10:45:57AM -0400, David Miller wrote:
> From: Vivien Didelot
> Date: Fri, 19 May 2017 17:00:35 -0400
>
> > DSA is by nature the support for a switch fabric, which can be composed
> > of a single, or multiple interconnected Ethernet
On 05/22/2017 10:20 AM, Juergen Gross wrote:
> On 22/05/17 15:30, Boris Ostrovsky wrote:
>> On 05/22/2017 04:56 AM, Juergen Gross wrote:
>>> Today only a few sysfs nodes under /sys/hypervisor/ are documented
>>> for Xen in Documentation/ABI/testing/sysfs-hypervisor-pmu. Rename
>>> this file to
On 22/05/2017 15:02, Sudeep Holla wrote:
[ ... ]
>> +drv->cpumask = _topology[cpu].core_sibling;
>> +
>
> This is not always true and not architecturally guaranteed. So instead
> of introducing this broken dependency, better to extract information
> from
On 05/22/2017 04:38 PM, David Miller wrote:
From: "Gustavo A. R. Silva"
Date: Mon, 22 May 2017 09:07:46 -0500
Execution cannot reach NET_IP_ALIGN inside the following statement:
ip_align = strict ? 2 : NET_IP_ALIGN
Addresses-Coverity-ID: 1409762
Signed-off-by:
On Sun, May 21, 2017 at 02:48:53PM +0200, Ralph Sennhauser wrote:
> Drop redundant declaration of #address-cells and #size-cells.
>
> Signed-off-by: Ralph Sennhauser
Reviewed-by: Andrew Lunn
Andrew
* Dave Gerlach [170519 11:00]:
> diff --git a/arch/arm/kernel/asm-offsets.c b/arch/arm/kernel/asm-offsets.c
> index 608008229c7d..d728b5660e36 100644
> --- a/arch/arm/kernel/asm-offsets.c
> +++ b/arch/arm/kernel/asm-offsets.c
> @@ -28,6 +28,7 @@
> #include
> #include
>
On Mon, 22 May 2017, Michal Hocko wrote:
> On Mon 22-05-17 08:00:11, Mikulas Patocka wrote:
> >
> > On Mon, 22 May 2017, Michal Hocko wrote:
> >
> > > > Sometimes, I/O to a device mapper device is blocked until the userspace
> > > > daemon dmeventd does some action (for example, when
* Rob Herring [170519 18:49]:
> On Fri, May 19, 2017 at 12:57:07PM -0500, Dave Gerlach wrote:
> > Update the Texas Instruments EMIF binding document to include the device
> > tree bindings for ti,emif-am3352 and ti,emif-am4372 which are used by
> > the ti-emif-sram driver to
On Mon, 2017-05-22 at 14:48 +0200, Neil Armstrong wrote:
> Signed-off-by: Neil Armstrong
I would prefer to have a short commit message here. With it included:
Acked-by: Jerome Brunet
> ---
> drivers/clk/meson/gxbb.h | 2 +-
>
On 05/22/2017 03:23 PM, Jerome Brunet wrote:
> On Mon, 2017-05-22 at 14:48 +0200, Neil Armstrong wrote:
>> Signed-off-by: Neil Armstrong
>
> I would prefer to have a short commit message here. With it included:
Indeed, sorry.
I'll push it with a short commit message
Hello Alexandr,
Ok, I will.
Regards,
-Sergey
On Mon, May 22, 2017 at 03:20:44PM +0200, Alexander Sverdlin
wrote:
> Hello Serge,
>
> On 22/05/17 15:03, Serge Semin wrote:
> >> I have an SGI Onyx2 and just recently acquired a working SGI Origin 200.
> >> The
> >>
On Mon, May 22, 2017 at 02:42:43PM +0300, Kirill A. Shutemov wrote:
> On Mon, May 22, 2017 at 09:12:42AM +0300, Mike Rapoport wrote:
> > Currently applications can explicitly enable or disable THP for a memory
> > region using MADV_HUGEPAGE or MADV_NOHUGEPAGE. However, once either of
> > these
On 22/05/17 09:57, Juergen Gross wrote:
> Currently there is no reliable user interface inside a Xen guest to
> determine its type (e.g. HVM, PV or PVH). Instead of letting user mode
> try to determine this by various rather hacky mechanisms (parsing of
> boot messages before they are gone, trying
Hi Alexander,
On Mon, May 22, 2017 at 2:08 PM, Solar Designer wrote:
> Hi Djalal,
>
> Thank you for your work on this!
>
> On Mon, May 22, 2017 at 01:57:03PM +0200, Djalal Harouni wrote:
>> *) When modules_autoload_mode is set to (2), automatic module loading is
>> disabled
Hi,
On Monday 22 May 2017 07:08 PM, Greg Kroah-Hartman wrote:
> On Mon, May 22, 2017 at 04:28:24PM +0530, Kishon Vijay Abraham I wrote:
>> Hi Greg,
>>
>> On Monday 22 May 2017 03:56 PM, Greg Kroah-Hartman wrote:
>>> On Fri, May 19, 2017 at 08:13:27PM +0530, Kishon Vijay Abraham I wrote:
Hi
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:.
But this could
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken
On Mon, May 22, 2017 at 01:34:34PM +0200, SF Markus Elfring wrote:
> >> Do you find information from a Linux allocation failure report sufficient
> >> for any function implementations here?
> >
> > If kmalloc() and friends guarantee to print a warning and backtrace on
> > every allocation
From: Markus Elfring
Date: Mon, 22 May 2017 16:02:03 +0200
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete an error message for a failed memory allocation in rds_ib_add_one()
Improve a size
Currently PCIe port services are assigned with different interrutps
only if MSI-x are supported by calling pcie_port_enable_msix().
If a root port supports MSI instead of MSI-x currently we fall back
to use a single shared interrupt for all the services.
This patch renames and extends
On Fri, 2017-05-19 at 08:47 -0400, Mark Salter wrote:
> On Fri, 2017-05-19 at 09:34 +1000, Stephen Rothwell wrote:
> > Hi Mark,
> >
> > On Wed, 17 May 2017 07:51:55 +1000 Stephen Rothwell
> > wrote:
> > >
> > > Fetching the c6x tree profuces this error:
> > >
> > >
On 22/05/17 11:09, Hans Verkuil wrote:
On 05/12/2017 05:22 AM, Minghsiu Tsai wrote:
Who should take care of the dtsi changes? I'm not sure who maintains the mdp
dts.
I will take care of the dtsi patches.
The driver change and the dtsi change need to be in sync, so it is probably
On Mon, May 22, 2017 at 11:49 AM, Geert Uytterhoeven
wrote:
> Hi Arnd, Helge,
>
> On Mon, May 22, 2017 at 11:35 AM, Geert Uytterhoeven
> wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v4.12-rc2[1] compared to
The watchdog framework takes care of feeding a hardware watchdog until
userspace opens /dev/watchdogN. If that never happens for some reason
(buggy init script, corrupt root filesystem or whatnot) but the kernel
itself is fine, the machine stays up indefinitely. This patch allows
setting an upper
On 22/05/17 15:45, Jan Beulich wrote:
On 22.05.17 at 10:57, wrote:
>> --- a/include/xen/xen.h
>> +++ b/include/xen/xen.h
>> @@ -9,8 +9,10 @@ enum xen_domain_type {
>>
>> #ifdef CONFIG_XEN
>> extern enum xen_domain_type xen_domain_type;
>> +extern char *xen_guest_type;
>
If a watchdog driver tells the framework that the device is running,
the framework takes care of feeding the watchdog until userspace opens
the device. If the userspace application which is supposed to do that
never comes up properly, the watchdog is fed indefinitely by the
kernel. This can be
On 22/05/17 15:30, Boris Ostrovsky wrote:
> On 05/22/2017 04:56 AM, Juergen Gross wrote:
>> Today only a few sysfs nodes under /sys/hypervisor/ are documented
>> for Xen in Documentation/ABI/testing/sysfs-hypervisor-pmu. Rename
>> this file to Documentation/ABI/testing/sysfs-hypervisor and add
>>
Add device tree binding for STM32F4.
Signed-off-by: Cosar Dindar
---
Documentation/devicetree/bindings/crypto/st,stm32-crc.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/crypto/st,stm32-crc.txt
Enable the CRC32 crypto on stm32429i-eval board.
Signed-off-by: Cosar Dindar
---
arch/arm/boot/dts/stm32429i-eval.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index
On Mon, May 22, 2017 at 10:11:51AM -0400, Jerome Glisse wrote:
> On Mon, May 22, 2017 at 04:12:15PM +0300, Kirill A. Shutemov wrote:
> > On Fri, May 19, 2017 at 02:01:26PM -0400, Jérôme Glisse wrote:
> > > After memory hot remove it seems we do not synchronize pgds for kernel
> > > virtual memory
Enable the CRC32 crypto on stm32429-disco board.
Signed-off-by: Cosar Dindar
---
arch/arm/boot/dts/stm32f429-disco.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429-disco.dts
b/arch/arm/boot/dts/stm32f429-disco.dts
index
This patch adds CRC (CRC32 Crypto) support for STM32F4 series.
As an hardware limitation polynomial and key setting are not supported.
They are fixed as 0x4C11DB7 (poly) and 0x (key).
CRC32C Castagnoli algorithm is not used.
Signed-off-by: Cosar Dindar
---
Add CRC32 Crypto support to stm32f429.
Signed-off-by: Cosar Dindar
---
arch/arm/boot/dts/stm32f429.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index b2a2b5c..18343de 100644
---
On Wed 17-05-17 11:16:38, Ross Zwisler wrote:
> When the pmd_devmap() checks were added by:
>
> commit 5c7fb56e5e3f ("mm, dax: dax-pmd vs thp-pmd vs hugetlbfs-pmd")
>
> to add better support for DAX huge pages, they were all added to the end of
> if() statements after existing pmd_trans_huge()
On Wed 17-05-17 11:16:39, Ross Zwisler wrote:
> We currently have two related PMD vs PTE races in the DAX code. These can
> both be easily triggered by having two threads reading and writing
> simultaneously to the same private mapping, with the key being that private
> mapping reads can be
Am Freitag, den 19.05.2017, 14:46 + schrieb David Laight:
> For XHCI it isn't too bad because it will do arbitrary scatter-gather
> (apart from the ring end).
> But I believe the earlier controllers only support fragments that
> end on usb packet boundaries.
>
> I looked at the usbnet code a
801 - 900 of 2324 matches
Mail list logo