On Mon, 2017-03-13 at 09:47 -0700, Florian Fainelli wrote:
> On 03/13/2017 09:11 AM, sean.w...@mediatek.com wrote:
> > From: Sean Wang
> >
> > Add device-tree binding for Mediatek MT7530 switch.
> >
> > Cc: devicet...@vger.kernel.org
> > Signed-off-by: Sean Wang
> > ---
> > .../devicetree/bind
On Tue, Mar 14, 2017 at 8:22 AM, Vivek Gautam
wrote:
> Adding vendor specific directories in phy to group
> phy drivers under their respective vendor umbrella.
>
> Also updated the MAINTAINERS file to reflect the correct
> directory structure for phy drivers.
>
> Signed-off-by: Vivek Gautam
> Ack
On 14/03/17 00:50, Stefano Stabellini wrote:
> Implement functions to handle the xenbus handshake. Upon connection,
> allocate the rings according to the protocol specification.
>
> Initialize a work_struct and a wait_queue. The work_struct will be used
> to schedule work upon receiving an event c
On 13.3.2017 17:18, Moritz Fischer wrote:
> On Mon, Mar 13, 2017 at 3:27 AM, Michal Simek wrote:
>> Hi Moritz,
>>
>> On 10.3.2017 23:42, Moritz Fischer wrote:
>>> On Fri, Mar 10, 2017 at 1:30 PM, Moritz Fischer wrote:
This adds support for the Xilinx LogiCORE PR Decoupler
soft-ip that d
On 14/03/17 00:50, Stefano Stabellini wrote:
> Introduce the Xen 9pfs transport driver: add struct xenbus_driver to
> register as a xenbus driver and add struct p9_trans_module to register
> as v9fs driver.
>
> All functions are empty stubs for now.
>
> Signed-off-by: Stefano Stabellini
> Review
Adding vendor specific directories in phy to group
phy drivers under their respective vendor umbrella.
Also updated the MAINTAINERS file to reflect the correct
directory structure for phy drivers.
Signed-off-by: Vivek Gautam
Acked-by: Heiko Stuebner
Acked-by: Viresh Kumar
Cc: Kishon Vijay Abra
On Mon, 2017-03-13 at 12:59 -0400, Vivien Didelot wrote:
> Hi Sean,
>
> sean.w...@mediatek.com writes:
>
> > + mtk_tag[1] = (1 << p->port) & MTK_HDR_XMIT_DP_BIT_MASK;
>
> This won't apply, the port index in now stored in p->dp->index.
>
> Thanks,
>
> Vivien
Hi Vivien,
It seems tha
On Mon, 2017-03-13 at 09:35 -0700, Florian Fainelli wrote:
> On 03/13/2017 09:11 AM, sean.w...@mediatek.com wrote:
> > From: Sean Wang
> >
> > Add the support for the 4-bytes tag for DSA port distinguishing inserted
> > allowing receiving and transmitting the packet via the particular port.
> > T
The list rx_done would be initialized when the linking on occurs.
Therefore, if a napi is scheduled without any linking on before,
the following kernel panic would happen.
BUG: unable to handle kernel NULL pointer dereference at 008
IP: [] r8152_poll+0xe1e/0x1210 [r8152
Adding vendor specific directories in phy to group
phy drivers under their respective vendor umbrella.
Also updated the MAINTAINERS file to reflect the correct
directory structure for phy drivers.
Signed-off-by: Vivek Gautam
Acked-by: Heiko Stuebner
Acked-by: Viresh Kumar
Cc: Kishon Vijay Abra
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc2 next-20170310]
[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/zhichang-yuan/LPC-legacy-ISA-I-O-suppo
On Tuesday 14 March 2017 12:54 AM, Grygorii Strashko wrote:
>
>
> On 03/13/2017 08:42 AM, Roger Quadros wrote:
>> Enable the 2 ethernet ports as CPSW ports in dual-mac mode
>>
>> Signed-off-by: Roger Quadros
>> [nsek...@ti.com: use AM33XX_IOPAD()]
>> Signed-off-by: Sekhar Nori
>> ---
>> arch/a
On Mon, 2017-03-13 at 17:36 +0100, Andrew Lunn wrote:
> > +- mediatek,reset-pin: Phandle to the pinctrl node used for the reset. Which
> > + must be required if the property mediatek,mcm of specified as
> > + "disabled". See
> > + Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt f
Arguments in the macros should be coverd in brackets to aviod any
precedence issues. Fixed it.
Signed-off-by: mshan
---
drivers/staging/fwserial/fwserial.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fwserial/fwserial.c
b/drivers/staging/fwserial/fwserial.c
index 41a49c8..d693c03 100644
--- a/drivers/staging/fwserial/fwserial.c
+++ b/drivers/staging
On Tue, 14 Mar 2017, Arushi Singhal wrote:
> Fix checkpatch issues: "CHECK: Alignment should match open parenthesis".
I thought you were going to take another approach to improve this code?
julia
>
> Signed-off-by: Arushi Singhal
> ---
> drivers/staging/sm750fb/ddk750_mode.c | 79
> +++
On Mon, Mar 13, 2017 at 09:52:14PM -0700, mshan wrote:
> Signed-off-by: mshan
> ---
> drivers/staging/fwserial/fwserial.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response
2017-03-10 10:41 GMT+09:00 Masahiro Yamada :
> It has been difficult lately for Michal to work on Kbuild on his
> regular basis. We discussed the maintainership of Kbuild, and I
> decided to be a co-maintainer.
>
> Add myself to the maintainer field, and replace the repository with
> my own.
>
> S
Description:
In driver module ks7010, "checkpatch.pl" flags error for adding parenthesis
around macro params.
Also, removing extra line.
Signed-off-by: Pushkar Jambhlekar
---
drivers/staging/ks7010/ks7010_sdio.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/d
On Mon, 2017-03-13 at 13:00 +0100, Matthias Brugger wrote:
>
> On 03/03/17 14:56, sean.w...@mediatek.com wrote:
> > From: Sean Wang
> >
> > This patch adds documentation for devicetree bindings
> > for LED support as the subnode of MT6323 PMIC
> >
> > Signed-off-by: Sean Wang
> > ---
> > Docume
Ni Nicolas,
2017-03-14 1:57 GMT+09:00 Nicolas Dichtel :
>> BTW, this series does not apply cleanly.
>>
>> If you could rebase it onto v4.11-rc1 tag,
>> it would be helpful.
> You really want this on top of 4.11-rc1 or the last linus tag, ie v4.11-rc2?
>
Basically, I queue up patches based on -rc
Line 460 looks suspicious. Can tmprange be different than range but not
be an ERR_PTR? If so, lpcdev->io_host will have an invalid value.
julia
-- Forwarded message --
Date: Tue, 14 Mar 2017 13:12:05 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re:
4 macros already defined in hdmi.h,
which is not required to redefine in hdmi_audio.c
Signed-off-by: Vinay Simha BN
---
drivers/gpu/drm/msm/hdmi/hdmi_audio.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/gpu/drm/msm/hdmi/hdmi_audio.c
b/drivers/gpu/drm/msm/hdmi/hdmi_audio.c
i
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc2 next-20170310]
[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/zhichang-yuan/LPC-legacy-ISA-I-O-suppo
Hi Kees,
2017-02-02 8:04 GMT+09:00 Kees Cook :
> If a structure is marked with __attribute__((designated_init)) from
> GCC or Sparse, it needs to have all static initializers using designated
> initialization. Fail the build for any missing cases. This attribute will
> be used by the randstruct p
The best place to register the CPU cooling device is from the cpufreq
driver as we would know if all the resources are already available or
not. That's what is done for the cpufreq-dt.c driver as well.
The cpu-cooling driver for dbx500 platform was just (un)registering
with the thermal framework a
Alig arguments with open parenthesis.
Signed-off-by: Arushi Singhal
---
changes in v3
- Improve the commit message.
drivers/staging/speakup/kobjects.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/speakup/kobjects.c
b/drivers/staging/speakup/kobjects.c
i
Patch fixes the warnings reported by checkpatch.pl
for please use a blank line after function/struct/union/enum
declarations.
Add a blank line after enum and struct declarations.
Signed-off-by: Arushi Singhal
---
changes in v3
- change the subject and commit message to make it more relevant.
Improve readability by fixing multiple checkpatch.pl
issues in speakup driver.
Arushi Singhal (2):
staging: speakup: Add blank line after declarations
staging: speakup: fix "Alignment match open parenthesis"
drivers/staging/speakup/kobjects.c | 2 +-
drivers/staging/speakup/main.c
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc2 next-20170310]
[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/zhichang-yuan/LPC-legacy-ISA-I-O-suppo
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc2 next-20170310]
[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/zhichang-yuan/LPC-legacy-ISA-I-O-suppo
On 03/13/2017 06:35 PM, Andrew Duggan wrote:
>
>
> On 03/13/2017 06:15 AM, Benjamin Tissoires wrote:
>> [Resending, forgot to add Jiri in CC]
>>
>> On Mar 13 2017 or thereabouts, Benjamin Tissoires wrote:
>>> On Mar 13 2017 or thereabouts, Thorsten Leemhuis wrote:
Lo! On 12.03.2017 02:55,
From: Jon Maxwell
Date: Fri, 10 Mar 2017 16:40:33 +1100
> As Eric Dumazet pointed out this also needs to be fixed in IPv6.
> v2: Contains the IPv6 tcp/Ipv6 dccp patches as well.
>
> We have seen a few incidents lately where a dst_enty has been freed
> with a dangling TCP socket reference (sk->sk
From: Doug Berger
Date: Mon, 13 Mar 2017 17:41:30 -0700
> This collection of patches contains changes related to adding
> support for the BCM7260, BCM7268, and BCM7271 devices that
> contain a new version of the GENET MAC IP block (v5) and a new
> fast ethernet (10/100BASE-T) internal PHY.
>
> T
Signed-off-by: mshan
---
drivers/staging/fwserial/fwserial.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fwserial/fwserial.c
b/drivers/staging/fwserial/fwserial.c
index 41a49c8..d693c03 100644
--- a/drivers/staging/fwserial/fwserial.c
+++ b/drivers/staging
On Mon, Mar 13, 2017 at 02:30:29PM -0700, Matthias Kaehlcke wrote:
> This fixes the following warning when building with clang and
> CONFIG_DMA_ENGINE_RAID=n :
>
> drivers/dma/dmaengine.c:1102:11: error: array index 2 is past the end of the
> array (which contains 1 element) [-Werror,-Warray-boun
Hi Mark,
On Wed, Mar 8, 2017 at 9:22 PM, Mark Brown wrote:
> The patch
>
>ASoC: sun8i-codec: Update mixer to use SOC_DAPM_DOUBLE
>
> has been applied to the asoc tree at
>
>git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
>
> All being well this means that it will be integr
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc2 next-20170310]
[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/zhichang-yuan/LPC-legacy-ISA-I-O-suppo
Pavel Machek reported the following warning on x86-32:
WARNING: kernel stack frame pointer at f50cdf98 in swapper/2:0 has bad value
(null)
The warning is caused by the unwinder not realizing that it reached the
end of the stack, due to an unusual prologue which gcc sometimes
generates for al
On Sun, Mar 05, 2017 at 09:37:03PM +0800, Icenowy Zheng wrote:
> Originally we enable a special gate bit when the compatible indicates
> A23/33.
>
> But according to BSP sources and user manuals, more SoCs will need this
> gate bit.
>
> So make it a common quirk configured in the config struct.
>
On Mon, Mar 13, 2017 at 07:50:21PM +0100, Borislav Petkov wrote:
>On Fri, Feb 17, 2017 at 10:30:33PM +0800, Wei Yang wrote:
>> In case (last_start <= step_size), start is for sure to be 0. So, it is
>
Hmm, I may write it more specific:
"start" is for sure to be set to 0 with round_down(last_start
On Tue, Feb 21, 2017 at 03:07:11PM -0800, Eric Biggers wrote:
> From: Eric Biggers
>
> Filesystem encryption ostensibly supported revoking a keyring key
> that had been used to "unlock" encrypted files, causing those files
> to become "locked" again. This was, however, buggy for several
> reasons
Hi Sakari,
I started preparing a long argument about it, but gave up in favor of a
simpler one.
Em Mon, 13 Mar 2017 14:46:22 +0200
Sakari Ailus escreveu:
> Drivers are written to support hardware, not particular use case.
No, it is just the reverse: drivers and hardware are developed to
supp
On Mon, Mar 06, 2017 at 12:17:39PM +, Ramiro Oliveira wrote:
> Add a DT property to control an optional external reset line
>
> Signed-off-by: Ramiro Oliveira
> ---
> drivers/dma/xilinx/xilinx_dma.c | 24
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
> diff -
qeic_of_init just get device_node of qeic from dtb and call qe_ic_init,
pass the device_node to qe_ic_init.
So merge qeic_of_init into qe_ic_init to get the qeic node in
qe_ic_init.
Signed-off-by: Zhao Qiang
---
drivers/irqchip/irq-qeic.c | 82 ++
incl
QEIC was supported on PowerPC, and dependent on PPC,
Now it is supported on other platforms, so remove PPCisms.
Signed-off-by: Zhao Qiang
---
arch/powerpc/platforms/83xx/km83xx.c | 1 -
arch/powerpc/platforms/83xx/misc.c| 1 -
arch/powerpc/platforms/83xx/mpc832x_mds.c
move the driver from drivers/soc/fsl/qe to drivers/irqchip,
merge qe_ic.h and qe_ic.c into irq-qeic.c.
Signed-off-by: Zhao Qiang
---
MAINTAINERS| 6 ++
drivers/irqchip/Makefile | 1 +
drivers/{soc/fsl/qe/qe_ic.c => irqchip/irq
The codes of qe_ic init from a variety of platforms are redundant,
merge them to a common function and put it to irqchip/irq-qeic.c
For non-p1021_mds mpc85xx_mds boards, use "qe_ic_init(np, 0,
qe_ic_cascade_low_mpic, qe_ic_cascade_high_mpic);" instead of
"qe_ic_init(np, 0, qe_ic_cascade_muxed_mpic
QEIC is supported more than just powerpc boards, so remove PPCisms.
changelog:
Changes for v8:
- use IRQCHIP_DECLARE() instead of subsys_initcall in qeic driver
- remove include/soc/fsl/qe/qe_ic.h
Zhao Qiang (4):
irqchip/qeic: move qeic driver from drivers/soc/fsl/qe
When allocating pg_data in alloc_node_data(), it will try to allocate from
local node first and then from any node. If it fails at the second trial,
it means there is not available memory on any node.
This patch fixes the error message and correct one typo.
Signed-off-by: Wei Yang
---
v2:
*
On Tue, Mar 14, 2017 at 08:17:00AM +0530, Vaibhav Jain wrote:
> Recently started seeing a kernel oops when a module tries removing a
> memory mapped sysfs bin_attribute. On closer investigation the root
> cause seems to be kernfs_release_file() trying to call
> kernfs_op.release() callback that's N
numa_nodemask_from_meminfo() is called to set bit according to
numa_meminfo. While the only two places for this call is used to set proper
bit to a copy of numa_nodes_parsed from numa_meminfo. With current code
path, those numa node information in numa_meminfo is a subset of
numa_nodes_parsed. So i
On 13-03-17, 14:32, Kevin Hilman wrote:
> Ulf Hansson writes:
>
> > On 13 March 2017 at 17:01, Ulf Hansson wrote:
> >> On 22 February 2017 at 09:28, Viresh Kumar wrote:
> >>> They were never used in the kernel, not sure why they got merged into
> >>> the kernel though. Get rid of them.
> >>
> >
On Tue, 14 Mar 2017 10:00:07 +0800
Qi Hou wrote:
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index 577f026..e8b35e4 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -2627,8 +2627,6 @@ __visible void trace_hardirqs_off_caller(unsigned long
> i
On March 14, 2017 6:19 AM Shakeel Butt wrote:
>
> Recently kswapd has been modified to give up after MAX_RECLAIM_RETRIES
> number of unsucessful iterations. Before going to sleep, kswapd thread
> will unconditionally wakeup all threads sleeping on pfmemalloc_wait.
> However the awoken threads wi
On Mon, Mar 13, 2017 at 07:11:12AM -0700, kernelci.org bot wrote:
> stable-rc boot: 530 boots: 5 failed, 516 passed with 9 offline
> (v4.10.2-76-g43100e143367)
These are ok, right? And 4.9 seems to not be doing many boots, is the
build farm just busy?
thanks,
greg k-h
Please stop sending "guesswork" patches. This message to you is not
new. I am running out of avenues where I can ask you to cease and
desist; spamming maintainers like this is not acceptable. You are
one step away from being in a kill-file.
On Mon, Mar 13, 2017 at 10:00 PM, Qi Hou wrote:
> T
On Mon, Mar 13, 2017 at 03:38:11PM -0700, Guenter Roeck wrote:
> On Mon, Mar 13, 2017 at 04:43:09PM +0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.10.3 release.
> > There are 75 patches in this series, all will be posted as a response
> > to this one. I
> "Tomas" == Tomas Winkler writes:
Tomas> Fix compilation warning drivers/scsi/ufs/ufshcd.c:7645:13:
Tomas> warning: comparison of unsigned expression < 0 is always false
Tomas> [-Wtype-limits] if ((value < UFS_PM_LVL_0) || (value >=
Tomas> UFS_PM_LVL_MAX))
Applied to 4.11/scsi-fixes, thanks
On Tue, Feb 21, 2017 at 11:38:04PM +0300, Eugeniy Paltsev wrote:
> +static struct axi_dma_desc *axi_desc_get(struct axi_dma_chan *chan)
> +{
> + struct dw_axi_dma *dw = chan->chip->dw;
> + struct axi_dma_desc *desc;
> + dma_addr_t phys;
> +
> + desc = dma_pool_zalloc(dw->desc_pool,
On Wed, Mar 08, 2017 at 08:39:55PM -0800, Andrew Lutomirski wrote:
> On Wed, Mar 8, 2017 at 3:41 PM, Dmitry V. Levin wrote:
[...]
> > Is there any progress with this (or any alternative) solution?
> >
> > I see the kernel side has changed a bit, and the strace part
> > is in a better shape than 5 y
Hi,
xfstests cases:
generic/075 generic/112 generic/127 generic/231 generic/263
fail with DAX, pass without it. Both xfs and ext4.
It was okay on 0306 -next tree.
+ ./check generic/075
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 hp-dl360g9-12
4.11.0-rc1-linux-next-5be4921-ne
On 03/03/17 11:51, Alexey Kardashevskiy wrote:
> With just CONFIG_DEBUG_INFO=y, the makefile adds "-g" to
> KBUILD_CFLAGS/KBUILD_AFLAGS and the test passes.
>
> However, if CONFIG_DEBUG_INFO_SPLIT is also enabled, the makefile
> adds "-gsplit-dwarf" instead which makes the test fail with $?==1
> b
On Mon, Mar 13, 2017 at 02:00:10PM +0100, Borislav Petkov wrote:
>On Mon, Feb 06, 2017 at 11:35:28PM +0800, Wei Yang wrote:
>> When allocating pg_data in alloc_node_data(), it will try to allocate from
>> local node first and then from any node. If it fails at the second trial,
>> it means there is
On Mon, Mar 13, 2017 at 02:30:46PM +0100, Borislav Petkov wrote:
>On Mon, Feb 06, 2017 at 11:35:29PM +0800, Wei Yang wrote:
>> numa_nodemask_from_meminfo() is called to set bit according to
>> numa_meminfo. While the only two places for this call is used to set proper
>> bit to a copy of numa_nodes
Recently started seeing a kernel oops when a module tries removing a
memory mapped sysfs bin_attribute. On closer investigation the root
cause seems to be kernfs_release_file() trying to call
kernfs_op.release() callback that's NULL for such sysfs
bin_attributes. The oops occurs when kernfs_release
On Mon, Mar 13, 2017 at 07:06:25PM -0700, Doug Berger wrote:
> On 03/13/2017 06:06 PM, Andrew Lunn wrote:
> > On Mon, Mar 13, 2017 at 05:41:32PM -0700, Doug Berger wrote:
> >> +static int bcm7xxx_28nm_ephy_01_afe_config_init(struct phy_device *phydev)
> >> +{
> >> + int ret;
> >> +
> >> + /* set
On 03/14/2017 01:00 AM, Alex Deucher wrote:
> Does your kernel have this patch:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ef736d394e85b1bf1fd65ba5e5257b85f6c82325
Yes, my kernel has this patch (this issue first occurred in v4.10).
--
Cheers,
Umang Raghuva
On Tue, Mar 14, 2017 at 01:20:27AM +, Brown, Aaron F wrote:
> > Borislav Petkov writes:
> > > On Sun, Mar 12, 2017 at 03:55:08PM +0200, Andy Shevchenko wrote:
> > >
> > >> The only change that IMHO matters happened between v4.10 and v4.11-
> > rc1 is this:
> > >>
> > >> @@ -6276,8 +6274,8 @@ s
> "Cathy" == Cathy Avery writes:
Hi Cathy,
Cathy> I haven't received any feedback yet.
Cathy> Should I resend?
You sent this right at the beginning of the merge window. That almost
guarantees that nobody will have time to look at it.
Whereas now is a good time to send submissions for 4.12
Hi Vineet,
On Mon, 13 Mar 2017, Vineet Gupta wrote:
> I've not looked at the patches closely (or read the references paper fully
> yet),
> but at first glance it seems on ARC architecture, we can can potentially
> use/leverage this mechanism to implement the shared TLB entries. Before anyone
> sh
On Wed, Mar 01, 2017 at 02:07:21PM +, Colin King wrote:
> From: Colin Ian King
>
> The check to see if cd is null is redundant, pdata->channels is
> never null at this point, and hence &pdata->channels[i] cannot
> be null, so remove the null check.
>
> Detected by CoverityScan, CID#1357194 (
On Mon, Mar 13, 2017 at 11:14:07AM +, James Hogan wrote:
> Hi Greg,
>
> On Sat, Mar 04, 2017 at 01:09:58PM +, James Hogan wrote:
> > Commit 6a171b299379 ("serial: 8250_dw: Allow hardware flow control to be
> > used") recently broke the 8250_dw driver on platforms which don't select
> > HAV
On 03/14, Chao Yu wrote:
>On 2017/3/14 3:22, Jaegeuk Kim wrote:
>> On 03/13, Thorsten Leemhuis wrote:
>>> @Chao Yu/@Jaegeuk Kim: I'm considering to add this to the regressions
>>> report for 4.11; or is there a reason why it shouldn't be considered a
>>> regression? Ciao, Thorsten
>>
>> Hi,
>>
>>
Thank you for your very helpful answer. I really do appreciate it.
It's possible that this device is using high speed because it offers a feature
to transfer its internal clipboard to the host, and it allows that clipboard to
contain lots of data. Interestingly, though, hidden within a usage not
On Mon, Mar 13, 2017 at 11:57:18AM -0300, Arnaldo Carvalho de Melo wrote:
> > I'll just rename this to use the tools/perf/ style for such functions,
> > making it:
> >
> > static int hists__scnprintf_sort_fields(hists, buf, size)
>
> But then, while testing,
>
> Before:
>
> $ perf report
On 03/13/2017 03:32 PM, David Miller wrote:
From: Guenter Roeck
Date: Fri, 10 Mar 2017 17:45:21 -0800
An insert/remove stress test generated the following log message sequence.
...
Use netdev_dbg() instead of netdev_warn() for the repeating messages
to reduce logging noise.
Signed-off-by: G
The dgnc_tty_send_break() has a switch-case condition for msec.
It is no use except case -1.
Signed-off-by: Daeseok Youn
---
V2: The two patches in previous series are merged into one patch.
drivers/staging/dgnc/dgnc_tty.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --
On 2017/3/14 3:22, Jaegeuk Kim wrote:
> On 03/13, Thorsten Leemhuis wrote:
>> @Chao Yu/@Jaegeuk Kim: I'm considering to add this to the regressions
>> report for 4.11; or is there a reason why it shouldn't be considered a
>> regression? Ciao, Thorsten
>
> Hi,
>
> I'm planning to submit f2fs updat
The bd variables in functions are already assigned from
ch->ch_bd but it is not used in those functions except checking NULL.
The ch->ch_bd could be replaced with bd variable.
Signed-off-by: Daeseok Youn
---
V2: Patches in previous series are splited but it could be merged into one.
There are li
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Philippe Reynes
> Sent: Sunday, February 5, 2017 3:11 PM
> To: Kirsher, Jeffrey T ; da...@davemloft.net
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux-
> ker...@vger.kernel.org; Philippe
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 1771c6e1a567ea0ba20a4ffe68a1419fd8ef
Author: Andrey Ryabinin
AuthorDate: Fri May 20 16:59:31 2016 -0700
Commit: Linus
On 03/13/2017 06:06 PM, Andrew Lunn wrote:
> On Mon, Mar 13, 2017 at 05:41:32PM -0700, Doug Berger wrote:
>> +static int bcm7xxx_28nm_ephy_01_afe_config_init(struct phy_device *phydev)
>> +{
>> +int ret;
>> +
>> +/* set shadow mode 2 */
>> +ret = phy_set_clr_bits(phydev, MII_BCM7XXX_TES
On 14 March 2017 at 09:10, Jun Li wrote:
> Hi,
>
>> -Original Message-
>> From: Baolin Wang [mailto:baolin.w...@linaro.org]
>> Sent: Monday, March 13, 2017 4:44 PM
>> To: Jun Li
>> Cc: NeilBrown ; Felipe Balbi ; Greg KH
>> ; Sebastian Reichel ; Dmitry
>> Eremin-Solenikov ; David Woodhouse
The current order of calls within trace_hardirqs_off_caller() would provoke
an "unannotated irqs-off" WARNING.
This warning was reported by check_flags() when it found that the hardirqs has
been disabled but the irq-flags state, "hardirqs_enabled", has not been cleared.
Check_flags() is called vi
On 2017/3/14 2:35, Vince Weaver wrote:
> On Sat, 25 Feb 2017, Peter Zijlstra wrote:
>
>> On Sat, Feb 25, 2017 at 04:10:37PM +0800, Tan Xiaojun wrote:
>>
>>> 2)If it is, where we will fix it more appropriate, perf_fuzzer(not set
>>> 0 or 100) or kernel(limit 1 to 99), or maybe it is the bug of
>>>
The --next option shows the next task for each context switch, providing
more context for the sequence of scheduler events.
$ perf sched timehist --next | head
Samples do not have callchains.
timecpu task name wait time sch delay
run time
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Philippe Reynes
> Sent: Sunday, February 5, 2017 2:55 PM
> To: Kirsher, Jeffrey T ; da...@davemloft.net
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux-
> ker...@vger.kernel.org; Philippe
2017-03-14 7:26 GMT+09:00 Greg KH :
> On Sun, Mar 12, 2017 at 11:47:28PM +0900, Daeseok Youn wrote:
>> The bd variable in dgnc_tty_digiseta() is assigned with
>> ch->ch_bd but it is not used in this function except checking NULL.
>> The ch->ch_bd could be replaced with bd variable in dgnc_tty_digis
On Mon, 13 Mar 2017, Samuel Thibault wrote:
> Alan Stern, on dim. 12 mars 2017 21:40:33 -0400, wrote:
> > On Sun, 12 Mar 2017, Dave Mielke wrote:
> > > [quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400]
> > >
> > > >A device's speed is only partially related to its USB version. A
> > > >U
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Philippe Reynes
> Sent: Sunday, February 5, 2017 9:56 AM
> To: Kirsher, Jeffrey T ; da...@davemloft.net
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux-
> ker...@vger.kernel.org; Philippe
On Tue, Mar 14, 2017 at 01:20:27AM +, Brown, Aaron F wrote:
> Believe it or not we actually do test these changes. This one was
> tested by me and I did not have the same results you and the other
> people reporting this trace did. I made it back in the lab today and
> have spent a good part of
On Sun, 12 Mar 2017, Dave Mielke wrote:
> [quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400]
>
> >No, I was wondering why an HID device would run at high speed. Both
> >you and Samuel implied that this was because it was a USB-2 device.
> >But that is not an adequate answer, because it
+CC Ingo, tglx
Hi Till,
On 03/13/2017 03:14 PM, Till Smejkal wrote:
> Introduce a different type of address spaces which are first class citizens
> in the OS. That means that the kernel now handles two types of AS, those
> which are closely coupled with a process and those which aren't. While the
On 03/13/2017 06:15 AM, Benjamin Tissoires wrote:
[Resending, forgot to add Jiri in CC]
On Mar 13 2017 or thereabouts, Benjamin Tissoires wrote:
On Mar 13 2017 or thereabouts, Thorsten Leemhuis wrote:
Lo! On 12.03.2017 02:55, Cameron Gutman wrote:
Beginning in 4.11-rc1, it looks like RMI4 i
On 2017/3/14 3:57, Jaegeuk Kim wrote:
> On 03/13, Kinglong Mee wrote:
>> On 3/13/2017 20:10, Chao Yu wrote:
>>> free_nid_bitmap and free_nid_count in update_free_nid_bitmap should be
>>> updated atomically, use free_list_lock cover them to avoid race in
>>
>> nid_list_lock?
>
> Think so.
> I merge
From: Masaki Ota
-Fix the issue that V8(E7=73 03 28) devices are not assined correct device
information bit from OTP.
-Specified correct OTP bit for the V8 device setting of Button pad, DualPoint
and Touchpad size.
-Deleted extra code from alps_v8_protocol_data decision process.
Signed-off-by:
From: Masaki Ota
- V8 Button pad Stick Right and Middle button don't work.
- Alps stick devices have physical buttons absolutely, so delete
"ALPS_BUTTONPAD" check Flag from Stick button process.
Signed-off-by: Masaki Ota
Acked-by: Pali Rohar
---
drivers/input/mouse/alps.c | 6 ++
1 file
On 2017年03月13日 22:05, Steven Rostedt wrote:
On Mon, 13 Mar 2017 18:08:48 +0800
Qi Hou wrote:
The current order of calls within trace_hardirqs_off() would provoke an
"unannotated irqs-off" WARNING.
This warning was reported by check_flags() when it found that the hardirqs has
been disabled b
Merged.
Thanks.
2017년 03월 12일 03:04에 Krzysztof Kozlowski 이(가) 쓴 글:
> Support for Exynos4415 is going away because there are no internal nor
> external users.
>
> Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"),
> the platform cannot be instantiated so remove also the drive
1 - 100 of 1216 matches
Mail list logo
