The recently added mlxsw driver produces warnings in ARM
allmodconfig:
drivers/net/ethernet/mellanox/mlxsw/pci.c: In function 'mlxsw_pci_cmd_exec':
drivers/net/ethernet/mellanox/mlxsw/pci.c:1585:59: warning: right shift count
>= width of type [-Wshift-count-overflow]
linux/byteorder/big_endian.h:
* Rasmus Villemoes wrote:
> +#define _COMMA ,
> +#define _COND_PUNCTUATION_0(p)
> +#define _COND_PUNCTUATION_1(p) p
> +
> +#define CHOOSE_EXPR(cfg, expr, ...) _CHOOSE_EXPR(cfg, expr, ##__VA_ARGS__,
> /* empty defalt arg */)
> +#define _CHOOSE_EXPR(cfg, expr, def, ...)
> __CHOOSE_EXPR(__ARG_PLA
Wed, Oct 07, 2015 at 08:53:02AM CEST, j...@perches.com wrote:
>On Tue, 2015-10-06 at 23:47 +0200, Arnd Bergmann wrote:
>> The recently added mlxsw driver produces warnings in ARM
>> allmodconfig:
>>
>> drivers/net/ethernet/mellanox/mlxsw/pci.c: In function 'mlxsw_pci_cmd_exec':
>> drivers/net/ethe
On Tue, 2015-10-06 at 23:47 +0200, Arnd Bergmann wrote:
> The recently added mlxsw driver produces warnings in ARM
> allmodconfig:
>
> drivers/net/ethernet/mellanox/mlxsw/pci.c: In function 'mlxsw_pci_cmd_exec':
> drivers/net/ethernet/mellanox/mlxsw/pci.c:1585:59: warning: right shift count
> >=
From: Andrey Smetanin
Before vmbus_connect() synic is setup per vcpu - this means
hypervisor receives writes at synic msr's and probably allocate
hypervisor resources per synic setup.
If vmbus_connect() failed for some reason it's neccessary to cleanup
synic setup by call hv_synic_cleanup() at e
On 10/06/2015 09:51 PM, Alex Williamson wrote:
On Tue, 2015-10-06 at 18:23 +0300, Avi Kivity wrote:
On 10/06/2015 05:56 PM, Michael S. Tsirkin wrote:
On Tue, Oct 06, 2015 at 05:43:50PM +0300, Vlad Zolotarov wrote:
The only "like VFIO" behavior we implement here is binding the MSI-X
interrupt
On 10/07/2015 02:40 AM, kbuild test robot wrote:
> drivers/nfc/s3fwrn5/i2c.c:293:3-8: No need to set .owner here. The core will
> do it.
>
> Remove .owner field if calls are used which set it automatically
>
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
>
> CC: Robert Bald
drivers/staging/wilc1000/host_interface.c:2852:15-22: WARNING: kzalloc should
be used for pu8keybuf, instead of kmalloc/memset
drivers/staging/wilc1000/host_interface.c:2904:15-22: WARNING: kzalloc should
be used for pu8keybuf, instead of kmalloc/memset
drivers/staging/wilc1000/host_interface.c:6
Am Dienstag, den 06.10.2015, 16:02 -0700 schrieb Pushpal Sidhu:
> On Tue, Oct 6, 2015 at 3:16 PM, Fabio Estevam
> wrote:
> > On Tue, Oct 6, 2015 at 6:52 PM, Pushpal Sidhu > > wrote:
> > > Hi All,
> > >
> > > I'm attempting to use a standard fb console (using the
> > > imx6qdl-gw54xx.dtsi), but I
Tue, Oct 06, 2015 at 11:47:44PM CEST, a...@arndb.de wrote:
>The recently added mlxsw driver produces warnings in ARM
>allmodconfig:
>
>drivers/net/ethernet/mellanox/mlxsw/pci.c: In function 'mlxsw_pci_cmd_exec':
>drivers/net/ethernet/mellanox/mlxsw/pci.c:1585:59: warning: right shift count
>>= wid
Hi Stephen,
On 7 October 2015 at 06:51, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the driver-core tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/base/power/opp/debugfs.c: In function 'opp_debug_create_one':
> drivers/base/power/opp/debugfs.
Hi all,
Friendly ping. :)
Best regards,
- Yakir
On 09/22/2015 03:20 PM, Yakir Yang wrote:
Hi all,
The Samsung Exynos eDP controller and Rockchip RK3288 eDP controller
share the same IP, so a lot of parts can be re-used. I split the common
code into bridge directory, then rk3288 an
On Wed, Oct 07, 2015 at 07:08:25AM +0200, Vincent Stehlé wrote:
> drivers/staging/wilc1000/host_interface.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/wilc1000/host_interface.c
> b/drivers/staging/wilc1000/host_interface.c
> index 2cf82b2..2fe3023 10
Hi all,
Changes since 20151006:
I used the h8300 tree from next-20150828 since the current tree has been
rebased onto linux-next again :-(
The net-next tree lost its build failure.
The battery tree still had its build failure so I used the version from
next-20150925.
The xen-tip tree gained a
The change to fbtft_write_vmem16_bus9() is a bugfix, which is great, but
it's not mentioned in the changelog. Really it should be a separate
commit.
Fixes: 02eb884f4e26 ('drivers: staging: fbtft: fbtft-bus.c: Fix different
address space warning on I/O mem')
So it looks like this:
[patch 1] fb.h
* Andy Lutomirski wrote:
> On Tue, Oct 6, 2015 at 10:56 AM, Eric Dumazet wrote:
> > On Tue, 2015-10-06 at 10:50 -0700, Alexei Starovoitov wrote:
> >
> >> was also thinking that we can do it only in paths that actually
> >> have multiple protocol layers, since today bpf is mainly used with
> >>
On Tue, 2015-10-06 at 11:25 -0700, Laura Abbott wrote:
> On 10/05/2015 08:35 PM, Michael Ellerman wrote:
> > On Fri, 2015-10-02 at 08:43 -0700, Laura Abbott wrote:
> >> Hi,
> >>
> >> We received a report (https://bugzilla.redhat.com/show_bug.cgi?id=1267395)
> >> of bad assembly
> >> when compiling
On 2015年10月02日 22:33, Heiko Stübner wrote:
Hi Mark,
Am Freitag, 26. Juni 2015, 09:27:18 schrieb Mark Yao:
We want to display a buffer allocated by other driver, need import
the buffer to gem.
Signed-off-by: Mark Yao
This looks interesting ... do you want to follow up on it?
Heiko
Hi Hei
* Chris Metcalf wrote:
> Both alpha and tile needed implementations of zero_bytemask.
>
> The alpha version is untested.
>
> Signed-off-by: Chris Metcalf
> ---
> arch/alpha/include/asm/word-at-a-time.h | 2 ++
> arch/tile/include/asm/word-at-a-time.h | 8 +++-
> 2 files changed, 9 inser
Some drivers use member screen_base of struct fb_info to store non-
__iomem pointers, creating the need for ugly __force typecasts to
avoid sparse warnings. This adds an alternate pointer without the
__iomem qualifyer for this use.
Signed-off-by: Lars Svensson
---
include/linux/fb.h | 5 -
1
Member screen_base in struct fb_info is declared with __iomem
qualifier causing sparse warnings when used as a regular ponter.
To avoid the warnings, instead use alternate non-__iomem pointer,
screen_buffer, troughout the driver.
Signed-off-by: Lars Svensson
---
v2: removed all references to scre
This patch creates a platform driver for the SCM so that we can adequately
manage resources. This removes clients having to carry the necessary
clocks to use the SCM resources.
Signed-off-by: Andy Gross
---
.../devicetree/bindings/firmware/qcom,scm.txt | 25
drivers/firmware/qcom_sc
On 5.10.2015 16:44, Michal Hocko wrote:
> So I can see basically only few ways out of this deadlock situation.
> Either we face the reality and allow small allocations (withtout
> __GFP_NOFAIL) to fail after all attempts to reclaim memory have failed
> (so after even OOM killer hasn't made any prog
On Fri, Oct 2, 2015 at 6:10 AM, Neil Horman wrote:
> On Thu, Oct 01, 2015 at 08:25:46PM -0700, Vinson Lee wrote:
>> Hi.
>>
>> I am seeing a netpoll_send_skb_on_dev warning with bnx2. It happens on
>> Linux 4.1 and I am able to reproduce the warning with Linux 4.3-rc3.
>>
>> [ cut here
The host_int_init() function can dereference the pstrWFIDrv pointer
while it is NULL on its error path. Jump directly to the _fail_ error
label in the end of the error handling path to avoid that.
By doing that we also skip stopping our kthread and destroying
our message queue, but they wer
Hi Greg,
After merging the driver-core tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/base/power/opp/debugfs.c: In function 'opp_debug_create_one':
drivers/base/power/opp/debugfs.c:48:7: warning: passing argument 4 of
'debugfs_create_bool' from incompatibl
In function obj_malloc:
if (!class->huge)
/* record handle in the header of allocated chunk */
link->handle = handle;
else
/* record handle in first_page->private */
set_page_private(first_page, handle);
The huge's page
On Tue, Oct 6, 2015 at 9:54 PM, Minchan Kim wrote:
> Hello,
>
> On Mon, Oct 05, 2015 at 04:23:01PM +0800, Hui Zhu wrote:
>> In function obj_malloc:
>> if (!class->huge)
>> /* record handle in the header of allocated chunk */
>> link->handle = handle;
>> else
I intend to give to you a portion of my Wealth as a free-will financial
donation to you.
Respond now to partake.
Regards
Maria-Elisabeth Schaeffler
Email:charityinquiri...@qq.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.
Hi Andrew,
Today's linux-next merge of the akpm-current tree got conflicts in:
mm/failslab.c
mm/page_alloc.c
between commit:
621a5f7ad9cd ("debugfs: Pass bool pointer to debugfs_create_bool()")
from the driver-core tree and commit:
67c145d9ff18 ("mm, page_alloc: rename __GFP_WAIT to _
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
drivers/usb/host/u132-hcd.c
between commit:
d5f9e73309b7 ("USB: u132-hcd: Fix seperate word in printk message")
from the usb tree and commit:
ac4f832eb227 ("mm, page_alloc: distinguish between being unable t
Hi,
On 10/06/2015 02:47 PM, Brian Norris wrote:
Hi Archit,
On Mon, Oct 05, 2015 at 12:21:54PM +0530, Archit Taneja wrote:
On 10/02/2015 08:35 AM, Brian Norris wrote:
On Wed, Aug 19, 2015 at 10:19:03AM +0530, Archit Taneja wrote:
The Qualcomm NAND controller is found in SoCs like IPQ806x, MSM
Recently, we made a driver utilizing kmap_atomic_to_page. Of course, it's not
mainlined. People may be using it outside mainline just like us.
vmalloc has vmalloc_to_page, pkmap has kmap_to page, and fixmap has
kmap_atomic_to_page. Then.. how about letting virt_to_page do them all?
On 10/07/20
On 08/09/2015 12:04 AM, Russell King wrote:
On a mode set, DRM makes the following sequence of calls:
* for_each_encoder
* bridge mode_fixup
* encoder mode_fixup
* crtc mode_fixup
* for_each_encoder
* bridge disable
* encoder prepare
* bridge post_disab
Hi Nicholas,
After merging the target-updates tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/hwtracing/stm/policy.c:212:2: error: unknown field 'show_attribute'
specified in initializer
.show_attribute = stp_policy_node_attr_show,
^
drivers/hwtracing/stm/poli
Hi Russell & Andy
On 08/09/2015 12:03 AM, Russell King wrote:
Only enable audio support if the sink supports audio in some form, as
defined via its EDID. We discover this capability using the generic
drm_detect_monitor_audio() function.
Signed-off-by: Russell King
Some to 06/12 reply.
Test
Hi Russell & Andy
On 08/09/2015 12:03 AM, Russell King wrote:
The FSL kernel detects the HDMI vendor id, and uses this to set
hdmi->edid_cfg.hdmi_cap, which is then used to set mdvi appropriately,
rather than detecting whether we are outputting a CEA mode. Update
the dw_hdmi code to use this lo
On Mon, Oct 05, 2015 at 11:04:35AM -0700, Dave Hansen wrote:
>
> The warning comes out of ext4_walk_page_buffers() and the dirty state
> comes from page_zero_new_buffers(). That seems a _bit_ goofy that the
> filesystem is marking the page dirty and then so shortly warning about it.
Yes, this is
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: 07 October 2015 04:51
> To: Scott Branden; Brian Norris; Anup Patel
> Cc: linux-arm-ker...@lists.infradead.org; Rob Herring; Pawel Moll; Mark
> Rutland; Ian Campbell; Kumar Gala; Catalin Marinas; Will Deac
Hi William,
[auto build test WARNING on v4.3-rc4 -- if it's inappropriate base, please
ignore]
coccinelle warnings: (new ones prefixed by >>)
>> drivers/gpio/gpio-104-idio-16.c:151:3-8: No need to set .owner here. The
>> core will do it.
Please review and possibly fold the followup patch.
-
drivers/gpio/gpio-104-idio-16.c:151:3-8: No need to set .owner here. The core
will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: William Breathitt Gray
Signed-off-by: Fengguang Wu
---
gpio-104-id
Hi,
Daniel Lezcano writes:
> On 10/06/2015 07:02 PM, Felipe Balbi wrote:
>> Introduce a new clocksource driver for Texas
>> Instruments 32.768 Hz device which is available
>> on most OMAP-like devices.
>>
>> Signed-off-by: Felipe Balbi
>
> Hi Felipe,
>
> With the couple of nits below fixed, yo
On Tue, Oct 6, 2015 at 8:02 PM, Pushpal Sidhu wrote:
> When I took your patch and adapted it for imx6qdl-gw54xx.dtsi, I found
> that HDMI video out was slightly shifted to the left and resolution
> remained at 1024x768p.
>
> I also found that when I disabled DRM_IMX_LDB, HDMI out stopped
> workin
- On Oct 6, 2015, at 7:56 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> Allow Ftrace, Perf, and LTTng to hook on the irqsoff tracer and trace
> longest irqsoff and preemptoff critical sections, or those beyond a
> specified threshold.
>
> This requires introducing a __trace_(
Hi Linus,
The following changes since commit 5634347dee31373a8faf084f4cdbf6d5ea0b03a4:
Merge tag 'arm64-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2015-10-02 14:54:16
-0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nf
Hi all,
After merging the regulator tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/regulator/core.c: At top level:
drivers/regulator/core.c:139:13: warning: 'regulator_lock_supply' defined but
not used [-Wunused-function]
static void regulator_lock_supply
The ACCES 104-IDIO-16 family of PC/104 utility boards feature 16
optically isolated inputs and 16 optically isolated FET solid state
outputs. This driver provides GPIO support for these 32 channels of
digital I/O. Change-of-State detection interrupts are not supported.
GPIO 0-15 correspond to digi
On Wed, Oct 07, 2015 at 12:11:34AM +0100, Al Viro wrote:
> On Tue, Oct 06, 2015 at 12:32:28AM -0400, Jacob Kiefer wrote:
>
> > int rtl8723a_set_rssi_cmd(struct rtw_adapter *padapter, u8 *param)
> > {
> > - *((u32 *)param) = cpu_to_le32(*((u32 *)param));
> > + __le32 leparam;
> >
> > - Fil
On 10/6/2015 1:56 AM, Marek Szyprowski wrote:
> DWC2 module on some platforms needs three additional hardware
> resources: phy controller, clock and power supply. All of them must be
> enabled/activated to properly initialize and operate. This was initially
> handled in s3c-hsotg driver, which has
On 10/06/2015 07:25 PM, Eric Anholt wrote:
> This adds support for enabling, disabling, and setting the rate of the
> audio domain clocks. It will be necessary for setting the pixel clock
> for HDMI in the VC4 driver and let us write a cpufreq driver. It will
> also improve compatibility with use
This patch removes the "const" qualifier from kvm_events_tp declaration
to account for the fact that some architectures may need to update this
variable dynamically. For instance, powerpc will need to update this
variable dynamically depending on the machine type.
Signed-off-by: Hemant Kumar
---
perf kvm can be used to analyze guest exit reasons. This support already
exists in x86. Hence, porting it to powerpc.
- To trace KVM events :
perf kvm stat record
If many guests are running, we can track for a specific guest by using
--pid as in : perf kvm stat record --pid
- To see the
Powerpc provides hcall events that also provides insights into guest
behaviour. Enhance perf kvm stat to record and analyze hcall events.
- To trace hcall events :
perf kvm stat record
- To show the results :
perf kvm stat report --event=hcall
The result shows the number of hypervisor call
Its better to remove the dependency on uapi/kvm_perf.h to allow dynamic
discovery of kvm events (if its needed). To do this, some extern
variables have been introduced with which we can keep the generic
functions generic.
Signed-off-by: Hemant Kumar
---
Changelog:
v8 to v9:
- Removed the macro de
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
arch/x86/xen/p2m.c
between commit:
98dd166ea3a3 ("x86/xen/p2m: hint at the last populated P2M entry")
from Linus' tree and commit:
c5fdd42b47ab ("x86/xen: export xen_alloc_p2m_entry()")
from the xen-tip tree.
I fi
This is intended to add ZTE device PIDs on kernel.
Signed-off-by: Liu.Zhao
---
drivers/usb/serial/option.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index 876423b..6b4a766 100644
--- a/drivers/usb/seria
> -Original Message-
> From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie]
> Sent: Tuesday, October 06, 2015 10:54 PM
> >>
> >> Aside from that, I'm curious which types of capsules you've used here
> >> too - does it include the MFH header ? Keep in mind the initial
> >> firmware t
On Tue, 6 Oct 2015, Russell King - ARM Linux wrote:
> On Tue, Oct 06, 2015 at 08:09:33PM +0900, Chanho Min wrote:
> > Since kmap_atomic returns the pkmap address without a new mapping to
> > fixmap for the page that is already mapped by kmap, It should be
> > considered for the pkmap address in km
On Wed, 2015-10-07 at 07:44 +1100, paul.sz...@sydney.edu.au wrote:
> I agree that pinning may be bad... should not the kernel penalize the
> badly pinned processes?
I didn't say pinning is bad, I said was what you're seeing is not a bug.
-Mike
--
To unsubscribe from this list: send the
Stefan Wahren writes:
> Hi Eric,
>
> Am 02.10.2015 um 21:54 schrieb Eric Anholt:
>> This adds support for enabling, disabling, and setting the rate of the
>> audio domain clocks. It will be necessary for setting the pixel clock
>> for HDMI in the VC4 driver and let us write a cpufreq driver. It
On Mon, Oct 05, 2015 at 08:00:40PM +0300, Alexander Kapshuk wrote:
> Thanks very much for everyone's feedback.
>
> Instead of flooding this mailing list with another bunch of ver_linux
> patches, I thought I would post another implementation, and see if you
> find any of the proposed changes worth
This adds support for enabling, disabling, and setting the rate of the
audio domain clocks. It will be necessary for setting the pixel clock
for HDMI in the VC4 driver and let us write a cpufreq driver. It will
also improve compatibility with user changes to the firmware's
config.txt, since our p
Ping.
On Tue, Sep 29, 2015 at 07:16:49PM -0400, Rich Felker wrote:
> From: Rich Felker
>
> The ELF binary loader in binfmt_elf.c requires an MMU, making it
> impossible to use regular ELF binaries on NOMMU archs. However, the
> FDPIC ELF loader in binfmt_elf_fdpic.c is fully capable as a loader
This is required since
commit 7e5071199355 ("mfd: tps6105x: Use i2c regmap to access registers").
Signed-off-by: Axel Lin
---
drivers/mfd/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index 87e84e7..0063c92 100644
--- a/drivers/mfd/Kconfig
On Mon, Oct 5, 2015 at 1:25 PM, Alexander Duyck
wrote:
> On 10/05/2015 06:59 AM, Vlastimil Babka wrote:
>>
>> On 10/02/2015 12:18 PM, Konstantin Khlebnikov wrote:
>>>
>>> When openvswitch tries allocate memory from offline numa node 0:
>>> stats = kmem_cache_alloc_node(flow_stats_cache, GFP_KERNEL
On 06/10/15 12:59, Arnd Bergmann wrote:
> The newly added pwm-brcmstb driver fails to build if CONFIG_PM_SLEEP
> is enabled:
>
> drivers/pwm/pwm-brcmstb.c: In function 'brcmstb_pwm_suspend':
> drivers/pwm/pwm-brcmstb.c:309:42: error: 'dev' undeclared (first use in this
> function)
> struct brcm
Since commit 7e5071199355 ("mfd: tps6105x: Use i2c regmap to access
registers"), we can use regmap helper functions instead of open coded.
Signed-off-by: Axel Lin
---
Hi Grigoryev,
I don't have this h/w, can you help test this patch? Thanks.
This patch depends on commit 7e5071199355
"mfd: tps610
This patch modifies the id and name of external connector with the
additional prefix to clarify both attribute and meaning of external
connector as following:
- EXTCON_CHG_* mean the charger connector.
- EXTCON_JACK_* mean the jack connector.
- EXTCON_DISP_* mean the display port connector.
Follow
Document a new Device Tree property 'samsung,s2mps11-wrstbi-ground'
indicating that WRSTBI pin of S2MPS13 PMIC is pulled down so
corresponding buck warm reset function should be disabled.
Signed-off-by: Krzysztof Kozlowski
---
Changs since v1:
None.
---
Documentation/devicetree/bindings/mfd/s2
On Wed, 2015-09-30 at 16:45 -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Sep 30, 2015 at 09:09:09PM +0200, Jiri Olsa escreveu:
> > On Wed, Sep 30, 2015 at 11:28:36AM -0700, Sukadev Bhattiprolu wrote:
> > > From e29a7236122c4d807ec9ebc721b5d7d75c8d Mon Sep 17 00:00:00 2001
> > > From: Sukade
There are different revisions of the same chipset. For example S2MPS13 has
more than 2 revisions. They differ slightly in regulator constraints.
Print the revision number to easily find which PMIC is used on the board.
Signed-off-by: Krzysztof Kozlowski
---
Changs since v1:
None.
---
drivers/m
Hi,
On 07/10/2015 at 01:19:09 +0200, Marek Vasut wrote :
> >>/* The calculated value from the ADC is in Kelvin, we
> >>* want Celsius for hwmon so the offset is
> >>- * -272.15 * scale
> >>+ * -273.15 * scale
> >>*/
> >>- *val = -1075;
> >>- *val2 = 691699;
> >>+ *val = -1079;
> >>+ *val2 = 644268
The WRSTBI bit (disabled by default but enabled by bootloader), when
set, is responsible for resetting voltages to default values of
certain bucks on falling edge of Warm Reset Input pin from AP.
However on some boards (with S2MPS13) the pin is pulled down so any
suspend will effectively trigger t
On 06/10/15 14:54, Vivien Didelot wrote:
> In order to push switchdev objects down to DSA drivers, I need to include
> switchdev.h in dsa.h. But compilation fails because of a circular dependency
> issue, since dsa.h is also included in linux/netdevice.h.
Just for the record, what does this circul
drivers/nfc/s3fwrn5/i2c.c:293:3-8: No need to set .owner here. The core will do
it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Robert Baldyga
Signed-off-by: Fengguang Wu
---
i2c.c |1 -
1 file ch
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 049e6dde7e57f0054fdc49102e7ef4830c698b46
commit: c04c674fadeb4a8e6522fc838d4620f7cfd4c621 nfc: s3fwrn5: Add driver for
Samsung S3FWRN5 NFC Chip
date: 7 weeks ago
coccinelle warnings: (new ones prefixed b
From: Rafael J. Wysocki
If the upcoming system suspend is not going to be handled by the
platform firmware, like in the suspend-to-idle case, it is not
necessary to reset the controller in i8042_pm_suspend(), so avoid
doing that.
Moreover, if the system resume currently in progress has not been
On Arndale board (unlike Odroid U3) the USB3503 hub controller is
connected in phy mode (not through I2C). For successful probe it needs
to get reference to proper phy and enable it.
Signed-off-by: Krzysztof Kozlowski
Reported-by: Kevin Hilman
Reported-by: Arnd Bergmann
Cc: Kevin Hilman
Cc: Ar
Document new 'phys' and 'phys-names' properties.
Signed-off-by: Krzysztof Kozlowski
Cc: Kevin Hilman
Cc: Arnd Bergmann
Cc: riku.voi...@linaro.org
Cc: Marek Szyprowski
---
Documentation/devicetree/bindings/usb/usb3503.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/de
The USB3503 hub controller can be connected through I2C interface (e.g.
on Odroid-U3 board) or directly by phy (e.g. on Arndale board). Thus the
usb3503 driver can act as a i2c or platform device.
In the second configuration (phy) the driver did not get a reference to
necessary phy to use it. This
Hi,
Introduction
This patchset tries to fix probing of usb3503 on Arndale board
if the Samsung PHY driver is probed later (or built as a module).
*The patchset was not tested on Arndale board.*
I don't have that board. Please test it and say if the usb3503 deferred probe
works fine
Hi Bjorn,
Thanks for the feedback. Much of the issues you mentioned look pretty
straight forward to resolve, and will fix of for the next revision.
I have some immediate follow up comments to two issues you brought up:
On Tue, 6 Oct 2015, Bjorn Helgaas wrote:
+static int vmd_find_free_domain(v
Allow Ftrace, Perf, and LTTng to hook on the irqsoff tracer and trace
longest irqsoff and preemptoff critical sections, or those beyond a
specified threshold.
This requires introducing a __trace_() tracepoint static inline
which bypass static jump labels, because calling a breakpoint from the
irqs
The documentation on top of __DECLARE_TRACE() does not match its
implementation since the condition check has been added to the
RCU lockdep checks. Update the documentation to match its
implementation.
Fixes: a05d59a56733 "tracing: Add condition check to RCU lockdep checks"
Signed-off-by: Mathieu
From: "Sean O. Stalley"
Add registers defined in PCI-SIG's Enhanced allocation ECN.
Signed-off-by: Sean O. Stalley
[david.da...@cavium.com: Added more definitions for PCI_EA_BEI_*]
Signed-off-by: Signed-off-by: David Daney
---
include/uapi/linux/pci_regs.h | 44 +++
From: David Daney
SRIOV BARs can be specified via EA entries. Extend the EA parser to
extract the SRIOV BAR resources, and modify sriov_init() to use
resources previously obtained via EA.
Signed-off-by: David Daney
---
drivers/pci/iov.c | 11 +--
drivers/pci/pci.c | 7 +++
2 file
From: David Daney
The new Enhanced Allocation (EA) capability support creates resources
with the IORESOURCE_PCI_FIXED set. This causes a couple of problems:
1) Since these resources cannot be relocated or resized, their
alignment is not really defined, and it is therefore not specified.
T
From: David Daney
The original patches are from Sean O. Stalley. I made a few tweaks,
but feel that it is substancially Sean's work, so I am keeping the
patch set version numbering scheme going.
Tested on Cavium ThunderX system with 4 Root Complexes containing 50
devices/bridges provisioned with
From: "Sean O. Stalley"
Add support for devices using Enhanced Allocation entries instead of BARs.
This patch allows the kernel to parse the EA Extended Capability structure
in PCI configspace and claim the BAR-equivalent resources.
Signed-off-by: Sean O. Stalley
[david.da...@cavium.com: Add mo
Hi Robert,
On Mon, Aug 31, 2015 at 10:02:40AM +0200, Robert Baldyga wrote:
> [ +cc Samuel Ortiz and ]
>
> Hi Samuel,
>
> Could you please apply this patch?
Applied, thanks.
Cheers,
Samuel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ma
This allows using OpenCores I2C controller attached to its host in
native-endian mode with bi-endian CPUs. Example of such system is Xtensa
XTFPGA platform.
Acked-by: Peter Korsgaard
Signed-off-by: Max Filippov
---
Changes v1->v2:
- expand changelog with motivation for the change.
drivers/i2c/
On Wed, Oct 7, 2015 at 1:26 AM, Dmitry Torokhov
wrote:
> On Wed, Oct 07, 2015 at 01:31:44AM +0200, Rafael J. Wysocki wrote:
>> On Tuesday, October 06, 2015 03:43:08 PM Dmitry Torokhov wrote:
>> > On Wed, Oct 07, 2015 at 01:08:30AM +0200, Rafael J. Wysocki wrote:
>> > > On Tuesday, October 06, 2015
SRB status can have additional information. Mask these out before processing
SRB status.
This patch was sent as part of a collection of patches more than a year ago.
While the rest of the patches in the set were comitted, this patch was not.
I woulod like to thank Olaf for noticing that this patc
Commit 570c9a7a ("Input: joydev - use memdup_user() to duplicate
memory from user-space") changed the kmalloc() and copy_from_user()
with a single call to memdup_user() but wrongly used the same error
path than the old code in which the buffer allocated by kmalloc() was
freed if copy_from_user(
The mm-of-the-moment snapshot 2015-10-06-16-30 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On 10/03/2015 12:27 AM, Ingo Molnar wrote:
> - I'd also suggest providing an initial value with the 'alloc' call. It's
> true
>that user-space can do this itself in assembly, OTOH there's no reason not
> to
>provide a C interface for this.
You mean an initial value for the rights regi
On Wed, Oct 07, 2015 at 01:31:44AM +0200, Rafael J. Wysocki wrote:
> On Tuesday, October 06, 2015 03:43:08 PM Dmitry Torokhov wrote:
> > On Wed, Oct 07, 2015 at 01:08:30AM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, October 06, 2015 03:34:42 PM Dmitry Torokhov wrote:
> > > > On Wed, Oct 07, 2
On Tue, Oct 06, 2015 at 10:54:47PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Tuesday, October 06, 2015 6:44 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > linux-f2fs-de...@lists.sour
On 10/06/2015 07:02 PM, Felipe Balbi wrote:
Introduce a new clocksource driver for Texas
Instruments 32.768 Hz device which is available
on most OMAP-like devices.
Signed-off-by: Felipe Balbi
Hi Felipe,
With the couple of nits below fixed, you can my:
Acked-by: Daniel Lezcano
[ ... ]
+#
Hi Chao,
On Tue, Oct 06, 2015 at 10:54:12PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Saturday, October 03, 2015 12:48 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > linux-f2fs-de..
1 - 100 of 1030 matches
Mail list logo