Did You Receive Our Last Notification?(Reply Via fly.emiratesairl...@5d6d.cn)
--
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 FAQ at
On 09/20/2013 06:51 AM, Tony Prisk wrote:
On 20/09/13 07:12, Sebastian Hesselbarth wrote:
On 09/19/2013 09:02 PM, Tony Prisk wrote:
On 19/09/13 05:53, Sebastian Hesselbarth wrote:
Currently, clock providers for vt8500 depend on machine_init providing
pmc_base address before calling of_clk_init
Currently, clock providers for vt8500 depend on machine_init providing
pmc_base address before calling of_clk_init. With upcoming arch-wide
.time_init calling of_clk_init, we should make clock providers independent
of mach code. This adds a pmc_base parsing helper to current clock provider
that get
On 20 September 2013 10:56, Yinghai Lu wrote:
> If the hw support intel_pstate and acpi_cpufreq, intel_pstate will
> get loaded at first.
s/at //
>
> acpi_cpufreq_init will call acpi_cpufreq_early_init()
> and it allocate perf data and init those perf data in ACPI core, (that
s/it /that will /
On Fri, Sep 20, 2013 at 11:04:40AM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> On Tuesday 17 September 2013 09:11 PM, Felipe Balbi wrote:
> > On Wed, Sep 04, 2013 at 02:27:06PM +0530, Kishon Vijay Abraham I wrote:
> >> On Tuesday 03 September 2013 09:20 PM, Greg KH wrote:
> >>> On Tue, Sep
* Ricardo Ribalda Delgado wrote:
> Anything else to fix on this patch?
Looks good to me, thanks!
Acked-by: Ingo Molnar
Ingo
--
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://
Hi Greg,
On Tuesday 17 September 2013 09:11 PM, Felipe Balbi wrote:
> On Wed, Sep 04, 2013 at 02:27:06PM +0530, Kishon Vijay Abraham I wrote:
>> On Tuesday 03 September 2013 09:20 PM, Greg KH wrote:
>>> On Tue, Sep 03, 2013 at 08:55:23PM +0530, Kishon Vijay Abraham I wrote:
Hi Greg,
On Thu, Sep 19, 2013 at 9:23 PM, Viresh Kumar wrote:
> On 20 September 2013 07:01, Yinghai Lu wrote:
>> Sorry, looks like this one is not enough.
>>
>> please let me know if you prefer me send addon patch
>> or revised one.
>
> Atleast you can let us know what the problem is? And then we
> can d
If the hw support intel_pstate and acpi_cpufreq, intel_pstate will
get loaded at first.
acpi_cpufreq_init will call acpi_cpufreq_early_init()
and it allocate perf data and init those perf data in ACPI core, (that
will go over all cpus).
but late it will free them as cpufreq_register_driver(acpi_cp
On 09/19/2013 08:07 PM, Joe Perches wrote:
On Wed, 2013-09-18 at 20:27 -0500, Daniel Santos wrote:
if I use ERR_PTR() on a signed int on a x86_64 where pointer
is 64 bits and int is 32, wouldn't that mean a signed conversion
instruction where the sign bit has to be moved from bit 31 to 63?
No.
* Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit a8e0108cac181a7b141dacaa99ea52efaf9b5f07:
>
> perf: Fix UAPI export of PERF_EVENT_IOC_ID (2013-09-18 11:29:07 +0200)
>
* Josef Bacik wrote:
> We can starve out the transaction commit with a bunch of caching threads
> all running at the same time. This is because we will only drop the
> extent_commit_sem if we need_resched(), which isn't likely to happen
> since we will be reading a lot from the disk so have
On Thu, Sep 19, 2013 at 9:46 PM, Stephen Rothwell wrote:
> Hi all,
>
> I will be having a 3 week break leading up to the kernel
> summit. This means that next-20130927 (next Friday) will be the last
> linux-next release until next-20131028 (or maybe 29 depending on
> jetlag). I presume that Linu
On Thu, Sep 19, 2013 at 9:23 PM, Joe Perches wrote:
> On Fri, 2013-09-20 at 13:09 +0900, Tetsuo Handa wrote:
>> Hello.
>
> Tetsuo-san:
>
>> We are discussing about removal of %n support from vsnprintf() at
>> https://lkml.org/lkml/2013/9/16/52 , and you are using %n in seq_printf().
>
> Well, I'm
On 20/09/13 07:12, Sebastian Hesselbarth wrote:
On 09/19/2013 09:02 PM, Tony Prisk wrote:
On 19/09/13 05:53, Sebastian Hesselbarth wrote:
Currently, clock providers for vt8500 depend on machine_init providing
pmc_base address before calling of_clk_init. With upcoming arch-wide
.time_init callin
Hi all,
I will be having a 3 week break leading up to the kernel
summit. This means that next-20130927 (next Friday) will be the last
linux-next release until next-20131028 (or maybe 29 depending on
jetlag). I presume that Linus will be up to v3.12-rc7 by then and -rc7
is often the last before a
... Please plan accordingly.
Changes since 20130919:
The drm-intel tree gained a conflict against the the drm-intel-fixes tree.
The pinctrl tree gained a build failure.
I have created today's linux-next tree a
On 09/19/2013 03:31 AM, Andi Kleen wrote:
On Wed, Sep 18, 2013 at 02:02:37PM -0500, H. Peter Anvin wrote:
Yes, a bit sad. We allow bracketing with the get/put_user_try/catch blocks,
but that is x86-specific.
I don't think a generic option is possible without compiler support, but it
might be
On 20 September 2013 07:01, Yinghai Lu wrote:
> Sorry, looks like this one is not enough.
>
> please let me know if you prefer me send addon patch
> or revised one.
Atleast you can let us know what the problem is? And then we
can decide on that.. But anyway, you can send a new patch
based over l
On Fri, 2013-09-20 at 13:09 +0900, Tetsuo Handa wrote:
> Hello.
Tetsuo-san:
> We are discussing about removal of %n support from vsnprintf() at
> https://lkml.org/lkml/2013/9/16/52 , and you are using %n in seq_printf().
Well, I'm not using (mere alcohol isn't using, right?)
but I still have the
On 19 September 2013 23:41, Srivatsa S. Bhat
wrote:
> But there was no code to set the per-cpu values to -1 to begin with. Since
> the per-cpu variable was defined as static, it would have been initialized
> to zero. Thus, we would never actually hit the BUG_ON() condition, since
> policy_cpu didn
Driver core sets driver data to NULL upon failure or remove.
Signed-off-by: Sachin Kamat
---
drivers/regulator/tps6524x-regulator.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/regulator/tps6524x-regulator.c
b/drivers/regulator/tps6524x-regulator.c
index 62e8d28..8b9ee39 100644
Hello.
We are discussing about removal of %n support from vsnprintf() at
https://lkml.org/lkml/2013/9/16/52 , and you are using %n in seq_printf().
I posted https://lkml.org/lkml/diff/2013/9/19/53/1 which introduces
seq_setwidth() / seq_pad() which can avoid use of %n in seq_printf().
Assuming th
On Thu, Sep 19, 2013 at 11:06 PM, Darrick J. Wong
wrote:
> The "force" parameter in __blk_queue_bounce was being ignored, which means
> that
> stable page snapshots are not always happening (on ext3). This of course
> leads to DIF disks reporting checksum errors, so fix this regression.
>
> The
On Wed, Sep 18, 2013 at 5:31 AM, Peter Zijlstra wrote:
> On Tue, Sep 17, 2013 at 02:48:13PM +0800, Yan, Zheng wrote:
>> From: "Yan, Zheng"
>>
>> uncore_validate_group() can't call smp_processor_id() because it is
>> in preemptible context. Pass NUMA_NO_NODE to the allocator instead.
>>
>> Signed-
IN control driver for the
GPIO controller on bf54x and bf60x"). asm/portmux.h only exists on
blackfin ...
I have used the version of the pinctrl tree from next-20130919 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpzwUVdB31w_.pgp
Description: PGP signature
On Thu, 2013-09-19 at 16:00 -0300, Arnaldo Carvalho de Melo wrote:
> Em Sun, Sep 08, 2013 at 07:19:12PM -0700, Davidlohr Bueso escreveu:
> > This patchset is a first in a series of perf-lock enhancements I am working
> > on. Overall it is pretty straightforward, dealing with cleanups, and some
> >
file size used only once, so removed due its useless prior allocation.
It's not necessary to verify f_op in the load_aout_library, since the
prior kernel_read/vfs_read function already does.
Made coding style fixes and printk replacements.
Tested using qemu, a handcrafted a.out binary and an a.out
ia32_aout had no safe checks concerning the mmap and f_op in this module.
It's not necessary to verify f_op in the load_aout_library, since the
prior kernel_read/vfs_read function already does.
Made coding style fixes and printks replacements.
Tested using qemu, a handcrafted a.out binary and an a
On Thu, Sep 19, 2013 at 12:00:29PM +0100, Quentin Armitage wrote:
> There appears to be an error in the second address of the second XOR
> engine in the Kirkwood SoC device tree, which is specified as 0xd0b00
> but should be 0x60b00.
>
> For confirmation of address see
> http://www.marvell.com/emb
file size used only once, so removed due its useless prior allocation.
It's not necessary to verify f_op in the load_aout_library, since the
prior kernel_read/vfs_read function already does.
Made coding style fixes and printk replacements.
Tested using qemu, a handcrafted a.out binary and a a.out
Casts of int to pointer need additional casts to (unsigned long)
when compiled for x86-64 to silence the compiler.
Signed-off-by: Joe Perches
---
drivers/video/arkfb.c| 2 +-
drivers/video/vt8623fb.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/arkfb.c
ia32_aout had no safe checks concerning the mmap and f_op in this module.
It's not necessary to verify f_op in the load_aout_library, since the
prior kernel_read/vfs_read function already does.
Made coding style fixes and printks replacements.
Tested using qemu, a handcrafted a.out binary and a a.
The "force" parameter in __blk_queue_bounce was being ignored, which means that
stable page snapshots are not always happening (on ext3). This of course
leads to DIF disks reporting checksum errors, so fix this regression.
The regression was introduced in commit 6bc454d1 (bounce: Refactor
__blk_q
On 09/19/2013 02:11 PM, Linus Torvalds wrote:
On Thu, Sep 19, 2013 at 1:06 PM, Will Deacon wrote:
The cmpxchg() function tends not to support 64-bit arguments on 32-bit
architectures. This could be either due to use of unsigned long arguments
(like on ARM) or lack of instruction support (cmpxch
On Thu, Sep 19, 2013 at 10:40:30AM +0100, Mel Gorman wrote:
> On Thu, Sep 19, 2013 at 10:32:50AM +0100, Mel Gorman wrote:
> > Commit ffecfd1a (block: optionally snapshot page contents to provide
> > stable pages during write) uses bounce buffers for stable page writes in
> > jbd and ext3. Simplisti
On Friday 20 September 2013 01:34 AM, Yann E. MORIN wrote:
> Benjamin, All,
>
> On 2013-09-19 15:13 -0400, Benjamin Poirier spake thusly:
>> On 2013/09/19 19:27, Yann E. MORIN wrote:
>>> Benjamin, Madhavan, All,
>>>
>>> On 2013-09-19 11:22 -0400, Benjamin Poirier spake thusly:
On 2013/09/19 1
On Thu, 2013-09-19 at 19:02 -0500, Linus Torvalds wrote:
> On Thu, Sep 19, 2013 at 2:51 PM, Frederic Weisbecker
> wrote:
> >
> > It fixes stacks overruns reported by Benjamin Herrenschmidt:
> > http://lkml.kernel.org/r/1378330796.4321.50.camel%40pasglop
>
> So I don't really dislike this patch-s
s/framebugger/framebuffer/
Signed-off-by: Joe Perches
---
drivers/video/arkfb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/arkfb.c b/drivers/video/arkfb.c
index ee0f1a1..b13f3f2 100644
--- a/drivers/video/arkfb.c
+++ b/drivers/video/arkfb.c
@@ -1048,7 +1048
This driver apparently hasn't compiled since 2.5 days as
it uses a #define that isn't around anymore.
Remove it.
Signed-off-by: Joe Perches
---
drivers/video/Kconfig | 10 -
drivers/video/Makefile | 1 -
drivers/video/pmag-aa-fb.c | 510 -
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_display.c between commit cc173961a680
("drm/i915: do not update cursor in crtc mode set") from the
drm-intel-fixes tree and commit e9fd1c02aca7 ("drm/i915: don't enable
DPLL for DSI") from the drm-i
Add fb_ convenience macros for emitting the
"fb%d: ", struct fb_info->node value.
Neatens and shortens the code a bit.
Signed-off-by: Joe Perches
---
include/linux/fb.h | 12
1 file changed, 12 insertions(+)
diff --git a/include/linux/fb.h b/include/linux/fb.h
index ffac70a..70c48
Neaten and shorten the code using the new fb_ macros.
Signed-off-by: Joe Perches
---
drivers/auxdisplay/cfag12864bfb.c| 3 +-
drivers/video/68328fb.c | 9 +++---
drivers/video/amifb.c| 4 +--
drivers/video/arcfb.c| 8 ++---
drivers/video/arkfb
On Thu, Sep 19, 2013 at 3:37 PM, Rafael J. Wysocki wrote:
> On Thursday, September 19, 2013 09:38:32 AM Viresh Kumar wrote:
>> On 19 September 2013 09:35, Yinghai Lu wrote:
>> > System that cpu support intel_pstate, acpi_cpufreq fail to
>> > load, and udev keep trying until trace get filled up an
cscsope says there are no callers for mmc_try_claim_host in the kernel.
No reason to keep it.
Signed-off-by: Grant Grundler
---
drivers/mmc/core/core.c | 25 -
include/linux/mmc/core.h | 1 -
2 files changed, 26 deletions(-)
diff --git a/drivers/mmc/core/core.c b/drive
On Wed, 2013-09-18 at 20:27 -0500, Daniel Santos wrote:
> if I use ERR_PTR() on a signed int on a x86_64 where pointer
> is 64 bits and int is 32, wouldn't that mean a signed conversion
> instruction where the sign bit has to be moved from bit 31 to 63?
No. It's cast to long
static inline void
On Thu, Sep 19, 2013 at 4:19 PM, Woodhouse, David
wrote:
> On Thu, 2013-09-19 at 15:57 -0700, Brian Norris wrote:
>> On Thu, Sep 19, 2013 at 2:39 PM, Woodhouse, David
>> wrote:
>> > On Thu, 2013-09-19 at 12:47 -0700, Olof Johansson wrote:
>> >>
>> >> - A fix for build breakage in the MTD subsyste
When do disk pull/insert test we encountered below:
WARNING: at fs/sysfs/dir.c:455 sysfs_add_one+0xbc/0xe0()
Hardware name: SUN FIRE X4370 M2 SERVER
sysfs: cannot create duplicate filename
'/devices/pci:00/:00:03.0/:0d:00.0/host6/port-6:1/expander-6:1/port-6:1:14/end_device-6:1:14/tar
On Thu, Sep 19, 2013 at 2:51 PM, Frederic Weisbecker wrote:
>
> It fixes stacks overruns reported by Benjamin Herrenschmidt:
> http://lkml.kernel.org/r/1378330796.4321.50.camel%40pasglop
So I don't really dislike this patch-series, but isn't "irq_exit()"
(which calls the new softirq_on_stack()) a
On Tue, Sep 17, 2013 at 12:01:30PM +0200, Geert Uytterhoeven wrote:
> This is a preliminary set of patches to add kexec support for m68k.
Great, this has been a long time coming!
> - Kexec only, no kdump support yet (do you have enough RAM to keep a
> crashdump kernel in memory at all times
On Thu, Sep 19, 2013 at 11:20:22AM +0200, Geert Uytterhoeven wrote:
> On Tue, Sep 17, 2013 at 12:01 PM, Geert Uytterhoeven
> wrote:
> > This is a preliminary set of patches to add kexec support for m68k.
>
> > - [PATCH 1/3] m68k: Add preliminary kexec support
> > - [PATCH 2/3] m68k: Add suppo
On Thu, Sep 19, 2013 at 06:57:27PM -0400, Peter Hurley wrote:
> On 09/19/2013 11:48 AM, Josef Bacik wrote:
> >Btrfs needs a simple way to know if it needs to let go of it's read lock on a
> >rwsem. Introduce rwsem_is_contended to check to see if there are any
> >waiters on
> >this rwsem currently
On Thu, 2013-09-19 at 15:57 -0700, Brian Norris wrote:
> On Thu, Sep 19, 2013 at 2:39 PM, Woodhouse, David
> wrote:
> > On Thu, 2013-09-19 at 12:47 -0700, Olof Johansson wrote:
> >>
> >> - A fix for build breakage in the MTD subsystem for some PXA devices.
> >> David Woodhouse has this patch in
On Wed, Sep 18, 2013 at 09:48:44PM -0700, Roy Franz wrote:
> On Wed, Sep 18, 2013 at 8:44 PM, Adam Borowski wrote:
> > [UCS2 truncation]
>
> I stuck to re-arranging the code that was there, as I don't know enough
> about character encodings to propose changes.
I on the other hand don't know the
On 09/19/13 13:17, Randy Dunlap wrote:
> On 09/18/13 20:44, Jeff P. Zacher wrote:
>>
>>
>> You are correct that this problem shown in the forum was in 3.5.4. However,
>> I am
>> having wither the same or similar problem in 3.10.7.
>> Here is the broken config file, saved as .config-bad
>>
>
>
On 09/19/2013 11:48 AM, Josef Bacik wrote:
Btrfs needs a simple way to know if it needs to let go of it's read lock on a
rwsem. Introduce rwsem_is_contended to check to see if there are any waiters on
this rwsem currently. This is just a hueristic, it is meant to be light and not
100% accurate
On Thu, Sep 19, 2013 at 2:39 PM, Woodhouse, David
wrote:
> On Thu, 2013-09-19 at 12:47 -0700, Olof Johansson wrote:
>>
>> - A fix for build breakage in the MTD subsystem for some PXA devices.
>> David Woodhouse has this patch in his for-next branch but has not been
>> responding to our request
On Thu, Sep 19, 2013 at 11:49:41AM -0600, Stephen Warren wrote:
> On 09/19/2013 06:18 AM, David Gibson wrote:
> > On Wed, Sep 18, 2013 at 02:23:02PM -0600, Stephen Warren wrote:
> >> From: Stephen Warren
> >>
> >> ePAPR 1.1 section 2.2.1.1 "Node Name Requirements" specifies that
> >> any node tha
On 09/19/2013 05:35 PM, Daniel Santos wrote:
Hmm, I cannot reproduce the error. :( I'm using next-20130919
currently (x86_64), and if I try to just "make O=lib" it fails w/o my
patches. The only file that should depend upon error_strings.h is
lib/string.c.
Ahh! I've
On Thu 2013-09-19 07:37:15, Greg KH wrote:
> On Thu, Sep 19, 2013 at 10:20:48AM -0400, Jason Cooper wrote:
> > On Thu, Sep 19, 2013 at 04:10:46PM +0200, Michal Simek wrote:
> > > On 09/19/2013 04:06 PM, Greg KH wrote:
> > > > On Thu, Sep 19, 2013 at 02:52:37PM +0200, Pavel Machek wrote:
> > > >> On
Joe Perches :
[...]
> David selects them regardless.
>
> from Documentation/networking/netdev-FAQ.txt:
I don't believe that those who read Documentation/stable_kernel_rules.txt
will magically read networking/netdev-FAQ.txt as well nor figure that
while they should not mark the patches stables (s
ith a "make O=foo" build directory? I
see:
/bin/sh: /data/fs/linux-2.6-fscache/include/generated/error_strings.h:
No such file or directory
when I try it.
Hmm, I cannot reproduce the error. :( I'm using next-20130919 currently
(x86_64), and if I try to just "make O=lib
On 9/19/13 4:25 PM, "Verma, Vishal L" wrote:
>On 9/19/13 3:45 PM, "Thomas Meyer" wrote:
>
>>Use kzalloc rather than kmalloc followed by memset with 0.
>>Found by coccinelle spatch "api/alloc/kzalloc-simple.cocci"
>>
>>Signed-off-by: Thomas Meyer
>>---
>
>Thomas,
>
>This has already been applied
On Wednesday 18 September 2013 19:42:12 Tony Lindgren wrote:
> * Pali Rohár [130918 09:08]:
> > On Wednesday 18 September 2013 15:16:44 Pavel Machek wrote:
> > > On Sun 2013-09-08 02:02:52, Aaro Koskinen wrote:
> > > > Hi,
> > > >
> > > > On Fri, Sep 06, 2013 at 10:34:05PM +0200, Pali Rohár
wrot
On Thursday 19 September 2013 23:29:22 Tony Lindgren wrote:
> * Pali Rohár [130919 14:10]:
> > On Thursday 19 September 2013 00:26:43 Tony Lindgren wrote:
> > > * Pali Rohár [130918 15:02]:
> > > > Without max_current data in board file lp5523 driver
> > > > does not change current.
> > >
> > >
On Thursday, September 19, 2013 09:38:32 AM Viresh Kumar wrote:
> On 19 September 2013 09:35, Yinghai Lu wrote:
> > System that cpu support intel_pstate, acpi_cpufreq fail to
> > load, and udev keep trying until trace get filled up and
> > kernel crash.
> >
> > The root cause is driver return ret
On 9/19/13 3:45 PM, "Thomas Meyer" wrote:
>Use kzalloc rather than kmalloc followed by memset with 0.
>Found by coccinelle spatch "api/alloc/kzalloc-simple.cocci"
>
>Signed-off-by: Thomas Meyer
>---
Thomas,
This has already been applied to Matthew's tree:
http://git.infradead.org/users/willy/l
On Thu, Sep 19, 2013 at 2:39 PM, Woodhouse, David
wrote:
> On Thu, 2013-09-19 at 12:47 -0700, Olof Johansson wrote:
>>
>> - A fix for build breakage in the MTD subsystem for some PXA devices.
>> David Woodhouse has this patch in his for-next branch but has not been
>> responding to our request
Here is the output:
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=050d ProdID=065a Rev= 1.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=0002723E2D29
C:* #Ifs= 4 Cfg#= 1 Atr=a0 M
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/staging/rtl8188eu/os_dep/ioctl_linux.c
b/drivers/staging/rtl8188eu/os_dep/ioctl_linux.c
--- a/drivers/staging/rtl
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/staging/rtl8188eu/hal/rtl8188e_dm.c
b/drivers/staging/rtl8188eu/hal/rtl8188e_dm.c
--- a/drivers/staging/rtl8188eu
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/scsi/csiostor/csio_mb.c b/drivers/scsi/csiostor/csio_mb.c
--- a/drivers/scsi/csiostor/csio_mb.c
+++ b/drivers/scsi
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/staging/lustre/lustre/obdecho/echo_client.c
b/drivers/staging/lustre/lustre/obdecho/echo_client.c
--- a/drivers/s
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/staging/octeon-usb/cvmx-usb.c
b/drivers/staging/octeon-usb/cvmx-usb.c
--- a/drivers/staging/octeon-usb/cvmx-usb.c
On Thu, 2013-09-19 at 23:42 +0200, Thomas Meyer wrote:
> sizeof when applied to a pointer typed expression gives the size of the
> pointer.
Hi Thomas, thanks for doing the series...
> diff -u -p a/arch/xtensa/platforms/iss/network.c
> b/arch/xtensa/platforms/iss/network.c
[]
> @@ -737,7 +737,7 @
Use kzalloc rather than kmalloc followed by memset with 0.
Found by coccinelle spatch "api/alloc/kzalloc-simple.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/scsi/aic7xxx/aic79xx_osm.c
b/drivers/scsi/aic7xxx/aic79xx_osm.c
--- a/drivers/scsi/aic7xxx/aic79xx_osm.c
+++ b/drivers/scsi
Use kzalloc rather than kmalloc followed by memset with 0.
Found by coccinelle spatch "api/alloc/kzalloc-simple.cocci"
Run against version v3.11-7547-g44598f9
Let me know when you as a maintainer are not interested in these kind of
patches.
I can exclude you by path; all cocci findings in e.g. "
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/staging/rtl8188eu/core/rtw_mp.c
b/drivers/staging/rtl8188eu/core/rtw_mp.c
--- a/drivers/staging/rtl8188eu/core/rt
Use kzalloc rather than kmalloc followed by memset with 0.
Found by coccinelle spatch "api/alloc/kzalloc-simple.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/block/nvme-scsi.c b/drivers/block/nvme-scsi.c
--- a/drivers/block/nvme-scsi.c
+++ b/drivers/block/nvme-scsi.c
@@ -933,13 +93
On Thu, Sep 19, 2013 at 02:15:35PM -0700, Guenter Roeck wrote:
> On Thu, Sep 19, 2013 at 11:05:12AM -0700, Mike Turquette wrote:
> > Quoting Soren Brinkmann (2013-09-18 15:43:38)
> > > diff --git a/Documentation/devicetree/bindings/clock/silabs,si570.txt
> > > b/Documentation/devicetree/bindings/c
Hi Tim,
On Tue, Sep 10, 2013 at 10:23:13AM -0600, Tim Gardner wrote:
> BugLink: http://bugs.launchpad.net/bugs/1222850
>
> This input device can get into a state that produces a high
> volume of device status errors. Attempt to throttle these
> error messages such that the kernel log is not flood
On Thu, 2013-09-19 at 23:32 +0200, Francois Romieu wrote:
> Joe Perches :
> [...]
> > diff --git a/Documentation/stable_kernel_rules.txt
> > b/Documentation/stable_kernel_rules.txt
> > index b0714d8..a2d6da0 100644
> > --- a/Documentation/stable_kernel_rules.txt
> > +++ b/Documentation/stable_ker
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/arch/xtensa/platforms/iss/network.c
b/arch/xtensa/platforms/iss/network.c
--- a/arch/xtensa/platforms/iss/network.c
+++ b
sizeof when applied to a pointer typed expression gives the size of the
pointer.
Found by coccinelle spatch "misc/noderef.cocci"
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/iio/adc/at91_adc.c b/drivers/iio/adc/at91_adc.c
--- a/drivers/iio/adc/at91_adc.c
+++ b/drivers/iio/adc/at91_adc.c
On Tue, Sep 10, 2013 at 4:13 PM, Christoph Lameter wrote:
>
> Note: This patch is based on the vmstat patches in Andrew's tree
> to be merged for the 3.12 kernel.
Sorry for being dumb but this patch doesn't apply for me on either
mmotm nor Linus master. What did I miss?
Gilad
--
Gilad Ben-Yo
On Thu, 2013-09-19 at 12:47 -0700, Olof Johansson wrote:
>
> - A fix for build breakage in the MTD subsystem for some PXA devices.
> David Woodhouse has this patch in his for-next branch but has not been
> responding to our requests to send it up so here it is.
> I should have amended the co
Joe Perches :
[...]
> diff --git a/Documentation/stable_kernel_rules.txt
> b/Documentation/stable_kernel_rules.txt
> index b0714d8..a2d6da0 100644
> --- a/Documentation/stable_kernel_rules.txt
> +++ b/Documentation/stable_kernel_rules.txt
> @@ -29,6 +29,11 @@ Rules on what kind of patches are acc
* Pali Rohár [130919 14:10]:
> On Thursday 19 September 2013 00:26:43 Tony Lindgren wrote:
> > * Pali Rohár [130918 15:02]:
> > > Without max_current data in board file lp5523 driver does
> > > not change current.
> >
> > Hmm is this a regression or are there other reasons to merge
> > this duri
Since Operating Performance Points(OPP) data structures are specific
to device specific power management, be specific and rename opp_* data
structures in OPP library with dev_pm_opp_* equivalent.
Impacted structures are:
struct opp
enum opp_event
Minor checkpatch warning fixes as a result of this
On Thu, Sep 19, 2013 at 11:05:12AM -0700, Mike Turquette wrote:
> Quoting Soren Brinkmann (2013-09-18 15:43:38)
> > diff --git a/Documentation/devicetree/bindings/clock/silabs,si570.txt
> > b/Documentation/devicetree/bindings/clock/silabs,si570.txt
> > new file mode 100644
> > index 000..7ab5c
On Thu, 5 Sep 2013 17:46:12 +0200 Jan Kara wrote:
> Sorry for a delayed reply. I was on vacation...
>
> On Fri 23-08-13 12:58:22, Andrew Morton wrote:
> > On Fri, 23 Aug 2013 21:48:36 +0200 (CEST) Jiri Kosina
> > wrote:
> >
> > > > > We have customers (quite a few of them actually) which
On Sun, 2013-09-15 at 20:04 -0700, Davidlohr Bueso wrote:
> This patchset deals with the selinux and rmid races Manfred found on
> the ipc scaling work that has been going on. It specifically addresses
> shared mem and msg queues. While semaphores still need updated, I want
> to make sure these are
On Wednesday, September 18, 2013 03:06:52 PM Richard Guy Briggs wrote:
> Re-named confusing local variable names (status_set and status_get didn't
> agree with their command type name) and reduced their scope.
>
> Future-proof API changes by not depending on the exact size of the
> audit_status st
Since Operating Performance Points(OPP) functions are specific to
device specific power management, be specific and rename opp_*
accessors in OPP library with dev_pm_opp_* equivalent.
Impacted functions are:
opp_get_voltage
opp_get_freq
opp_get_opp_count
opp_find_freq_exact
opp_find_freq_floor
opp
Since Operating Performance Points(OPP) functions are specific to
device specific power management, be specific and rename opp.h
to pm_opp.h
Reported-by: Randy Dunlap
Signed-off-by: Nishanth Menon
---
Documentation/power/opp.txt |2 +-
arch/arm/mach-imx/mach-imx6q.c |
On 16:03-20130919, Nishanth Menon wrote:
> Hi,
>
> Based on [1], Randy rightly pointed out that OPP functions and data
> structures could be a bit specific to Power management.
>
> So, the following series is based on v3.12-rc1 tag.
>
> If folks like it broken in a dif
On Thu, Sep 19, 2013 at 01:59:38PM -0700, Sören Brinkmann wrote:
> On Thu, Sep 19, 2013 at 09:44:38AM -0700, Guenter Roeck wrote:
> > On Thu, Sep 19, 2013 at 09:01:01AM -0700, Sören Brinkmann wrote:
> > > On Thu, Sep 19, 2013 at 06:17:12AM -0700, Guenter Roeck wrote:
> > > > On Wed, Sep 18, 2013 at
On Fri, Sep 13, 2013 at 7:38 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 448bd85 (PCI/PM: add PCIe runtime D3cold support) added a
> piece of code to pci_acpi_wake_dev() causing that function to behave
> in a special way for devices in D3cold (so that their configuration
> r
> From: Dave Airlie [mailto:airl...@gmail.com]
> Sent: Thursday, September 19, 2013 1:15 PM
>
> On Fri, Sep 20, 2013 at 6:10 AM, Daniel Vetter wrote:
> > On Thu, Sep 19, 2013 at 06:32:47PM +, Paul Zimmerman wrote:
> >> > From: Paul Zimmerman
> >> > Sent: Thursday, September 19, 2013 11:21 AM
On Thursday 19 September 2013 00:26:43 Tony Lindgren wrote:
> * Pali Rohár [130918 15:02]:
> > Without max_current data in board file lp5523 driver does
> > not change current.
>
> Hmm is this a regression or are there other reasons to merge
> this during the -rc cycle?
>
I think this is regres
1 - 100 of 450 matches
Mail list logo
