2017-05-27 18:47 GMT+02:00 Andy Shevchenko :
> On Sat, May 27, 2017 at 7:45 PM, Andy Shevchenko
> wrote:
>> On Thu, May 25, 2017 at 11:33 AM, Bartosz Golaszewski wrote:
>>> We're currently only checking the first character of the input to the
>>> debugfs event files, so a string like '0sdfdsf' is
Tomasz,
On Sun, 28 May 2017, Tomasz Figa wrote:
> On Sat, May 27, 2017 at 8:12 PM, Thomas Gleixner wrote:
> I think we might simply have a language barrier here unfortunately. I
> agree, though, that we need a better description of the problem. Next
> time we will help Jeffy with polishing the co
Once controller is in DEAD or DELETING state a call to delete_destroy
from nvme_uninit_ctrl results in setting the latency tolerance via
nvme_set_latency_tolerance callback even though queues have already
been killed. This in turn leads the PID to go into uninterruptible
sleep and prevents removal
This patches fixes the controller removal going to sleep for ever
without completion. Also as a side-effect if this patch:
https://patchwork.kernel.org/patch/9740945/ goes throw which takes a
dev lock before calling reset from PCI layer would deadlock if a
successive call happens to land for same
From: Colin Ian King
Trivial fix to spelling mistake in dev_err message
Signed-off-by: Colin Ian King
---
drivers/remoteproc/remoteproc_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/remoteproc/remoteproc_core.c
b/drivers/remoteproc/remoteproc_core.c
index
Signed-off-by: Madalin Bucur
Signed-off-by: Camelia Groza
---
Documentation/networking/dpaa.txt | 194 ++
1 file changed, 194 insertions(+)
create mode 100644 Documentation/networking/dpaa.txt
diff --git a/Documentation/networking/dpaa.txt
b/Documentation/n
On Fri, 2017-05-26 at 10:48 +0200, Daniel Lezcano wrote:
> The recent changes made the fttmr010 to be more generic and support different
> timers with a very few differences like moxart or aspeed.
>
> The aspeed timer uses a countdown and there is a test against the aspeed2400
> compatible string
If i understand the current direction for smalloc, its to implement it
without the ability to "unseal," which has implications on how LSM
implementations and other users of these dynamic allocations handle
things. If its implemented without a writeable interface for modules
which need it, then swit
Hi Paul,
After merging the rcu tree, today's linux-next build (bfin
BF526-EZBRD_defconfig and several other bfin configs) failed like this:
In file included from include/linux/srcu.h:60:0,
from include/linux/notifier.h:15,
from include/linux/memory_hotplug.h:6,
>> Still, isn't there subsystem-level default that all events are disabled
>> by default? If such, then current hi8435 state breaks subsystem-level
>> rules, which is a [userspace-visible] bug. I'm not sure how far should
>> we go in bug compatibility.
>
> It is indeed the subsystem default (as m
On Mon, May 29, 2017 at 7:40 AM, Hyunchul Lee wrote:
>
> and I missed the following case.
>
> in some embedded systems, clean-up for shutdown should be fast.
> during this clean-up, freeze file system to guarantee integrity.
> umount with MNT_DETACH is not suitable because of not killing tasks.
>
Hi Linus,
After merging the gpio tree, today's linux-next build (arm
orion5x_defconfig) failed like this:
drivers/gpio/gpio-mvebu.c:1062: undefined reference to
`__devm_regmap_init_mmio_clk'
drivers/gpio/gpio-mvebu.c:1078: undefined reference to
`__devm_regmap_init_mmio_clk'
Caused by commit
Reza Arbab writes:
> On Fri, May 26, 2017 at 01:46:58PM +1000, Michael Ellerman wrote:
>>Reza Arbab writes:
>>
>>> On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote:
The commit message for 3af229f2071f says:
In practice, we never see a system with 256 NUMA nodes,
Currently applications can explicitly enable or disable THP for a memory
region using MADV_HUGEPAGE or MADV_NOHUGEPAGE. However, once either of
these advises is used, the region will always have
VM_HUGEPAGE/VM_NOHUGEPAGE flag set in vma->vm_flags.
The MADV_RESET_HUGEPAGE resets both these flags and
From: Eric Biggers
synaptics_query_hardware() was being passed a
'struct synaptics_device_info' in uninitialized stack memory, then not
always initializing all fields. This caused garbage to show up in
certain fields, making the touchpad unusable.
Fix by zeroing the device info, so all fields d
Rob Landley writes:
> On 05/25/2017 04:24 PM, Stephen Rothwell wrote:
>> Hi Michael,
>>
>> On Thu, 25 May 2017 23:02:06 +1000 Michael Ellerman
>> wrote:
>>>
>>> It'll be:
>>>
>>> ee35011fd032 ("initramfs: make initramfs honor CONFIG_DEVTMPFS_MOUNT")
>>
>> And Andrew has asked me to drop that p
Hi Rafael,
On 5/28/2017 12:48 AM, Rafael J. Wysocki wrote:
> On Saturday, May 27, 2017 07:17:42 PM Sricharan R wrote:
>> While deferring the probe of IOMMU masters, xlate and
>> add_device callbacks called from iort_iommu_configure
>> can pass back error values like -ENODEV, which means
>> the IOM
Oops, sent last one without patch on accident. Attached this time.
This has been happening for me since 4.10
dquot_writeback_dquots expects a lock to be held on super_block->s_umount ,
and reiserfs_sync_fs, which calls dquot_writeback_dquots, does not
obtain such a lock.
Thus, the following wa
This has been happening for me since 4.10
dquot_writeback_dquots expects a lock to be held on super_block->s_umount ,
and reiserfs_sync_fs, which calls dquot_writeback_dquots, does not
obtain such a lock.
Thus, the following warning is generated:
[Sun May 28 04:58:06 2017] [ cut her
OCC provides historical minimum and maximum value for the sensor
readings. This patch exports them as highest and lowest attributes
for the inband sensors copied by OCC to main memory.
Signed-off-by: Shilpasri G Bhat
---
Changes from V4:
- Got rid of 'len' variable in populate_attr_groups
drive
and I missed the following case.
in some embedded systems, clean-up for shutdown should be fast.
during this clean-up, freeze file system to guarantee integrity.
umount with MNT_DETACH is not suitable because of not killing tasks.
On Mon, May 29, 2017 at 10:18:34AM +0900, Hyunchul Lee wrote:
> H
Signed-off-by: Martin Schiller
---
drivers/pinctrl/pinctrl-xway.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-xway.c b/drivers/pinctrl/pinctrl-xway.c
index d4167e2..f9e98a7 100644
--- a/drivers/pinctrl/pinctrl-xway.c
+++ b/drivers/pinctrl/pinctrl-xw
Hi Gustavo,
> desc = dmaengine_prep_slave_sg(dma->ch, sgt->sgl, sgt->nents,
> dma->direction, DMA_PREP_INTERRUPT);
>
> + if (!desc) {
> + dev_err(&sdd->master->dev,
> + "%s:dmaengine_prep_slave_sg Failed\n", __func__)
Hi all,
Changes since 20170526:
Non-merge commits (relative to Linus' tree): 2862
3154 files changed, 118750 insertions(+), 64872 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/lin
On 05/27/2017 06:53 AM, David Woods wrote:
> Using the device_property interfaces allows the dw_mmc driver to work
> on platforms which run on either device tree or ACPI.
>
> Signed-off-by: David Woods
> Reviewed-by: Chris Metcalf
> Cc: sta...@vger.linux.org
Acked-by: Jaehoon Chung
Best Regar
Any further review comments on this patch series?
can it go in 4.13?
On Tue, May 16, 2017 at 2:03 PM, Ganapatrao Kulkarni
wrote:
> Extending json/jevent framework for parsing arm64 event files.
> Adding jevents for ThunderX2 implementation defined PMU events.
>
> v3:
>- Addressed comments fro
The help info of `make -C=1` is little confusing, make it clear.
Signed-off-by: Cao jin
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index efa267a..b34a34d 100644
--- a/Makefile
+++ b/Makefile
@@ -1417,7 +1417,7 @@ help:
@echo ' m
Hi Mark, Will,
can you please review this patchset?
On Wed, May 17, 2017 at 12:30 PM, Ganapatrao Kulkarni
wrote:
> This adds PMU driver for Cavium's ThunderX2 SoC UNCORE devices.
> The SoC has PMU support in its L3 cache controller (L3C) and in the
> DDR4 Memory Controller (DMC).
>
> Ganapatrao
Thanks for catching this.
BR,
Souvik
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-
> x86-ow...@vger.kernel.org] On Behalf Of priyalee.kushw...@intel.com
> Sent: Saturday, May 27, 2017 8:48 PM
> To: dvh...@infradead.org; Chakravarty, Souvik
Signed-off-by: Josh Benson
---
drivers/thermal/thermal_hwmon.c | 20 +++-
1 file changed, 3 insertions(+), 17 deletions(-)
diff --git a/drivers/thermal/thermal_hwmon.c b/drivers/thermal/thermal_hwmon.c
index 541af5946203..c4a508a124dc 100644
--- a/drivers/thermal/thermal_hwmon.c
Hi, Richard.
On Mon, May 29, 2017 at 09:43:46AM +0900, Hyunchul Lee wrote:
> On Sat, May 27, 2017 at 01:23:38AM -0700, Christoph Hellwig wrote:
> > > +static int ubifs_freeze_super(struct super_block *sb)
> > > +{
> > > + struct ubifs_info *c = sb->s_fs_info;
> > > + int err;
> > > +
> > > + dbg_g
Current busy-wait loops are implemented by repeatedly calling cpu_relax()
to give an arch option for a low-latency option to improve power and/or
SMT resource contention.
This poses some difficulties for powerpc, which has SMT priority setting
instructions (priorities determine how ifetch cycles a
Guenter Roeck writes:
> On 05/26/2017 06:22 PM, Murilo Opsfelder Araujo wrote:
>> drivers/watchdog/wdrtas.c uses symbols defined in arch/powerpc/kernel/rtas.c,
>> which are exported iff CONFIG_PPC_RTAS is selected. Building wdrtas.c without
>> setting CONFIG_PPC_RTAS throws the following errors:
hi Linux
http://www.retirodecasais.novidadedevida.com.br/poll_success.php?rule=266d8zbvkqkdm2
Yours
Dennis
Hi, Richard.
On Fri, May 26, 2017 at 11:52:42AM +0200, Richard Weinberger wrote:
> Hyunchul,
>
> Am 26.05.2017 um 01:30 schrieb Hyunchul Lee:
> > From: Hyunchul Lee
> >
> > for un/freeze support, implement freeze_super and un/freeze_fs
> > of super_operations.
> > ubifs_freeze_super just calls
__zram_bvec_write has some of duplicated logic for zram meta
data handling of same_page|dedup_page|compressed_page.
This patch aims to clean it up without behavior change.
Cc: Sergey Senozhatsky
Signed-off-by: Minchan Kim
---
drivers/block/zram/zram_drv.c | 70 +-
On Sat, May 27, 2017 at 01:23:38AM -0700, Christoph Hellwig wrote:
> > +static int ubifs_freeze_super(struct super_block *sb)
> > +{
> > + struct ubifs_info *c = sb->s_fs_info;
> > + int err;
> > +
> > + dbg_gen("starting");
> > + /* freeze_super always succeeds if file system is in read-on
Hi Wolfram
Thankyou for the fixup
On 28/05/17 18:30, Wolfram Sang wrote:
> It is 'R-Car', not 'RCar'. No code or binding changes, only descriptive text.
>
> Signed-off-by: Wolfram Sang
Acked-by: Kieran Bingham
Mauro,
I'll leave this for you to pick up when you're ready.
Thanks
Kieran
>
Hey, things continue to look good, and rc3 isn't even very big. I'm
hoping there's not another shoe about to drop, but so far this really
feels like a nice calm release cycle, despite the size of the merge
window.
Knock wood.
Anyway, rc3 has a little bit of everything. The biggest single change
i
On Fri, May 26, 2017 at 10:02:25PM +0100, Piotr Gregor wrote:
> The test for INTx masking via config space command performed
> in pci_intx_mask_supported() should be performed before PCI device
> can be used. This is to avoid reading/writing of PCI_COMMAND_INTX_DISABLE
> register which may collide
On 01/01/2017 02:42 PM, Florian Fainelli wrote:
> Hi all,
>
> This patch series removes dead DSA code in the blackfin board specific
> code. There is no in tree driver for the KSZ8893M, and clearly this
> would not compile anymore.
>
> Preparatory patch to help remove the legacy DSA platform de
Hi Andrew,
On Fri, 26 May 2017 23:36:00 -0700 Andrew Morton
wrote:
>
> On Fri, 26 May 2017 15:48:51 -0500 Dave Kleikamp
> wrote:
>
> > Andrew,
> >
> > Do you want to pick this up into akpm-current? I could push it through
> > the jfs tree, but without the change to write_one_page(), my versi
On Sun, May 28, 2017 at 11:56 AM, Boris Lukashev
wrote:
> So what about a middle ground where CoW semantics are used to enforce
> the state of these allocations as RO, but provide a strictly
> controlled pathway to read the RO data, copy and modify it, then write
> and seal into a new allocation.
On Sun, May 28, 2017 at 1:29 PM, Tetsuo Handa
wrote:
> Commit 3dfc9b02864b19f4 ("LSM: Initialize security_hook_heads upon
> registration.") treats "struct security_hook_heads" as an implicit array
> of "struct list_head" so that we can eliminate code for static
> initialization. Although we haven'
Hi Paolo, Hi Jonathan,
On Sun, May 28, 2017 at 4:43 PM, Jonathan Cameron wrote:
> On Sun, 28 May 2017 13:24:38 +0200
> Paolo Cretaro wrote:
>
>> Fix sparse warning: Using plain integer as NULL pointer
>>
>> Signed-off-by: Paolo Cretaro
> This looks fine to me, but ideally you should always try
Hi Sean,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.12-rc2 next-20170526]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/arm-dts-extend-mt7623-s
On Wed, May 24, 2017 at 9:01 AM, Vince Weaver wrote:
>
> On Wed, 24 May 2017, Andi Kleen wrote:
>
> > > Right, I did not even consider the rdpmc, but yeah, you will get a count
> > > that
> > > is not relevant to the user visible event. Unless you fake it using the
> > > time
> > > scaling field
Commit 3dfc9b02864b19f4 ("LSM: Initialize security_hook_heads upon
registration.") treats "struct security_hook_heads" as an implicit array
of "struct list_head" so that we can eliminate code for static
initialization. Although we haven't encountered compilers which do not
treat sizeof(security_hoo
From: Borislav Petkov
With CONFIG_DEBUG_PREEMPT enabled, I get:
BUG: using smp_processor_id() in preemptible [] code: swapper/0/1
caller is debug_smp_processor_id
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc2+ #2
Call Trace:
dump_stack
check_preemption_disabled
de
> The code for the special v1p8 / v2p8 gpios is ugly as sin, it operates on
> a global v2p8_gpio value rather then storing info in the gmin_subdev struct,
> as such passing the subdev->dev pointer would be simply wrong. AFAICT the
> v1p8 / v2p8 gpio code is the only caller passing in a NULL pointer
On Mon, 29 May 2017 02:06:41 +0800
Chen Guanqiao wrote:
> Fix "symbol 'xxx' was not declared. Should it be static?" sparse warnings.
>
> Signed-off-by: Chen Guanqiao
> ---
Reviewed-by: Alan Cox
Hi Tejun,
I suspect this is a long-standing bug introduced by all the pool rework
you did at some point, but I don't really know nor can I figure out how
to fix it right now. I guess it could possibly also be a lockdep issue,
or an issue in how it's used, but I definitely know that this used to
wo
On Thu 2017-05-25 12:46:04, Bernd Petrovitsch wrote:
> On Thu, 2017-05-25 at 03:35 -0700, Joe Perches wrote:
> > On Wed, 2017-05-24 at 13:18 +0300, Alexey Dobriyan wrote:
> > > Proper fix is to introduce typed allocation macros with the following
> > > signatures:
> > >
> > > T* lmalloc(T, gfp);
>
Hi!
> The status reported directly by the battery controller is not always
> reliable and should be corrected based on the current draw information.
>
> This implements such a correction with a dedicated function, called
> when retrieving the supply status.
>
> @@ -1182,6 +1196,8 @@ static int
One-time sealable memory makes the most sense from a defensive
perspective - red team reads this stuff, the races mentioned will be
implemented as described to win the day, and probably in other
innovative ways. If a gap is left in the implementation, without
explicit coverage by an adjacent functi
On Sun, May 28, 2017 at 11:18 AM, Bernhard Held wrote:
> Hi,
>
> this patch breaks the boot of my kernel. The last message is "Booting
> the kernel.".
>
> My setup might be unusual: I'm running a Xenon E5450 (LGA 771) in a
> Gigbayte G33-DS3R board (LGA 775). The BIOS is patched with the
> microco
Hi,
this patch breaks the boot of my kernel. The last message is "Booting
the kernel.".
My setup might be unusual: I'm running a Xenon E5450 (LGA 771) in a
Gigbayte G33-DS3R board (LGA 775). The BIOS is patched with the
microcode of the E5450 and recognizes the CPU.
Please find below the dmesg
On 28/05/2017 15:59, Linus Walleij wrote:
> On Tue, May 16, 2017 at 9:58 AM, Andrew Jeffery wrote:
>
>> Also clean up space-before-tab issues in the documentation.
>>
>> Signed-off-by: Andrew Jeffery
>
> Reviewed-by: Linus Walleij
>
> Does this collide with Daniel's 2500 patch?
>
> Sorry for
Hi,
On 28-05-17 19:08, Alan Cox wrote:
On Sun, 28 May 2017 14:30:35 +0200
Hans de Goede wrote:
Do not call dev_warn with a NULL device, this silence the following 2
warnings:
[ 14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO
[ 14.392257] (NULL device *): Failed to
On Wed, May 24, 2017 at 10:45 AM, Igor Stoppa wrote:
> On 23/05/17 23:11, Kees Cook wrote:
>> On Tue, May 23, 2017 at 2:43 AM, Igor Stoppa wrote:
>> I meant this:
>>
>> CPU 1 CPU 2
>> create
>> alloc
>> write
>> seal
>> ...
>> unseal
>> write
>> write
>> seal
>>
>> The CPU 2 w
On Fri, May 26, 2017 at 09:10:21PM +0200, Karim Eshapa wrote:
> Use strlcpy with sized buffer instead of strncpy to
> avoid non NUL-terminated source strings problems.
Huh? But it does get terminated.
> Signed-off-by: Karim Eshapa
> ---
> drivers/edac/edac_mc_sysfs.c | 6 ++
> 1 file change
Fix "symbol 'xxx' was not declared. Should it be static?" sparse warnings.
Signed-off-by: Chen Guanqiao
---
drivers/staging/media/atomisp/i2c/lm3554.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/atomisp/i2c/lm3554.c
b/drivers/staging/media/a
On 5/27/2017 6:26 PM, Tetsuo Handa wrote:
> Kees Cook wrote:
>> On Sat, May 27, 2017 at 4:17 AM, Tetsuo Handa
>> wrote:
>>> Commit 3dfc9b02864b19f4 ("LSM: Initialize security_hook_heads upon
>>> registration.") treats "struct security_hook_heads" as an implicit array
>>> of "struct list_head" so t
On Sun, May 28, 2017 at 11:47:58AM +0200, Michal Suchanek wrote:
> On Tue, 9 May 2017 17:43:27 -0700
> Dmitry Torokhov wrote:
>
> > Hi Michal,
> >
> > On Tue, May 09, 2017 at 09:14:18PM +0200, Michal Suchanek wrote:
> > > There is nothing mac-specific about this driver. Non-mac hardware
> > > wi
On 28/05/2017 16:43, Jonathan Cameron wrote:
> On Sun, 28 May 2017 13:24:38 +0200
> Paolo Cretaro wrote:
>
>> Fix sparse warning: Using plain integer as NULL pointer
>>
>> Signed-off-by: Paolo Cretaro
> This looks fine to me, but ideally you should always try to include
> the driver author - par
[trying again with correct linux-mm address...]
On Sun, May 28, 2017 at 1:15 AM, Christoph Hellwig wrote:
> On Fri, May 26, 2017 at 01:17:12PM -0700, Kees Cook wrote:
>> The NIU ethernet driver intentionally stores a page struct pointer on
>> top of the "mapping" field. Whitelist this case:
>>
>>
On Sun, May 28, 2017 at 1:15 AM, Christoph Hellwig wrote:
> On Fri, May 26, 2017 at 01:17:12PM -0700, Kees Cook wrote:
>> The NIU ethernet driver intentionally stores a page struct pointer on
>> top of the "mapping" field. Whitelist this case:
>>
>> drivers/net/ethernet/sun/niu.c: In function ‘niu
On Fri, May 26, 2017 at 02:34:43PM -0400, Jason Baron wrote:
> Kaby Lake seems to work just like Skylake.
>
> Signed-off-by: Jason Baron
> Reported-and-tested-by: Doug Thompson
> Cc: Borislav Petkov
> Cc: Mauro Carvalho Chehab
> Cc: Tony Luck
> ---
> drivers/edac/ie31200_edac.c | 12
On Wed, May 24, 2017 at 03:41:46PM -0500, Yazen Ghannam wrote:
> From: Yazen Ghannam
>
> There needs to be a list_head outside of a linked list in order to iterate
> over it and have access to all its elements. This is because the
> list_for_each* macros iterate starting from head->next rather th
On Sun, 28 May 2017 14:30:35 +0200
Hans de Goede wrote:
> Do not call dev_warn with a NULL device, this silence the following 2
> warnings:
>
> [ 14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO
> [ 14.392257] (NULL device *): Failed to find gmin variable gmin_V1P8GPIO
On Sun, May 28, 2017 at 9:50 AM, Chris Healy wrote:
>
>
>
>
> From: Jonathan Cameron
> Sent: Sunday, May 28, 2017 8:48 AM
> To: Nikita Yoush
> Cc: Hartmut Knaack; Lars-Peter Clausen; Peter Meerwald-Stadler; Sanchayan
> Maity; Gregor Boirie; Matt Ranostay; linux-..
On Sun, May 28, 2017 at 1:12 AM, Christoph Hellwig wrote:
> What about the untested patch below to just fix the issue?
>
> ---
> From e9eb519c854d2f3d16a4def492577a883246e290 Mon Sep 17 00:00:00 2001
> From: Christoph Hellwig
> Date: Sun, 28 May 2017 11:03:34 +0300
> Subject: security/keys: don't
On Sun, May 28, 2017 at 12:53 AM, Christoph Hellwig wrote:
> On Fri, May 26, 2017 at 01:17:05PM -0700, Kees Cook wrote:
>> When the call to nfs_devname() fails, the error path attempts to retain
>> the error via the mnt variable, but this requires a cast across very
>> different types (char * to s
On 2017-05-27 15:38, Andy Shevchenko wrote:
> On Fri, May 26, 2017 at 7:07 PM, Jan Kiszka wrote:
>> By now, stmmac_pci_info only contains a single entry.
>
> _For now_.
>
>> Register this
>> directly with the PCI device table, removing one indirection.
>
> I am not sure this patch is needed.
>
On 2017-05-27 15:28, Andy Shevchenko wrote:
> On Fri, May 26, 2017 at 7:07 PM, Jan Kiszka wrote:
>> Avoids reimplementation of DMI matching in stmmac_pci_find_phy_addr.
>
>> struct stmmac_pci_dmi_data {
>> - const char *name;
>> - const char *asset_tag;
>> - unsigned int func;
On 2017-05-27 15:52, Andy Shevchenko wrote:
> On Fri, May 26, 2017 at 7:02 PM, Jan Kiszka wrote:
>> This implements the setup of RS232 and the switch-over to RS485 or RS422
>> for the Siemens IOT2040. That uses an EXAR XR17V352 with external logic
>> to switch between the different modes. The exte
On 2017-05-27 01:04, Andy Shevchenko wrote:
> +Cc Mathias
>
> On Wed, May 24, 2017 at 9:04 PM, Jan Kiszka wrote:
>> This ensures that adjustments to x86_platform done by the hypervisor
>> setup is already respected by this simple calibration.
>>
>> The current user of this, introduced by 1b5aeebf
On 2017-05-27 15:48, Andy Shevchenko wrote:
> On Fri, May 26, 2017 at 7:02 PM, Jan Kiszka wrote:
>> On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the
>> rest is required to operate the UART. To allow modeling this case,
>> expand the platform device data structure to specify a (
On 2017-05-27 16:01, Andy Shevchenko wrote:
> On Fri, May 26, 2017 at 2:12 PM, Jan Kiszka wrote:
>> On 2017-05-26 13:04, André Draszik wrote:
>
>>> +log_buf_addr =
>>> int(str(gdb.parse_and_eval("'printk.c'::log_buf")).split()[0], 16)
>>
>> Overlong line. Please stay pep8 compliant.
>
>
Hello Linus,
I know this is (very) late, but please consider these six fixes for next rc3.
I tried sending these via Rui, but I think I missed the window to get
him still in office, so I am sending directly to you.
Changelog in this pull:
- Fixes on TI SoC driver, Broadcom, qoriq.
- Small sparse
On Fri, May 05, 2017 at 02:08:31PM -0700, Florian Fainelli wrote:
> On 04/25/2017 05:56 PM, Florian Fainelli wrote:
> > Changes in v3:
> >
> > - added check in usb_gadget_map_request_by_dev (Felipe), new patch
> > - improved commit message description (Clemens)
> > - added additiona checks for urb
Hi John,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.12-rc2 next-20170526]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/arm-dts-extend-mt7623-s
On Wed, 24 May 2017 20:50:45 +0100
Jonathan Cameron wrote:
> On Wed, 24 May 2017 02:09:06 +0200
> Stefan Brüns wrote:
>
> > INA226/230/231 has integration times per voltage channel and common
> > averaging setting for both channels, while the INA219/220 only has a
> > combined integration time/
On Sun, May 28, 2017 at 7:11 AM, Rik van Riel wrote:
> On Sat, 2017-05-27 at 09:00 -0700, Andy Lutomirski wrote:
>> On Sat, May 27, 2017 at 6:31 AM, kernel test robot
>> wrote:
>> >
>> > FYI, we noticed the following commit:
>> >
>> > commit: e2a7dcce31f10bd7471b4245a6d1f2de344e7adf ("x86/mm: Rew
On Thu, 25 May 2017 08:47:47 +0300
Nikita Yushchenko wrote:
> 24.05.2017 22:27, Jonathan Cameron wrote:
> > On Tue, 23 May 2017 11:08:30 +0300
> > Nikita Yushchenko wrote:
> >
> >> Having all events enabled by default is misleading.
> >> Userspace should explicitly enable events they want to
On Thu, 25 May 2017 09:27:18 +0300
Nikita Yushchenko wrote:
> > Reset GPIO is active low.
> >
> > Currently driver uses gpiod_set_value(1) to clean reset, which depends
> > on device tree to contain GPIO_ACTIVE_HIGH - that does not match
> > reality.
> >
> > This fixe
On 05/28/2017 07:49 AM, Vegard Nossum wrote:
On 05/28/17 13:45, Vegard Nossum wrote:
On 05/27/17 19:56, Guenter Roeck wrote:
Hi,
my qemu testis of mips images are failing in -next. Symptom is a hang during
boot; see http://kerneltests.org/builders/qemu-mips-next for some examples.
I bisected
On Thu, 25 May 2017 14:17:12 +0300
Eugen Hristev wrote:
> Add node information for ADTRG hardware pin and the three possible
> edge nodes that are available for the driver
>
> Signed-off-by: Eugen Hristev
Given this is effectively an internal interrupt (i.e. one that software
never sees) I won
On Thu, 25 May 2017 14:17:14 +0300
Eugen Hristev wrote:
> Added support for the external hardware trigger on pin ADTRG,
> integrated the three possible edges into the driver
> and created buffer management for data retrieval
>
> Signed-off-by: Eugen Hristev
Looking pretty good, a few tiny nitpi
On Sat, May 27, 2017 at 6:23 PM, Icenowy Zheng wrote:
> Allwinner R40 has a clock controlling unit like the ones on other
> Allwinner SoCs after sun6i, and can also use a CCU-based driver.
>
> Add a compatible string for it.
>
> Signed-off-by: Icenowy Zheng
> Acked-by: Rob Herring
Reviewed-by:
On Sat, May 27, 2017 at 6:23 PM, Icenowy Zheng wrote:
> Allwinner R40 has a pin controller like the ones in older Allwinner SoCs
> (especially A20), and can use modified version of the A10/A20 pinctrl
> driver.
>
> Add a compatible string for it.
>
> Signed-off-by: Icenowy Zheng
> Acked-by: Rob H
On Thu, 25 May 2017 11:03:20 +0300
Nikita Yushchenko wrote:
> >> "Crap origin" here is that in vast majority of cases, polarity is
> >> per-chip, not per-chip-use, knowledge. And proper location for per-chip
> >> knowledge is chip's driver. Moving this knowledge to per-chip-use
> >> location in
On Sat, May 27, 2017 at 6:23 PM, Icenowy Zheng wrote:
> As we added A20 support to A10 pinctrl driver, now we can delete the
> dedicated A20 pinctrl driver, which is duplicated code.
>
> Signed-off-by: Icenowy Zheng
> ---
> Changes in v3:
> - Only remove the A20 driver(A10 driver for A20 is enabl
On Sat, May 27, 2017 at 6:23 PM, Icenowy Zheng wrote:
> As A20 is designed as a pin-compatible upgrade of A10, their pin
> controller are very similar, and can share one driver.
>
> Add A20 support to the A10 driver.
>
> Signed-off-by: Icenowy Zheng
Reviewed-by: Chen-Yu Tsai
在 2017-04-16 14:51，Icenowy Zheng 写道：
A new usbid of UTV007 is found in a newly bought device.
The usbid is 1f71:3301.
The ID on the chip is:
UTV007
A89029.1
1520L18K1
Both video and audio is tested with the modified usbtv driver.
Signed-off-by: Icenowy Zheng
Acked-by: Lubomir Rintel
Ping?
On 05/28/2017 07:49 AM, Vegard Nossum wrote:
On 05/28/17 13:45, Vegard Nossum wrote:
On 05/27/17 19:56, Guenter Roeck wrote:
Hi,
my qemu testis of mips images are failing in -next. Symptom is a hang during
boot; see http://kerneltests.org/builders/qemu-mips-next for some examples.
I bisected
On Sat, May 27, 2017 at 6:23 PM, Icenowy Zheng wrote:
> Allwinner A10, A20 and R40 SoCs have similar GPIO layout.
>
> Add SoC definitions in pinctrl-sunxi.h, in order to merge A20 support
> into A10 driver, and add R40 support into it.
>
> Signed-off-by: Icenowy Zheng
Reviewed-by: Chen-Yu Tsai
On Sat, May 27, 2017 at 6:22 PM, Icenowy Zheng wrote:
> Allwinner R40 is a new SoC, with Quad Core Cortex-A7 and peripherals
> like A20.
>
> Add support for it.
>
> Signed-off-by: Icenowy Zheng
> ---
> Changes in v3:
> - Use V1.0 documents.
>
> Documentation/arm/sunxi/README | 6
On Sun, May 28, 2017 at 12:09 AM, Maxime Ripard
wrote:
> It appears that the total vertical resolution needs to be doubled when
> we're not in interlaced. Make sure that is the case.
>
> Signed-off-by: Maxime Ripard
Reviewed-by: Chen-Yu Tsai
On Fri, 26 May 2017 12:07:41 +0530
Arvind Yadav wrote:
> clk_prepare_enable() can fail here and we must check its return value.
>
> Signed-off-by: Arvind Yadav
Straight forward looking so I've applied this to the togreg
branch of iio.git and pushed it out as testing for the autobuilders
to play
1 - 100 of 208 matches
Mail list logo
