Hello,
Thanks for your feedback!
On Wed, 14 Oct 2015 11:21:38 -0700, Stephen Boyd wrote:
> > Stephen, what do you suggest to fix this issue?
>
> Simplest fix is to revert this hunk.
Indeed, this is the simplest fix. But it's going backward with what you
were trying to do originally, so it
On Wednesday 14 October 2015 12:46:19 Scott Branden wrote:
> >
> > My patch fixes it by always selecting COMMON_CLK_IPROC from
> > ARCH_BCM_CYGNUS. I wasn't sure whether you want COMMON_CLK_IPROC
> > to still be user-selectable, so I left that in place. Normally
> > I'd expect it to be a silent
On Wed, 2015-10-14 at 12:20 -0400, shrybman wrote:
> All 3.4-rc kernels I have tried displayed this issue.
> This report looks similar https://lkml.org/lkml/2015/9/26/165.
> I also have a Core 2 cpu on a Asus P5B (not deluxe) board.
> ...
> ACPI: Core revision 20150818
> ACPI: 1 ACPI AML
Before, we were opening and closing a mc_io's dpmcp object
in fsl_mc_portal_reset(), since that was the only function that was
calling dpmcp MC operations. However, it is better for maintainability
to open the dpmcp object when it gets associated with an mc_io object,
and close it when this
mc_adev is a local variable for the allocated dpmcp object.
Renamed mc_adev as dpmcp_dev for clarity.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-allocator.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
Changed these two fields from 32-bit integers to 16-bit integers in
struct fsl_mc_io, as 32 bits is too much for these fields. This
change does not affect other components since fsl_mc_io is an opaque
type.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/include/mc-sys.h | 4 ++--
Each fsl_mc_io object is associated with an fsl_mc_device object
of type "dpmcp" representing the MC portal associated with the
fsl_mc_io object. Before, we were representing this association with
an fsl_mc_resource pointer. To enhance code clarity, it is more
straight forward to use an
Whitespace cleanup-- add missing spaces in column 1 of copyright
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/include/dpcon-cmd.h | 60 +++---
1 file changed, 30 insertions(+), 30 deletions(-)
diff --git a/drivers/staging/fsl-mc/include/dpcon-cmd.h
The macros were a left-over from a previous implementation
of the dpmcp APIs and are no longer used.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/dpmcp-cmd.h | 79 --
1 file changed, 79 deletions(-)
diff --git
This patch series includes the following code cleanup and
bug fixes for the fsl-mc bus driver:
Patch 1: Naming cleanup in fsl_mc-portal_allocate
Patch 2: fsl_mc_io object refactoring
Patch 3: dpmcp opening/closing refactoring
Patch 4: Changed dev_info() calls to dev_dbg()
Patch 5: Changed types
Call fsl_mc_resource_pool_remove_device() only if mc_dev->resource
is not NULL.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-allocator.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/fsl-mc/bus/mc-allocator.c
Hi Chen,
[auto build test ERROR on tip/x86/core -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
owner needs to be initialized as THIS_MOUDLE.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-bus.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/fsl-mc/bus/mc-bus.c
b/drivers/staging/fsl-mc/bus/mc-bus.c
index 4ac3d07..84db55b 100644
---
Check that resource is not NULL before de-referencing it.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-allocator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fsl-mc/bus/mc-allocator.c
b/drivers/staging/fsl-mc/bus/mc-allocator.c
On Wed, Oct 14, 2015 at 12:38 PM, Tejun Heo wrote:
>
> Doesn't seem that way. This is from 597d0275736d^ - right before
> TIMER_NOT_PINNED is introduced. add_timer() eventually calls into
> __mod_timer().
>
> if (likely(base->running_timer != timer)) {
>
This patch introduces the MACH_STM32F429 to make possible to only select
STM32F429 pinctrl driver.
By default, all the MACH_STM32Fxxx flags will be set with STM32 defconfig.
Signed-off-by: Maxime Coquelin
---
arch/arm/Kconfig | 5 +
1 file changed, 5 insertions(+)
diff --git
Signed-off-by: Maxime Coquelin
---
.../bindings/pinctrl/st,stm32-pinctrl.txt | 113 +
1 file changed, 113 insertions(+)
create mode 100644
Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
diff --git
This patch selects USART1 pin configuration on PA9/PA10 pins
for both Eval and Disco boards.
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stm32429i-eval.dts | 2 ++
arch/arm/boot/dts/stm32f429-disco.dts | 2 ++
arch/arm/boot/dts/stm32f429.dtsi | 13 +
3 files
The STM32F429 MCU has 11 GPIO banks, with 16 pins per bank.
Signed-off-by: Maxime Coquelin
---
arch/arm/boot/dts/stm32f429.dtsi | 97
1 file changed, 97 insertions(+)
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index
This patch adds pinctrl and GPIO support to STMicroelectronic's STM32
family of MCUs.
While it only supports STM32F429 for now, it has been designed to enable
support of other MCUs of the family (e.g. STM32F746).
Signed-off-by: Maxime Coquelin
---
drivers/pinctrl/Kconfig |
Signed-off-by: Maxime Coquelin
---
arch/arm/Kconfig | 1 +
drivers/pinctrl/stm32/pinctrl-stm32f429.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index bf94e54..8b1afd4 100644
--- a/arch/arm/Kconfig
+++
On 10/14, Peter Zijlstra wrote:
>
> On Mon, Oct 12, 2015 at 07:34:02PM +0200, Oleg Nesterov wrote:
> >
> > I simply can't understand... To me it looks as if we can simply remove
> > the cpu_active() check in select_fallback_rq().
> >
> > If we race with cpu_down(), cpu_active() is cleared by
Hi Linus, all,
As you suggested during the submission of the STM32 machine support,
I reworked the STM32 pinctrl driver to use the standardized pin config
bindings.
The STM32 family has 16 pins per GPIO bank, and the number of bank varies
depending on the model.
Pins can be multiplexed either
Signed-off-by: Maxime Coquelin
---
include/dt-bindings/pinctrl/pinctrl-stm32.h | 12 +
include/dt-bindings/pinctrl/stm32f429-pinfunc.h | 1241 +++
2 files changed, 1253 insertions(+)
create mode 100644 include/dt-bindings/pinctrl/pinctrl-stm32.h
create mode 100644
Replaced error gotos with direct returns in fsl_mc_allocator_probe()
and fsl_mc_allocator_remove(), since the only error handling done
in those functions is to exit.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-allocator.c | 23
When initializing the object attributes for the root dprc, the
irq_count was uninitialized. Initialize it to 1.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-bus.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/fsl-mc/bus/mc-bus.c
Changed dev_info() calls to dev_dbg() in
fsl_mc_allocator_probe/fsl_mc_allocator_remove, as they
are useful only for debugging.
---
CHANGE HISTORY
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-allocator.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On 10/14/2015 01:13 PM, Tony Lindgren wrote:
> * Franklin S Cooper Jr. [151014 09:27]:
>>
>> On 10/14/2015 11:18 AM, Tony Lindgren wrote:
>>> * Franklin S Cooper Jr. [151014 07:37]:
On 10/14/2015 09:11 AM, Roger Quadros wrote:
> On 14/10/15 16:26, Franklin S Cooper Jr. wrote:
>>
On 15-10-13 03:23 PM, Arnd Bergmann wrote:
On Tuesday 13 October 2015 18:04:50 Jon Mason wrote:
On a related note, I'm seeing problems when CONFIG_CYGNUS is set but
CONFIG_COMMON_CLK_IPROC is disabled, as that currently leads to a link
failure.
I can double check, but it should be on by
Hi LABBE,
[auto build test ERROR on pm/linux-next -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/LABBE-Corentin/acpi-set-return-value-to-const-char-for-some-functions/20151015-030935
config:
On Wed, Oct 14, 2015 at 09:49:24AM +0800, Tan Xiaojun wrote:
> debugfs_remove is used to remove a file or an empty directory from
> the debugfs filesystem, but mci->debugfs is not empty.
>
> This is not easily discovered, because debugfs_remove return nothing
> when failed. It can be test like
Hi Jon,
Yes, please only add SoC part number compatible strings, not board
compatible strings.
On 15-10-14 08:34 AM, Jon Mason wrote:
On Tue, Oct 13, 2015 at 03:37:49PM -0700, Florian Fainelli wrote:
On 13/10/15 14:40, Jon Mason wrote:
On Sat, Oct 10, 2015 at 04:42:04PM +0200, Hauke
>
> On Fri, Oct 09, 2015 at 06:31:23PM +, Liang, Kan wrote:
>
> SNIP
>
> > > could not reproduce this one.. any chance you could compile with
> > > DEBUG=1 and re-run in gdb for more details? like which of the frees
> > > got crazy.. ?
> > >
> > The crash is not caused by this patch set.
Hi Chen,
[auto build test ERROR on tip/x86/core -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
On 10/14/2015 09:08 PM, Javier Martinez Canillas wrote:
> Hello Stephen,
>
> On 10/14/2015 08:38 PM, Stephen Boyd wrote:
>> On 10/13, Javier Martinez Canillas wrote:
>>> diff --git a/drivers/clk/versatile/Kconfig b/drivers/clk/versatile/Kconfig
>>> index 1530c9352a76..fc50b6264bed 100644
>>> ---
Hello, Linus.
On Wed, Oct 14, 2015 at 12:16:48PM -0700, Linus Torvalds wrote:
> On Wed, Oct 14, 2015 at 12:02 PM, Tejun Heo wrote:
> >
> > But wasn't add_timer() always CPU-local at the time? add_timer()
> > allowing cross-cpu migrations came way after that.
>
> add_timer() has actually never
Hi,
On Wed, Oct 14, 2015 at 07:36:37PM +0530, Sakshi Bansal wrote:
> Fixed allignment issues and line over 80 characters
You are also doing many other things which are not mention in the
commit log.
> /*
> - printk_ratelimited("Port %d
Hi,Javi
> -Original Message-
> From: Javi Merino [mailto:javi.mer...@arm.com]
> Sent: Thursday, October 15, 2015 1:08 AM
> To: Chen, Yu C
> Cc: linux...@vger.kernel.org; edubez...@gmail.com; Zhang, Rui; linux-
> ker...@vger.kernel.org; sta...@vger.kernel.org; Pandruvada, Srinivas
>
* Mark Jackson [151014 06:35]:
> Add USB hooks into NanoBone DTS file
Hmm looking at things, we really should not set status = "disabled"
for any of the internal devices. Setting "disabled" makes the kernel
completely ignore the device and we're better off from PM point of
view to probe and idle
The implementation for Open-Channel SSDs is divided into media
management and targets. This patch implements a generic media manager
for open-channel SSDs. After a media manager has been initialized,
single or multiple targets can be instantiated with the media managed as
the backend.
This target allows an Open-Channel SSD to be exposed asas a block
device.
It implements a round-robin approach for sector allocation,
together with a greedy cost-based garbage collector.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/Kconfig |7 +
drivers/lightnvm/Makefile |1 +
This driver implements the I/O flow for a LightNVM device driver. It
does no transfers. It can be used to test setup/teardown of devices and
evaluating performance of media managers and targets.
The framework of the driver is derived from the null_blk module.
Signed-off-by: Matias Bjørling
---
This patchset implements support for Open-Channel SSDs.
Applies against Jens' for-next and is available through the lkml_v10 branch at:
https://github.com/OpenChannelSSD/linux
Sorry, missed the patch for nvme_nvm_unregister prototype definition update.
Changes since v9:
- Fix compilation of
The first generation of Open-Channel SSDs is based on NVMe. The
integration requires that a NVMe device register itself as a LightNVM
device.
Detection is made through PCI IDs. Current supported devices are the
qemu nvme simulator and CNEX Labs Westlake SSD. The qemu nvme enables
support through
Open-channel SSDs are devices that share responsibilities with the host
in order to implement and maintain features that typical SSDs keep
strictly in firmware. These include (i) the Flash Translation Layer
(FTL), (ii) bad block management, and (iii) hardware units such as the
flash controller,
Hi Javi,
> -Original Message-
> From: Javi Merino [mailto:javi.mer...@arm.com]
> Sent: Thursday, October 15, 2015 1:08 AM
> To: Chen, Yu C
> Cc: linux...@vger.kernel.org; edubez...@gmail.com; Zhang, Rui; linux-
> ker...@vger.kernel.org; sta...@vger.kernel.org; Pandruvada, Srinivas
>
Some array of const char are not set as const.
This patch fix that.
Signed-off-by: LABBE Corentin
---
drivers/ata/pata_it821x.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/ata/pata_it821x.c b/drivers/ata/pata_it821x.c
index a5088ec..7a21edf 100644
---
On Wed, Oct 14, 2015 at 12:02 PM, Tejun Heo wrote:
>
> But wasn't add_timer() always CPU-local at the time? add_timer()
> allowing cross-cpu migrations came way after that.
add_timer() has actually never been "local CPU only" either.
What add_timer() does is to keep the timer on the old CPU
The sha x86 crypto code use two define for the same thing:
NUM_SHA1_DIGEST_WORDS and SHA1_DIGEST_LENGTH
Replace them by SHA1_DIGEST_SIZE/4
Signed-off-by: LABBE Corentin
---
arch/x86/crypto/sha-mb/sha1_mb.c| 2 +-
arch/x86/crypto/sha-mb/sha_mb_ctx.h | 1 -
arch/x86/crypto/sha-mb/sha_mb_mgr.h
On 10/14/2015 10:57 AM, Rob Herring wrote:
On Wed, Oct 14, 2015 at 9:48 AM, Daniel Walker wrote:
There's one last little wrinkle .. In the current setup the defconfig
CONFIG_CMDLINE="" is used as a default in case the device tree has nothing
in it. In my changes, there is no identical
Some array of const char are not set as const.
This patch fix that.
Signed-off-by: LABBE Corentin
---
drivers/crypto/n2_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/n2_core.c b/drivers/crypto/n2_core.c
index 8ea6c32..febbd5e 100644
---
Some array of const char are not set as const.
This patch fix that.
Signed-off-by: LABBE Corentin
---
drivers/crypto/sahara.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/crypto/sahara.c b/drivers/crypto/sahara.c
index 804c0f5..f68c24a 100644
---
The define SHA1_DIGEST_LENGTH is not used anywhere, so remove it.
Signed-off-by: LABBE Corentin
---
include/linux/mpi.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/include/linux/mpi.h b/include/linux/mpi.h
index 641b7d6..a792b38 100644
--- a/include/linux/mpi.h
+++
Arnd Bergmann writes:
> On Monday 12 October 2015 19:03:44 Robert Jarzmik wrote:
>> Arnd Bergmann writes:
>>
>> > Some recently added code to avoid a bug introduced a build error
>> > when CONFIG_PM is disabled and a macro is hidden:
>> >
>> > arch/arm/mach-pxa/pxa3xx.c: In function
SHA_MAX_STATE_SIZE is just the number of u32 word for SHA512.
So replace the raw value "16" by their meaning (SHA512_DIGEST_SIZE / 4)
Signed-off-by: LABBE Corentin
---
arch/s390/crypto/sha.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/s390/crypto/sha.h
On Wed, Oct 14, 2015 at 11:59 AM, Christoph Lameter wrote:
> On Wed, 14 Oct 2015, Linus Torvalds wrote:
>
>> And "schedule_delayed_work()" uses WORK_CPU_UNBOUND.
>
> Uhhh. Someone changed that?
It always did. This is from 2007:
int fastcall schedule_delayed_work(struct delayed_work *dwork,
It was found while running a database workload on large systems that
significant time was spent trying to acquire the sighand lock.
The issue was that whenever an itimer expired, many threads ended up
simultaneously trying to send the signal. Most of the time, nothing
happened after acquiring the
Hello Stephen,
On 10/14/2015 08:38 PM, Stephen Boyd wrote:
> On 10/13, Javier Martinez Canillas wrote:
>> diff --git a/drivers/clk/versatile/Kconfig b/drivers/clk/versatile/Kconfig
>> index 1530c9352a76..fc50b6264bed 100644
>> --- a/drivers/clk/versatile/Kconfig
>> +++
In the next patch in this series, a new field 'checking_timer' will
be added to 'struct thread_group_cputimer'. Both this and the
existing 'running' integer field are just used as boolean values. To
save space in the structure, we can make both of these fields booleans.
This is a preparatory
The fastpath_timer_check() contains logic to check for if any timers
are set by checking if !task_cputime_zero(). Similarly, we can do this
before calling check_thread_timers(). In the case where there
are only process-wide timers, this will skip all of the computations for
per-thread timers when
While running a database workload on a 16 socket machine, there were
scalability issues related to itimers. The following link contains a
more detailed summary of the issues at the application level.
https://lkml.org/lkml/2015/8/26/737
Commit 1018016c706f addressed the issue with the
On 10/14, Peter Zijlstra wrote:
>
> On Thu, Oct 08, 2015 at 04:51:31PM +0200, Oleg Nesterov wrote:
> > cpu_stop_queue_work() checks stopper->enabled before it queues the
> > work, but ->enabled == T can only guarantee cpu_stop_signal_done()
> > if we race with cpu_down().
> >
> > This is not
In fastpath_timer_check(), the task_cputime() function is always
called to compute the utime and stime values. However, this is not
necessary if there are no per-thread timers to check for. This patch
modifies the code such that we compute the task_cputime values only
when there are per-thread
This patch set some array of const char as const.
In the same time, some function return pointer to thoses array without
properly giving the information that the data is const.
This patch set the return type of thoses functions as const char *
Signed-off-by: LABBE Corentin
---
Hello, Linus.
On Wed, Oct 14, 2015 at 10:36:50AM -0700, Linus Torvalds wrote:
> > For both delayed and !delayed work items on per-cpu workqueues,
> > queueing without specifying a specific CPU always meant queueing on
> > the local CPU.
>
> That's just not true, as far as I can tell.
>
> I went
On Wed, Oct 14, 2015 at 11:37 AM, Linus Torvalds
wrote:
>
> Yes, yes, it so _happens_ that "add_timer()" preferentially uses the
> current CPU etc, so in practice it may have happened to work. But
> there's absolutely zero reason to think it should always work that
> way.
Side note: even in
On Wed, 14 Oct 2015, Linus Torvalds wrote:
> And "schedule_delayed_work()" uses WORK_CPU_UNBOUND.
Uhhh. Someone changed that?
> In this email you seem to even agree that its' bogus, but then you
> wrote another email saying that the code isn't confused, because it
> uses
On Wed, 14 Oct 2015, Linus Torvalds wrote:
> On Wed, Oct 14, 2015 at 10:57 AM, Christoph Lameter wrote:
> >
> > Well yes the schedule_delayed_work_on() call is from another cpu and the
> > schedule_delayed_work() from the same. No confusion there.
>
> So "schedule_delayed_work()" does *not*
On some platforms, there is occasional panic triggered when trying to
resume from hibernation, a typical panic looks like:
"BUG: unable to handle kernel paging request at 880085894000
IP: [] load_image_lzo+0x8c2/0xe70"
This is because e820 map has been changed by BIOS before/after
This reverts commit bb304a5c6fc63d8506cd9741a3a5f35b73605625.
Because this patch leads to kthread zombies.
call_usermodehelper_exec_sync() does fork() + wait() with "unignored"
SIGCHLD. What we have missed is that this worker thread can have other
children previously forked by
Hello,
I noticed by accident the kworker zombies on my testing machine.
Can't reproduce (although I think it won't be hard to make a
test-case), but I think the reason is clear, see the changelog.
We could fix this by using kthread_create() if !UMH_WAIT_PROC,
but imo it would be better to revert
These drivers have depends that aren't build dependencies, so it's
a good idea to allow these drivers to always be built when the
COMPILE_TEST option is enabled.
That way, the drivers can be built with a config generated by make
allyesconfig and check if a patch would break the build.
On Wed, 2015-10-14 at 11:34 -0700, Lee Duncan wrote:
> On 10/14/2015 06:55 AM, James Bottomley wrote:
> > On Wed, 2015-10-07 at 16:51 -0700, Lee Duncan wrote:
> >> Update the SCSI hosts module to use the ida_simple*() routines
> >> to manage its host_no index instead of an ATOMIC integer. This
>
On Wed, Oct 14, 2015 at 11:34 AM, Stas Sergeev wrote:
> 14.10.2015 21:06, Andy Lutomirski пишет:
>>> Also it doesn't seem to be saying what happens if CS is 32-bit
>>> and SS is invalid (the flag is not set).
>>
>> A new signal will be delivered. sigreturn doesn't modify its behavior
>> in this
On 10/09, Viresh Kumar wrote:
> +struct dentry *debugfs_create_xlong(const char *name, umode_t mode,
> + struct dentry *parent, unsigned long *value)
> +{
> + return debugfs_create_file(name, mode, parent, value, _xlong);
Were you going to refresh this on my
On 13/10/15 09:46, Vivien Didelot wrote:
> No driver implements port_fdb_getnext anymore, and port_fdb_dump is
> preferred anyway, so remove this function from DSA.
>
> Signed-off-by: Vivien Didelot
Acked-by: Florian Fainelli
--
Florian
--
To unsubscribe from this list: send the line
On 13/10/15 09:46, Vivien Didelot wrote:
> Not all switch chips support a Get Next operation to iterate on its FDB.
> So add a more simple port_fdb_dump function for them.
>
> Signed-off-by: Vivien Didelot
Acked-by: Florian Fainelli
--
Florian
--
To unsubscribe from this list: send the line
While plugging / unplugging on a DWC2 host port with "slub_debug=FZPUA"
enabled, I found a crash that was quite obviously a use after free.
It appears that in some cases when we handle the various sub-cases of
HCINT we may end up freeing the QTD. If there is more than one bit set
in HCINT we may
This driver only has runtime but no build time dependencies, so it can be
built for testing purposes if the Kconfig COMPILE_TEST option is enabled.
This is useful to have more build coverage and make sure that drivers are
not affected by changes that could cause build regressions.
Signed-off-by:
On Wed, Oct 14, 2015 at 11:03 AM, Christoph Lameter wrote:
> On Wed, 14 Oct 2015, Linus Torvalds wrote:
>>
>> So why is this a bugfix? If cpu == WORK_CPU_UNBOUND, then things
>> _shouldn't_ care which cpu it gets run on.
>
> UNBOUND means not fixed to a processor.
That's exactly what I'm saying.
On 10/13, Javier Martinez Canillas wrote:
> diff --git a/drivers/clk/versatile/Kconfig b/drivers/clk/versatile/Kconfig
> index 1530c9352a76..fc50b6264bed 100644
> --- a/drivers/clk/versatile/Kconfig
> +++ b/drivers/clk/versatile/Kconfig
> @@ -1,6 +1,6 @@
> config COMMON_CLK_VERSATILE
> bool
On Wed, Oct 14, 2015 at 10:57 AM, Christoph Lameter wrote:
>
> Well yes the schedule_delayed_work_on() call is from another cpu and the
> schedule_delayed_work() from the same. No confusion there.
So "schedule_delayed_work()" does *not* guarantee that the work will
run on the same CPU.
Yes,
Hi Matias,
[auto build test ERROR on block/for-next -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Matias-Bj-rling/Support-for-Open-Channel-SSDs/20151014-224617
config: mips-allyesconfig (attached
14.10.2015 21:06, Andy Lutomirski пишет:
>> Also it doesn't seem to be saying what happens if CS is 32-bit
>> and SS is invalid (the flag is not set).
>
> A new signal will be delivered. sigreturn doesn't modify its behavior
> in this case -- it does the default thing, which is to honor the SS
On 10/14/2015 06:55 AM, James Bottomley wrote:
> On Wed, 2015-10-07 at 16:51 -0700, Lee Duncan wrote:
>> Update the SCSI hosts module to use the ida_simple*() routines
>> to manage its host_no index instead of an ATOMIC integer. This
>> means that the SCSI host number will now be reclaimable.
>
>
On 10/14, Tomeu Vizoso wrote:
> When the DISP1 power domain is powered off, there's two clocks that need
> to be temporarily reparented to OSC, and back to their original parents
> when the domain is powered on again.
>
> We expose these two clocks in the DT bindings so that the DT node of the
>
Fix obvious mistake: FS/GS should be DS/ES.
Signed-off-by: Chuck Ebbert
diff --git a/arch/x86/kernel/process_64.c b/arch/x86/kernel/process_64.c
index d7f1d5c..e835d26 100644
--- a/arch/x86/kernel/process_64.c
+++ b/arch/x86/kernel/process_64.c
@@ -332,7 +332,7 @@ __switch_to(struct task_struct
On 10/14, Javier Martinez Canillas wrote:
> The email address listed in MODULE_AUTHOR() no longer exist so to prevent
> people to send emails to the old address, replace it with my current one.
>
> Signed-off-by: Javier Martinez Canillas
>
> ---
Applied to clk-next
--
Qualcomm Innovation
Hi Luis,
[auto build test ERROR on thermal/next -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Luis-de-Bethencourt/thermal-kconfig-When-possible-compile-drivers-with-COMPILE_TEST/20151015-001830
config:
This patch is to the rtl871x_ioctl_linux.c file that fixes up following
warnings reported by checkpatch.pl :
-Block comments use * on subsequent lines
-Block comments use a trailing */ on a separate line
Signed-off-by: Punit Vara
---
drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 26
This patch is to the rtl871x_ioctl_linux.c file that fixes up following
warning reported by checkpatch.pl :
-Prefer ether_addr_equal() or ether_addr_equal_unaligned() over memcmp()
bssid and pnetwork->network.MacAddress both are 6 byte
array which aligned with u16
Signed-off-by: Punit Vara
---
Put constant on the right side of a test.Problem found using checkpatch:
Warning:Comparisons should place the constant on the right side of the test
Signed-off-by: Punit Vara
---
drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 16
1 file changed, 8 insertions(+), 8
This patch is to the rtl871x_ioctl_linux.c that fixes up following
warning by checkpatch.pl:
-Prefer eth_broadcast_addr() over memset()
Signed-off-by: Punit Vara
---
drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
This set of patch fixes following warnings reported by checkpatch.pl:
-Prefer eth_broadcast_addr() over memset()
-Prefer ether_addr_equal() or ether_addr_equal_unaligned() over memcmp()
-Block comments use * on subsequent lines
-Block comments use a trailing */ on a separate line
-Comparisons
On Wed, Oct 14, 2015 at 10:33 AM, Sören Brinkmann
wrote:
> On Wed, 2015-10-14 at 07:24PM +0200, Lars-Peter Clausen wrote:
>> On 10/14/2015 06:54 PM, Sören Brinkmann wrote:
>> > On Wed, 2015-10-14 at 05:57PM +0200, Lars-Peter Clausen wrote:
>> >> On 10/14/2015 05:18 PM, Sören Brinkmann wrote:
>>
On 10/14, Thomas Petazzoni wrote:
> On Fri, 31 Jul 2015 10:03:54 -0700, Stephen Boyd wrote:
> > @@ -209,9 +208,8 @@ static void __init of_cpu_clk_setup(struct device_node
> > *node)
> > goto bail_out;
> >
> > sprintf(clk_name, "cpu%d", cpu);
> > -
On Wed, Oct 14, 2015 at 08:45:56AM -0700, James Bottomley wrote:
> OK, so I really need you to separate the problems. Fixing the bug
> you're reporting does not require a complete rework of the locking
> infrastructure; it just requires replacing the traversal macro with the
> safe version, can
* Franklin S Cooper Jr. [151014 09:27]:
>
>
> On 10/14/2015 11:18 AM, Tony Lindgren wrote:
> > * Franklin S Cooper Jr. [151014 07:37]:
> >>
> >> On 10/14/2015 09:11 AM, Roger Quadros wrote:
> >>> On 14/10/15 16:26, Franklin S Cooper Jr. wrote:
> On 10/14/2015 06:52 AM, Roger Quadros
On Wed, Oct 14, 2015 at 07:38:22PM +0530, Sakshi Bansal wrote:
> Fixed allignmnet issues and block comments usage
>
Split it apart by type of fix.
> @@ -617,7 +618,7 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
> } else {
> nvec->rx =
On Wed, Oct 14, 2015 at 10:40 AM, Stas Sergeev wrote:
> 14.10.2015 19:40, Andy Lutomirski пишет:
+ *
+ * Kernels that set UC_SIGCONTEXT_SS will also set UC_STRICT_RESTORE_SS
+ * when delivering a signal that came from 64-bit code.
+ *
+ * Sigreturn modifies its behavior
301 - 400 of 2330 matches
Mail list logo
