The patch
spi: atmel-quadspi: add support for sam9x60 qspi controller
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
Hi Quentin,
On Wed, Feb 06, 2019 at 10:13:18AM +, Quentin Perret wrote:
> Hi Matthias,
>
> On Tuesday 05 Feb 2019 at 09:52:25 (-0800), Matthias Kaehlcke wrote:
> > Try and register an Energy Model from mediatek-cpufreq to allow
> > interested subsystems like the task scheduler to use the
On Tue, Feb 05, 2019 at 08:33:28PM -0500, Brian Masney wrote:
> This patch adds a new vibrator driver that supports various Qualcomm
> MSM SOCs. Driver was tested on a LG Nexus 5 (hammerhead) phone.
>
> Signed-off-by: Brian Masney
Applied together with binding patch, thank you.
> ---
> Changes
> On 6 Feb 2019, at 19:02, jackm wrote:
>
> On Wed, 6 Feb 2019 16:40:14 +0100
> Håkon Bugge wrote:
>
>> Jack,
>>
>> A major contributor to the long processing time in the PF driver
>> proxying QP1 packets is:
>>
>> create_pv_resources
>> -> ib_create_cq(ctx->ib_dev,
We need to access I2C bus when switching brightness, and that may block,
therefore we have to set stmfts_brightness_set() as LED's
brightness_set_blocking() method.
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/tm2-touchkey.c | 10 +-
1 file changed, 5 insertions(+), 5
Add this missing compatibility string to the Reset Controller
compatible string chip list.
Signed-off-by: Nicolas Ferre
Reviewed-by: Rob Herring
---
v2: split series and collect tag
Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Add support for additional reset causes and the proper compatibility
string for sam9x60 SoC. The restart function is the same as the samx7.
Signed-off-by: Nicolas Ferre
Acked-by: Sebastian Reichel
---
v2: split series and collect tag
Sebastian,
I add your Acked-by tag here but as I would like
Commit-ID: 82434d23f36de42f70925f70d645ed3b1394361b
Gitweb: https://git.kernel.org/tip/82434d23f36de42f70925f70d645ed3b1394361b
Author: Kirill A. Shutemov
AuthorDate: Wed, 6 Feb 2019 18:29:08 +0300
Committer: Borislav Petkov
CommitDate: Wed, 6 Feb 2019 19:08:34 +0100
On Tue, Feb 05, 2019 at 12:11:08AM -0300, Paul Cercueil wrote:
> --- /dev/null
> +++ b/sound/soc/codecs/jz4725b.c
> @@ -0,0 +1,599 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * JZ4725B CODEC driver
Same comment for the headers here. Otherwise this looks good so I'll
apply, please send
On Wed, 2019-02-06 at 17:00 +0100, Thierry Reding wrote:
[...]
> > reset_control_get_exclusive() // implicitly acquires, may fail
> > reset_control_acquire() // optional, just makes acquire explicit (no-op)
> > reset_control_assert/deassert()
> > reset_control_release()
>
> I don't think we can
Update the Reset Controller's binding to add new SoC compatibility string.
Signed-off-by: Nicolas Ferre
Reviewed-by: Rob Herring
---
v2: split series and collect tag
Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
On Tue, Feb 05, 2019 at 12:11:05AM -0300, Paul Cercueil wrote:
> +++ b/sound/soc/codecs/jz4740.c
> @@ -1,14 +1,8 @@
> +// SPDX-License-Identifier: GPL-2.0
> /*
> - * Copyright (C) 2009-2010, Lars-Peter Clausen
> - *
Please convert the whole comment to C++ style so it looks more
consistent with
On Wed, Feb 06, 2019 at 06:47:57PM +0300, Kirill A. Shutemov wrote:
> What about this:
Yap, thanks!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Now that LEDs core allows "blocking" flavor of "set brightness" method we
can use it and get rid of private work item.
Signed-off-by: Dmitry Torokhov
---
drivers/input/misc/ims-pcu.c | 27 ---
1 file changed, 8 insertions(+), 19 deletions(-)
diff --git
Eric, at al,
Sorry, I am on on vacation, can't even read this thread right now,
so I am not sure I understand the problem correctly...
On 02/05, Eric W. Biederman wrote:
>
> @@ -2393,6 +2393,11 @@ bool get_signal(struct ksignal *ksig)
> goto relock;
> }
>
> + /* Has this
> On Feb 6, 2019, at 9:52 AM, Michael S. Tsirkin wrote:
>
> On Tue, Feb 05, 2019 at 09:13:30PM -0800, Nadav Amit wrote:
>> Various enhancements for VMware balloon, some of which are remainder
>> from a previous patch-set.
>>
>> Patch 1: Aumps the version number, following recent changes
>>
Commit-ID: 45b13b424faafb81c8c44541f093a682fdabdefc
Gitweb: https://git.kernel.org/tip/45b13b424faafb81c8c44541f093a682fdabdefc
Author: Kirill A. Shutemov
AuthorDate: Wed, 6 Feb 2019 14:52:53 +0300
Committer: Borislav Petkov
CommitDate: Wed, 6 Feb 2019 18:56:18 +0100
Add this SFR compatible definition for the sam9x60 SoC. Will be needed
in OHCI driver: ohci-at91.c.
Signed-off-by: Nicolas Ferre
---
Hi Rob,
It seems that this patch was lost in my series "[PATCH 0/8] ARM: at91/dt:
update to existing drivers for the sam9x60 SoC". I split it and resend it only
On Wed, Feb 06, 2019 at 07:56:37AM -0500, Nitesh Narayan Lal wrote:
>
> On 2/5/19 3:49 PM, Michael S. Tsirkin wrote:
> > On Mon, Feb 04, 2019 at 03:18:52PM -0500, Nitesh Narayan Lal wrote:
> >> This patch enables the caller to expose a single buffers to the
> >> other end using vring descriptor.
On Wed, 6 Feb 2019 16:40:14 +0100
Håkon Bugge wrote:
> Jack,
>
> A major contributor to the long processing time in the PF driver
> proxying QP1 packets is:
>
> create_pv_resources
>-> ib_create_cq(ctx->ib_dev, mlx4_ib_tunnel_comp_handler,
>NULL, ctx,
On Wed, Feb 06, 2019 at 10:57:31AM +0100, Stefan Agner wrote:
> Add length to the struct dw_pcie and check that the accessors
> dw_pcie_(rd|wr)_conf() do not read/write beyond that point.
>
> Suggested-by: Trent Piepho
> Signed-off-by: Stefan Agner
> ---
> Changes in v4:
> - Move length check
Taking a sleeping lock to _only_ increment a variable is quite the
overkill, and pretty much all users do this. Furthermore, some drivers
(ie: infiniband and scif) that need pinned semantics can go to quite
some trouble to actually delay via workqueue (un)accounting for pinned
pages when not
On Wed, Feb 06, 2019 at 03:00:26PM +0100, David Hildenbrand wrote:
> On 04.02.19 23:56, Michael S. Tsirkin wrote:
> >
> > On Wed, Jan 09, 2019 at 08:17:31PM +0530, Pankaj Gupta wrote:
> >> This patch series has implementation for "virtio pmem".
> >> "virtio pmem" is fake persistent
usnic_uiom_get_pages() uses gup_longterm() so we cannot really
get rid of mmap_sem altogether in the driver, but we can get
rid of some complexity that mmap_sem brings with only pinned_vm.
We can get rid of the wq altogether as we no longer need to
defer work to unpin pages as the counter is now
ib_umem_get() uses gup_longterm() and relies on the lock to
stabilze the vma_list, so we cannot really get rid of mmap_sem
altogether, but now that the counter is atomic, we can get of
some complexity that mmap_sem brings with only pinned_vm.
Reviewed-by: Ira Weiny
Signed-off-by: Davidlohr Bueso
The driver uses mmap_sem for both pinned_vm accounting and
get_user_pages(). By using gup_fast() and letting the mm handle
the lock if needed, we can no longer rely on the semaphore and
simplify the whole thing.
Cc: sudeep.d...@intel.com
Cc: ashutosh.di...@intel.com
Reviewed-by: Ira Weiny
Changes from v2 (https://patchwork.kernel.org/cover/10774255/):
- Added more reviews for patch 1 and also fixed mm/debug.c to
use llx insted of lx so gcc doesn't complain.
- Re did patch 3 (qib rdma) such that we still have to take
mmap_sem as it now uses gup_longterm(). gup_fast()
This driver already uses gup_fast() and thus we can just drop
the mmap_sem protection around the pinned_vm counter. Note that
the window between when hfi1_can_pin_pages() is called and the
actual counter is incremented remains the same as mmap_sem was
_only_ used for when ->pinned_vm was touched.
The driver uses mmap_sem for both pinned_vm accounting and
get_user_pages(). Because rdma drivers might want to use
gup_longterm() in the future we still need some sort of
mmap_sem serialization (as opposed to removing it entirely
by using gup_fast()). Now that pinned_vm is atomic the
writer lock
NATWEST BANK PLC,
10 Southwark Street ,
London Bridge , London - UK
SE1 1TT
RC: 121878
Our Ref: NTB/WESTMIN/INTER-15
Your Ref: Affidavit: AFX 076GD7B24
Tell=+447035969549
Fax+448435643403
REF:- INSTRUCTION TO CREDIT YOUR ACCOUNT WITH THE SUM OF (US$10Million)
This is the second time we are
The upcoming GCC 9 release extends the -Wmissing-attributes warnings
(enabled by -Wall) to C and aliases: it warns when particular function
attributes are missing in the aliases but not in their target.
In particular, it triggers for all the init/cleanup_module
aliases in the kernel (defined by
This removes a line left while adding the correct compatibility string for
sama5d3 10/100 interface. Now use the "atmel,sama5d3-macb" string.
Signed-off-by: Nicolas Ferre
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/net/macb.txt | 3 +--
1 file changed, 1 insertion(+), 2
Add a new compatibility string for this product. It's using
at91sam9260-macb layout but has a newer hardware revision: it's safer
to use its own string.
Signed-off-by: Nicolas Ferre
---
v2: applies on top of next-20190206
drivers/net/ethernet/cadence/macb_main.c | 1 +
1 file changed, 1
Add the compatibility sting documentation for sam9x60 10/100 interface.
Signed-off-by: Nicolas Ferre
---
Hi Rob,
Your tag is missing for this patch.
Documentation/devicetree/bindings/net/macb.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
The hci_dev struct hdev is referenced in work queues and timers started
by open() in some protocols. This creates a race between the
initialization function and the work or timer which can result hdev
being dereferenced while it is still null.
The syzbot report contains a reliable reproducer
On Wed, Feb 06, 2019 at 03:29:06PM +, Kees Cook wrote:
> I'm fine adjusting all this to do things better. Ultimately, we're
> still walking two lists to process their intersection.
I'm wondering if we could start with a single range including all memory
and then keep exluding until we're done
On Wed, Feb 06, 2019 at 10:31:14AM -0700, Jason Gunthorpe wrote:
> On Wed, Feb 06, 2019 at 10:50:00AM +0100, Jan Kara wrote:
>
> > MM/FS asks for lease to be revoked. The revoke handler agrees with the
> > other side on cancelling RDMA or whatever and drops the page pins.
>
> This takes a trip
All,
On 16/01/2019 at 10:57, Nicolas Ferre wrote:
> Hi,
>
> This series collects some little modifications to DT bindings and associated
> drivers changes for supporting the upcoming SAM9X60 SoC.
>
> I took the advantage of this series for fixing some of the leftovers in DT
> bindings for reset
On Tue, Feb 05, 2019 at 09:13:30PM -0800, Nadav Amit wrote:
> Various enhancements for VMware balloon, some of which are remainder
> from a previous patch-set.
>
> Patch 1: Aumps the version number, following recent changes
> Patch 2: Adds support for 64-bit memory limit
> Patches 3-4: Support
On Wed, Feb 6, 2019 at 12:30 PM Dmitry Torokhov
wrote:
>
> Yeah. But devm irq gave most trouble because we did not have enough
> devm APIs so we often ended up with mixed devm/non-devm usage and that
> is what was causing most of the issues. If we can switch everything to
> devm then devm irq is
Liquidio only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it
a great candidate to be converted to use the ndo_get_port_parent_id()
NDO instead of implementing switchdev_port_attr_get().
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
In preparation for getting rid of switchdev_ops, create a dedicated NDO
operation for getting the port's parent identifier. There are
essentially two classes of drivers that need to implement getting the
port's parent ID which are VF/PF drivers with a built-in switch, and
pure switchdev drivers
mlxsw implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
ethsw implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Signed-off-by: Florian Fainelli
---
mlxsw implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
netdevsim only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get().
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
drivers/net/netdevsim/netdev.c | 23
Ocelot only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID as a valid
switchdev attribute getter, convert it to use ndo_get_port_parent_id()
and get rid of the switchdev_ops::switchdev_port_attr_get altogether.
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
DSA implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
Now that we have a dedicated NDO for getting a port's parent ID, get rid
of SWITCHDEV_ATTR_ID_PORT_PARENT_ID and convert all callers to use the
NDO exclusively. This is a preliminary change to getting rid of
switchdev_ops eventually.
Signed-off-by: Florian Fainelli
---
include/net/switchdev.h
NFP only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get().
Since NFP uses switchdev_port_same_parent_id() convert it to use
netdev_port_same_parent_id().
Acked-by:
mlx5e only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get().
Since mlx5e makes use of switchdev_port_parent_id() convert it to use
netdev_port_same_parent_id().
Hi all,
Based on discussion with Ido and feedback from Jakub there are clearly
two classes of users that implement SWITCHDEV_ATTR_ID_PORT_PARENT_ID:
- PF/VF drivers which typically only implement return the port's parent
ID, yet have to implement switchdev_port_attr_get() just for that
-
BNXT only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get(). The conversion is
straight forward here since the PF and VF code use the same getter.
Since bnxt makes
On Wed, Feb 06, 2019 at 09:36:55AM -0800, Nick Desaulniers wrote:
> On Wed, Feb 6, 2019 at 9:32 AM Jon Flatley wrote:
> >
> > On Wed, Feb 6, 2019 at 8:45 AM Nathan Chancellor
> > wrote:
> > >
> > > On Tue, Feb 05, 2019 at 05:26:05PM +0900, Masahiro Yamada wrote:
> > > > On Sat, Feb 2, 2019 at
On Wed, 6 Feb 2019 09:33:35 -0800
Nadav Amit wrote:
> >>/* Copy ftrace_caller onto the trampoline memory */
> >>ret = probe_kernel_read(trampoline, (void *)start_offset, size);
> >> @@ -818,6 +820,13 @@ create_trampoline(struct ftrace_ops *ops, unsigned
> >> int *tramp_size)
> >>/*
From: Guenter Roeck
While ioctls normally return a negative error or 0 on success, this is not
the case for CROS_EC_DEV_IOCXCMD in the cros_ec driver, which returns the
number of bytes read instead. However, CROS_EC_DEV_IOCRDMEM in the same
driver does not return the number of byte read on
06.02.2019 17:56, Dmitry Osipenko пишет:
> 06.02.2019 17:53, Thierry Reding пишет:
>> On Tue, Feb 05, 2019 at 05:26:25PM +0300, Dmitry Osipenko wrote:
>> [...]
>>> Oh, another important moment is that physically contiguous dma_buf
>>> allocation isn't guaranteed by the DMA API. This may become a
On Wed, Feb 6, 2019 at 9:32 AM Jon Flatley wrote:
>
> On Wed, Feb 6, 2019 at 8:45 AM Nathan Chancellor
> wrote:
> >
> > On Tue, Feb 05, 2019 at 05:26:05PM +0900, Masahiro Yamada wrote:
> > > On Sat, Feb 2, 2019 at 6:10 AM wrote:
> > > >
> > > > From: Jon Flatley
> > > >
> > > > gcc produces
From: Kalle Valo
Date: Wed, 06 Feb 2019 09:17:10 +0200
> here's a pull request to net-next for 5.1, more info below. Please let
> me know if there are any problems.
Pulled, thanks Kalle!
Sequel to your non response to my previous email, I am thus;
re-sending this to you. I contacted you because a deceased client of
mine left behind some funds in dormant account which I want you to
assist in distributing.
Regards,
Andrew Smith
> On Feb 6, 2019, at 8:22 AM, Steven Rostedt wrote:
>
> On Wed, 16 Jan 2019 16:32:50 -0800
> Rick Edgecombe wrote:
>
>> From: Nadav Amit
>>
>> Since alloc_module() will not set the pages as executable soon, we need
>> to do so for ftrace trampoline pages after they are allocated.
>>
>> For
USB PHY driver supports all versions of stingray SS and HS USB PHYs.
- Version 1 is a combo PHY contains both SS and HS PHYs.
- Version 2 is a single HS PHY.
These PHYs support both Generic xHCI host controller driver and BDC
Broadcom device controller driver.
Signed-off-by: Srinath Mannam
Add DT binding document for Stingray USB PHY.
Signed-off-by: Srinath Mannam
Reviewed-by: Florian Fainelli
Reviewed-by: Scott Branden
---
.../bindings/phy/brcm,stingray-usb-phy.txt | 62 ++
1 file changed, 62 insertions(+)
create mode 100644
These patches add Stingray USB PHY driver and its corresponding
DT nodes with documentation.
This patch set is based on Linux-5.0-rc2.
Changes from v2:
- Addressed Kishon review comments
- Updated patchset to Linux-5.0-rc2
Changes from v1:
- Addressed Kishon review comments
- phy init
Add DT nodes for
- Two xHCI host controllers
- Two BDC Broadcom USB device controller
- Five USB PHY controllers
[xHCI0] [BDC0][xHCI1][BDC1]
| | | |
--- ---
|
On Wed, Feb 6, 2019 at 8:45 AM Nathan Chancellor
wrote:
>
> On Tue, Feb 05, 2019 at 05:26:05PM +0900, Masahiro Yamada wrote:
> > On Sat, Feb 2, 2019 at 6:10 AM wrote:
> > >
> > > From: Jon Flatley
> > >
> > > gcc produces format warnings that clang suppresses. To keep behavior
> > > consistent
Quoting Matti Vaittinen (2019-02-06 01:39:38)
> @@ -86,9 +87,21 @@ static int bd71837_clk_probe(struct platform_device *pdev)
> dev_err(>dev, "No parent clk found\n");
> return -EINVAL;
> }
> -
> - c->reg = BD718XX_REG_OUT32K;
> - c->mask =
On Wed, 6 Feb 2019 10:19:37 -0700
Keith Busch wrote:
> On Wed, Feb 06, 2019 at 12:31:00PM +, Jonathan Cameron wrote:
> > On Thu, 24 Jan 2019 16:07:14 -0700
> > Keith Busch wrote:
> >
> > 1) It seems this version added a hard dependence on having the memory node
> >listed in the Memory
On Wed, Feb 06, 2019 at 10:50:00AM +0100, Jan Kara wrote:
> MM/FS asks for lease to be revoked. The revoke handler agrees with the
> other side on cancelling RDMA or whatever and drops the page pins.
This takes a trip through userspace since the communication protocol
is entirely managed in
Quoting Matti Vaittinen (2019-02-06 01:38:54)
> Header rohm-bd718x7.h was split to generic and component specific
> parts. This changed the struct bd718x7. Adapt the clk driver to
> these changes.
>
> Signed-off-by: Matti Vaittinen
> ---
Acked-by: Stephen Boyd
On Wed, Feb 6, 2019 at 8:47 AM Greg KH wrote:
>
> On Tue, Feb 05, 2019 at 02:12:31PM -0500, Sven Van Asbroeck wrote:
> > On Tue, Feb 5, 2019 at 1:43 PM Greg KH wrote:
> > >
> > >
> > > It really should happen when the device is removed (if it is a driver
> > > that binds to a device.)
> >
> >
On Wed, Feb 6, 2019 at 5:31 PM Miguel Ojeda
wrote:
>
> On Mon, Feb 4, 2019 at 4:08 PM Jessica Yu wrote:
> >
> > IMHO I think annotating with __init is more straightforward, instead
> > of cherry-picking attributes (we wouldn't know at first glance why the
> > aliases are specifically annotated
Hi,
On 06/02/2019 16:14, Peter Zijlstra wrote:
[...]
>> @@ -9545,6 +9545,17 @@ static void nohz_balancer_kick(struct rq *rq)
>> }
>>
>> rcu_read_lock();
>> +
>> +if (static_branch_unlikely(_asym_cpucapacity))
>> +/*
>> + * For asymmetric systems, we do not
Hi,
On 06/02/2019 16:04, Peter Zijlstra wrote:
[...]
>> @@ -9561,6 +9573,14 @@ static void nohz_balancer_kick(struct rq *rq)
>
> sd = rcu_dereference(rq->sd);
> if (sd) {
> if ((rq->cfs.h_nr_running >= 1) &&
> check_cpu_capacity(rq, sd)) {
>
On Fri, 25 Jan 2019 at 11:35, Ard Biesheuvel wrote:
>
> On Fri, 25 Jan 2019 at 12:30, Christian König
> wrote:
> >
> > Am 25.01.19 um 09:43 schrieb Ard Biesheuvel:
> > > On Thu, 24 Jan 2019 at 15:01, Alex Deucher wrote:
> > >> On Thu, Jan 24, 2019 at 9:00 AM Ard Biesheuvel
> > >> wrote:
> >
Eugeniy Paltsev (2):
ARC: U-boot: check arguments paranoidly
ARC: U-boot: check magic number passed from u-boot
arch/arc/kernel/head.S | 7 ++--
arch/arc/kernel/setup.c | 91 +
2 files changed, 74 insertions(+), 24 deletions(-)
--
2.14.5
In case of devboards we really often disable bootloader and load
Linux image in memory via JTAG. In case of using kernel with
CONFIG_ARC_UBOOT_SUPPORT enabled we may crash as we will try to
interpret some junk in a registers as a pointers to bootargs/etc
which aren't set by anyone in case of JTAG
Handle U-boot arguments paranoidly:
* don't allow to pass unknown tag.
* try to use external device tree blob only if corresponding tag
(TAG_DTB) is set.
* don't check: uboot_tag if kernel build with no ARC_UBOOT_SUPPORT.
While I'm at it refactor U-boot arguments handling code.
On Wed, Jan 23, 2019 at 05:46:56PM +0800, ufo19890...@gmail.com wrote:
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index e2ff4b6..35e89ca 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -858,6 +858,19 @@ static void update_curr_fair(struct rq *rq)
> }
>
>
On Wed, Feb 06, 2019 at 12:31:00PM +, Jonathan Cameron wrote:
> On Thu, 24 Jan 2019 16:07:14 -0700
> Keith Busch wrote:
>
> 1) It seems this version added a hard dependence on having the memory node
>listed in the Memory Proximity Domain attribute structures. I'm not 100%
>sure
On Tue, 5 Feb 2019 20:16:11 -0600
Josh Poimboeuf wrote:
> On Tue, Feb 05, 2019 at 01:38:21PM -0500, Steven Rostedt wrote:
> > Just a FYI.
> >
> > After a recent upgrade in debian testing, I was not able to build the
> > kernel. I have a custom build of gcc, so I thought it was strange that
> >
On Wed, Feb 06, 2019 at 05:07:49PM +0100, Roberto Sassu wrote:
> Seems ok to me. I'll send patch 3/6 and 4/6.
Your series has been applied to master and next. Thank you.
/Jarkko
Series Applied and queued.
see
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/log/?h=next
On 31.01.2019 09:52, Michael Mueller wrote:
> The Guest Information Area (GIB) and its mechanics is part of
> the AIV facility. It provides hardware support to process
> Adapter
Thanks for the patch Stephen. Sorry, it took a while to get to this and
understand how this works.
On Thu, Jan 31 2019 at 00:10 -0700, Stephen Boyd wrote:
Quoting Stephen Boyd (2019-01-31 13:53:42)
I'm prototyping out some code to do the remapping based on this type of
DT property, because it
ARCH_MEMORY_PROBE is a useful thing for testing and debugging hotplug,
but being able to exercise the (arguably trickier) hot-remove path would
be even more useful. Extend the feature to allow removal of offline
sections to be triggered manually to aid development.
Signed-off-by: Robin Murphy
On 2/6/2019 6:55 AM, Georgi Djakov wrote:
Hi Jeffrey,
On 2/6/19 00:32, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-02-05 14:15:16)
On 2/5/2019 3:01 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-30 08:35:44)
The XO clock generally feeds into other clock controllers as the parent
On 2/6/2019 2:23 AM, Tetsuo Handa wrote:
> On 2019/02/04 17:07, Dmitry Vyukov wrote:
>> On Fri, Feb 1, 2019 at 2:09 PM Tetsuo Handa
>> wrote:
>>> On 2019/02/01 19:50, Dmitry Vyukov wrote:
On Fri, Feb 1, 2019 at 11:44 AM Tetsuo Handa
wrote:
> On 2019/02/01 19:09, Dmitry Vyukov
Hi Gilad,
On Wed, 6 Feb 2019 at 17:40, Gilad Ben-Yossef wrote:
>
> Hi all,
>
> A regression was spotted in the ccree driver running on Arm 32 bit
> causing a kernel panic during the crypto API self test phase (panic
> messages included with this message) happening in the PM resume
> callback
On Wed, 6 Feb 2019 11:54:20 -0500
Steven Rostedt wrote:
> On Wed, 6 Feb 2019 17:24:45 +0100 (CET)
> Miroslav Benes wrote:
>
>
> > > No worries. I'm also in holiday mode. I marked the patch in my INBOX
> > > and hopefully when I'm back to work it's not buried and lost for months.
> > >
> > >
The patch
regulator: rk808: Convert rk805 buck1/2 to use linear range
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: as3722: Correct minor typo
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
regulator: fixed/gpio: Pull inversion/OD into gpiolib
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
regulator: gpio: Convert to use descriptors
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
regulator: core: Only support passing enable GPIO descriptors
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: gpio: Simplify probe path
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
> > > >> Looking into timestamps and transactions, DMA timeouts after start of
> > > >> DMA for I2C1 to touch during this transaction.
> > > >> While it is waiting for I2C1 DMA transfer, lots of DVC
> > > >> transactions happened thru DMA which are successful
> > > >>
> > > >> What is the I2C1
On Wed, 6 Feb 2019 17:24:45 +0100 (CET)
Miroslav Benes wrote:
> > No worries. I'm also in holiday mode. I marked the patch in my INBOX
> > and hopefully when I'm back to work it's not buried and lost for months.
> >
> > Even if it is, I periodically purge my INBOX where I find missing
> >
On Wed, Feb 06, 2019 at 04:15:52PM +0100, David Sterba wrote:
> On Tue, Feb 05, 2019 at 03:48:48PM -0500, Dennis Zhou wrote:
> > > Ok great! I'm going to add a v2 for 0012 to add taking the spin_lock
> > > just to be safe in cleanup. I should have that ready in a few minutes.
> > >
> >
> >
>From ef64a8d1f4ec44f52bd13a825288a91667121708 Mon Sep 17 00:00:00 2001
From: Dennis Zhou
Date: Thu, 17 Jan 2019 12:13:27 -0800
Currently, the only user of set_level() is zlib which sets an internal
workspace parameter. As level is now plumbed into get_workspace(), this
can be handled there
>From 16b7c3fe05984a95436da1e9e01c80de1fdbba25 Mon Sep 17 00:00:00 2001
From: Dennis Zhou
Date: Sat, 19 Jan 2019 18:51:39 -0800
Zstd compression requires different amounts of memory for each level of
compression. The prior patches implemented indirection to allow for each
compression type to
401 - 500 of 994 matches
Mail list logo
