Hi Arnd.
2016-04-17 4:23 GMT+09:00 Arnd Bergmann :
> Better count the files:
>
> $ git grep -wl clk_register | wc -l
> 179
>
> $ git grep -wl reset_controller_register | wc -l
> 25
>
> This is more like seven times as many, which seems about right.
Ah, right. I exaggerated too much.
>> Reset
On Sun, 2016-04-17 at 07:43 +0200, Julia Lawall wrote:
> On Sat, 16 Apr 2016, Joe Perches wrote:
> > On Sat, 2016-04-16 at 12:04 -0700, Joe Perches wrote:
> > > Add a test for use of ACCESS_ONCE that could be written using
> > > READ_ONCE or WRITE_ONCE.
> > >
> > > --fix it too if desired.
> >
>
Nicolai Stange writes:
> Currently, in mb_find_order_for_block(), there's a loop like the following:
>
> while (order <= e4b->bd_blkbits + 1) {
> ...
> bb += 1 << (e4b->bd_blkbits - order);
> }
>
> Note that the updated bb is used in the loop's next iteration only.
>
> However, at the
On 11/04/16 16:08, Crestez Dan Leonard wrote:
> On 04/10/2016 04:12 PM, Jonathan Cameron wrote:
>> On 07/04/16 20:48, Peter Meerwald-Stadler wrote:
>>>
This just adds support for reporting illuminance with default settings.
All default registers are written on probe because the devic
On 11/04/16 17:11, Crestez Dan Leonard wrote:
> On 04/07/2016 10:59 PM, Peter Meerwald-Stadler wrote:
>>> static int max44000_probe(struct i2c_client *client,
>>> const struct i2c_device_id *id)
>>> {
>>> @@ -513,6 +569,12 @@ static int max44000_probe(struct i2c_client *client,
On 15/04/16 21:16, mchri...@redhat.com wrote:
> From: Mike Christie
>
> The last patch added a REQ_OP_FLUSH for request_fn drivers
> and the next patch renames REQ_FLUSH to REQ_PREFLUSH which
> will be used by file systems and make_request_fn drivers so
> they can send a write/flush combo.
>
> T
From: Alexander Usyskin
Global me_client_index is used only during the enumeration process and
can be effectively replaced by me_addr data from the last enumeration
response as we always enumerate clients in the increasing order.
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
--
From: Alexander Usyskin
In the case when disconnection is initiated from the FW
the driver is flushing items from the write control list while
iterating over it:
mei_irq_write_handler()
list_for_each_entry_safe(ctrl_wr_list) <-- outer loop
mei_cl_irq_disconnect_rsp()
From: Alexander Usyskin
When a message is received and amthif client is not in reading state
the message is ignored and left dangling in the queue. This may happen
after one of the amthif host connections is closed w/o completing the
reading. Another client will pick up a wrong message on next re
On 11/04/16 19:52, Crestez Dan Leonard wrote:
> This just adds support for reporting illuminance with default settings.
>
> Important default registers are written on probe because the device
> otherwise lacks a reset function.
>
> Signed-off-by: Crestez Dan Leonard
cc'ing Mark Brown for regcach
The new MACsec driver uses the AES crypto algorithm, but can be configured
even if CONFIG_CRYPTO is disabled, leading to a build error:
warning: (MAC80211 && MACSEC) selects CRYPTO_GCM which has unmet direct
dependencies (CRYPTO)
warning: (BT && CEPH_LIB && INET && MAC802154 && MAC80211 && BLK_DE
On Sat, Apr 16, 2016 at 2:19 AM, Jon Masters wrote:
> On 04/15/2016 01:06 PM, Tomasz Nowicki wrote:
>> From the functionality point of view this series might be split into the
>> following logic parts:
>> 1. Necessary fixes as the preparation for using driver on ARM64.
>> 2. New ECAM API and updat
On 11/04/16 19:52, Crestez Dan Leonard wrote:
> The proximity sensor relies on sending pulses to an external IR led and
> it is disabled by default on powerup. The driver will enable it with a
> default power setting.
>
> Signed-off-by: Crestez Dan Leonard
> ---
> drivers/iio/light/max44000.c |
On 11/04/16 19:52, Crestez Dan Leonard wrote:
> This is exposed as an output channel with "led" as an extend_name.
>
> Other sensors also have support for controlling an external LED. It's
> not clear that simply exposing an undecorated output channel is the
> correct approach.
Agreed that this is
On 11/04/16 19:52, Crestez Dan Leonard wrote:
> This patch exposes ALSTIM as illuminance_integration_time and ALSPGA as
> illuminance_scale.
>
> Changing ALSTIM also changes the number of bits available in the data
> register. This is handled inside raw value reading because:
> * It's very easy to
On 11/04/16 19:52, Crestez Dan Leonard wrote:
> Signed-off-by: Crestez Dan Leonard
One trivial comment inline.
> ---
> drivers/iio/light/max44000.c | 62
>
> 1 file changed, 62 insertions(+)
>
> diff --git a/drivers/iio/light/max44000.c b/drivers/iio
On Sat, Apr 16, 2016 at 08:26:48PM +0100, Jonathan Cameron wrote:
> On 10/04/16 20:22, Ksenija Stanojevic wrote:
> > Set INPUT_PROP_DIRECT to indicate that it is a touchscreen on the
> > device to help userspace classify it.
> >
> > Signed-off-by: Ksenija Stanojevic
> Sounds correct to me. Dmitr
On 11/04/16 15:24, Crestez Dan Leonard wrote:
> These chips have an almost identical interface but support a different
> number of value bits. Datasheet links for comparison:
>
> * http://www.ti.com/lit/ds/symlink/adc081c021.pdf
> * http://www.ti.com/lit/ds/symlink/adc101c021.pdf
> * http://www
On 11/04/16 15:24, Crestez Dan Leonard wrote:
> Using this requires software triggers like CONFIG_IIO_HRTIMER_TRIGGER.
>
> The device can be configured to do internal periodic sampling but does not
> offer some sort of interrupt on data ready. Interrupts can only trigger when
> values get out of a
On 17/04/16 10:33, Dmitry Torokhov wrote:
> On Sat, Apr 16, 2016 at 08:26:48PM +0100, Jonathan Cameron wrote:
>> On 10/04/16 20:22, Ksenija Stanojevic wrote:
>>> Set INPUT_PROP_DIRECT to indicate that it is a touchscreen on the
>>> device to help userspace classify it.
>>>
>>> Signed-off-by: Ksenij
On Wednesday 13 April 2016 11:15:13 David Miller wrote:
> From: Stephen Rothwell
> Date: Wed, 13 Apr 2016 17:50:28 +1000
>
> > After merging the net-next tree, today's linux-next build (arm
> > allmodconfig) failed like thisi (this has actually been failing for a
> > few days, now):
> >
> > ERRO
On 15/04/16 15:13, Daniel Baluta wrote:
> This is useful for easily adding SPI support in later patches.
>
> Now bmc150_magn exports core functions to be used by I2C/SPI drivers
> instances. For the moment only I2C driver is supported.
>
> Signed-off-by: Daniel Baluta
This looks good to me - al
On 15/04/16 15:13, Daniel Baluta wrote:
> Signed-off-by: Daniel Baluta
Looks good. I like regmap sometimes ;)
Applied to the togreg branch of iio.git - initially pushed out as
testing for the autobuilders to try spotting what we've missed.
Jonathan
> ---
> drivers/iio/magnetometer/Kconfig
Hi all,
I've hit the following while fuzzing with syzkaller inside a KVM tools guest
running the latest -next kernel:
[ 1912.231243]
==
[ 1912.231319] BUG: KASAN: use-after-free in free_vmap_area_noflush+0x106/0x210
at addr 88
On 14/04/16 15:41, Laxman Dewangan wrote:
> In some of platform, thermal sensors like NCT thermistors are
> connected to the one of ADC channel. The temperature is read by
> reading the voltage across the sensor resistance via ADC. Lookup
> table for ADC read value to temperature is referred to get
Hi all,
I've hit the following while fuzzing with syzkaller inside a KVM tools guest
running the latest -next kernel:
[ 1065.516003] BUG: Bad page map in process syz-executor pte:7025
pmd:1b5743067
[ 1065.516016] page:ea0001c0 count:1 mapcount:-1 mapping:
(null) index:0x0
On Sun, 17 Apr 2016, Joe Perches wrote:
> On Sun, 2016-04-17 at 07:43 +0200, Julia Lawall wrote:
> > On Sat, 16 Apr 2016, Joe Perches wrote:
> > > On Sat, 2016-04-16 at 12:04 -0700, Joe Perches wrote:
> > > > Add a test for use of ACCESS_ONCE that could be written using
> > > > READ_ONCE or WRIT
On 14/04/16 04:12, zengzhao...@163.com wrote:
> From: Zhaoxiu Zeng
>
> Signed-off-by: Zhaoxiu Zeng
Acked-by: Jonathan Cameron
I did ack the previous version and this seems unchanged,
so please do pick up those Acks and carry them with the
series and it makes it obvious when reviewers need to l
A suitably versatile semantic patch is below. Feel free to update
at
least the copyright line, and perhaps the initial explanation and the
strings printed in report and org modes.
julia
/// Use READ_ONCE or WRITE_ONCE instead of ACCESS_ONCE.
///
// Confidence: High
// Copyright: (C) 2016 Joe
On 13/04/16 20:01, Crestez Dan Leonard wrote:
> Device is an integrated gyro/accel/magn and temperature sensor. The
> device has two i2c/spi interfaces: one for the gyro and one for the
> accel/magn/temp sensor.
>
> Datasheet: http://www2.st.com/resource/en/datasheet/lsm9ds0.pdf
>
> The patch use
On Fri, Apr 15, 2016 at 06:20:15PM +, Wang Nan wrote:
> Create a new class named 'trigger' to model the state of a trigger and
> implement auxtrace_snapshot with it.
>
> auxtrace_record__snapshot_started and auxtrace_snapshot_err are absorbed.
>
> 'trigger' defines 4 state transitioning funct
On Fri, Apr 15, 2016 at 06:20:15PM +, Wang Nan wrote:
SNIP
> +
> +#define __TRIGGER_VAR(n) n##_state
> +#define __DEF_TRIGGER_VOID_FUNC(n, op) \
> +static inline void n##_##op(void) {trigger_##op(&__TRIGGER_VAR(n)); }
> +
> +#define __DEF_TRIGGER_FUNC(n, type, op) \
> +static inlin
On 06/04/16 11:31, Laxman Dewangan wrote:
> Some of kernel driver uses the IIO framework to get the sensor
> value via ADC or IIO HW driver. The client driver get iio channel
> by iio_channel_get() and release it by calling iio_channel_release().
>
> Add resource managed version (devm_*) of these
On Fri 15-04-16 11:25:26, Tejun Heo wrote:
> Hello,
Hi,
> On Fri, Apr 15, 2016 at 05:08:15PM +0200, Michal Hocko wrote:
[...]
> > Well it certainly is not that trivial because it relies on being
> > exclusive with global context. I will have to look closer of course but
> > I cannot guarantee I w
On 06/04/16 11:31, Laxman Dewangan wrote:
> Some of kernel driver uses the IIO framework to get the sensor
> value via ADC or IIO HW driver. The client driver get iio channel
> by iio_channel_get_all() and release it by calling
> iio_channel_release_all().
>
> Add resource managed version (devm_*)
On Fri 15-04-16 15:17:19, Tejun Heo wrote:
> mem_cgroup_move_charge() invokes lru_add_drain_all() so that the pvec
> pages can be moved too. lru_add_drain_all() schedules and flushes
> work items on system_wq which depends on being able to create new
> kworkers to make forward progress. Since 1ed
On Fri, Apr 15, 2016 at 06:28:31PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Apr 15, 2016 at 06:15:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> > > Hi all,
> > >
> > > After merging the tip tree, today's linux-next
On Fri, Apr 15, 2016 at 03:01:06PM -0700, Bjorn Andersson wrote:
> On Fri 15 Apr 11:59 PDT 2016, Stephen Boyd wrote:
>
> [..]
>
> > 8<-
> > From: Stephen Boyd
> > Subject: [PATCH] Input: pmic8xxx-pwrkey: Fix algorithm for converting
> > trigger
> > delay
> >
> > The trigger delay algo
> To bring you two up to date, we have effectively two separate devices
> (very nearly) sat behind a single i2c address. They have non overlapping
> register maps.
I think the MFD subsystem should have a few multifunction I2C devices
handled already. You migh get ideas there. Never needed it mys
Hi,
On Sun, Apr 17, 2016 at 09:14:08AM +0300, Ivaylo Dimitrov wrote:
> On 17.04.2016 03:05, Sebastian Reichel wrote:
> >On Sat, Apr 16, 2016 at 09:37:23AM +0300, Ivaylo Dimitrov wrote:
> >>Without that, regulators are left in the mode last set by the bootloader or
> >>by the kernel the device was
On Sun, 2016-04-17 at 01:34 +0200, Arnd Bergmann wrote:
> On Wednesday 13 April 2016 10:38:26 Johannes Berg wrote:
> >
> > >
> > > The patch was build-tested / debugged by removing the
> > > "if VERBOSE > SHOW_ERROR_MESSAGES" guards.
> > Stands to reason that we should just remove the (more or le
On Thu, Apr 14, 2016 at 09:17:33PM +0200, Boris Brezillon wrote:
> Call pwm_apply_args() just after requesting the PWM device so that the
> polarity and period are initialized according to the information provided
> in pwm_args.
>
> This is an intermediate state, and pwm_apply_args() should be dro
Hello Jens, hello block level and vm/mm developers,
I am still seeing this in kernel 4.5.
Bug 83561 - Suboptimal chainsaw behavior in copying between to SD cards
https://bugzilla.kernel.org/show_bug.cgi?id=83561
Its basically the same what happens when rsyncing onto an NFS mount when
the network
On Sun, Apr 17, 2016 at 02:12:07PM +0200, Jiri Olsa wrote:
> On Fri, Apr 15, 2016 at 06:28:31PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Apr 15, 2016 at 06:15:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> > > >
On Tuesday 12 April 2016 09:03:38 Rob Herring wrote:
> On Mon, Apr 11, 2016 at 01:11:46PM +0530, Nava kishore Manne wrote:
> > This patch updates the driver to support 64-bit DMA
> > addressing.
> >
> > Signed-off-by: Nava kishore Manne
> > ---
> > .../devicetree/bindings/usb/udc-xilinx.txt
On Sat, Apr 16, 2016 at 08:58:49PM -0400, Javier Martinez Canillas wrote:
> But regardless of the ABBA deadlock, there are reasons why the clk API is
> split into an {,un}prepare and {en,dis}able functions (e.g: non-atomic vs
> atomic) and it is a common pattern for drivers to prepare the clock(s)
On Sat, Apr 16, 2016 at 09:14:52PM -0400, Javier Martinez Canillas wrote:
> The clk_prepare_enable() function can fail so check the return value
> and propagate the error to the caller in case of a failure.
>
> Signed-off-by: Javier Martinez Canillas
> ---
>
> Changes in v2: None
>
> drivers/i
On Sat, Apr 16, 2016 at 09:14:53PM -0400, Javier Martinez Canillas wrote:
> The exynos5 I2C controller driver always prepares and enables a clock
> before using it and then disables unprepares it when the clock is not
> used anymore.
>
> But this can cause a possible ABBA deadlock in some scenario
clk_get_rate() takes a mutex, hence cannot be used while IRQ's been
disabled. Replace it with a locked version.
[3.430853] [] (dump_stack) from []
(__schedule_bug+0x50/0x64)
[3.431079] [] (__schedule_bug) from []
(__schedule+0x5c8/0x688)
[3.431453] [] (__schedule) from []
(schedule_
Hi Dan,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce
commit: 888cdbc2c9a76a0e450f533b1957cdbfe7d483d5 hugetlb: fix compile error on
tile
date: 3 months a
On Monday 11 April 2016 16:08:14 kbuild test robot wrote:
>
>230 * @offset: register offset
>231 * @val: data to be written
>232 **/
>233 static void xudc_write64(void __iomem *addr, u32 offset, u64 val)
>234 {
>235 #if defined(CONFIG_PHYS_ADDR_T_64BIT)
> > 236
Hello,
On (03/30/16 16:12), Minchan Kim wrote:
[..]
> +static int get_zspage_inuse(struct page *first_page)
> +{
> + struct zs_meta *m;
> +
> + VM_BUG_ON_PAGE(!is_first_page(first_page), first_page);
> +
> + m = (struct zs_meta *)&first_page->mapping;
..
> +static void set_zspage_inuse
Hello,
On (03/30/16 16:12), Minchan Kim wrote:
>
> Every zspage in a size_class has same number of max objects so
> we could move it to a size_class.
>
Reviewed-by: Sergey Senozhatsky
-ss
Fixed one coding style issue in the
file router_proc.c (Lustre staging driver)
Signed-off-by: Panos Vlachos
---
drivers/staging/lustre/lnet/lnet/router_proc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lnet/lnet/router_proc.c
b/drivers/staging/l
Hello,
On (03/30/16 16:12), Minchan Kim wrote:
> We don't use page->_mapcount any more so no need to reset.
>
> Signed-off-by: Minchan Kim
Reviewed-by: Sergey Senozhatsky
-ss
> ---
> mm/zsmalloc.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
On 2016-04-17 13:44, Jonathan Cameron wrote:
> On 13/04/16 20:01, Crestez Dan Leonard wrote:
>> Device is an integrated gyro/accel/magn and temperature sensor. The
>> device has two i2c/spi interfaces: one for the gyro and one for the
>> accel/magn/temp sensor.
>>
>> Datasheet: http://www2.st.com
Hello,
On (03/30/16 16:12), Minchan Kim wrote:
> For supporting migration from VM, we need to have address_space
> on every page so zsmalloc shouldn't use page->mapping. So,
> this patch moves zs_meta from mapping to freelist.
>
> Signed-off-by: Minchan Kim
a small get_zspage_meta() helper woul
Without that, regulators are left in the mode last set by the bootloader or
by the kernel the device was rebooted from. This leads to various problems,
like non-working peripherals.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 9 +
1 file changed, 9 insertions(+)
Ralf,
> > All errors (new ones prefixed by >>):
> >
> >{standard input}: Assembler messages:
> > >> {standard input}:136: Error: number (0x90008000) larger than 32
> > >> bits
> >{standard input}:161: Error: number (0x90008000) larger than 32
> > bits
>
> This is a tool
Hello,
On (03/30/16 16:12), Minchan Kim wrote:
[..]
> +static void objidx_to_page_and_offset(struct size_class *class,
> + struct page *first_page,
> + unsigned long obj_idx,
> + struct page **obj_page,
> +
Pozdravy a komplimenty.
Jsem Mr.Peter Wong pracuji s Bank of China Mám návrh podnikat v melodii US $
22.500.000 milionu, které mají být prevedeny na zahranicním úctu s vaší pomoc,
pokud chtejí.
V prípade zájmu Vám pošlu veškeré údaje o transakcích na obdržení odpovedi.
Mužete me kontaktovat n
On Sat, Apr 16, 2016 at 06:41:39PM -0400, Vivien Didelot wrote:
> There is no point in having a special case for the revision when probing
> a switch model. The code gets cluttered with unnecessary defines, and
> leads to errors when code such as mv88e6131_setup compares
> PORT_SWITCH_ID_6131_B2 to
On Sunday 10 April 2016 21:29:59 Robert Jarzmik wrote:
> +
> +DT_MACHINE_START(PXA_DT, "Marvell PXA3xx (Device Tree Support)")
> + .map_io = pxa3xx_map_io,
> + .init_irq = pxa3xx_dt_init_irq,
> + .handle_irq = pxa3xx_handle_irq,
> + .restart= pxa_re
On Sat, Apr 16, 2016 at 06:41:40PM -0400, Vivien Didelot wrote:
> Read the switch ID only once, at probe time, to avoid multiple read
> accesses and MII bus checking.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
Thanks
Andrew
> ---
> drivers/net/dsa/mv88e6xxx.c | 54
>
> @@ -3100,16 +3100,19 @@ char *mv88e6xxx_drv_probe(struct device *dsa_dev,
> struct device *host_dev,
> prod_num = (id & 0xfff0) >> 4;
> rev = id & 0x000f;
>
> - name = mv88e6xxx_lookup_name(id, table, num);
> - if (!name)
> + info = mv88e6xxx_lookup_info(prod_num, table
Hi Dmitry,
On Sun, 17 Apr 2016 05:45:48 -0700
Dmitry Torokhov wrote:
> On Thu, Apr 14, 2016 at 09:17:33PM +0200, Boris Brezillon wrote:
> > Call pwm_apply_args() just after requesting the PWM device so that the
> > polarity and period are initialized according to the information provided
> > in
Added one missing Haswell model.
Signed-off-by: Srinivas Pandruvada
---
arch/x86/events/intel/rapl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/events/intel/rapl.c b/arch/x86/events/intel/rapl.c
index 70c93f9..c83c141 100644
--- a/arch/x86/events/intel/rapl.c
+++ b/arch/x86/eve
Hi,
I have an i.MX6Q board with the current mainline tree from Linus and
systemd 229, which also acts as watchdog daemon.
(RuntimeWatchdogSec=60)
Since commit 11d7aba9ceb7 ("watchdog: imx2: Convert to use
infrastructure triggered keepalives") I get a kernel lockdep warning
after systemd launches.
On Sun, 2016-04-17 at 13:39 +0200, Julia Lawall wrote:
> A suitably versatile semantic patch is below. Feel free to update
> at least the copyright line, and perhaps the initial explanation
> and the strings printed in report and org modes.
Seems sensible enough, thanks Julia.
// Copyright: (C)
Greg,
Some time back I had sent a buch of patches for
Hyper-V drivers. Are they still in the queue or should I resend
them.
Regards,
K. Y
On Sunday 10 April 2016 17:43:52 Alexandre Belloni wrote:
> > > config RTC
> > > tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
> > > - depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
> > > - && !ARM && !SUPERH && !S390 && !A
On 16 April 2016 at 09:58, Boris Brezillon
wrote:
> On Fri, 15 Apr 2016 21:54:10 +0200
> Rafał Miłecki wrote:
>
>> Now we have all drivers properly setting this new field we can start
>> using it and proceed with deprecating NAND_ECC_SOFT_BCH.
>>
>> Signed-off-by: Rafał Miłecki
>> ---
>> driver
Hi Andrew,
Andrew Lunn writes:
>> @@ -3100,16 +3100,19 @@ char *mv88e6xxx_drv_probe(struct device *dsa_dev,
>> struct device *host_dev,
>> prod_num = (id & 0xfff0) >> 4;
>> rev = id & 0x000f;
>>
>> -name = mv88e6xxx_lookup_name(id, table, num);
>> -if (!name)
>> +info =
On Sun, 17 Apr 2016 18:27:40 +0200
Rafał Miłecki wrote:
> On 16 April 2016 at 09:58, Boris Brezillon
> wrote:
> > On Fri, 15 Apr 2016 21:54:10 +0200
> > Rafał Miłecki wrote:
> >
> >> Now we have all drivers properly setting this new field we can start
> >> using it and proceed with deprecating
On Sun, 17 Apr 2016 18:50:05 +0200
Boris Brezillon wrote:
> On Sun, 17 Apr 2016 18:27:40 +0200
> Rafał Miłecki wrote:
>
> > On 16 April 2016 at 09:58, Boris Brezillon
> > wrote:
> > > On Fri, 15 Apr 2016 21:54:10 +0200
> > > Rafał Miłecki wrote:
> > >
> > >> Now we have all drivers properly s
On 17 April 2016 at 18:50, Boris Brezillon
wrote:
> On Sun, 17 Apr 2016 18:27:40 +0200
> Rafał Miłecki wrote:
>
>> On 16 April 2016 at 09:58, Boris Brezillon
>> wrote:
>> > On Fri, 15 Apr 2016 21:54:10 +0200
>> > Rafał Miłecki wrote:
>> >
>> >> Now we have all drivers properly setting this new
Hi all,
I've hit the following while fuzzing with syzkaller inside a KVM tools guest
running the latest -next kernel:
[ 2590.845375]
==
[ 2590.845445] BUG: KASAN: use-after-free in pcpu_extend_area_map+0x8a/0x130 at
addr 88035
On Wed 13-04-16 14:49:43, Michal Hocko wrote:
> On Wed 13-04-16 12:27:31, Ingo Molnar wrote:
> >
> > * Ingo Molnar wrote:
> >
> > > I'm testing your patches today, if they are otherwise OK [...]
> >
> > got this build failure:
> >
> > ./arch/x86/include/asm/rwsem.h:106:2: error: ‘asm’ operan
On Sunday 17 April 2016 06:09 AM, Greg Kroah-Hartman wrote:
On Sun, Apr 17, 2016 at 02:12:47AM +0200, Arnd Bergmann wrote:
The patch to make uartlite_be/uartlite_le const was well-intended but
caused a new build warning:
tty/serial/uartlite.c: In function 'ulite_request_port':
tty/serial/uartli
On Sunday 17 April 2016 05:30 PM, Jonathan Cameron wrote:
On 06/04/16 11:31, Laxman Dewangan wrote:
Some of kernel driver uses the IIO framework to get the sensor
value via ADC or IIO HW driver. The client driver get iio channel
by iio_channel_get() and release it by calling iio_channel_release
On Fri, 15 Apr 2016 21:54:12 +0200
Rafał Miłecki wrote:
> This value should not be part of nand_ecc_modes_t as it specifies
> algorithm not a mode. We successfully managed to introduce new "algo"
> field which is respected now.
>
> Signed-off-by: Rafał Miłecki
> ---
> drivers/mtd/nand/fsmc_nan
On 17 April 2016 at 19:05, Boris Brezillon
wrote:
> On Fri, 15 Apr 2016 21:54:12 +0200
> Rafał Miłecki wrote:
>
>> This value should not be part of nand_ecc_modes_t as it specifies
>> algorithm not a mode. We successfully managed to introduce new "algo"
>> field which is respected now.
>>
>> Sign
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/davinci_nand.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/mtd/nand/davinci_nand.c b/drivers/mtd/
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
V2: Set algo to Hamming based on mode being SOFT. Add a comment how to
modify it if we ever need to.
---
drivers/mtd/nand/atmel_nand.c | 13 +
1 file chan
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/bf5xx_nand.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/nand/bf5xx_nand.c b/drivers/mtd/nand/bf5xx_nand.c
index b38f414..37da423 100
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/nand_base.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
index dd02c09..e1f3cf8 100644
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
This patch may be skipped if we apply
[PATCH 00/12] mtd: get rid of of_mtd.{c,h} and of_get_nand_xx()
patchset first.
---
drivers/mtd/nand/hisi504_nand.c | 1 +
1 file ch
Now we have all drivers properly setting this new field we can start
using it. For a very short period of time we should support both values:
NAND_ECC_SOFT and NAND_ECC_SOFT_BCH treating them the same. It's because
of_get_nand_ecc_mode may still be setting NAND_ECC_SOFT_BCH.
Signed-off-by: Rafał M
There isn't any difference between handling NAND_ECC_SOFT and
NAND_ECC_SOFT_BCH now. What matters is the new field called "algo".
Please note we're keeping backward DT compatibility. We are still
treating "soft_bch" value as the one setting Hamming algorithm, it's
just handled in of_get_nand_ecc_al
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
drivers/staging/mt29f_spinand/mt29f_spinand.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/mt29f_spinand/mt29f_spinand.c
b/drivers/staging/mt29f_s
NAND core sets ECC algorithm in algo field now and it should be
preferred over the mode field. This also prepares driver for dropping
NAND_ECC_SOFT_BCH.
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/fsmc_nand.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/driver
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
arch/cris/arch-v32/drivers/mach-a3/nandflash.c | 1 +
arch/cris/arch-v32/drivers/mach-fs/nandflash.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/cris/arch-
This value should not be part of nand_ecc_modes_t as it specifies
algorithm not a mode. We successfully managed to introduce new "algo"
field which is respected now.
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/fsmc_nand.c | 3 +--
drivers/mtd/nand/jz4780_nand.c | 1 -
drivers/mtd/nand/
Drop the ps->num_ports variable in favor of a new member of the info
structure. This removes the need to assign it at setup time.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6123.c | 16 +++-
drivers/net/dsa/mv88e6131.c | 22 +-
ps->id is not needed anymore, so remove it as well as the related
defined values.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6xxx.c | 1 -
drivers/net/dsa/mv88e6xxx.h | 32
2 files changed, 33 deletions(-)
diff --git a/driv
Change the dsa_switch_driver.probe function to return a const char *.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/bcm_sf2.c | 6 +++---
drivers/net/dsa/mv88e6060.c | 10 +-
drivers/net/dsa/mv88e6123.c | 6 +++---
drivers/net/dsa/mv88e6131.c | 6 +++---
drivers/net/dsa/mv88e617
Add a new switch info structure which is meant to store switch models
static information, such as product number, name, number of ports,
number of databases, etc.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6123.c | 15 +++
drivers/net/dsa/mv88e6131.c | 19 ++--
This patchset factorizes the mv88e6xxx code by sharing a new extendable
info structure to store static data such as switch family, product
number, number of ports, number of databases and the name.
The next step is to add a "flags" bitmap member to the info structure in
order to simplify the share
Add an mv88e6xxx_family enum to the info structure for better family
indentification.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6123.c | 3 ++
drivers/net/dsa/mv88e6131.c | 4 +++
drivers/net/dsa/mv88e6171.c | 4 +++
drivers/net/dsa/mv88e6352.c | 6
Every driver assigns ps->ds even though it gets assigned in the shared
mv88e6xxx_setup_common function. Kill redundancy.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6123.c | 2 --
drivers/net/dsa/mv88e6131.c | 2 --
drivers/net/dsa/mv88e6171.c | 2 --
drivers
1 - 100 of 619 matches
Mail list logo
