Hi Andrejz,
On Thu, Jul 3, 2014 at 5:23 PM, Andrzej Hajda wrote:
>
> Hi Alexandre,
>
> Thanks for the patch.
>
> On 07/02/2014 02:19 PM, Alexandre Courbot wrote:
>> As per section 5.6.1 of the DSI specification, all DSI transmitters must
>> support continuous clock behavior on the clock lane,
At Wed, 2 Jul 2014 09:55:05 -0700,
Luis R. Rodriguez wrote:
>
> From: "Luis R. Rodriguez"
>
> Now that the udev firmware loader is optional request_firmware()
> will not provide any information on the kernel ring buffer if
> direct firmware loading failed and udev firmware loading is disabled.
On Jul 3, 2014, at 10:59 PM, Maxime Ripard
wrote:
> On Thu, Jul 03, 2014 at 10:39:08PM +0800, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
>>> +++ b/drivers/power/reset/at91-reset.c
>>> @@ -0,0 +1,202 @@
>>> +/*
>>> + * Atmel AT91 SAM9 SoCs reset code
>>> + *
>>> + * Copyright (C) 2014 Maxime
On 2014-07-04 05:27, Hu Yaohui wrote:
> Hi All,
> Is direct device assignment in nested VM supported in the latest KVM
> mainline now?
Le Tan is currently working on emulated device assignment (VT-d
emulation in QEMU). This is the necessary first step and could later be
extended to enable
Chen-san,
I would like to recommend that you summarize pros/cons for all ideas so far.
For example,
-
A) make new system call for transrate
A-1) systemcall(ID, NS1, NS2) into (ID).
pros:
- foo
- baa
cons:
- hoge
- hogehogehoge
A-2)
On 2014-07-04 04:52, Wanpeng Li wrote:
> On Thu, Jul 03, 2014 at 01:27:05PM -0400, Bandan Das wrote:
> [...]
>> # modprobe kvm_intel ept=0 nested=1 enable_shadow_vmcs=0
>>
>> The Host CPU - Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
>> qemu cmd to run L1 -
>> # qemu-system-x86_64 -drive
>>
From: Pramod Gurav
Fixes below warning while compiling the kernel.
fs/direct-io.c: In function ‘__blockdev_direct_IO’:
fs/direct-io.c:1011:12: warning: ‘to’ may be used uninitialized in this
function [-Wmaybe-uninitialized]
fs/direct-io.c:913:16: note: ‘to’ was declared here
At Thu, 3 Jul 2014 13:02:52 +0100,
Mark Brown wrote:
>
> On Thu, Jul 03, 2014 at 03:08:08PM +0530, Vinod Koul wrote:
>
> > Yes makes sense to go thru ASoC tree. Mark can you keep this in immutable
> > branch, which I can merge to my tree for any future fixes...
>
> Fine by me - Takashi?
Sure,
On Thu, Jul 3 2014 Joe Julian wrote:
> I have a knox enclosure with an unresponsive drive. When the mpt2sas
> module is loaded the module loading process hangs. modprobe/insmod is
> stuck and any further attempts to load modules also hang. By
> blacklisting the module and loading it last, I
(2014/07/04 2:01), Oleg Nesterov wrote:
> On 07/03, Oleg Nesterov wrote:
>>
>> Hmm. Off-topic, but it seems that instance_rmdir() leaks the memory? Say,
>> file->filter?
>
> Perhaps I am totally confused, but don't we need something like the patch
> below? I'll try to recheck later...
>
> Better
On Wed, Jun 25, 2014 at 10:08 PM, Peter Zijlstra wrote:
> On Wed, Jun 25, 2014 at 10:23:21AM -0600, Stephen Warren wrote:
>> On 06/25/2014 04:19 AM, Peter Zijlstra wrote:
>> > On Wed, Jun 25, 2014 at 03:24:11PM +0530, Srivatsa S. Bhat wrote:
>> >> Wait, that was a stupid idea. hotplug_cfd()
On Fri, Jul 04, 2014 at 05:23:56AM +0200, Mike Galbraith wrote:
> On Thu, 2014-07-03 at 09:29 -0700, Paul E. McKenney wrote:
> > On Thu, Jul 03, 2014 at 07:48:40AM +0200, Mike Galbraith wrote:
> > > On Wed, 2014-07-02 at 22:21 -0700, Paul E. McKenney wrote:
> > > > On Thu, Jul 03, 2014 at
Hi Suman,
On Thu, Jul 3, 2014 at 8:28 PM, Suman Anna wrote:
> OK, but we would still require this function to lookup the registered
> device from the controller-phandle to retrieve the base_id.
Can we retrieve the base_id from the parent DT node itself?
Thanks,
Ohad.
--
To unsubscribe from
Hi Suman,
On Thu, Jul 3, 2014 at 8:35 PM, Suman Anna wrote:
> Not at the moment, with the existing platform implementations. So, if I
> understand you correctly, you are asking to leave out the xlate ops and
> make the of_hwspin_lock_simple_xlate() internal until a need for an
> xlate method
Hi Felipe,
Today's linux-next merge of the usb-gadget tree got a conflict in
drivers/usb/musb/musb_cppi41.c between commit c58d80f523ff ("usb: musb:
Ensure that cppi41 timer gets armed on premature DMA TX irq") from the
usb.current tree and commit 50aea6fca771 ("usb: musb: cppi41: fire
hrtimer
(2014/07/04 1:22), Oleg Nesterov wrote:
>> One possible scenario is here; someone disables an event and tries to remove
>> it (both will be done by different syscalls). If we don't synchronize
>> the first disabling, the event flag set disabled, but the event itself
>> is not disabled. Thus event
On Thu, 2014-07-03 at 16:08 -0700, Austin Schuh wrote:
> On Tue, Jul 1, 2014 at 12:32 PM, Austin Schuh wrote:
> > On Mon, Jun 30, 2014 at 8:01 PM, Austin Schuh
> > wrote:
> >> On Fri, Jun 27, 2014 at 7:24 AM, Thomas Gleixner
> >> wrote:
> >>> Completely untested patch below.
>
> I've tested
Hi Nick,
On Fri, Jul 4, 2014 at 2:07 AM, Nick Krause wrote:
> Very well then I will read the documentation on Kconfig in order to
> understand that and fix up my patches for that.
> On the other hand I will send a email before the patches to tell in
> what order to apply them.
As already asked
While searching for FIX ME messages when using cscope on the latest kernels I
get a message on 68 of this file and was wondering what I need to define SMFRAM
as in order for it to point to things needed to support this portion
of the hardware.
Cheers Nick
--
To unsubscribe from this list: send
On 4 July 2014 03:46, Mike Turquette wrote:
> Sorry for being dense, but I still do not get why trying to dynamically
> discover a shared rate-changeable clock is a better approach than simply
> describing the hardware in DT?
>
> Is adding a property to the CPU binding that describes how the CPUs
From: Viresh Kumar
Currently, the ->set_mode() method of a clockevent device is not
allowed to fail, so it has no return value. In order to add new
clockevent modes, and allow the setting of those modes to fail, we
need the clockevent core to be able to detect when setting a mode
fails.
To
Currently, the ->set_mode() method of a clockevent device is not
allowed to fail, so it has no return value. In order to add new
clockevent modes, and allow the setting of those modes to fail, we
need the clockevent core to be able to detect when setting a mode
fails.
Rather than changing the
From: Viresh Kumar
Clockevents core now supports ->set_dev_mode() (as a replacement to
->set_mode()), with capability to return error codes.
This patch migrates few clockevent drivers to the new method to demonstrate how
to convert to the new interface.
Drivers are modified to return -ENOSYS
From: Steven Rostedt
Date: Thu, 3 Jul 2014 12:41:46 -0400
> Do you have any problem with this patch going through my tree? It
> compiles, but I do not have any hardware to test it. If you can verify
> that this patch works and ack it, it would be much appreciated.
>
> This code is at:
>
>
On Fri, 2014-07-04 at 09:15 +0530, Sachin Kamat wrote:
> In any case, if this patch is going to be appled, please fix typo in subject
>
> s/Samsunt/Samsung
I think Sangboem is going to submit something appropriate
instead.
--
To unsubscribe from this list: send the line "unsubscribe
Hi Tejun,
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git review-mq-percpu_ref
commit c924ec35e72ce0d6c289b858d323f7eb3f5076a5 ("block, blk-mq: draining can't
be skipped even if bypass_depth was non-zero")
Hi all,
Sorry please ignore this report: it seems there are no obvious
relationship between the code change and the regression.
Thanks,
Fengguang
On Fri, Jul 04, 2014 at 11:45:31AM +0800, Jet Chen wrote:
> Hi Aaron,
>
> FYI, we noticed the below changes on
>
> commit
On Fri, Jul 4, 2014 at 5:23 AM, Sangbeom Kim wrote:
> On Friday, July 04, 2014 7:08 AM, Joe Perches wrote:
>
>> F: drivers/regulator/s2m*.c
>> F: drivers/regulator/s5m*.c
>> -F: drivers/rtc/rtc-sec.c
>> F: include/linux/mfd/samsung/
>>
>
> Yes, You are right.
> There is no rtc-sec.c
>
Hi Aaron,
FYI, we noticed the below changes on
commit ed235875e2ca983197831337a986f0517074e1a0 ("kernel/watchdog.c: print
traces for all cpus on lockup detection")
test case: lkp-snb01/will-it-scale/signal1
f3aca3d09525f87 ed235875e2ca983197831337a
--- -
Am Freitag, 4. Juli 2014, 11:12:35 schrieb Herbert Xu:
Hi Herbert,
> On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> > For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> > memory location immediately before the drbg_state->tfm variable
> > is the buffer that
Am Freitag, 4. Juli 2014, 11:08:10 schrieb Herbert Xu:
Hi Herbert,
> On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> > For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> > memory location immediately before the drbg_state->tfm variable
> > is the buffer that
Hi All,
Is direct device assignment in nested VM supported in the latest KVM
mainline now?
Thanks,
Yaohui
--
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
This patch fixed spelling typo in various template files
within Documentation/Docbook.
Signed-off-by: Masanari Iida
---
Documentation/DocBook/gadget.tmpl | 2 +-
Documentation/DocBook/genericirq.tmpl | 4 ++--
Documentation/DocBook/kernel-locking.tmpl | 2 +-
On Thu, 2014-07-03 at 09:29 -0700, Paul E. McKenney wrote:
> On Thu, Jul 03, 2014 at 07:48:40AM +0200, Mike Galbraith wrote:
> > On Wed, 2014-07-02 at 22:21 -0700, Paul E. McKenney wrote:
> > > On Thu, Jul 03, 2014 at 05:31:19AM +0200, Mike Galbraith wrote:
> >
> > > > NO_HZ_FULL is a property
> IF you've turned on debugging options, then you've already lost more
> performance that careful packing of the dentry slab cache gains you.
> There's no point in carefully tuning DNAME_INLINE_LEN for debug
> options - it's just code that will break and annoy people as debug
> implementations
On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> memory location immediately before the drbg_state->tfm variable
> is the buffer that the BCC function operates on. BCC operates
> blockwise. Making the temp
Please drop this wrong post and see V2.
Thanks,
Ethan
On 2014/7/4 22:48, Ethan Zhao wrote:
netxen driver has implemented netxen_nic_get_ethtool_stats() interface,
but doesn't collect stats.rxdropped in driver, so we will get
different statistic information while using ifconfig and ethtool.
On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> memory location immediately before the drbg_state->tfm variable
> is the buffer that the BCC function operates on. BCC operates
> blockwise. Making the temp
> -Original Message-
> From: Neil Zhang
> Sent: 2014年5月14日 15:52
> To: Neil Zhang; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Cc: rmk+ker...@arm.linux.org.uk
> Subject: RE: [PATCH] ARM: remove redundant code in machine_halt
>
> > -Original Message-
> >
This commit:
commit 6f6343f53d133bae516caf3d254bce37d8774625
Author: Masami Hiramatsu
Date: Thu Apr 17 17:17:33 2014 +0900
kprobes/x86: Call exception handlers directly from do_int3/do_debug
Trying to dereference addr when addr is user-controlled is
completely bogus.
On Thu, Jul 03, 2014 at 01:27:05PM -0400, Bandan Das wrote:
[...]
># modprobe kvm_intel ept=0 nested=1 enable_shadow_vmcs=0
>
>The Host CPU - Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
>qemu cmd to run L1 -
># qemu-system-x86_64 -drive
On Thu, Jul 3, 2014 at 4:39 AM, Ian Abbott wrote:
> On 2014-07-03 03:15, Chase Southwood wrote:
>>
>> This patchset moves a misplaced include to the proper file, swaps out an
>> overly
>> aggressive placement of apci1564_reset(), and cleans up
>> apci1564_interrupt().
>>
>> Chase Southwood (3):
On Fri, 2014-07-04 at 09:33 +0800, Barry Song wrote:
> >> -Original Message-
> >> From: Joe Perches [mailto:j...@perches.com]
> >> Sent: Friday, July 04, 2014 6:08 AM
[]
> >> commit 7bf21bc81f28 ("clk: sirf: re-arch to make the codes support both
> >> prima2 and atlas6") moved the files,
Hi,
just use the MMC_CAP2_SDIO_IRQ_NOTHREAD?
if (!err && host->sdio_irq && !(host->quirks & MMC_CAP2_SDIO_IRQ_NOTHREAD))
wake_up_process(host->sdio_irq_thread);
I didn't test this..but i believe that it will be fixed.
Best Regards,
Jaehoon Chung
On 07/04/2014 12:47 AM, Fu, Zhonghui
Hi Gleb,
On 07/03/2014 12:34 AM, Gleb Natapov wrote:
On Wed, Jul 02, 2014 at 05:00:36PM +0800, Tang Chen wrote:
ept identity pagetable is pinned in memory, and as a result it cannot be
migrated/hot-removed.
But actually it doesn't need to be pinned in memory.
This patch introduces a new vcpu
The code has a variable to change the polarity of the PWM backlight control but
it was not being initialized. This patch adds a devicetree entry to set the
variable if required.
Signed-off-by: Michael Welling
---
.../devicetree/bindings/video/atmel,lcdc.txt |1 +
Hi Gleb,
Thanks for the advices. Please see below.
On 07/03/2014 09:55 PM, Gleb Natapov wrote:
..
@@ -575,6 +575,7 @@ struct kvm_arch {
unsigned int tss_addr;
struct page *apic_access_page;
+ bool apic_access_page_migrated;
Better have two requests
Hi Gleb,
Thanks for the advices. Please see below.
On 07/03/2014 09:55 PM, Gleb Natapov wrote:
..
@@ -575,6 +575,7 @@ struct kvm_arch {
unsigned int tss_addr;
struct page *apic_access_page;
+ bool apic_access_page_migrated;
Better have two requests
2014-07-03 7:35 GMT+08:00 Colin King :
> From: Colin Ian King
>
> Smatch detected two memory leaks on saved_ec:
>
> drivers/acpi/ec.c:1070 acpi_ec_ecdt_probe() warn: possible
> memory leak of 'saved_ec'
> drivers/acpi/ec.c:1109 acpi_ec_ecdt_probe() warn: possible
> memory leak of 'saved_ec'
>
On Thu, 2014-07-03 at 18:46 -0700, Jason Low wrote:
> On Fri, 2014-07-04 at 11:01 +1000, Dave Chinner wrote:
> > FWIW, the rwsems in the struct xfs_inode are often heavily
> > read/write contended, so there are lots of IO related workloads that
> > are going to regress on XFS without this
On Fri, 2014-07-04 at 11:01 +1000, Dave Chinner wrote:
> [re-added lkml]
>
> On Thu, Jul 03, 2014 at 11:50:20AM -0700, Jason Low wrote:
> > On Wed, Jul 2, 2014 at 7:32 PM, Dave Chinner wrote:
> > > This is what the kernel profile looks like on the strided run:
> > >
> > > - 83.06% [kernel]
On Fri, Jul 04, 2014 at 11:16:39AM +1000, Dave Chinner wrote:
> On Thu, Jul 03, 2014 at 05:52:12PM -0400, Naoya Horiguchi wrote:
> > We need the pagecache tags to be exported to userspace later in this
> > series for fincore(2), so this patch moves the definition to the new
> > include file for
We calculate difference between two readings of a clock to see how
much time has elapsed. Part of the time between rq_clock(rq) -
dl_se->deadline can indeed be accounted for by reading a different
clock
(i.e., rq_clock_task()) if the task was running during the period.
And that is how
Hi all,
After merging the net tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "phy_resume" [drivers/net/ethernet/stmicro/stmmac/stmmac.ko] undefined!
Caused by commit 0acf16768740 ("net: stmmac: add platform init/exit for
Altera's ARM socfpga").
I reverted that
>> -Original Message-
>> From: Joe Perches [mailto:j...@perches.com]
>> Sent: Friday, July 04, 2014 6:08 AM
>> To: Andrew Morton
>> Cc: Barry Song; linux-kernel@vger.kernel.org
>> Subject: [PATCH 04/16] MAINTAINERS: Update clk/sirf patterns
>>
>> commit 7bf21bc81f28 ("clk: sirf: re-arch to
On Thu, Jul 03, 2014 at 12:53:01PM -0700, Andi Kleen wrote:
> Rasmus Villemoes writes:
>
> > In dcache.h, DNAME_INLINE_LEN is carefully chosen so that sizeof(struct
> > dentry) is a (specific) multiple of 64 bytes. Obviously this breaks when
> > certain debug options are chosen (DEBUG_LOCK_ALLOC
On Wed, 2 Jul 2014, Nicholas Krause wrote:
> Removes a FIXME comment in this file due to it not compiling as it now
> compiles.
What got fixed?
It doesn't say "FIXME - this doesn't compile".
>
> Signed-off-by: Nicholas Krause
> ---
> arch/m68k/include/asm/sun3_pgalloc.h | 1 -
> 1 file
In __rtc_set_alarm(), the error after __rtc_read_time() is not checked.
If rtc device fail to read time, we cannot guarantee the following process.
Add the verification code for returned __rtc_read_time() error.
Signed-off-by: Hyogi Gim
---
drivers/rtc/interface.c | 2 ++
1 file changed, 2
On Thu, Jul 03, 2014 at 05:52:12PM -0400, Naoya Horiguchi wrote:
> We need the pagecache tags to be exported to userspace later in this
> series for fincore(2), so this patch moves the definition to the new
> include file for preparation. We also use the number of pagecache tags,
> so this patch
The Tegra USB complex has a particularly annoying misdesign: some of the
UTMI pad configuration registers are global for all the 3 USB controllers
on the chip, but those registers are located in the first controller's
register space and will be cleared when the reset to the first
controller is
Hi all,
Here's a second version of the probe order issue series. This time I've
added the USB1 resets to the PHYs, thus replacing the really ugly parts
with something slightly better. Old device trees will still probe
successfully, but instead of this bugfix they'll get a dev_warn().
The reset
tegra_usb_phy_close() is supposed to undo the effects of
tegra_usb_phy_init(). It is also currently added as the USB PHY shutdown
callback, which is wrong, since tegra_usb_phy_init() is only called
during probing wheras the shutdown callback can get called multiple
times. This then leads to
When Tegra was converted to use the standard reset bindings, the PHY was
forgotten, probably because all the resetting of the USB blocks were
done in the EHCI driver. What also went unnoticed is that resetting the
1st on-chip USB module also wipes some of the UTMI pad configuration
registers that
Add new properties to all of the Tegra PHYs that are now required
according to the binding.
In order to stay compatible with old device trees, the USB drivers
will still function without these reset properties but with the old,
potentially buggy behaviour.
Signed-off-by: Tuomas Tynkkynen
---
v2
On Thu, 2014-07-03 at 16:35 -0400, Waiman Long wrote:
> I do see a point in reducing the size of the rwsem structure. However, I
> don't quite understand the point of converting pointers in the
> optimistic_spin_queue structure to atomic_t. The structure is cacheline
> aligned and there is no
[re-added lkml]
On Thu, Jul 03, 2014 at 11:50:20AM -0700, Jason Low wrote:
> On Wed, Jul 2, 2014 at 7:32 PM, Dave Chinner wrote:
> > This is what the kernel profile looks like on the strided run:
> >
> > - 83.06% [kernel] [k] osq_lock
> >- osq_lock
> > - 100.00%
(2014/07/03 16:44), Namhyung Kim wrote:
> Hi Masami,
>
> On Thu, 03 Jul 2014 14:46:09 +0900, Masami Hiramatsu wrote:
>> One possible scenario is here; someone disables an event and tries to remove
>> it (both will be done by different syscalls). If we don't synchronize
>> the first disabling, the
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.16-rc4
for you to fetch changes up to
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-3.16-rc4
for you to fetch changes up to
The following changes since commit 4c834452aad01531db949414f94f817a86348d59:
Linux 3.16-rc3 (2014-06-29 14:11:36 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-3.16-rc4
for you to fetch changes up to
(2014/07/03 22:21), Steven Rostedt wrote:
> Fengguang Wu's build bot detected that if moduleloader.h is included in
> a C file (used by ftrace and kprobes to access module_alloc() when
> available), that it can fail to build if CONFIG_MODULES and
> CONFIG_MODULES_USE_ELF_REL is not defined.
>
>
Whenever files are added, moved, or deleted, the
MAINTAINERS file patterns can be out of sync or
outdated.
To try to keep MAINTAINERS more up-to-date, add a
one-time warning whenever a patch does any of those.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 13 -
1 file
Good day,
We are Christian loan organization, we help people financially for a loan,
if interested, please contact us at marieloanlend...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
t; This patch should fix the BUG.
> >
> > Cc: sta...@vger.kernel.org
> > Reported-and-Tested-by: Alexander E. Patrakov
> > Signed-off-by: Minchan Kim
>
> Hi Minchan,
>
> This patch causes the following lockdep warning:
>
>
> [ 249.54554
On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote:
> On Wed, 2 Jul 2014, Hugh Dickins wrote:
> > On Wed, 2 Jul 2014, Johannes Weiner wrote:
> > >
> > > Could you give the following patch a spin? I put it in the mmots
> > > stack on top of
Hi Tanmay, Liviu,
On 7/4/2014 2:57 AM, Tanmay Inamdar wrote:
Reposting on request of several people since previously posted one was
corrupted.
This patch adds the arch support for PCI(e) for arm64. The files
added or modified in this patch are based on PCI(e) support in
32bit arm.
Please note
(2014/07/03 18:51), Borislav Petkov wrote:
On Thu, Jul 03, 2014 at 01:52:52PM +0900, Yasuaki Ishimatsu wrote:
I think that the reason to apply CPU number to ACPI ID is that CPU is
used for the application without considering physical CPU. So even if
CPU number is changed, it is no matter.
I
On Friday, July 04, 2014 5:19 AM, Rickard Strandqvist wrote:
>
> Fix for possible null pointer dereferenc, and there is a risk
> for memory leak if something unexpected
s/dereferenc/dereference
The columns of this commit is too long.
Please keep about 80 columns.
> happens and the function
This patch fixed spelling typo found in DocBook/mtdnand.tmpl.
Signed-off-by: Masanari Iida
---
Documentation/DocBook/mtdnand.tmpl | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/Documentation/DocBook/mtdnand.tmpl
On Friday, July 04, 2014 7:08 AM, Joe Perches wrote:
> F: drivers/regulator/s2m*.c
> F: drivers/regulator/s5m*.c
> -F: drivers/rtc/rtc-sec.c
> F: include/linux/mfd/samsung/
>
Yes, You are right.
There is no rtc-sec.c
Instead, rtc-s5m.c was upstreamed.
I will post update patch.
On Tue, Jul 01, 2014 at 10:22:49PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Fri, Jun 13, 2014 at 07:11:58PM +, Paul Walmsley wrote:
> > Hi Felipe, Tomi,
> >
> > On Fri, 13 Jun 2014, Felipe Balbi wrote:
> >
> > > On Fri, Jun 13, 2014 at 11:15:46AM -0500, Felipe Balbi wrote:
> > > > From:
On Thu, Jul 03, 2014 at 03:08:00PM -0700, Joe Perches wrote:
> commit 51b1130eb582 ("rcutorture: Abstract rcu_torture_random()")
> moved the file, update the patterns
>
> Signed-off-by: Joe Perches
> cc: "Paul E. McKenney"
Acked-by: Paul E. McKenney
> ---
> MAINTAINERS | 4 ++--
> 1 file
On Tue, Jul 1, 2014 at 12:32 PM, Austin Schuh wrote:
> On Mon, Jun 30, 2014 at 8:01 PM, Austin Schuh wrote:
>> On Fri, Jun 27, 2014 at 7:24 AM, Thomas Gleixner wrote:
>>> Completely untested patch below.
I've tested it and looked it over now, and feel pretty confident in
the patch. Thanks
On 07/03/2014 10:35 AM, Jan Beulich wrote:
Relying on static functions used just once to get inlined (and
subsequently have dead code paths eliminated) is wrong: Compilers are
free to decide whether they do this, regardless of optimization level.
With this not happening for vdso_addr() (observed
On 07/03/2014 10:34 AM, Jan Beulich wrote:
Certain ld versions (observed with 2.20.0) put an empty .rela.dyn
section into shared object files, breaking the assumption on the number
of sections to be copied to the final output. Simply discard any empty
SHT_REL and SHT_RELA sections to address
From: Greg Kroah-Hartman
Jan points out that I forgot to make the needed fixes to the
lz4_uncompress_unknownoutputsize() function to mirror the changes done
in lz4_decompress() with regards to potential pointer overflows.
The only in-kernel user of this function is the zram code, which only
On Thu, Jul 03, 2014 at 10:49:23PM +0200, Marek Belisko wrote:
> From: NeilBrown
>
> If a 'gpio_reset' is specified, then hold it low while
> turning the power regulator on.
> This is needed for some wi2wi wireless modules, particularly
> when the regulator is held active by some other client.
>
The compiler can generate slightly smaller and simpler code when it
knows that "nbits" is non-negative. Since no-one passes a
negative bit-count, this shouldn't affect the semantics.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 4 ++--
lib/bitmap.c | 4 ++--
2 files
Since the extra bits are "don't care", there is no reason to mask the
last word to the used bits when complementing. This shaves off yet a
few bytes.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 2 +-
lib/bitmap.c | 2 +-
2 files changed, 2 insertions(+), 2
The compiler can generate slightly smaller and simpler code when it
knows that "nbits" is non-negative. Since no-one passes a
negative bit-count, this shouldn't affect the semantics.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 6 +++---
lib/bitmap.c | 4 ++--
2 files
The compiler can generate slightly smaller and simpler code when it
knows that "nbits" is non-negative. Since no-one passes a
negative bit-count, this shouldn't affect the semantics.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 4 ++--
lib/bitmap.c | 4 ++--
2 files
The compiler can generate slightly smaller and simpler code when it
knows that "nbits" is non-negative. Since no-one passes a
negative bit-count, this shouldn't affect the semantics.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 4 ++--
lib/bitmap.c | 4 ++--
2 files
The compiler can generate slightly smaller and simpler code when it
knows that "nbits" is non-negative. Since no-one passes a
negative bit-count, this shouldn't affect the semantics.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 2 +-
lib/bitmap.c | 4 ++--
2 files
The compiler can generate slightly smaller and simpler code when it
knows that "start" is non-negative.
Also, use the names "start" and "len" for the two parameters in both
header file and implementation, instead of the previous mix.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h |
Changing the pos parameter of __reg_op to unsigned allows the compiler
to generate slightly smaller and simpler code. Also update its callers
bitmap_*_region to receive and pass unsigned int. The return types of
bitmap_find_free_region and bitmap_allocate_region are still int to
allow a negative
A few lines above, it was stated that positions for non-set bits are
mapped to -1, which is obviously also what the code does.
Signed-off-by: Rasmus Villemoes
---
lib/bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/bitmap.c b/lib/bitmap.c
index d4b3a6d..2714df9
We want len to be the index of the first '\n', or the length of the
string if there is no newline. This is a good example of the
usefulness of strchrnul(). Use that instead, thus eliminating a branch
and a call to strlen().
Signed-off-by: Rasmus Villemoes
---
lib/bitmap.c | 9 ++---
1 file
The compiler can generate slightly smaller and simpler code when it
knows that "nbits" is non-negative. Since no-one passes a negative
bit-count, this shouldn't affect the semantics.
I didn't change the return type, since that might change the semantics
of some expression containing a call to
The compiler can generate slightly smaller and simpler code when it
knows that "nbits" is non-negative. Since no-one passes a
negative bit-count, this shouldn't affect the semantics.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 4 ++--
lib/bitmap.c | 4 ++--
2 files
The compiler can generate slightly smaller and simpler code when it
knows that "start" is non-negative.
Also, use the names "start" and "len" for the two parameters for
consistency with bitmap_set.
Signed-off-by: Rasmus Villemoes
---
include/linux/bitmap.h | 2 +-
lib/bitmap.c | 10
1 - 100 of 1974 matches
Mail list logo
