On Sat, Mar 4, 2017 at 5:23 PM, Bartosz Golaszewski
wrote:
> This driver never frees the interrupt descriptors it allocates. Fix
> it by using the resource managed version of irq_alloc_descs().
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
Commit-ID: 7d5c038a03acfbedeb3ffef9da1814a47191f6f1
Gitweb: http://git.kernel.org/tip/7d5c038a03acfbedeb3ffef9da1814a47191f6f1
Author: Dmitry Safonov
AuthorDate: Tue, 14 Mar 2017 14:41:26 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 14 Mar 2017 16:11:47 +0100
x86/hugetlb: Adjust t
On Sat, Mar 4, 2017 at 5:23 PM, Bartosz Golaszewski
wrote:
> The following series uses the recently introduced set of
> devm_irq_alloc_desc*() helpers in the GPIO drivers.
>
> While we're at it: if the modified drivers called request_irq(), it
> was changed to devm_request_irq() too.
>
> Some dri
Save a bit of time and avoid going through link speed change procedure
in configuration where link max speed is limited to Gen1 in DT.
Cc: yurov...@gmail.com
Cc: Lucas Stach
Cc: Bjorn Helgaas
Cc: Fabio Estevam
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-
As can be seen from [1]:
"...the different behavior between iMX6Q PCIe and iMX7D PCIe maybe
caused by the different controller version.
Regarding to the DOC description, the DIRECT_SPEED_CHANGE should be
cleared after the speed change from GEN1 to GEN2. Unfortunately, when
GEN1 device is used, th
Some designs implement reset GPIO via a GPIO expander connected to a
peripheral bus. One such example would be i.MX7 Sabre board where said
GPIO is provided by SPI shift register connected to a bitbanged SPI
bus. In order to support such designs allow reset GPIO request to defer
probing of the driv
Add various bits of code needed to support i.MX7D variant of the IP.
Cc: yurov...@gmail.com
Cc: Lucas Stach
Cc: Bjorn Helgaas
Cc: Rob Herring
Cc: Mark Rutland
Cc: Lee Jones
Cc: Fabio Estevam
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.
Hello, everyone:
This is a sixth iteration of the code that adds PCI-subsystem bits
necessary for enabling PCI support on i.MX7.
Chagnes since v5:
- Collected ACKs from Lee and Rob
Changes since v4 (can be found at [version4]):
- Dropped typo-fix patch (originally patch #1 of t
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 c
Hello,
This series add OF device ID tables to misc I2C drivers whose devices are
either used in Device Tree source files or are listed in binding docs as
a compatible string.
That's done because the plan is to change the I2C core to report proper OF
modaliases instead of always reporting a MODALI
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 c
On Sat, Mar 4, 2017 at 5:23 PM, Bartosz Golaszewski
wrote:
> Use device resource managed variants of irq_alloc_descs() and
> request_irq() and remove the code manually freeing irq resources.
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
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 c
On 03/14, Peter Zijlstra wrote:
>
> mutex_unlock(ctx->lock);
> put_ctx() /* >0 */
> free_task();
> mutex_lock(ctx->lock);
> mutex_lock(A->child_mutex);
>
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 c
2017-03-12 12:20+0100, Dmitry Vyukov:
> On Tue, Jan 17, 2017 at 5:00 PM, Dmitry Vyukov wrote:
>> On Tue, Jan 17, 2017 at 4:20 PM, Paolo Bonzini wrote:
>>>
>>>
>>> On 13/01/2017 12:15, Dmitry Vyukov wrote:
I've commented out the WARNING for now, but I am seeing lots of
use-after-fre
On Sat, Mar 4, 2017 at 5:23 PM, Bartosz Golaszewski
wrote:
> This driver never frees the interrupt descriptors it allocates. Fix
> it by using the resource managed version of irq_alloc_descs().
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
On Sat, Mar 4, 2017 at 5:23 PM, Bartosz Golaszewski
wrote:
> Use device resource managed variants of irq_alloc_descs() and
> request_irq() and remove the code manually freeing irq resources.
>
> Signed-off-by: Bartosz Golaszewski
Patch applied.
Yours,
Linus Walleij
On Tue, 14 Mar 2017, Gerd Hoffmann wrote:
> On a loaded virtualization host (dozen guests booting at the same time)
> it may happen that the ohci controller emulation doesn't manage to do
> timely frame processing, with the result that the io watchdog fires and
> considers the controller being dea
On Tue, Mar 14, 2017 at 10:21 PM, Minghsiu Tsai
wrote:
> The symptom is continuous log "mtk-jpeg 18004000.jpegdec: Context is NULL"
> in kernel log. It is becauese the error handling in irq doesn't clear
> interrupt.
>
> The calling flow like as below when issue happen
> mtk_jpeg_device_run()
> mt
On Tue, 2017-03-14 at 15:02 +, Lee Jones wrote:
> On Mon, 13 Mar 2017, Andy Shevchenko wrote:
>
> > Crystal Cove and Whiskey Cove are two different PMICs which are
> > installed on Intel Atom SoC based platforms.
> >
> > Moreover there are two independent drivers that by some reason are
> > s
From: Rafael J. Wysocki
Currently, intel_pstate_update_perf_limits() first converts the
policy minimum and maximum limits into percentages of the maximum
turbo frequency (rounding up to an integer) and then converts these
percentages into fractions by using fixed-point arithmetic to divide
them b
From: Rafael J. Wysocki
The coordination of P-state limits used by intel_pstate in the active
mode (ie. by default) is convoluted, hard to explain and confusing.
Fix that by modifying intel_pstate to use one set of per-policy
(ie. set via the cpufreq policy interface) limits for each logical
CPU
On Tue, Mar 14, 2017 at 04:19:10PM +0100, Oleg Nesterov wrote:
> On 03/14, Peter Zijlstra wrote:
> >
> > mutex_unlock(ctx->lock);
> > put_ctx() /* >0 */
> > free_task();
> > mutex_lock(ctx->lock);
> >
From: Rafael J. Wysocki
intel_pstate_verify_policy() forces per-policy cpufreq limits to
stay within the global limits set via min/max_perf_pct.
The reason for doing that was the reinitialization of performance
limits in intel_pstate_set_policy() that prevented the max limit from
being set to an
Hi,
Three limits-related fixes more.
[1/3] fixes a regression introduced by another recent fix.
[2/3] gets rid of excessive rounding errors in computations.
[3/3] makes limits work in the most straightforward way possible.
On top of https://patchwork.kernel.org/patch/9622401/ .
Thanks,
Rafael
On Tue, Jan 10, 2017 at 7:51 PM, William Breathitt Gray
wrote:
> PC/104 drivers should be hidden on machines which do not support PC/104
> devices. This patch adds the PC104 Kconfig option as a dependency for
> the relevant PC/104 device driver Kconfig options.
>
> Cc: Linus Walleij
> Cc: Alexan
Hi Stafford,
On Tue, Mar 14, 2017 at 3:56 PM, Stafford Horne wrote:
> This was detected by allmodconfig, errors reported:
>
> ERROR: "empty_zero_page" [net/ceph/libceph.ko] undefined!
> ERROR: "__ucmpdi2" [lib/842/842_decompress.ko] undefined!
> ERROR: "empty_zero_page" [fs/nfs/objlayout/objla
On (03/14/17 09:14), Dmitry Vyukov wrote:
> Another one now involving rds_tcp_listen_stop
:
> kworker/u4:1/19 is trying to acquire lock:
> (sk_lock-AF_INET){+.+.+.}, at: [] lock_sock
> include/net/sock.h:1460 [inline]
> (sk_lock-AF_INET){+.+.+.}, at: []
> rds_tcp_listen_stop+0x5c/0x150 net/rds
On Tue, Feb 28, 2017 at 5:51 PM, Fabrice Gasnier wrote:
> Provide OF support. Device drivers can get IIO triggers from dt.
> Introduce IIO trigger specifiers, so there are:
> - IIO trigger providers, e.g. dt nodes designated with
> #io-trigger-cells=
> - IIO trigger consumers, e.g. phandles lis
On Fri, 10 Mar 2017 23:39:44 +0100, Matthias Schiffer wrote:
> @@ -233,17 +234,30 @@ static struct vxlan_dev *vxlan_vs_find_vni(struct
> vxlan_sock *vs, __be32 vni)
> vni = 0;
>
> hlist_for_each_entry_rcu(vxlan, vni_head(vs, vni), hlist) {
> - if (vxlan->default_d
On Wed, Mar 8, 2017 at 6:43 PM, Will Deacon wrote:
> On Wed, Mar 08, 2017 at 03:20:41PM +, Mark Rutland wrote:
>> On Wed, Mar 08, 2017 at 02:42:10PM +0100, Dmitry Vyukov wrote:
>> > I think if we scope compiler atomic builtins to KASAN/KTSAN/KMSAN (and
>> > consequently x86/arm64) initially, i
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/mm
head: 7d5c038a03acfbedeb3ffef9da1814a47191f6f1
commit: 7d5c038a03acfbedeb3ffef9da1814a47191f6f1 [1/1] x86/hugetlb: Adjust to
the new native/compat mmap bases
config: i386-randconfig-x002-201711 (attached as .config)
compi
On Tue, Mar 14, 2017 at 04:22:52PM +0100, Dmitry Vyukov wrote:
> Any other suggestions?
> - return i + xadd(&v->counter, i);
> + return i + arch_xadd(&v->counter, i);
> +#define xadd(ptr, v) \
> +({ \
> +
On Tue, 2017-03-14 at 08:09 -0700, Eric Dumazet wrote:
> On Tue, Mar 14, 2017 at 8:03 AM, Paolo Abeni wrote:
>
> > I'm wondering if we really need to keep the fragment queue lock held
> > while sending the icmp packet ? we hold a reference to the struct, so
> > it can't be deleted, and AFAICS aft
On Tue, Mar 14, 2017 at 04:22:52PM +0100, Dmitry Vyukov wrote:
> -static __always_inline int atomic_read(const atomic_t *v)
> +static __always_inline int arch_atomic_read(const atomic_t *v)
> {
> - return READ_ONCE((v)->counter);
> + return READ_ONCE_NOCHECK((v)->counter);
Should NOCHEKC
Commit-ID: e13b73dd9c8003993b171173ba803363faf74238
Gitweb: http://git.kernel.org/tip/e13b73dd9c8003993b171173ba803363faf74238
Author: Dmitry Safonov
AuthorDate: Tue, 14 Mar 2017 14:41:26 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 14 Mar 2017 16:29:16 +0100
x86/hugetlb: Adjust t
System Reset Controller in i.MX7 doesn't have any commonality with IP
block found in i.MX5 and i.MX6 SoC families. Given that and the new
upstream driver for i.MX7 variant (see
https://lkml.org/lkml/2017/2/21/466) remove "fsl,imx51-src" from
compatibility string.
Cc: yurov...@gmail.com
Cc: Fabio E
On Tue, Mar 14, 2017 at 4:58 PM, Filip Štědronský wrote:
> Hi,
>
> On Tue, Mar 14, 2017 at 01:18:01PM +0200, Amir Goldstein wrote:
>> I claim that fanotify filters event by mount not because it
>> was a requirement, but because it was an implementation challenge
>> to do otherwise.
>>
>> And I cla
> Il giorno 07 mar 2017, alle ore 02:00, Bart Van Assche
> ha scritto:
>
> On Sat, 2017-03-04 at 17:01 +0100, Paolo Valente wrote:
>> Finally, a few details on the patchset.
>>
>> The first two patches introduce BFQ-v0, which is more or less the
>> first version of BFQ submitted a few years ag
On Mon, Mar 6, 2017 at 11:02 AM, Uwe Kleine-König
wrote:
>> Anyway, for sh-sci.c, platforms either have DT and GPIOLIB, or they do not
>> need mctrl-gpio.
>
> So we're in agreement now that HALFGPIOLIB is the way to go?
> Linus, what do you think?
I'm too swamped in mail and work to figure this
On Tue, Mar 14, 2017 at 02:58:24PM +0100, Radim Krčmář wrote:
> 2017-03-14 01:44+0200, Michael S. Tsirkin:
> > Guests running Mac OS 5, 6, and 7 (Leopard through Lion) have a problem:
> > unless explicitly provided with kernel command line argument
> > "idlehalt=0" they'd implicitly assume MONITOR
On 03/03/2017 12:53 AM, Randy Dunlap wrote:
On 03/01/17 10:22, Georgi Djakov wrote:
diff --git a/drivers/interconnect/Kconfig b/drivers/interconnect/Kconfig
new file mode 100644
index ..103524b59905
--- /dev/null
+++ b/drivers/interconnect/Kconfig
@@ -0,0 +1,10 @@
+menuconfig INTERC
On Tue, Mar 14, 2017 at 12:08:33PM +, Sudeep Holla wrote:
> On Tue, Feb 21, 2017 at 7:11 PM, Stafford Horne wrote:
> > From: Stefan Kristiansson
> >
> > Motivation for this is to be able to print the way information
> > properly in print_cpuinfo(), instead of hardcoding it to one.
> >
>
> An
On Tue, Mar 14, 2017 at 06:45:49PM +0800, Jeffy Chen wrote:
> Currently we are adding all components from the dts, if one of their
> drivers been disabled, we would not be able to bring up others.
>
> Refactor component match logic, follow exynos drm.
>
> Signed-off-by: Jeffy Chen
Thanks for re
On 03/14, Peter Zijlstra wrote:
>
> Do we want a WARN_ON_ONCE(atomic_read(&tsk->usage)); in free_task()?
> Because in the above scenario we're freeing it with references on.
Not sure, in this case copy_process() should decrement tsk->usage
before free_task(), note the atomic_set(&tsk->usage, 2) in
On Monday, March 13, 2017 09:07:24 PM Krzysztof Kozlowski wrote:
> Structures watchdog_device, watchdog_ops and s3c2410_wdt_variant are not
> modified so they can be made const to increase code safeness.
>
> Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Bartlomiej Zolnierkiewicz
Best regards
On Tue, Mar 14, 2017 at 12:33 PM, Andrey Smirnov
wrote:
> System Reset Controller in i.MX7 doesn't have any commonality with IP
> block found in i.MX5 and i.MX6 SoC families. Given that and the new
> upstream driver for i.MX7 variant (see
> https://lkml.org/lkml/2017/2/21/466) remove "fsl,imx51-sr
On Wed, Mar 1, 2017 at 7:01 PM, Icenowy Zheng wrote:
> As the pinctrl driver selecting is refactored in Kconfig file of
> pinctrl-sunxi, now we can select only PINCTRL for Allwinner platform,
> and the default value of several pinctrl drivers useful on ARM64
> Allwinner SoCs will become Y.
>
> Th
On 03/14/2017 09:35 AM, Paolo Valente wrote:
> First, I've developed BFQ in a sort of
> first-the-problem-then-the-solution way. That is, each time, I have
> first implemented a benchmark that enabled me to highlight the problem
> and get all relevant statistics on it, then I have worked on BFQ to
On 03/03/2017 08:21 AM, Rob Herring wrote:
On Wed, Mar 01, 2017 at 08:22:33PM +0200, Georgi Djakov wrote:
Modern SoCs have multiple processors and various dedicated cores (video, gpu,
graphics, modem). These cores are talking to each other and can generate a lot
of data flowing through the on-ch
> And the way how this function is used is a horrible hack. It's called from
> a random driver at some random point in time.
>
> The proper solution is to identify the bus at the point where the bus is
> discovered and switch it to mmconfig if possible.
But how would you know that it is safe?
AFA
Hi Linus,
On 03/14/2017 09:23 AM, Linus Walleij wrote:
> On Wed, Feb 22, 2017 at 5:56 PM, Sebastien Bourdelin
> wrote:
>> On 02/04/2017 05:14 AM, Linus Walleij wrote:
>
+ gpiod_set_array_value_cansleep(gpios->ndescs, gpios->desc, values);
>>>
>>> This can also fail and you should chec
2017-03-14 16:18 GMT+01:00 Linus Walleij :
>
> Excellent series, applied all and pushing to the build servers for
> testing.
>
Thanks!
> Interested in the job to go over to drivers/pinctrl and check if we
> have some dangling descs there if this works out?
>
If time permits, I will be improving
Hi Lucas,
Thanks for the comments!
On 03/09/2017 11:56 AM, Lucas Stach wrote:
Am Mittwoch, den 01.03.2017, 20:22 +0200 schrieb Georgi Djakov:
This patch introduce a new API to get the requirement and configure the
interconnect buses across the entire chipset to fit with the current demand.
The
On Tue, Mar 14, 2017 at 04:37:05PM +0100, Oleg Nesterov wrote:
> On 03/14, Peter Zijlstra wrote:
> >
> > Do we want a WARN_ON_ONCE(atomic_read(&tsk->usage)); in free_task()?
> > Because in the above scenario we're freeing it with references on.
>
> Not sure, in this case copy_process() should decr
On Tue, Mar 14, 2017 at 04:32:30PM +0100, Peter Zijlstra wrote:
> On Tue, Mar 14, 2017 at 04:22:52PM +0100, Dmitry Vyukov wrote:
> > -static __always_inline int atomic_read(const atomic_t *v)
> > +static __always_inline int arch_atomic_read(const atomic_t *v)
> > {
> > - return READ_ONCE((v)->co
On 03/03/2017 04:07 AM, Saravana Kannan wrote:
On 03/01/2017 10:22 AM, Georgi Djakov wrote:
This patch introduce a new API to get the requirement and configure the
interconnect buses across the entire chipset to fit with the current
demand.
[..]
+int interconnect_set(struct interconnect_pat
* Roger Quadros [170313 04:55]:
> --- a/arch/arm/mach-omap2/omap_hwmod.c
> +++ b/arch/arm/mach-omap2/omap_hwmod.c
> @@ -2149,7 +2149,7 @@ static int _idle(struct omap_hwmod *oh)
> _idle_sysc(oh);
> _del_initiator_dep(oh, mpu_oh);
>
> - if (oh->clkdm)
> + if (oh->clkd
Cut-n-paste enablement of 802.3ad bonding on 25G NICs, which currently
report 0 as their bandwidth.
CC: Jay Vosburgh
CC: Veaceslav Falico
CC: Andy Gospodarek
CC: net...@vger.kernel.org
Signed-off-by: Jarod Wilson
---
note: I swear I saw a patch for this already, but I don't see it on the
list
Hi Daniel,
Yes checkpatch.pl was telling us this. I didn't think we had the
"authority" to modify that file. Is it OK if we put the
vendor-prefixes.txt change in the first patch (device tree bindings) or
so you think we should have an 0003 patch for just that?
Brian
On 03/14/2017 06:16 AM
On Tuesday, March 14, 2017 04:55:46 PM Krzysztof Kozlowski wrote:
> On Tue, Mar 14, 2017 at 4:46 PM, Bartlomiej Zolnierkiewicz
> wrote:
> >
> > Hi,
> >
> > On Saturday, March 11, 2017 08:25:34 PM Krzysztof Kozlowski wrote:
> >> There is no need for separate defines for Exynos4 and Exynos5 phy enab
On 14/03/17 14:09, Stafford Horne wrote:
> On Tue, Mar 14, 2017 at 01:45:24PM +, Sudeep Holla wrote:
>>
>>
>> On 14/03/17 13:11, Stefan Kristiansson wrote:
>>> On Tue, Mar 14, 2017 at 12:08:33PM +, Sudeep Holla wrote:
On Tue, Feb 21, 2017 at 7:11 PM, Stafford Horne wrote:
> From
On Tue, Mar 14, 2017 at 3:03 PM, Bartlomiej Zolnierkiewicz
wrote:
>
> Hi,
>
> On Saturday, March 11, 2017 07:25:22 PM Krzysztof Kozlowski wrote:
>> The Exynos4412 has the same watchdog as newer SoCs (e.g. Exynos5250).
>> Just like the others, for working it requires additional steps in Power
>> Ma
-infrastructure-v3/20170314-163334
base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
lib/crc32.c:148: warning: No description found for parameter 'tab)[256]'
lib/crc32.c:148: warning:
On Wed, Mar 1, 2017 at 7:01 PM, Icenowy Zheng wrote:
> ARM64 Allwinner SoCs used to have every pinctrl driver selected in
> ARCH_SUNXI. Change this to make their default value to (ARM64 &&
> ARCH_SUNXI).
>
> Signed-off-by: Icenowy Zheng
> Reviewed-by: Andre Przywara
Patch applied with Maxime's
On Mon, Mar 13, 2017 at 2:05 PM, Andy Lutomirski wrote:
> On Mon, Mar 13, 2017 at 9:55 AM, Peter Zijlstra wrote:
>> On Mon, Mar 13, 2017 at 09:44:02AM -0700, Andy Lutomirski wrote:
>>> static void x86_pmu_event_mapped(struct perf_event *event)
>>> {
>>> if (!(event->hw.flags & PERF_X86_EVENT_
On Tue, Mar 14, 2017 at 3:44 PM, Vignesh R wrote:
> On Monday 13 March 2017 01:35 AM, Andy Shevchenko wrote:
>> On Wed, Mar 8, 2017 at 2:19 PM, Vignesh R wrote:
>>> Passing "serial" as name during request_irq() results in all serial port
>>> irqs have same name. This does not help much to easily
Included in the current storvsc driver for Hyper-V is the ability
to access luns on an FC fabric via a virtualized fiber channel
adapter exposed by the Hyper-V host. The driver also attaches to the FC
transport to allow host and port names to be published under
/sys/class/fc_host/hostX. Current cus
On Mon, 2017-03-13 at 18:43 +0100, Andrey Konovalov wrote:
> On Thu, Jan 12, 2017 at 11:40 AM, Chas Williams <3ch...@gmail.com> wrote:
> > On Wed, 2017-01-11 at 20:36 -0800, Cong Wang wrote:
> >> On Wed, Jan 11, 2017 at 11:46 AM, Michal Hocko wrote:
> >> > On Wed 11-01-17 20:45:25, Michal Hocko wr
On 2017.03.12 10:19 Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> PID controller parameters only need to be initialized if the
> get_target_pstate_use_performance() P-state selection routine
> is going to be used. It is not necessary to initialize them
> otherwise, so don't do that.
>
>
Hi Rafael,
I can not get this patch to apply.
My start point is kernel 4.11-rc2, so maybe (probably) it is my problem.
On 2017.03.12 10:22 Rafael J. Wysocki wrote:
... [cut] ...
> drivers/cpufreq/intel_pstate.c | 77
> -
> 1 file changed, 53 insertions(
On 03/13/2017 05:19 AM, Michal Hocko wrote:
On Fri 10-03-17 12:39:27, Yasuaki Ishimatsu wrote:
On 03/10/2017 08:58 AM, Michal Hocko wrote:
[...]
OK so I did with -m 2G,slots=4,maxmem=4G -numa node,mem=1G -numa node,mem=1G
which generated
[...]
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x
On 14/03/17 15:53, Brian Dodge wrote:
Hi Daniel,
Yes checkpatch.pl was telling us this. I didn't think we had the
"authority" to modify that file.
You don't really need authority to propose changes (e.g. send a patch).
I guess you might attract sharp words from a maintainer if the proposed
c
hi Matthew,
On 3/13/2017 4:09 PM, matthew.gerl...@linux.intel.com wrote:
On Fri, 10 Mar 2017, Li, Yi wrote:
Hi Matthew
Hi Yi,
On 3/10/2017 11:44 AM, matthew.gerl...@linux.intel.com wrote:
On Thu, 9 Mar 2017, yi1...@linux.intel.com wrote:
From: Yi Li
Hi Yi,
Just one question
Hi David,
On 01/03/17 01:48, David Daney wrote:
> For an already existing irqdomain hierarchy, as might be obtained via
> a call to pci_enable_msix(), a PCI driver wishing to add an additional
> irqdomain to the hierarchy needs to be able to insert the irqdomain to
> that already initialized hiera
Add support for the National Instruments 169445 board
Changes from v3:
- Remove unused ngpios DT property from documentation for the NAND GPIO
bindings and the actual board device tree.
- Add no-output property to the same, for the GPIO controller that is only
used for input signals from NAN
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan
---
.../bindings/gpio/ni,169445-nand-gpio.txt | 38 ++
drivers/gpio/gpio-mmio.c | 1
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mips/boot/dts/ni/169445.dts
On 01/03/17 15:23, Aleksey Makarov wrote:
> The original patch makes the condition always true, so it is wrong.
>
> It masks (but not fixes) the bug described in the commit message
> but introduces a regression (no console is selected by SPCR)
> in regular (no 'console=ttyAMA') case.
>
> s/||/&
[added arm64 maintainers and arm list to recipients]
Hi,
Am Donnerstag, 9. März 2017, 17:24:07 CET schrieb Kirill A. Shutemov:
> Convert all non-architecture-specific code to 5-level paging.
>
> It's mostly mechanical adding handling one more page table level in
> places where we deal with pud_
Hi Arnd,
2017-01-14 0:40 GMT+09:00 Arnd Bergmann :
> In commit a76bcf557ef4 ("Kbuild: enable -Wmaybe-uninitialized warning
> for "make W=1""), I reverted another change that happened to fix a problem
> with old compilers, and now we get this report again with old compilers
> (prior to gcc-4.8) and
On Wed, 22 Feb 2017, Rask Ingemann Lambertsen wrote:
> commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot")
> was intended to fix the case where a board uses an AXP806 in slave mode,
> but the boot loader leaves it in master mode for lack of AXP806 support.
> But now the driv
On Wed, 22 Feb 2017, Rask Ingemann Lambertsen wrote:
> commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot")
> was intended to fix the case where a board uses an AXP806 in slave mode,
> but the boot loader leaves it in master mode for lack of AXP806 support.
> But now the driv
On Tue 14-03-17 12:05:59, YASUAKI ISHIMATSU wrote:
>
>
> On 03/13/2017 05:19 AM, Michal Hocko wrote:
> >On Fri 10-03-17 12:39:27, Yasuaki Ishimatsu wrote:
> >>On 03/10/2017 08:58 AM, Michal Hocko wrote:
[...]
> >>># echo online_movable > /sys/devices/system/memory/memory34/state
> >>># grep . /sy
Hi Tyler,
"Baicar, Tyler" writes:
> Hello Punit,
>
> I ran the test with and without the kernel patch you're suggesting
> below. I do not see the "bad pmd ..." print that you are seeing in
> either case.
Thanks for trying out the patch. It's important to understand why we are
seeing the differe
On 13 February 2017 at 12:02, Andy Yan wrote:
> Rockchip finally named the SOC as RV1108, so change it.
>
> Signed-off-by: Andy Yan
Thanks, applied for fixes!
Kind regards
Uffe
>
> ---
>
> Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 d
On Tue, Mar 14, 2017 at 12:47:02AM -0700, Lance Roy wrote:
> I am not sure how the rcu_scheduler_active changes in __synchronize_srcu work,
> but there seem to be a few problems in them. First,
> "if (done && likely(!driving))" on line 453 doesn't appear to ever happen,
> as driving doesn't get set
On 10 February 2017 at 23:54, Alexey Khoroshilov wrote:
> There is no check if clk_prepare_enable() succeed in sdhci_pxav2_probe().
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov
Thanks, applied for next!
Kind regards
Uffe
> ---
> driv
On 18 February 2017 at 18:06, Michał Zegan wrote:
> The mmc host was added in meson_mmc_probe, but never removed in
> meson_mmc_remove.
> Fix that by removing the host before deallocating other resources.
>
> Signed-off-by: Michał Zegan
> Tested-by: Michał Zegan
Thanks, applied for next!
Kind
On 1 March 2017 at 23:11, Guenter Roeck wrote:
> HS400-ES devices fail to initialize with the following error messages.
>
> mmc1: power class selection to bus width 8 ddr 0 failed
> mmc1: error -110 whilst initialising MMC card
>
> This was seen on Samsung Chromebook Plus. Code analysis points to
Le lundi 13 mars 2017 à 10:45 +, Russell King - ARM Linux a écrit :
> On Mon, Mar 13, 2017 at 11:02:34AM +0100, Hans Verkuil wrote:
> > On 03/11/2017 07:14 PM, Steve Longerbeam wrote:
> > > The event must be user visible, otherwise the user has no indication
> > > the error, and can't correct i
On 18 February 2017 at 18:06, Michał Zegan wrote:
> This patch fixes the case where meson_mmc_probe function fails before
> core_clk is enabled.
> Originally, that would result in a try to disable the core clock, and if
> it was not already enabled, it would result in a kernel warning.
> This issu
Hi Wolfgang,
On 03/14/2017 08:11 AM, Wolfgang Grandegger wrote:
> ... snip ...
>>> A few other things to check:
>>>
>>> Run "cangen" and monitor the message with "candump -e any,0:0,#FFF".
>>> Then 1) disconnect the cable or 2) short-circuit CAN low and high at the
>>> connector. You should s
Hi Aleksey,
(Sorry for the delayed response, was on vacation)
On 02/03/17 13:11, Aleksey Makarov wrote:
> If a console was specified by ACPI SPCR table _and_ command line parameters
> like
> "console=ttyAMA0" _and_ "earlycon" were specified, then log messages
> appear twice.
>
> This issue was
On Mon, Mar 13, 2017 at 08:55:21AM -0700, Paul E. McKenney wrote:
> On Mon, Mar 13, 2017 at 01:46:21PM +0100, Peter Zijlstra wrote:
> > On Thu, Mar 09, 2017 at 10:37:32AM -0800, Paul E. McKenney wrote:
> > > And it does pass light testing. I will hammer it harder this evening.
> > >
> > > So plea
2017-01-22 23:02 GMT+09:00 Masahiro Yamada :
> The patterns '.*.orig' and '.*.rej' are cleaned away by '*.orig' and
> '*.rej' seen two lines above.
>
> Signed-off-by: Masahiro Yamada
Applied to linux-kbuild/kbuild.
--
Best Regards
Masahiro Yamada
On 19 February 2017 at 04:19, Andreas Färber wrote:
> Suppress COMMON_CLK_PXA and MMC_PXA for now as they don't build on arm64.
> Also suppress the deprecated SERIAL_PXA in favor of SERIAL_8250_PXA.
>
> Signed-off-by: Andreas Färber
> ---
> arch/arm64/Kconfig.platforms | 5 +
> drivers/clk/K
On Tue, 2017-03-14 at 16:35 +0100, Paolo Valente wrote:
> > Il giorno 07 mar 2017, alle ore 02:00, Bart Van Assche
> > ha scritto:
> >
> > Additionally, the complexity of the code is huge. Just like for CFQ,
> > sooner or later someone will run into a bug or a performance issue
> > and will post
Hi,
On Sunday, March 12, 2017 08:28:43 PM Sergei Shtylyov wrote:
> Hello!
>
> On 03/09/2017 04:01 PM, Bartlomiej Zolnierkiewicz wrote:
>
> > Add Palmchip BK3710 PATA controller driver.
> >
> > Signed-off-by: Bartlomiej Zolnierkiewicz
> [...]
> > diff --git a/drivers/ata/pata_bk3710.c b/drivers
801 - 900 of 1088 matches
Mail list logo
