On 21/07/15 17:38, Stefan Wahren wrote:
Hi Srinivas,
Srinivas Kandagatla hat am 20. Juli 2015 um
16:44 geschrieben:
From: Maxime Ripard
Now that we have the nvmem framework, we can consolidate the common
driver code. Move the driver to the framework, and hopefully, it will
fix the sysfs
The `cmdtest` and `cmd` handlers for the AO subdevice
(`usbduxsigma_ao_cmdtest()` and `usbduxsigma_ao_cmd()`) support "scan"
timing of commands with all channels updated every "scan" period. There
is some disabled code to use "convert" timing in high speed mode. That
would allow channels to be
On 23/07/15 16:26, Stefan Wahren wrote:
Hi Srinivas,
Am 20.07.2015 um 16:43 schrieb Srinivas Kandagatla:
This patch adds just providers part of the framework just to enable easy
review.
Up until now, NVMEM drivers like eeprom were stored in drivers/misc,
where they all had to duplicate
On 23/07/15 16:18, Stefan Wahren wrote:
Hi Srinivas,
Am 20.07.2015 um 16:44 schrieb Srinivas Kandagatla:
From: Maxime Ripard
Now that we have the nvmem framework, we can consolidate the common
driver code. Move the driver to the framework, and hopefully, it will
fix the sysfs file creation
On Tue, 21 Jul 2015, Vaibhav Hiremath wrote:
> This patch adds mfd_cell/clk-subdevice for 88PM800 MFD
> (and family of devices).
>
> Signed-off-by: Vaibhav Hiremath
> ---
> drivers/mfd/88pm800.c | 25 +
> 1 file changed, 25 insertions(+)
>
> diff --git
Fix some minor problems in the testing of asynchronous commands for the AI
and AO subdevices and remove some redundant code.
The main problem is that the testing of a new command can affect the
operation of an already running command, which it isn't supposed to do. (In
practice, applications
The return value of the `cmdtest` handler for a subdevice checks the
prospective new command in various steps and returns the step number at
which any problem was detected, or 0 if no problem was detected. It is
allowed to modify the command in various ways at each step. Corrections
for
The return value of the `cmdtest` handler for a subdevice checks the
prospective new command in various steps and returns the step number at
which any problem was detected, or 0 if no problem was detected. It is
allowed to modify the command in various ways at each step. Corrections
for
From: Colin Ian King
static analysis by cppcheck has found a check on alloc_bitset that
always evaluates as false and hence never finds an allocation failure:
[drivers/md/dm-cache-policy-smq.c:1689]: (warning) Logical conjunction
always evaluates to false: !EXPR && EXPR.
Fix this by removing
The AI subdevice `cmdtest` handler `usbduxsigma_ai_cmdtest()` ensures
that `cmd->scan_begin_src == TRIG_TIMER` by the end of step 2 of the
command checking code, so assume that this is the case for step 3
onwards and remove the redundant code.
Signed-off-by: Ian Abbott
---
`devpriv->ai_timer` is used while an asynchronous command is running on
the AI subdevice. It also gets modified by the subdevice's `cmdtest`
handler for checking new asynchronous commands
(`usbduxsigma_ai_cmdtest()`), which is not correct as it's allowed to
check new commands while an old command
`devpriv->ao_timer` is used while an asynchronous command is running on
the AO subdevice. It also gets modified by the subdevice's `cmdtest`
handler for checking new asynchronous commands,
`usbduxsigma_ao_cmdtest()`, which is not correct as it's allowed to
check new commands while an old command
On Tue, Jul 21, 2015 at 2:55 AM, Peter Zijlstra wrote:
> On Mon, Jul 20, 2015 at 11:49:06AM -0400, Kan Liang wrote:
>> +static void freq_event_update(struct perf_event *event)
>> +{
>> + u64 prev;
>> + u64 now;
>> +
>> + /* Assume counters are 64bit */
>> + now =
On Wed, 22 Jul 2015, Linus Walleij wrote:
> Signal that this is a builting driver and call its probe function
> immediately on init. Suppress binding attributes and delete the
> .remove() function since it is never unloaded. Tag probe() and
> functions only called from probe() with __init. Delete
On Wed, 22 Jul 2015, Linus Walleij wrote:
> There is a special function for debug prints rather than the
> usual hexdump function, let's use it.
>
> Signed-off-by: Linus Walleij
> ---
> drivers/mfd/ipaq-micro.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied, thanks.
On Wed, 22 Jul 2015, Linus Walleij wrote:
> Clean out a misspelled "HW" (MW) and remove commented-out
> codeline.
>
> Signed-off-by: Linus Walleij
> ---
> drivers/mfd/ipaq-micro.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Applied, thanks.
> diff --git
On Thu, 2015-07-23 at 09:36 -0600, Jan Beulich wrote:
> >
> > > > On 23.07.15 at 17:25, wrote:
> > Yes, I agree with you. But such risk is very low -- 1) the regular
> > case
> > (no fallback) is used most of the cases, 2) the code using WT knows
> > what
> > type of memory it is dealing
On Thu, Jul 23, 2015 at 9:52 AM, Marc Zyngier wrote:
> On 23/07/15 14:06, Bjorn Helgaas wrote:
>> On Thu, Jul 23, 2015 at 10:26:23AM +0100, Marc Zyngier wrote:
>>> In order to be able to populate the device msi_domain field,
>>> add the necessary hooks to propagate the host bridge msi_domain
>>>
On 07/23/2015 04:45 AM, yalin wang wrote:
A little change to patch_map() function,
use set_fixmap_offset() to make code more clear.
Signed-off-by: yalin wang
---
arch/arm64/kernel/insn.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/kernel/insn.c
On 7/16/2015 9:01 PM, R, Vignesh wrote:
> Hi,
>
> On 07/16/2015 03:24 AM, Paul Walmsley wrote:
>> Hi,
>>
>> some comments.
>>
>> On Wed, 3 Jun 2015, Vignesh R wrote:
>>
>>> Add hwmod entries for the PWMSS on DRA7.
>>>
>>> Set l4_root_clk_div as the main_clk of PWMSS. It is fixed-factored clock
On 07/23/2015 10:39 AM, Seth Forshee wrote:
> On Thu, Jul 23, 2015 at 09:57:20AM -0400, Stephen Smalley wrote:
>> On 07/22/2015 04:40 PM, Stephen Smalley wrote:
>>> On 07/22/2015 04:25 PM, Stephen Smalley wrote:
On 07/22/2015 12:14 PM, Seth Forshee wrote:
> On Wed, Jul 22, 2015 at
>>> On 23.07.15 at 17:25, wrote:
> Yes, I agree with you. But such risk is very low -- 1) the regular case
> (no fallback) is used most of the cases, 2) the code using WT knows what
> type of memory it is dealing with. For example, pmem may map NVDIMM with
> WT, and any sane BIOS sets MTRR to
On Thu, 23 Jul 2015 12:42:15 +0200
Peter Zijlstra wrote:
> static __always_inline bool arch_static_branch_jump(struct static_key *key,
> bool inv)
> {
> if (!inv) {
> asm_volatile_goto("1:"
> "jmp %l[l_yes]\n\t"
And what happens when this gets
The SYSENTER stack is only used in configurations that support 32-bit
code and, hence, SYSENTER. Remove it in 64-bit non-compat configurations.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/processor.h | 2 ++
1 file changed, 2 insertions(+)
diff --git
Oddly, 64-bit kernels already allocate a percpu sysenter stack, but
they don't enable it. Enable the stack and tweak the rest of the
sysenter setup code to be similar to the 32-bit version.
This eliminates the only place in the kernel in which TF could be set
without a valid stack.
This should have no functional effect at all.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/cpu/common.c | 34 +++---
1 file changed, 19 insertions(+), 15 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index
Now that we have a valid stack between SYSENTER and SWAPGS, let
paravirt use it.
Signed-off-by: Andy Lutomirski
---
arch/x86/entry/entry_64_compat.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/entry/entry_64_compat.S b/arch/x86/entry/entry_64_compat.S
index
Switch from wrmsr to wrmsrl_safe to prepare to merge the 32-bit and
64-bit code, and use __KERNEL_CS explicitly to initialize
MSR_IA32_SYSENTER_CS. While we're at it, tweak the whitespace a
bit.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/cpu/common.c | 12 +---
1 file changed,
These are boring patches. They're a cleanup, and something like them is
mandatory if we want to wean the 64-bit #DB handler off IST.
The latter will be useful if we want to eliminate the IST reprogramming
that we during NMIs unless we ban #DB outright inside NMIs. Even if we
ban #DB inside NMI,
On Tue, 21 Jul 2015, S Twiss wrote:
> From: S Twiss
>
> Add device tree bindings for the DA9062 RTC driver component
>
> Signed-off-by: Steve Twiss
>
> ---
> Checks performed with linux-next/next-20150708/scripts/checkpatch.pl
> da9062.txttotal: 0 errors, 0 warnings, 88
From: Vitaly Kuznetsov
Hyper-V module needs to disable cpu hotplug (offlining) as there is no
support from hypervisor side to reassign already opened event channels
to a different CPU. Currently it is been done by altering
smp_ops.cpu_disable but it is hackish.
Signed-off-by: Vitaly Kuznetsov
From: Dexuan Cui
It is to fix:
hv_kvp_daemon.c:705:2: warning: format not a string literal and no format
arguments [-Wformat-security]
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
tools/hv/hv_kvp_daemon.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
From: Vitaly Kuznetsov
Commit e513229b4c38 ("Drivers: hv: vmbus: prevent cpu offlining on newer
hypervisors") was altering smp_ops.cpu_disable to prevent CPU offlining.
We can bo better by using cpu_hotplug_enable/disable functions instead of
such hard-coding.
Reported-by: Radim Kr.má<
From: Vitaly Kuznetsov
As a prerequisite to exporting cpu_hotplug_enable/cpu_hotplug_disable
functions to modules we need to convert cpu_hotplug_disabled to a counter
to properly support disable -> disable -> enable call sequences. E.g.
after Hyper-V vmbus module (which is supposed to be the
On 22 July 2015 at 09:49, Alexander Shishkin
wrote:
> Alexander Shishkin writes:
>
>> Hi Greg and everybody,
>
> Seems like a polite nudge might be in order. :)
>
> Cheers,
> --
> Alex
Greg and all,
I have reviewed the portion of Alex's work that pertains to the
generic STM interface - in its
Changes since v6:
- Rearrange patches. [Thomas Gleixner]
- Fix a typo in PATCH 2 description [Thomas Gleixner].
- Add Reviewed-by: [Thomas Gleixner].
Changes since v5:
- Split PATCH 1 into two (PATCH 1/3 and 3/3), rewrite changelogs. [Thomas
Gleixner]
Changes since v4:
- In
Hi Srinivas,
Am 20.07.2015 um 16:43 schrieb Srinivas Kandagatla:
> This patch adds just providers part of the framework just to enable easy
> review.
>
> Up until now, NVMEM drivers like eeprom were stored in drivers/misc,
> where they all had to duplicate pretty much the same code to register
>
On Tue, 21 Jul 2015, S Twiss wrote:
> From: S Twiss
>
> Add MFD core driver support for a RTC component
>
> - MFD core adds the RTC resources da9062_rtc_resources[] for the RTC
> alarm and tick timer IRQ
> - An appropriate mfd_cell has been added into da9062_devs[] to support
> a component
On Thu, 2015-07-23 at 08:50 -0600, Jan Beulich wrote:
> >
> > > > On 23.07.15 at 16:27, wrote:
> > On Thu, 2015-07-23 at 00:42 -0600, Jan Beulich wrote:
> > > >
> > > > > > On 22.07.15 at 20:06, wrote:
> > > > Add comments to the cachemode translation tables to clarify that
> > > > the default
On Thu, 23 Jul 2015, Vlastimil Babka wrote:
> On 07/22/2015 08:43 PM, Eric B Munson wrote:
> > On Wed, 22 Jul 2015, Vlastimil Babka wrote:
> >
> >>
> >> Hi,
> >>
> >> I think you should include a complete description of which
> >> transitions for vma states and mlock2/munlock2 flags applied on
On Wed, 22 Jul 2015, Mike Kravetz wrote:
> On 07/22/2015 03:30 PM, Andrew Morton wrote:
> >On Wed, 22 Jul 2015 15:19:54 -0700 Davidlohr Bueso wrote:
> >
> >>>
> >>>I didn't know that libhugetlbfs has tests. I wonder if that makes
> >>>tools/testing/selftests/vm's hugetlbfstest harmful?
> >>
>
Previously, period_ns and duty_ns were only used to determine the
ratio of ON and OFF time, the default frequency of 200 Hz was never
changed.
The PCA9685 however is capable of changing the PWM output frequency,
which is expected when changing the period.
This patch configures the prescaler
Problems:
- When duty_ns == period_ns, the full OFF bit was not cleared and the
PWM output of the PCA9685 stayed off.
- When duty_ns == period_ns and the catch-all channel was used, the
ALL_LED_OFF_L register was not cleared.
- The full ON bit was not cleared when setting the OFF time,
Hi,
the first patch from this series contains bugfixes and the second patch
adds support for changing the PWM output frequency of the PCA9685.
Regards,
Clemens
Cc: Thierry Reding
Cc: Steffen Trumtrar
Changes in v2:
- Only put chip into sleep mode if the bounds checking succeeds
Changes in
On Sun, 19 Jul 2015, Christian Engelmayer wrote:
> Function led_rgb_store() contains some direct returns in error cases that
> leak the already allocated cros_ec_command message structure. Make sure
> that 'msg' is freed in all exit paths. Detected by Coverity CID 1309666.
>
> Signed-off-by:
On Mon, 20 Jul 2015, Richard Fitzgerald wrote:
> Explicitly set the regmap endianness instead of relying on
> the default being correct.
>
> Signed-off-by: Richard Fitzgerald
> ---
> drivers/mfd/wm5102-tables.c |4
> drivers/mfd/wm5110-tables.c |4
>
Hi Srinivas,
Am 20.07.2015 um 16:44 schrieb Srinivas Kandagatla:
> From: Maxime Ripard
>
> Now that we have the nvmem framework, we can consolidate the common
> driver code. Move the driver to the framework, and hopefully, it will
> fix the sysfs file creation race.
>
> Signed-off-by: Maxime
On Fri, 17 Jul 2015, Javier Martinez Canillas wrote:
> The MAX77802 is a chip that contains regulators, 2 32kHz clocks,
> a RTC and an I2C interface to program the individual components.
>
> The are already DT bindings for the regulators and clocks and
> these reference to a
On Mon, 20 Jul 2015, S Twiss wrote:
> From: S Twiss
>
> Add device tree bindings for the DA9062 OnKey driver component
>
> Signed-off-by: Steve Twiss
>
> ---
> Checks performed with linux-next/next-20150708/scripts/checkpatch.pl
> da9062.txttotal: 0 errors, 0 warnings, 97
Hi again,
On Thu, Jul 23, 2015 at 09:55:32AM -0500, Felipe Balbi wrote:
> > diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
> > index 0447788..b7a5119 100644
> > --- a/drivers/usb/dwc3/core.h
> > +++ b/drivers/usb/dwc3/core.h
> > @@ -124,6 +124,7 @@
> > #define DWC3_GEVNTCOUNT(n)
On Wed, Jul 22, 2015 at 06:23:26PM +0800, Daniel Kurtz wrote:
> of_regulator_match.driver_data is (void *). tps6586x uses it to store an
> anonymous enum value (those TPS6586X_ID_ values).
Applied, but please use subject lines matching the style for the
subsystem and you might want to look at
On Mon, 20 Jul 2015, S Twiss wrote:
> From: S Twiss
>
> Add MFD core driver support for a OnKey component
>
> - MFD core adds the resource da9062_onkey_resources[] for the OnKey
> - An appropriate value has been added into mfd_cell da9062_devs[] to
> support component .name = "da9062-onkey"
On Tue, Jul 21, 2015 at 05:35:19PM -0400, Murali Karicheri wrote:
> The MPS configuration should be done *before* pci_bus_add_devices().
> After pci_bus_add_devices(), drivers may be bound to devices, and
> the PCI core shouldn't touch device configuration while a driver
> owns the device.
>
>
Hi Steven,
Can you take a look if this is ok with you? This is the part
that touches tools/lib/traceevent/, the rest of the patchset that then
uses it is at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tmp.perf/core
Best regards,
- Arnaldo
commit
The patch
regulator: tps6586x: silence pointer-to-int-cast
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
On 07/22/2015 06:00 PM, Tyler Baker wrote:
> Hi Naresh,
>
> On 7 July 2015 at 05:03, wrote:
>> From: Naresh Kamboju
>>
>> zram_lib.sh: create library with initialization/cleanup functions
>> zram01.sh: creates general purpose ram disks with different filesystems
>> zram02.sh: creates block
On 05/06/2015 at 16:59:43 +0300, Octavian Purdila wrote :
> Since patch "i2c / ACPI: Use 0 to indicate that device does not have
> interrupt assigned" [1], 0 is not a valid i2c client irq anymore, so
> change all driver's checks accordingly.
>
> The same issue occurs when the device is
On Thu, Jul 23, 2015 at 10:19:52AM -0400, Jason Baron wrote:
> >
> > #define static_branch_likely(x)
> > \
> > ({
> > \
> > bool branch;
Pixcir_i2c_tsc driver can now wakeup the system from lower power state
via pinctrl and IO daisy chain using generic wakeirq framwework. Add
optional wakeup irq entry to allow pixcir_i2c_tsc to wake system from
low power state.
Signed-off-by: Vignesh R
---
v3:
* Drop "irq" suffix from
This is the v3 of the patch series to add optional wake irq support for
pixcir_i2c_tsc.
Tested on am437x-gp-evm, with some out of tree patches to support
suspend/resume on am437x.
Vignesh R (2):
input: touchscreen: pixcir_i2c_ts: Add support for optional wakeup
interrupt
ARM: dts:
Hi,
On Thu, Jul 23, 2015 at 03:41:35PM +0530, Nikhil Badola wrote:
> Add adjust_frame_length_quirk for writing to fladj register
> which adjusts (micro)frame length to value provided by
> "snps,configure-fladj" property thus avoiding USB 2.0 devices
> to time-out over a longer run
>
>
On am437x-gp-evm, pixcir touchscreen can wake the system from low power
state by generating wake-up interrupt via pinctrl and IO daisy chain.
Add support for optional wakeup interrupt source by regsitering to
automated wake IRQ framework introduced by commit 4990d4fe327b ("PM /
Wakeirq: Add
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Pan Xinhui
> Sent: Thursday, July 23, 2015 4:54 AM
> To: linux-kernel@vger.kernel.org
> Subject: [PATCH] x86/mm/pat: Do a small optimization when dump PAT memtype
>
On Tue, 21 Jul 2015 12:57:08 -0400
Jason Baron wrote:
> On 07/21/2015 12:12 PM, Peter Zijlstra wrote:
> > On Tue, Jul 21, 2015 at 08:51:51AM -0700, Andy Lutomirski wrote:
> >> To clarify my (mis-)understanding:
> >>
> >> There are two degrees of freedom in a static_key. They can start out
> >>
On 23/07/15 14:18, Bjorn Helgaas wrote:
> On Thu, Jul 23, 2015 at 10:26:19AM +0100, Marc Zyngier wrote:
>> MSI-like interrupts are starting to creep out of the PCI world, and
>> can now be seen into a number of "platform"-type busses. The
>> introduction of the MSI domains feature in v3.19
On 23/07/15 14:06, Bjorn Helgaas wrote:
> On Thu, Jul 23, 2015 at 10:26:23AM +0100, Marc Zyngier wrote:
>> In order to be able to populate the device msi_domain field,
>> add the necessary hooks to propagate the host bridge msi_domain
>> across secondary busses to devices.
>>
>> So far, nobody
On Fri, 17 Jul 2015, Javier Martinez Canillas wrote:
> I added support for the max77802 drivers and have been maintaining them.
> So add an entry for these drivers to make tools like get_maintainer.pl
> to work and make people submitting patches add me to the CC list.
>
> Signed-off-by: Javier
On Tue, 07 Jul 2015, Boris Brezillon wrote:
> Some HLCDC registers cannot be written until the hardware has finished
> applying the previous configuration request. If they are written while
> an action is still in progress, the new configuration might be silently
> ignored, resulting in
Hi,
On Thu, Jul 23, 2015 at 8:20 AM, Incarnation P. Lee
wrote:
> drivers/staging/lustre/lustre/obdclass/cl_page.c
It is custom that you write slightly more introductory text here. Just
a file name is pointless.
The subject should probably contain [PATCH 0/5]. This would be
automatically fixed
>>> On 23.07.15 at 16:27, wrote:
> On Thu, 2015-07-23 at 00:42 -0600, Jan Beulich wrote:
>> >
>> > > > On 22.07.15 at 20:06, wrote:
>> > Add comments to the cachemode translation tables to clarify that
>> > the default values are set as minimal supported mode, which are
>> > necessary to handle
On Thu, Jul 23, 2015 at 04:33:08PM +0200, Peter Zijlstra wrote:
> Lemme finish this and I'll post it.
Compile tested on x86_64 only..
Please have a look, I think you said I got some of the logic wrong, I've
not double checked that.
I'll go write comments and double check things.
---
On Mon, 20 Jul 2015, Chris Zhong wrote:
> add the description about dvs1, dvs2, and add the example.
>
> Signed-off-by: Chris Zhong
> Reviewed-by: Doug Anderson
>
> ---
>
> Changes in v4:
> - Remove the description about dvs-ok
>
> Changes in v3:
> - Modify the syntax error
>
> Changes in
On Tue, 14 Jul 2015, Bjorn Andersson wrote:
> Implement irq_chip->irq_get_irqchip_state to make it possible for PMIC
> block drivers to access the IRQ real time status bits. The status bits
> are used for various kinds of input signals, e.g. GPIO.
>
> Signed-off-by: Bjorn Andersson
> ---
>
>
On 07/23/2015 07:13 AM, Andrea Arcangeli wrote:
> On Thu, Jul 23, 2015 at 11:49:38AM +0100, Catalin Marinas wrote:
>> On Thu, Jul 23, 2015 at 12:05:21AM +0100, Dave Hansen wrote:
>>> On 07/22/2015 03:48 PM, Catalin Marinas wrote:
You are right, on x86 the tlb_single_page_flush_ceiling seems
Hi Yong,
On Thu, Jul 16, 2015 at 5:04 PM, Yong Wu wrote:
>
> This patch add the iommu/larbs nodes for mt8173
To what tree does this apply?
Please rebase these patches (especially this one) on an Matthias'
current v4.2-next/for-next.
>
> Signed-off-by: Yong Wu
> ---
>
On Thu, Jul 23, 2015 at 09:57:20AM -0400, Stephen Smalley wrote:
> On 07/22/2015 04:40 PM, Stephen Smalley wrote:
> > On 07/22/2015 04:25 PM, Stephen Smalley wrote:
> >> On 07/22/2015 12:14 PM, Seth Forshee wrote:
> >>> On Wed, Jul 22, 2015 at 12:02:13PM -0400, Stephen Smalley wrote:
> On
On Thu, Jul 23, 2015 at 5:05 PM, wrote:
>
> Octavian Purdila writes:
>>
>> On Fri, Jun 5, 2015 at 4:59 PM, Octavian Purdila
>> wrote:
>>>
>>> Since patch "i2c / ACPI: Use 0 to indicate that device does not have
>>> interrupt assigned" [1], 0 is not a valid i2c client irq anymore, so
>>> change
fs/quota/dquot.c:1999:32-33: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Jan Kara
Signed-off-by: Fengguang Wu
---
dquot.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/fs/quota/dquot.c
+++ b/fs/quota/dquot.c
@@
On Thu, Jul 23, 2015 at 11:07:09AM +, Badola Nikhil wrote:
> > -Original Message-
> > From: Mark Rutland [mailto:mark.rutl...@arm.com]
> > Sent: Thursday, July 23, 2015 4:27 PM
> > To: Badola Nikhil-B46172
> > Cc: linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; ba...@ti.com
>
On Thu, Jul 23 2015 at 1:10am -0400,
Dave Chinner wrote:
> On Wed, Jul 22, 2015 at 11:28:06AM -0500, Eric Sandeen wrote:
> > On 7/22/15 8:34 AM, Mike Snitzer wrote:
> > > On Tue, Jul 21 2015 at 10:37pm -0400,
> > > Dave Chinner wrote:
> > >> On Tue, Jul 21, 2015 at 09:40:29PM -0400, Mike
On Thu, Jul 23, 2015 at 10:19:52AM -0400, Jason Baron wrote:
> > And I think it'll all work. Hmm?
>
> Cool. This also gives an extra degree of freedom in that it allows keys to
> be arbitrarily mixed with the likely/unlikely branch types. I'm not sure
> that's
> come up as a use-case, but seems
Hi Changbin,
(I assume I address your name properly, if not please excuse)
W dniu 23.07.2015 o 14:34, Du, Changbin pisze:
From 0a8e0d63a9887735c6782d7b0c15c2c1fdf1952a Mon Sep 17 00:00:00 2001
void composite_disconnect(struct usb_gadget *gadget)
{
struct usb_composite_dev
Dear experts,
In my test bed, I hope to set some processes and related network
softirqs to have highest priority than some other processes which can
be delayed or can be executed in cpu idle condition. These critical
processes that needs to have high priority are more
cpu-time-slice-sensitive,
On Thu, 2015-07-23 at 00:42 -0600, Jan Beulich wrote:
> >
> > > > On 22.07.15 at 20:06, wrote:
> > Add comments to the cachemode translation tables to clarify that
> > the default values are set as minimal supported mode, which are
> > necessary to handle WC and WT fallback to UC- when they are
Hello Henry,
On Thu, Jul 23, 2015 at 1:04 PM, Henry Chen wrote:
> On Thu, 2015-07-23 at 11:07 +0200, Javier Martinez Canillas wrote:
>
>> > +
>> > + if (ret < 0)
>> > + dev_err(>dev, "Failed to initialize regulator: %d\n",
>> > ret);
>> > +
>>
>> I don't think this is
Signed-off-by: Incarnation P. Lee
---
drivers/staging/lustre/lustre/obdclass/cl_page.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/lustre/lustre/obdclass/cl_page.c
b/drivers/staging/lustre/lustre/obdclass/cl_page.c
index 4cc17d3..428c6b2
On 07/21/2015 05:35 PM, Murali Karicheri wrote:
The MPS configuration should be done *before* pci_bus_add_devices().
After pci_bus_add_devices(), drivers may be bound to devices, and
the PCI core shouldn't touch device configuration while a driver
owns the device.
Signed-off-by: Murali
Signed-off-by: Incarnation P. Lee
---
drivers/staging/lustre/lustre/obdclass/cl_page.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lustre/obdclass/cl_page.c
b/drivers/staging/lustre/lustre/obdclass/cl_page.c
index c386c43..4cc17d3 100644
---
Signed-off-by: Incarnation P. Lee
---
drivers/staging/lustre/lustre/obdclass/cl_page.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/obdclass/cl_page.c
b/drivers/staging/lustre/lustre/obdclass/cl_page.c
index 8b2c1e7..739814e 100644
---
On Thu, Jul 23, 2015 at 12:06:26PM +0100, Morten Rasmussen wrote:
> On Wed, Jul 22, 2015 at 10:59:04PM +0800, Leo Yan wrote:
> > On Wed, Jul 22, 2015 at 02:31:04PM +0100, Morten Rasmussen wrote:
> > > On Tue, Jul 21, 2015 at 11:41:45PM +0800, Leo Yan wrote:
> > > > Hi Morten,
> > > >
> > > > On
Signed-off-by: Incarnation P. Lee
---
drivers/staging/lustre/lustre/obdclass/cl_page.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lustre/obdclass/cl_page.c
b/drivers/staging/lustre/lustre/obdclass/cl_page.c
index 739814e..c386c43 100644
---
Signed-off-by: Incarnation P. Lee
---
drivers/staging/lustre/lustre/obdclass/cl_page.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/lustre/lustre/obdclass/cl_page.c
b/drivers/staging/lustre/lustre/obdclass/cl_page.c
index a7f3032..8b2c1e7 100644
---
drivers/staging/lustre/lustre/obdclass/cl_page.c
Signed-off-by: Incarnation P. Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
On 07/23/2015 06:42 AM, Peter Zijlstra wrote:
> On Wed, Jul 22, 2015 at 01:06:44PM -0400, Jason Baron wrote:
>> Ok,
>>
>> So we could add all 4 possible initial states, where the
>> branches would be:
>>
>> static_likely_init_true_branch(struct static_likely_init_true_key *key)
>>
On Thu, Jul 23, 2015 at 11:49:38AM +0100, Catalin Marinas wrote:
> On Thu, Jul 23, 2015 at 12:05:21AM +0100, Dave Hansen wrote:
> > On 07/22/2015 03:48 PM, Catalin Marinas wrote:
> > > You are right, on x86 the tlb_single_page_flush_ceiling seems to be
> > > 33, so for an HPAGE_SIZE range the code
On Thu, Jul 23, 2015 at 11:43 AM, Dan Carpenter
wrote:
> On Thu, Jul 23, 2015 at 10:57:18AM +0900, Chanwoo Choi wrote:
>> +static int exynos_ppmu_v2_disable(struct devfreq_event_dev *edev)
>> +{
>> + struct exynos_ppmu *info = devfreq_event_get_drvdata(edev);
>> + u32 pmnc, clear;
>> +
>>
On Thu, Jul 23, 2015 at 4:01 PM, Valentin Rothberg
wrote:
> Hi Jan,
>
> On Thu, Jul 23, 2015 at 3:47 PM, Jan Kara wrote:
>> On Thu 23-07-15 13:18:06, Valentin Rothberg wrote:
>>> commit 106542e7987c ("fs: Remove ext3 filesystem driver") removed ext3
>>> and JBD, hence remove the superfluous
The touchscreen on the WinBook TW100 and TW700 don't match the default
display, with 0,0 touches being reported when touching at the bottom
right of the screen.
1280,800 0,800
+-+
| |
| |
| |
On Wed, 22 Jul 2015, David Rientjes wrote:
> Eek, yeah, that does look bad. I'm not even sure the
>
> if (nid < 0)
> nid = numa_node_id();
>
> is correct; I think this should be comparing to NUMA_NO_NODE rather than
> all negative numbers, otherwise we silently ignore
On Thu, Jul 23, 2015 at 10:14 AM, Chanwoo Choi wrote:
> Hi Krzysztof,
>
> On 07/23/2015 04:28 PM, Krzysztof Kozlowski wrote:
>> On 23.07.2015 10:57, Chanwoo Choi wrote:
>>> This patch adds the support for PPMU (Platform Performance Monitoring Unit)
>>> version 2.0 for Exynos5433 SoC. Exynos5433
501 - 600 of 1842 matches
Mail list logo
