commit d85b758f72b0 "virtio_net: fix support for small rings"
was supposed to increase the buffer size for small rings
but had an unintentional side effect of decreasing
it for large rings. This seems to break some setups -
it's not yet clear why, but increasing buffer size
back to what it was
Hi Azhar,
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on v4.12-rc3]
[cannot apply to next-20170601]
[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/Azhar-Shaikh
Hi Philipp,
[auto build test WARNING on pza/reset/next]
[also build test WARNING on v4.12-rc3 next-20170601]
[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/Philipp-Zabel/reset-APIs-to-manage
On 06/01/2017 02:21 PM, Nicholas A. Bellinger wrote:
Hi Jia-Ju,
On Wed, 2017-05-31 at 11:26 +0800, Jia-Ju Bai wrote:
The driver may sleep under a spin lock, and the function call path is:
iscsit_tpg_enable_portal_group (acquire the lock by spin_lock)
iscsi_update_param_value
On Fri, 2017-06-02 at 09:14 +0800, kernel test robot wrote:
> FYI, we noticed the following commit:
>
> commit: 105931d39f6a37845e07f65f7e23b4bed9d1d8f8 ("Move most of
> scsi_init_command() into scsi_initialize_rq()")
> https://github.com/bvanassche/linux for-next
>
> in testcase: boot
>
> on
Add devicetree bindings for Rockchip cru which found on
Rockchip SoCs.
Signed-off-by: Elaine Zhang
---
.../bindings/clock/rockchip,rk3128-cru.txt | 56 ++
1 file changed, 56 insertions(+)
create mode 100644
Add the clock tree definition for the new rk3128 SoC.
And it also applies to the RK3126 SoC.
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/Makefile | 1 +
drivers/clk/rockchip/clk-rk3128.c | 612 ++
2 files changed, 613
The driver and clk ID\SRST ID it's also applies to the RK3126 SoC.
change in V4:
remove the clk ID of usb480m_phy
change in V3:
export clk ID for usb480m and usb480m_phy
change in V2:
rename the rk312x to rk3128.
Elaine Zhang (3):
clk: rockchip: add dt-binding header for rk3128
Add the dt-bindings header for the rk3128,
that gets shared between the clock controller and
the clock references in the dts.
Add softreset ID for rk3128.
And it also applies to the RK3126 SoC.
Signed-off-by: Elaine Zhang
---
include/dt-bindings/clock/rk3128-cru.h |
On Fri, Jun 02, 2017 at 02:56:04AM +0300, Michael S. Tsirkin wrote:
> commit d85b758f72b0 "virtio_net: fix support for small rings"
> was supposed to increase the buffer size for small rings
> but had an unintentional side effect of decreasing
> it for large rings. This seems to break some setups
On Fri, Jun 2, 2017 at 8:57 AM, Deepa Dinamani wrote:
> On Thu, Jun 1, 2017 at 5:36 PM, John Stultz wrote:
>> On Thu, Jun 1, 2017 at 5:26 PM, Yan, Zheng wrote:
>>> On Thu, Jun 1, 2017 at 6:22 PM, Arnd Bergmann
On Thu, Jun 01, 2017 at 09:36:18AM +0200, Paolo Bonzini wrote:
> On 01/06/2017 03:05, Nick Desaulniers wrote:
> > On Wed, May 31, 2017 at 07:01:29AM -0400, Paolo Bonzini wrote:
> >>> + size = offsetof(struct fxregs_state, xmm_space[16]);
> >> This still has the same issue (it should be
On Fri, May 12, 2017 at 09:35:02AM +0900, Byungchul Park wrote:
> Although llist provides proper APIs, they are not used. Make them used.
+to ax...@kernel.dk
I didn't know your e-mail address has been changed.
Could you give your opinion about this patch?
> Signed-off-by: Byungchul Park
Ping?
On Mon, Apr 10, 2017 at 02:46:57PM -0400, Sasha Levin wrote:
> From: Alexander Levin
>
> Commit 77469c3f570 prevented setting the page as uptodate when we wrote the
> right amount of data, fix that.
>
> Fixes: 77469c3f570 ("9p: saner ->write_end() on failing
From: Nicholas Bellinger
When target_shutdown_sessions() is invoked to shutdown all active
sessions associated with a se_node_acl when se_node_acl->queue_depth
is changed via core_tpg_set_initiator_node_queue_depth(), it's
possible that new connections reconnect immediately
On Fri, 2 Jun 2017 03:24:35 +
"Chen, Xiaoguang" wrote:
> Hi Alex,
>
> >-Original Message-
> >From: Alex Williamson [mailto:alex.william...@redhat.com]
> >Sent: Friday, June 02, 2017 2:08 AM
> >To: Chen, Xiaoguang
> >Cc:
Hi all,
On Fri, 2 Jun 2017 14:05:35 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the target-bva tree got a conflict in:
>
> drivers/target/target_core_tpg.c
>
> between commits:
>
> 06fd91ce633d ("target/configfs: Kill se_lun->lun_link_magic")
>
On 02/06/17 01:08, Dilger, Andreas wrote:
> On Jun 1, 2017, at 14:56, Tordek wrote:
>> This is fairly minor but it reveals a few hidden warnings, could I get some
>> feedback on it?
>
> This is a known problem, but can't immediately be fixed because it affects
> the interface
On 06/01/2017 04:36 AM, Michael Ellerman wrote:
> Michael Bringmann writes:
>
>> On 05/29/2017 12:32 AM, Michael Ellerman wrote:
>>> Reza Arbab writes:
>>>
On Fri, May 26, 2017 at 01:46:58PM +1000, Michael Ellerman wrote:
> Reza
On Wed, May 31, 2017 at 08:45:23AM -0400, Jeff Layton wrote:
> v5: don't retrofit old API over the new infrastructure
> add fstype flag to indicate how wb errors are tracked within that fs
> add more function variants that take a errseq_t "since" value
> add second errseq_t to struct
[ adding lkml, dropping 'ndctl prefix ]
On Thu, Jun 1, 2017 at 10:39 PM, Dan Williams wrote:
> The inode destruction path for the 'dax' device filesystem incorrectly
> assumes that the inode was initialized through 'alloc_dax()'. However,
> if someone attempts to
On Thu, Jun 1, 2017 at 6:22 PM, Arnd Bergmann wrote:
> On Thu, Jun 1, 2017 at 11:56 AM, Yan, Zheng wrote:
>> On Sat, Apr 8, 2017 at 8:57 AM, Deepa Dinamani
>> wrote:
>
>>> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
>>> index
On Thu, Jun 1, 2017 at 5:26 PM, Yan, Zheng wrote:
> On Thu, Jun 1, 2017 at 6:22 PM, Arnd Bergmann wrote:
>> On Thu, Jun 1, 2017 at 11:56 AM, Yan, Zheng wrote:
>>> On Sat, Apr 8, 2017 at 8:57 AM, Deepa Dinamani
>>>
Commit 18dddadc78c9 ("drm/atomic: Introduce drm_atomic_helper_shutdown")
introduced a new helper to shutdown all CRTCs to replace the buggy
drm_crtc_force_disable_all() function. Make use of the new atomic
helper drm_atomic_helper_shutdown() to shutdown CRTCs.
Signed-off-by: Stefan Agner
Make use of the irq_preinstall/uninstall callback to clear and
mask all interrupts. Use write 1 to clear as documented by the
data sheet (writing a 0 seems to have cleared interrupt status
too). Remove fsl_dcu_drm_irq_init and call drm_irq_install
directly from fsl_dcu_load makes error handling a
Hi Chris,
Le Fri, 2 Jun 2017 15:21:14 +1200,
Chris Packham a écrit :
> This series adds device tree support to the mchp23k256 driver and
> support for the mchp23lcv1024 chip. I suspect there are more compatible
> variants that we could now enumerate if
On 05/26/2017 02:24 AM, Anup Patel wrote:
> The Broadcom Stingray SoC is a new member in Broadcom iProc
> SoC family.
>
> This patch adds initial DTS files for Broadcom Stingray SoC
> and two of its reference boards (bcm958742k and bcm958742t).
>
> We have lot of reference boards and large
On 02/06/17 10:23, Brian Norris wrote:
> On Thu, Jun 01, 2017 at 09:30:07PM +, Chris Packham wrote:
>> On 02/06/17 06:43, Brian Norris wrote:
>>> On Wed, May 17, 2017 at 05:29:11PM +0200, Boris Brezillon wrote:
Can we fix allocate_partition() to properly handle the
master->erasesize
Hi Jia-Ju,
[auto build test WARNING on wireless-drivers-next/master]
[also build test WARNING on v4.12-rc3 next-20170601]
[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/Jia-Ju-Bai/b43legacy-Fix
Hi,
On Mon, May 29, 2017 at 12:22:36PM +0200, Daniel Lezcano wrote:
> On Sun, May 28, 2017 at 12:26:00PM +0200, Ulf Hansson wrote:
> > Hi Olof,
> >
> > +Daniel
> >
> > On 26 May 2017 at 18:24, Olof Johansson wrote:
> > > Hi Ulf,
> > >
> > >
> > > On Fri, May 26, 2017 at 6:08
On Mon, May 29, 2017 at 05:17:54PM +0200, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> The STMicroelectronics dedicated mailing list ker...@stlinux.com
> is no more available, remove it to avoid bouncing mails.
>
> Several request to create a new mailing
On Mon, May 29, 2017 at 11:23:15AM +0200, Alexandre Belloni wrote:
> Arnd, Olof,
>
> Here are two fixes for 4.12.
>
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
>
On Wed, May 24, 2017 at 02:10:10PM +0900, Masahiro Yamada wrote:
> Most of DT files in ARM use #include "..." to make pre-processor
> include DT in the same directory, but this is one of the exceptional
> files that use #include <...> for that.
>
> Fix it to remove
On Thu, Jun 1, 2017 at 6:22 PM, Arnd Bergmann wrote:
> On Thu, Jun 1, 2017 at 11:56 AM, Yan, Zheng wrote:
>> On Sat, Apr 8, 2017 at 8:57 AM, Deepa Dinamani
>> wrote:
>
>>> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
>>> index
On Fri, May 26, 2017 at 09:55:31AM +0800, zhong jiang wrote:
>On 2017/5/26 9:36, Wei Yang wrote:
>> On Thu, May 25, 2017 at 11:04:44AM +0800, zhong jiang wrote:
>>> I hit the overlap issue, but it is hard to reproduced. if you think it is
>>> safe. and the situation
>>> is not happen. AFAIC, it
Dear Heiko,
在 2017年06月02日 04:22, Heiko Stuebner 写道:
Hi William,
Am Mittwoch, 31. Mai 2017, 09:21:23 CEST schrieb William Wu:
This patch adds usb otg/host controllers and phys nodes on rk322x.
Signed-off-by: William Wu
---
arch/arm/boot/dts/rk322x.dtsi | 138
On Thu, Jun 1, 2017 at 11:41 PM, Ray Jui wrote:
> Hi Oza,
>
> On 5/31/17 10:27 PM, Oza Pawandeep wrote:
>> PERST# must be asserted around ~500ms before
>> the reboot is applied.
>>
>> During soft reset (e.g., "reboot" from Linux) on some iProc based SoCs
>> LCPLL clock and
On 2017/6/2 7:23, Jessica Yu wrote:
> +++ Wanlong Gao [31/05/17 11:48 +0800]:
>>
>>
>> On 2017/5/31 11:30, Jessica Yu wrote:
>>> +++ Wanlong Gao [31/05/17 10:23 +0800]:
Hi Jessica,
On 2017/5/29 17:10, Jessica Yu wrote:
> +++ Xie XiuQi [20/05/17 15:46 +0800]:
>> From:
Hi Alex,
>-Original Message-
>From: Alex Williamson [mailto:alex.william...@redhat.com]
>Sent: Friday, June 02, 2017 2:08 AM
>To: Chen, Xiaoguang
>Cc: kra...@redhat.com; ch...@chris-wilson.co.uk; intel-
>g...@lists.freedesktop.org; linux-kernel@vger.kernel.org;
[+Cc Lv Zheng]
On 2017/6/2 0:21, Lorenzo Pieralisi wrote:
> On Thu, Jun 01, 2017 at 07:35:37PM +0530, Ganapatrao Kulkarni wrote:
>> ARM IORT specification has provision to define Proximity domain
>> in SMMUv3 IORT table. Adding required code to parse Proximity domain of
>> SMMUv3 IORT table.
Hi Bart,
Today's linux-next merge of the target-bva tree got a conflict in:
drivers/target/target_core_tpg.c
between commits:
06fd91ce633d ("target/configfs: Kill se_lun->lun_link_magic")
4f61e1e687c4 ("target: Avoid target_shutdown_sessions loop during queue_depth
change")
from the
On Wed, May 31, 2017 at 10:11:14PM +0100, Nick Dyer wrote:
> On Tue, May 30, 2017 at 09:59:13AM -0700, Dmitry Torokhov wrote:
> > On Tue, May 30, 2017 at 10:23:58AM +0200, Benjamin Tissoires wrote:
> > > On May 29 2017 or thereabouts, Dmitry Torokhov wrote:
> > > > Instead of printing bytes one by
Hi all,
Changes since 20170601:
The mfd tree still had its build failure so I used the version from
next-20170530.
The target-bva tree gained a conflict against the target-updates tree but
the resolution just caused a build failure, so I dropped the target-bva
tree for today.
Non-merge commits
On Fri, Jun 02, 2017 at 01:22:28AM +0200, Rafael J. Wysocki wrote:
> On Thu, May 25, 2017 at 10:49 AM, Chen Yu wrote:
> > Currently we saw a lot of "No irq handler" errors during hibernation,
> > which caused the system hang finally:
> >
> > [ 710.141581] ata4.00: qc timeout
Hi Philipp,
[auto build test ERROR on pza/reset/next]
[also build test ERROR on v4.12-rc3 next-20170601]
[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/Philipp-Zabel/reset-APIs-to-manage-a-list
+++ Wanlong Gao [31/05/17 11:48 +0800]:
On 2017/5/31 11:30, Jessica Yu wrote:
+++ Wanlong Gao [31/05/17 10:23 +0800]:
Hi Jessica,
On 2017/5/29 17:10, Jessica Yu wrote:
+++ Xie XiuQi [20/05/17 15:46 +0800]:
From: Wanlong Gao
Module name has a limited length, but
On Thu, May 25, 2017 at 10:49 AM, Chen Yu wrote:
> Currently we saw a lot of "No irq handler" errors during hibernation,
> which caused the system hang finally:
>
> [ 710.141581] ata4.00: qc timeout (cmd 0xec)
> [ 710.147135] ata4.00: failed to IDENTIFY (I/O error,
On Wed, May 31 2017, Thomas Meyer wrote:
> Signed-off-by: Thomas Meyer
> ---
> lib/extable.c | 30 +-
> 1 file changed, 13 insertions(+), 17 deletions(-)
>
> diff --git a/lib/extable.c b/lib/extable.c
> index 62968da..eb16cb3 100644
On Tue, May 23, 2017 at 11:00:55AM +0900, Byungchul Park wrote:
> When cpudl_find() returns any among free_cpus, the cpu might not be
> closer than others, considering sched domain. For example:
>
>this_cpu: 15
>free_cpus: 0, 1,..., 14 (== later_mask)
>best_cpu: 0
>
>topology:
>
dsa_switch_suspend() and dsa_switch_resume() are functions that belong in
net/dsa/dsa.c and are not part of the legacy platform support code.
Fixes: a6a71f19fe5e ("net: dsa: isolate legacy code")
Signed-off-by: Florian Fainelli
---
net/dsa/dsa.c| 47
On Thu, 2017-06-01 at 14:14 -0700, Bart Van Assche wrote:
> On 05/31/17 22:04, Nicholas A. Bellinger wrote:
> > Go ahead and get list review on drivers/target/ changes before pushing
> > them into linux-next, please.
> >
> > Btw, I don't care if you queue up one's that do have at least two
> >
On Wed, May 31, 2017 at 03:33:57PM -0700, Tahsin Erdogan wrote:
> Ext4 now supports xattr values that are up to 64k in size (vfs limit).
> Large xattr values are stored in external inodes each one holding a
> single value. Once written the data blocks of these inodes are immutable.
>
> The real
mem_cgroup_resize_limit() and mem_cgroup_resize_memsw_limit() have
identical logics. Refactor code so we don't need to keep two pieces
of code that does same thing.
Signed-off-by: Yu Zhao
---
mm/memcontrol.c | 71 +
1
Hi Johannes,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc3 next-20170601]
[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/Johannes-Thumshirn/nvme-introduce-NVMe
Hi Johannes,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc3 next-20170601]
[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/Johannes-Thumshirn/nvme-introduce-NVMe
On 2 June 2017 at 00:59, Rafael J. Wysocki wrote:
>
> Quoting from my cover letter:
>
> "After this series there still is a concern regarding the possible increase of
> power draw that may result from the processing of non-wakeup EC events while
> suspended which is why the
Hi Han,
On 2017-06-01 14:14, Han Xu wrote:
> On 06/01/2017 02:20 PM, Stefan Agner wrote:
>> This are the missing device tree parts to add NAND support for i.MX 7.
>> See previous patchset:
>>
Add "dis_rxdet_inp3_quirk" boolean property to USB3 node. This property
is used to disable rx detection in P3 PHY mode.
Signed-off-by: Ran Wang
---
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git
On Thursday 01 June 2017 01:57 PM, Shriya wrote:
Add support for POWER8+ PVR 004c0100 for Garrison
patch title could have been,
tools/perf/pmu-events: Support additional POWER8+ PVR in mapfile
But other than that,
Reviewed-by: Madhavan Srinivasan
Hi Sylwester,
Here is another patch in case you decide that it is
better to apply this one.
Thanks
--
Gustavo A. R. Silva
==
Fix the position of the arguments in function call.
Addresses-Coverity-ID: 1248800
Addresses-Coverity-ID: 1269141
Signed-off-by: Gustavo A. R. Silva
struct spi_imx_config used to hold data specific to the current
transfer. However, other data is in the drivers private data struct.
Let's drop struct spi_imx_config and put the variables into the
drivers private data struct aswell.
Signed-off-by: Sascha Hauer
---
clk_prepare_enable() and clk_prepare() can fail here and
we must check its return value.
Signed-off-by: Arvind Yadav
---
drivers/misc/atmel-ssc.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/atmel-ssc.c
On Thu, Jun 01, 2017 at 04:58:47AM -0700, Jiada Wang wrote:
> Hi Sascha
>
> On 05/29/2017 02:50 AM, Sascha Hauer wrote:
> > Hi,
> >
> > On Thu, May 25, 2017 at 10:02:42PM -0700, jiada_w...@mentor.com wrote:
> > > From: Jiada Wang
> > >
> > > previously burst length
When the spi_transfer given in spi_imx_setupxfer is NULL then
we have nothing to do. Bail out early in this case so that
we do not have to test for t != NULL multiple times later.
Signed-off-by: Sascha Hauer
---
drivers/spi/spi-imx.c | 10 +-
1 file changed, 5
'bpw' is ambiguous and only the context makes sure if bytes_per_word
or bits_per_word is meant. Use the full names instead to make reading
the code easier.
Signed-off-by: Sascha Hauer
---
drivers/spi/spi-imx.c | 12 ++--
1 file changed, 6 insertions(+), 6
We already have bits_per_word in the private driver struct and
bytes_per_word can be calculated from it, so remove bits_per_word.
Signed-off-by: Sascha Hauer
---
drivers/spi/spi-imx.c | 15 ---
1 file changed, 4 insertions(+), 11 deletions(-)
diff --git
It's unnecessary to call spi_imx_dma_configure() from probe(). It will
be called later anyway again when an actual DMA transfer is prepared.
Signed-off-by: Sascha Hauer
---
drivers/spi/spi-imx.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/spi/spi-imx.c
Am Dienstag, 30. Mai 2017, 23:52:46 CEST schrieb Randy Li:
> The only adc button connected to adc input is recovery button.
>
> Signed-off-by: Randy Li
applied for 4.13
Thanks
Heiko
On Thu, Jun 01, 2017 at 02:06:08PM +0200, Dmitry Vyukov wrote:
> On Wed, May 31, 2017 at 5:04 PM, Alan Cox wrote:
> > On Wed, 31 May 2017 20:16:12 +0900
> > Greg KH wrote:
> >
> >> On Wed, May 31, 2017 at 10:39:23AM +0200, Dmitry Vyukov
Hi Tim,
On 06/01/2017 05:25 PM, Tim Harvey wrote:
Hi Steve,
I've applied adv7180 device-tree config for the Gateworks ventana
boards on top of your imx-media-staging-md-v15 github branch but am
not able to get it to work.
Here's my device-tree patch that adds adv7180 to the GW54xx connected
On Thu, Jun 1, 2017 at 5:36 PM, John Stultz wrote:
> On Thu, Jun 1, 2017 at 5:26 PM, Yan, Zheng wrote:
>> On Thu, Jun 1, 2017 at 6:22 PM, Arnd Bergmann wrote:
>>> On Thu, Jun 1, 2017 at 11:56 AM, Yan, Zheng wrote:
Guenter Roeck writes:
> On Thu, Jun 01, 2017 at 02:36:38PM -0500, Eric W. Biederman wrote:
>> Guenter Roeck writes:
>>
>> > On Thu, Jun 01, 2017 at 12:08:58PM -0500, Eric W. Biederman wrote:
>> >> Guenter Roeck writes:
>> >> >
>> >>
The Colibri iMX7 modules come with 512MB on-module SLC NAND flash
populated. Make use of it by enabling the GPMI controller.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7-colibri.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git
This are the missing device tree parts to add NAND support for i.MX 7.
See previous patchset:
https://lkml.org/lkml/2017/4/21/832
The previous version also included driver changes, which are already
merged.
--
Stefan
Changes since v3:
- Only specify IMX7D_NAND_USDHC_BUS_ROOT_CLK which seems to
em_fxstor previously called fxstor_fixup. Both created instances of
struct fxregs_state on the stack, which triggered the warning:
arch/x86/kvm/emulate.c:4018:12: warning: stack frame size of 1080 bytes
in function
'em_fxrstor' [-Wframe-larger-than=]
static int em_fxrstor(struct
Add i.MX 7 GPMI NAND module.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7s.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi
index c4f12fd..48cfedb 100644
---
On 2017/6/2 9:45, Wei Yang wrote:
> On Fri, May 26, 2017 at 09:55:31AM +0800, zhong jiang wrote:
>> On 2017/5/26 9:36, Wei Yang wrote:
>>> On Thu, May 25, 2017 at 11:04:44AM +0800, zhong jiang wrote:
I hit the overlap issue, but it is hard to reproduced. if you think it is
safe. and
On Fri, 2017-06-02 at 13:39 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Last night the tagret-bva tree was rebased on top of the target-updates
> tree. Just now, part of the target-updates tree has been rewritten.
> So now I expect to get conflict(s) when I merge these trees since the
> commits
On Thu, Jun 01, 2017 at 10:47:36AM +0900, Andi Shyti wrote:
> Commit 4e552c8cb5bc ("leds: add LED_ON brightness as boolean value")
> has introduced the LED_ON enumeration value that can be used
> instead of LED_FULL which has more of a linear value.
>
> Because the tm2-touchscreen doesn't have
Hi Bart,
On Thu, 1 Jun 2017 14:14:06 -0700 Bart Van Assche
wrote:
>
> On 05/31/17 22:04, Nicholas A. Bellinger wrote:
> > Go ahead and get list review on drivers/target/ changes before pushing
> > them into linux-next, please.
> >
> > Btw, I don't care if you queue
On 05/24/2017 08:09 PM, Jarkko Sakkinen wrote:
On Wed, May 24, 2017 at 07:03:27PM -0400, Stefan Berger wrote:
On 05/24/2017 06:21 PM, Jarkko Sakkinen wrote:
On Wed, May 24, 2017 at 05:39:40PM -0400, Stefan Berger wrote:
Implement the request_locality function. To set the locality on the
erasesize is meaningful for flash devices but for SRAM there is no
concept of an erase block so erasesize is set to 0. When partitioning
these devices instead of ensuring partitions fall on erasesize
boundaries we ensure they fall on writesize boundaries.
Helped-by: Boris Brezillon
This series adds device tree support to the mchp23k256 driver and
support for the mchp23lcv1024 chip. I suspect there are more compatible
variants that we could now enumerate if desired.
Note: I've included 2 patches that have already been applied to l2-mtd.git for
context and so as not to upset
The mchp23lcv1024 is similar to the mchp23k256, the differences (from a
software point of view) are the capacity of the chip and the size of the
addresses used.
There is no way to detect the specific chip so we must be told via a
Device Tree or default to mchp23k256 when device tree is not used.
Setting the of_node for the mtd device allows the generic mtd code to
setup the partitions.
Signed-off-by: Chris Packham
Reviewed-by: Andrew Lunn
Tested-by: Andrew Lunn
---
Changes in v2
- collect revew/test from Andrew
Changes
These series of patches fix some issues for rockchip usb2-phy and amend
usb2-phy framework to support one phy which comprises with two host-ports.
In addition, this change also add rk3228 usb2-phy support.
Changes from v1:
- Replaced rk322x with rk3228 for PATCH 4/4.
- Included devicetree
On 2017/6/2 11:04, Wanlong Gao wrote:
>
>
> On 2017/6/2 7:23, Jessica Yu wrote:
>> +++ Wanlong Gao [31/05/17 11:48 +0800]:
>>>
>>>
>>> On 2017/5/31 11:30, Jessica Yu wrote:
+++ Wanlong Gao [31/05/17 10:23 +0800]:
> Hi Jessica,
>
> On 2017/5/29 17:10, Jessica Yu wrote:
>>
Hi Linus,
As mentioned I have a separate request for fixing a regression, but
also keeping the broken hw working, for certain USB-C DP adapters they
require a minimised n/m parameters, but an attempt to do this
generically has failed, we need to quirk these specific adapters.
However doing it
On Jun 1, 2017, at 14:56, Tordek wrote:
> This is fairly minor but it reveals a few hidden warnings, could I get some
> feedback on it?
This is a known problem, but can't immediately be fixed because it affects the
interface with
userspace tools. The correct solution is to
Ciao
Benvenuto al nostro negozio
24.88 euro per gli occhiali da sole di Ray Ban, trasporto libero direttamente
alla vostra casa
web: rbewpt .com
一份心情,飘飞着心絮的痕迹;一段友情,彼此永远珍藏在心底。深深祝福你,我的朋友:永远幸福!永远快乐!
On Wed, May 31, 2017 at 6:13 PM, Alex Williamson
wrote:
> On Wed, 31 May 2017 17:03:32 +0530
> Geetha sowjanya wrote:
>
>> Pci driver doesn't check if the device supports D3hot/D3cold power states
>> while setting these power states. The
On Thu, May 25, 2017 at 02:46:27PM +0800, Huang, Ying wrote:
> From: Huang Ying
>
> The .rw_page in struct block_device_operations is used by the swap
> subsystem to read/write the page contents from/into the corresponding
> swap slot in the swap device. To support the THP
On Thu, 1 Jun 2017, Casey Schaufler wrote:
> Subject: [PATCH] procfs: add smack subdir to attrs
Is there value in this without major stacking support?
--
James Morris
On 6/1/2017 4:38 PM, James Morris wrote:
> On Thu, 1 Jun 2017, Casey Schaufler wrote:
>
>> Subject: [PATCH] procfs: add smack subdir to attrs
> Is there value in this without major stacking support?
Yes. If a Smack aware application reads /proc/self/attr/current
it has no way to know if what it
On Wed, May 24, 2017 at 5:29 PM, Steve Longerbeam wrote:
> In version 7:
>
> - video-mux: switched to Philipp's latest video-mux driver and updated
> bindings docs, that makes use of the mmio-mux framework.
>
> - mmio-mux: includes Philipp's temporary patch that adds
On Thursday, June 01, 2017 01:08:16 AM Jongman Heo wrote:
> >
> >- Original Message -
> >Sender : Rafael J. Wysocki
> >Date : 2017-06-01 08:58 (GMT+9)
> >Title : Re: FW: [4.12 regression] "cpufreq: intel_pstate: Active mode
> >P-state limits rework"
> >
>
FYI, we noticed the following commit:
commit: 105931d39f6a37845e07f65f7e23b4bed9d1d8f8 ("Move most of
scsi_init_command() into scsi_initialize_rq()")
https://github.com/bvanassche/linux for-next
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -smp 2 -m 512M
caused below
On 06/02/2017 12:11 AM, Jonathan Corbet wrote:
On Thu, 01 Jun 2017 09:05:07 +0800
Jia-Ju Bai wrote:
I admit my patches are not well tested, and they may not well fix the bugs.
I am looking forward to opinions and suggestions :)
May I politely suggest that sending out
Allow BPF_PROG_TYPE_PERF_EVENT program types to attach to all
perf_event types, including HW_CACHE, RAW, and dynamic pmu events.
Only tracepoint/kprobe events are treated differently which require
BPF_PROG_TYPE_TRACEPOINT/BPF_PROG_TYPE_KPROBE program types accordingly.
Also add support for
v2->v3: more refactoring to address Peter's feedback.
Now all perf_events are attachable and readable
v1->v2: address Peter's feedback. Refactor patch 1 to allow attaching
bpf programs to all event types and reading counters from all of them as well
patch 2 - more tests
patch 3 - address Dave's
1 - 100 of 2256 matches
Mail list logo