Sam Ravnborg writes:
>> actually, y'know, proof-read it.
> Hmm..
>> + $(KERNELRELEASE) "$(patsubst
>> y,_,$(CONFIG_HAVE_SYMBOL_PREFIX_UNDERSCORE))"
>>
>> +config HAVE_UNDERSCORE_SYMBOL_PREFIX
>
> HAVE_UNDERSCORE_... or HAVE_SYMBOL_... confusion.
> I prefer the HAVE_SYMBOL_...
Hi Linus,
On 4 March 2013 22:38, Tony Prisk wrote:
> On Mon, 2013-03-04 at 14:39 +0530, Sachin Kamat wrote:
>> Use the newly introduced devm_ioremap_resource() instead of
>> devm_request_and_ioremap() which provides more consistent error handling.
>>
>> devm_ioremap_resource() provides its own er
James Hogan writes:
> Fix symbol versioning on architectures with symbol prefixes. Although
> the build was free from warnings the actual modules still wouldn't load
> as the versions table contained unprefixed symbol names, which were
> being compared against the prefixed symbol names when ch
Satoru Takeuchi writes:
> Hi Rusty,
>
> At Tue, 12 Mar 2013 15:43:33 -0700,
> Greg Kroah-Hartman wrote:
>> @@ -307,6 +312,14 @@ int hwrng_register(struct hwrng *rng)
>>
>> mutex_lock(&rng_mutex);
>>
>> +/* kmalloc makes this safe for virt_to_page() in virtio_rng.c */
>> +err = -EN
> > > /* and copy the data that needs to be copied */
> > > cmd_pos = offsetof(struct iwl_device_cmd, payload);
> > > + copy_size = sizeof(out_cmd->hdr);
> > > for (i = 0; i < IWL_MAX_CMD_TFDS; i++) {
> > > - if (!cmd->len[i])
> > > + int copy = 0;
> > > +
> > > + if (
Hi Al,
Today's linux-next merge of the signal tree got a conflict in
include/asm-generic/unistd.h between commit 837718bfd28b
("CONFIG_SYMBOL_PREFIX: cleanup") from the modules tree and commit
e1b5bb6d1236 ("consolidate cond_syscall and SYSCALL_ALIAS declarations")
from the signal tree.
The latte
Used devres APIs devm_request_threaded_irq and devm_regulator_get for
requesting irq and for getting regulator respectively.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/otg/twl4030-usb.c | 28
1 file changed, 8 insertions(+), 20 deletions(-)
diff --git a
This series has some misc cleanup and fixes. The fix solves the cold
plug issue in omap3 which some have reported. Developed these patches on
fixes-for-v3.9-rc3 after applying
http://www.spinics.net/lists/linux-usb/msg81563.html
(Grazvydas Ignotas patch series)
Tested for g_zero enumeration in pa
Having twl4030_usb_phy_init() (detects if a cable is connected before
twl4030 is probed) in twl4030 probe makes cable connect events to be
missed by musb glue, since it gets loaded after twl4030. Having
twl4030_usb_phy_init as a usb_phy ops lets twl4030_usb_phy_init to be
called when glue is ready.
No functional change. otg_set_vbus is already protected so removed the
check before calling otg_set_vbus.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/musb/omap2430.c b/drivers/us
Some PHYs load too early (twl4030) making omap glue to miss cable connect events
if the board is booted with cable connected. So adding usb_phy_init in
omap2430_musb_init lets PHYs to report events once glue is ready.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |2 +
Hi Doug,
On Wed, Mar 13, 2013 at 10:48 PM, Doug Anderson wrote:
> This is a fixup to two device tree nodes that have already landed but
> without clock nodes since the transition to common clock happened at
> the same time.
>
> Signed-off-by: Doug Anderson
> ---
> arch/arm/boot/dts/exynos5250.
From: chenggang
While we run "make clean" in perf's directory, and run the command:
"fine ./ -name *.o"
we will get:
./arch/x86/util/unwind.o
./arch/x86/util/header.o
./arch/x86/util/dwarf-regs.o
./util/scripting-engines/trace-event-python.o
./util/scripting-e
We don't want executable permissions set on files such as
devicetree syntax files, text files, defconfig files, or binary
hex files.
Cc: Andy Whitcroft
Cc: Joe Perches
Signed-off-by: Stephen Boyd
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scri
On Wed, Mar 13, 2013 at 6:04 AM, Huang Shijie wrote:
> On Wed, Mar 13, 2013 at 6:54 PM, Artem Bityutskiy
> wrote:
>> On Thu, 2013-03-07 at 18:49 +0800, Huang Shijie wrote:
>>> diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
>>> index 591eeeb..f0a9d93 100644
>>> --- a/include/linu
On Thursday 14 March 2013 03:29 AM, Grazvydas Ignotas wrote:
On Wed, Mar 13, 2013 at 10:47 AM, Kishon Vijay Abraham I wrote:
In the case where omap glue is loaded and musb core is not, glue->status
wont have a valid status if the phy drivers call omap_musb_mailbox. So
fixed the conditions here.
Hi Huang,
A few nitpicks, and a few real comments.
On Wed, Mar 13, 2013 at 7:59 PM, Huang Shijie wrote:
> When we meet a full-id nand type which @mfr_id is true, we can use
> the find_full_id_nand() to parse out the neccessary information for a
s/neccessary/necessary
> nand chip.
>
> If we mee
On Wed, Mar 13, 2013 at 7:59 PM, Huang Shijie wrote:
> I have 4 Toshiba nand chips which can not be parsed out by the
> id data. We can not get the oob size from the id data. So add them
> as the full-id nand chips in the first of nand_flash_ids.
>
> The nand_get_flash_type() scans the full id nan
From: Sahara
This makes return_address() return a correct value for CALLER_ADDRn.
To have a correct value from CALLER_ADDRn, we need to fix three points.
* The unwind_frame() does not update frame->lr but frame->pc for backtrace.
So frame->pc is meaningful for backtrace.
* data.level should be
Hi Jörn,
Today's linux-next merge of the bcon tree got a conflict in
drivers/block/Kconfig between commit 8722ff8cdbfa ("block: IBM RamSan
70/80 device driver") from Linus' tree and commit a2ff9d05bbb4 ("add
blockconsole version 1.1") from the bcon tree.
I fixed it up (see below) and can carry th
On Wed, Mar 13, 2013 at 7:59 PM, Huang Shijie wrote:
> As time goes on, we begin to meet the situation that we can not
> get enough information from some nand chips's id data.
> Take some Toshiba's nand chips for example.
> I have 4 Toshiba's nand chips in my hand:
> TC58NVG2S0F, TC58NVG3S
On 03/14/2013 09:35 AM, Marcelo Tosatti wrote:
> On Wed, Mar 13, 2013 at 10:07:06PM -0300, Marcelo Tosatti wrote:
>> On Wed, Mar 13, 2013 at 12:59:12PM +0800, Xiao Guangrong wrote:
>>> The current kvm_mmu_zap_all is really slow - it is holding mmu-lock to
>>> walk and zap all shadow pages one by on
I'm posting this lightly tested version since I may not be able to do
more testing/benchmarking until the weekend.
Davide's totalmess is still running, so that's probably a good sign :)
http://www.xmailserver.org/totalmess.c
I will look for more ways to break this (and benchmark when I stop
findin
Hello Maintainers:
are these warnings for head.S OK ?
make:
make V=1 EXTRA_CFLAGS=-W ARCH=arm randconfig
(this time, CONFIG_MMU=y)
warning information:
arch/arm/boot/compressed/head.S: Assembler messages:
arch/arm/boot/compressed/head.S:565: Warning: (null)
arch/arm/boot/compresse
Hi Tejun,
Today's linux-next merge of the workqueues tree got a conflict in
kernel/workqueue.c between commit e68035fb65de ("workqueue: convert to
idr_alloc()") from Linus' tree and commit fa1b54e69bc6 ("workqueue:
update synchronization rules on worker_pool_idr") from the workqueues
tree.
I fixe
Hi Laurent, Simon,
On Wed, Mar 13, 2013 at 9:58 PM, Laurent Pinchart
wrote:
> Hi Magnus,
>
> Thanks for the patches.
Thanks for your review!
> On Wednesday 13 March 2013 20:32:03 Magnus Damm wrote:
>> gpio: Renesas R-Car GPIO driver update
>>
>> [PATCH 01/03] gpio: Renesas R-Car GPIO driver V2
Mathieu Desnoyers wrote:
> Ported to the Linux kernel from Userspace RCU library, at commit
> 108a92e5b97ee91b2b902dba2dd2e78aab42f420.
>
> Ref: http://git.lttng.org/userspace-rcu.git
>
> It is provided as a starting point only. Test cases should be ported
> from Userspace RCU to kernel space an
On 14 March 2013 05:29, Alexander Graf wrote:
> On my Exynos 5 based Arndale system, I need to pull the reset line down
> and then let it go up again to actually perform a reset. Without that
> reset, I can't find any USB hubs on my bus, rendering the USB controller
> useless.
>
> We also only nee
On 03/08/2013 09:18 PM, Myron Stowe wrote:
On Thu, Mar 7, 2013 at 11:51 PM, Xiangliang Yu wrote:
Hi, Bjorn
Fix system hang issue: if first accessed resource file of BAR0 ~
BAR4, system will hang after executing lspci command
This needs more explanation. We've already read the BARs by the t
On Wed, Mar 13, 2013 at 10:14 PM, Laurent Pinchart
wrote:
> Hi Magnus,
>
> Thanks for the patch.
>
> I've reviewed the result of squashing the 3 patches together, I just have one
> comment.
>
> On Wednesday 13 March 2013 20:32:13 Magnus Damm wrote:
>> From: Magnus Damm
>>
>> This patch is V2 of a
Huh. This is very, very weird. Is this a repeatable crash?
- Ted
--
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
2013/3/14, Sergey Yanovich :
> MMC hosts are added asynchronously. We need to wait until detect returns to
> avoid failed root filesystem mounts.
> ---8<---
> VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6
> Please append a correct "root=" boot option; here are the availab
Hi Linus,
On Thu, Mar 14, 2013 at 2:20 AM, Linus Walleij wrote:
> On Tue, Mar 5, 2013 at 1:32 AM, Magnus Damm wrote:
>
>> +static int gpio_rcar_irq_set_type(struct irq_data *d, unsigned int type)
>> +{
>> + struct gpio_rcar_priv *p = irq_data_get_irq_chip_data(d);
>> + unsigned int h
This reduces the amount of code inside the ready list iteration loops
for better readability IMHO.
Signed-off-by: Eric Wong
Cc: Davide Libenzi
Cc: Al Viro
Cc: Andrew Morton
---
(I think this depends on my RCU wakeup source patch sitting in -mm)
fs/eventpoll.c | 22 --
1
On 14 March 2013 04:47, Alexandru Gheorghiu wrote:
> Replaced call to devm_request_and_ioremap with devm_ioremap_resource which
> provides better error handling.
>
> Signed-off-by: Alexandru Gheorghiu
> ---
Already sent a similar patch to do this:
https://patchwork.kernel.org/patch/2211801/
--
T
also has additional information (maybe useful):
arch/arm/kernel/entry-armv.S:404:2: 警告：#warning "NPTL on non MMU needs
fixing" [-Wcpp]
arch/arm/kernel/entry-armv.S:867:2: 警告：#warning "NPTL on non MMU needs
fixing" [-Wcpp]
arch/arm/kernel/entry-armv.S:940:2: 警告：#warning "NPTL on non MMU ne
Hello Maintainers:
when use randconfig:
make V=1 EXTRA_CFLAGS=-W ARCH=arm randconfig
(and "grep CONFIG_MMU .config" outputs "# CONFIG_MMU is not set")
the error information:
arch/arm/kernel/suspend.c: 在函数‘cpu_suspend’中:
arch/arm/kernel/suspend.c:56:32: 错误：提领指向不完全类型的指针
ar
Alexander,
On Wed, Mar 13, 2013 at 4:59 PM, Alexander Graf wrote:
> On my Exynos 5 based Arndale system, I need to pull the reset line down
> and then let it go up again to actually perform a reset. Without that
> reset, I can't find any USB hubs on my bus, rendering the USB controller
> useless.
On 14 March 2013 03:11, Rafael J. Wysocki wrote:
> On Tuesday, March 12, 2013 08:55:12 AM Viresh Kumar wrote:
>> On 12 March 2013 07:38, Rafael J. Wysocki wrote:
>> > One more question before I apply it.
>> >
>> > Is there any architecture/platform that will set
>> > CONFIG_CPU_FREQ_HAVE_MULTIPLE
Technically we do not need to hold ep->mtx during ep_free since we are
certain there are no other users of ep at that point. However, lockdep
complains with a "suspicious rcu_dereference_check() usage!" message;
so lock the mutex before ep_remove to silence the warning.
Signed-off-by: Eric Wong
When we meet a full-id nand type which @mfr_id is true, we can use
the find_full_id_nand() to parse out the neccessary information for a
nand chip.
If we meet a non full-id nand type, we can handle it in the lagacy way.
Signed-off-by: Huang Shijie
---
drivers/mtd/nand/nand_base.c | 36 +++
I have 4 Toshiba nand chips which can not be parsed out by the
id data. We can not get the oob size from the id data. So add them
as the full-id nand chips in the first of nand_flash_ids.
The nand_get_flash_type() scans the full id nands firstly.
If a full-id nand matchs, it will not continue to p
As time goes on, we begin to meet the situation that we can not
get enough information from some nand chips's id data.
Take some Toshiba's nand chips for example.
I have 4 Toshiba's nand chips in my hand:
TC58NVG2S0F, TC58NVG3S0F, TC58NVG5D2, TC58NVG6D2
When we read these chips' datasheets
As time goes on, we begin to meet the situation that we can not get enough
information from some nand chips's id data. Take some Toshiba's nand chips
for example. I have 4 Toshiba's nand chips in my hand:
TC58NVG2S0F, TC58NVG3S0F, TC58NVG5D2, TC58NVG6D2
When we read these chips' datasheets
get_unbound_pool(), workqueue_cpu_up_callback() and init_workqueues()
have similar code pieces to create and start the initial worker factor
those out into create_and_start_worker().
This patch doesn't introduce any functional changes.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 47 ++
Hello,
Currently, workqueue_lock protects most shared workqueue resources -
the pools, workqueues, pool_workqueues, draining, ID assignments,
mayday handling and so on. The coverage has grown organically and
there is no identified bottleneck coming from workqueue_lock, but it
has grown a bit too
When a manager creates or destroys workers, the operations are always
done with the manager_mutex held; however, initial worker creation or
worker destruction during pool release don't grab the mutex. They are
still correct as initial worker creation doesn't require
synchronization and grabbing ma
Currently, workqueue_lock protects most shared workqueue resources -
the pools, workqueues, pool_workqueues, draining, ID assignments,
mayday handling and so on. The coverage has grown organically and
there is no identified bottleneck coming from workqueue_lock, but it
has grown a bit too much and
On Wed, 2013-03-13 at 19:48 -0700, Greg Kroah-Hartman wrote:
> I always defer to the maintainer of the subsystem, so it's up to you.
Great! I'll add them all :-) It just irritates me when I do a stack
trace and see some strange results. Even when I know they are minor and
understand why they ha
This patch continues locking cleanup from the previous patch. It
breaks out pool_workqueue synchronization from workqueue_lock into a
new spinlock - pwq_lock. The followings are protected by pwq_lock.
* workqueue->pwqs
* workqueue->saved_max_active
The conversion is straight-forward. workqueue
With the recent locking updates, the only thing protected by
workqueue_lock is workqueue->maydays list. Rename workqueue_lock to
wq_mayday_lock.
This patch is pure rename.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 24
1 file changed, 12 insertions(+), 12 deleti
They're split across debugobj code for some reason. Collect them.
This patch is pure relocation.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 38 +++---
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
Manager operations are currently governed by two mutexes -
pool->manager_arb and ->assoc_mutex. The former is used to decide who
gets to be the manager and the latter to exclude the actual manager
operations including creation and destruction of workers. Anyone who
grabs ->manager_arb must perfor
On Wed, Mar 13, 2013 at 04:58:12PM -0700, Tejun Heo wrote:
> This patch is on top of wq/for-3.10 e626761691 ("workqueue: implement
> current_is_workqueue_rescuer()").
Oops, forgot the git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git review-misc-cleanups
Thanks.
--
tejun
--
On 14 March 2013 01:34, Alexander Shiyan wrote:
> This patch allow using syscon driver from the platform data, i.e.
> possibility using driver on systems without oftree support.
> For search syscon device from the client drivers,
> "syscon_regmap_lookup_by_pdevname" function was added.
>
> Signed-
On Wed, Mar 13, 2013 at 10:09:05PM -0400, Steven Rostedt wrote:
> Hi Greg,
>
> I was bringing Documentation/trace/ftrace.txt up to date, and obviously
> I found some minor bugs in the code while doing so :-) One of the
> things I've discovered, is that the new -mfentry option for gcc used for
> f
On Thu, Mar 14, 2013 at 05:06:23AM +0400, Sergey Yanovich wrote:
> MMC hosts are added asynchronously. We need to wait until detect returns to
> avoid failed root filesystem mounts.
> ---8<---
> VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6
> Please append a correct "root
Oleg Nesterov wrote:
> On 03/10, Eric Wong wrote:
> >
> > This fixes the following sparse error when using
> > CONFIG_SPARSE_RCU_POINTER=y and "make C=2 fs/eventpoll.o"
> >
> > fs/eventpoll.c:514:17: error: incompatible types in comparison expression
> > (different address spaces)
>
> ep_remov
Hi Tejun,
Today's linux-next merge of the cgroup tree got a conflict in
include/linux/res_counter.h between commit ebf47beb660e
("include/linux/res_counter.h needs errno.h") from Linus' tree and commit
9259826ccb81 ("res_counter: remove include of cgroup.h from
res_counter.h") from the cgroup tree
On Thu, 2013-03-14 at 02:10 +0800, Stephen Warren wrote:
> On 03/12/2013 11:40 PM, Bill Huang wrote:
> > On Wed, 2013-03-13 at 13:24 +0800, Stephen Warren wrote:
> >> On 03/12/2013 11:08 PM, Bill Huang wrote:
> >>> On Wed, 2013-03-13 at 12:42 +0800, Stephen Warren wrote:
> On 03/12/2013 07:47
Hi Greg,
I was bringing Documentation/trace/ftrace.txt up to date, and obviously
I found some minor bugs in the code while doing so :-) One of the
things I've discovered, is that the new -mfentry option for gcc used for
function tracing (for only x86 and gcc >= 4.6.0), the stack tracer gives
some
On Thu, 2013-03-14 at 01:50 +, Ben Hutchings wrote:
> On Tue, 2013-03-12 at 15:31 -0700, Greg Kroah-Hartman wrote:
> > 3.8-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Johannes Berg
> >
> > commit 8a964f44e01ad3bbc208c3e80d
On Wed, 2013-03-13 at 14:23 +1100, Dave Chinner wrote:
> On Mon, Mar 11, 2013 at 11:43:34PM -0700, Michel Lespinasse wrote:
> > Hi Dave,
> >
> > On Mon, Mar 11, 2013 at 7:36 PM, Dave Chinner wrote:
> > > On Sun, Mar 10, 2013 at 10:17:42PM -0700, Michel Lespinasse wrote:
> > >> - since all readers
On Wed, Mar 13, 2013 at 10:07:06PM -0300, Marcelo Tosatti wrote:
> On Wed, Mar 13, 2013 at 12:59:12PM +0800, Xiao Guangrong wrote:
> > The current kvm_mmu_zap_all is really slow - it is holding mmu-lock to
> > walk and zap all shadow pages one by one, also it need to zap all guest
> > page's rmap a
On Wed, Mar 13, 2013 at 12:59:12PM +0800, Xiao Guangrong wrote:
> The current kvm_mmu_zap_all is really slow - it is holding mmu-lock to
> walk and zap all shadow pages one by one, also it need to zap all guest
> page's rmap and all shadow page's parent spte list. Particularly, things
> become wors
Hi Maintainer,
Can you look at the patch which required by some Haswell platforms?
Thanks
-Youquan
On Wed, Mar 06, 2013 at 10:49:05AM -0500, Youquan Song wrote:
> There is a quirk patch 5e5a4f5d5a08c9c504fe956391ac3dae2c66556d
> "ata_piix: make DVD Drive recognisable on systems with Intel Sandy
On Tue, 2013-03-12 at 15:31 -0700, Greg Kroah-Hartman wrote:
> 3.8-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Johannes Berg
>
> commit 8a964f44e01ad3bbc208c3e80d931ba91b9ea786 upstream.
[...]
> --- a/drivers/net/wireless/iwlwifi/pcie
On 03/13/2013 11:35 AM, Eric W. Biederman wrote:
> Kees Cook writes:
>
>> Hi,
>>
>> It seem like we should block (at least) this combination. On 3.9, this
>> exploit works once uidmapping is added.
>>
>> http://www.openwall.com/lists/oss-security/2013/03/13/10
>
> Yes. That is a bad combination
[cc Russell]
On Wed, Mar 13, 2013 at 11:04 PM, Mark Jackson wrote:
> Can any help diagnose what my userspace task is doing to get the followings
> oops ?
>
> [ 42.587772] Unable to handle kernel paging request at virtual address
> bfac6004
> [ 42.595431] pgd = cf748000
> [ 42.598291] [bfac
Hi, Michal
Is there any comments on this?
2013/2/25 Bin Wang :
> KBUILD_OUTPUT is always empty here, so it is useless to test it. But
> while use O=.., objtree and srctree will be different. I compare them
> instead.
>
> Signed-off-by: Bin Wang
> ---
> scripts/package/Makefile | 2 +-
> 1 file
MMC hosts are added asynchronously. We need to wait until detect returns to
avoid failed root filesystem mounts.
---8<---
VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
mmc0: host does not supp
On Tue, 2013-03-12 at 15:31 -0700, Greg Kroah-Hartman wrote:
> 3.8-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Weston Andros Adamson
>
> commit a47970ff7814718fec31b7d966747c6aa1a3545f upstream.
[]
> --- a/fs/nfs/nfs4proc.c
> +++
On 14 March 2013 03:03, Linus Walleij wrote:
> On Wed, Mar 13, 2013 at 9:23 AM, Haojian Zhuang
> wrote:
>
>> pinctrl-pxa driver doesn't support well on DT mode. Now pinctrl-single
>> could support DT mode & pin configuration. Use pinctrl-single driver to
>> support MMP/PXA silicons instead.
>>
>>
On Wed, 2013-03-13 at 04:36 -0700, Michel Lespinasse wrote:
> Have you considered building your ldlock based on lib/rwsem-spinlock.c
> instead ? i.e. having an internal spinlock to protect the ldisc
> reference count and the reader and writer queues. This would seem much
> simpler get right. The do
MMC hosts are added asynchronously. We need to wait until detect returns to
avoid failed root filesystem mounts.
---8<---
VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
mmc0: host does not supp
On Wed, Mar 13, 2013 at 11:44 PM, Borislav Petkov wrote:
> + dri-devel.
>
> On Wed, Mar 13, 2013 at 02:34:31PM +0100, Rolf Offermanns wrote:
>> Hi,
>>
>> I get a kernel oops / panic with a 3.9.0rc2+ kernel (git from 2h ago) on my
>> Sony
>> Vaio laptop. It happened with rc1, too.
>>
>> Unfortunat
On Thu, 14 March 2013 11:20:40 +1100, Stephen Rothwell wrote:
>
> Added from today.
Excellent, thanks!
> One thing, the last few commits from Takashi do not have your
> Signed-off-by even though you committed them.
I think this is not bad enough to destroy history for, but I should
really figur
On my Exynos 5 based Arndale system, I need to pull the reset line down
and then let it go up again to actually perform a reset. Without that
reset, I can't find any USB hubs on my bus, rendering the USB controller
useless.
We also only need to reset the line after the phy node has been found.
Thi
Expose Tegra chip ID and revision in /sys/devices/soc for user mode
usage
Signed-off-by: Danny Huang
---
arch/arm/Kconfig| 1 +
arch/arm/mach-tegra/tegra.c | 29 -
2 files changed, 29 insertions(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/
On Wed, Mar 13, 2013 at 1:53 AM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Since commit 84c1e63c12 (dma: Remove erroneous __exit and __exit_p()
> references)
> the following section mismatch happens:
>
> WARNING: drivers/built-in.o(.text+0x20f94): Section mismatch in reference
> from the f
On Wed, Mar 13, 2013 at 04:50:49PM -0700, Benson Leung wrote:
> +
> +#define BYTE_PER_LINE 8
> +void cyapa_dump_data(struct cyapa *cyapa, size_t length, const u8 *data)
> +{
> +#ifdef DEBUG
> + struct device *dev = &cyapa->client->dev;
> + int i;
> + char buf[BYTE_PER_LINE * 3 + 1];
>
On Wed, 2013-03-13 at 00:17 +0400, Artem Savkov wrote:
> buf needs to be unsigned in dmi_present(), otherwise dmi_base calculation
> doesn't work properly leading to a wraparound during dmi_ioremap:
>
> [0.00] [ cut here ]
> [0.00] WARNING: at arch/x86/mm/io
On 13.03.2013, at 18:59, Doug Anderson wrote:
> Alexander,
>
> On Wed, Mar 13, 2013 at 10:45 AM, Alexander Graf wrote:
>>
+ gpio_free(gpio);
>>>
>>> Freeing the gpio is a little on the iffy side since you actually care
>>> about keeping the value. Perhaps you can change this to
>>
Hello Thomas,
Sorry to miss the V2 in the subject.
I have updated the comments in this new patch, could you consider to take it
into upstream?
Thanks.
Best Regards
Liu chuansheng
> -Original Message-
> From: Liu, Chuansheng
> Sent: Tuesday, March 12, 2013 5:58 PM
> To: t...@linutronix.
On Wed, 2013-03-13 at 10:17 +1100, Michael Neuling wrote:
> Thadeu Lima de Souza Cascardo wrote:
>
> > On Fri, Mar 08, 2013 at 03:29:55AM +, Ben Hutchings wrote:
> > > On Fri, 2013-03-08 at 13:51 +1100, Michael Neuling wrote:
> > > > This patch is breaking the celleb_defconfig on powerpc with
Hi "Jörn",
On Tue, 12 Mar 2013 19:33:11 -0400 Jörn Engel wrote:
>
> On Wed, 13 March 2013 11:11:44 +1100, Stephen Rothwell wrote:
> > On Tue, 12 Mar 2013 14:44:22 -0400 Jörn Engel wrote:
> > >
> > > Any chance to get the bcon tree included?
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/
Hi Stephen,
I am moving the MFD development from mfd-2.6.git/for-next to a new mfd-next
tree:
git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-next.git
Could you please point linux-next at it ? Many thanks in advance.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.in
On 14 March 2013 02:36, Sergey Yanovich wrote:
> 3.8.2 ARM kernel panics on boot. BUG() log:
>
> Where should I look?
It wasn't gcc or ldd. I hit a BUG_ON() in kernel code.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel
* Update incorrect and add missing synchronization labels.
* Update incorrect or misleading comments. Add new comments where
clarification is necessary. Reformat / rephrase some comments.
* drain_workqueue() can be used separately from destroy_workqueue()
but its warning message was incorre
Rename pwq_set_max_active() to pwq_adjust_max_active() and move
pool_workqueue->max_active synchronization and max_active
determination logic into it.
The new function should be called with workqueue_lock held for stable
workqueue->saved_max_active, determines the current max_active value
the targ
Since 9e8cd2f589 ("workqueue: implement apply_workqueue_attrs()"),
init_and_link_pwq() may be called to initialize a new pool_workqueue
for a workqueue which is already online, but the function was setting
pwq->max_active to wq->saved_max_active without proper
synchronization.
Fix it by calling pw
There's no reason to make these trivial wrappers full (exported)
functions. Inline the followings.
queue_work()
queue_delayed_work()
mod_delayed_work()
schedule_work_on()
schedule_work()
schedule_delayed_work_on()
schedule_delayed_work()
keventd_up()
Signed-off-by: Tejun Heo
---
includ
pwq_set_max_active() is gonna be modified and used during
pool_workqueue init. Move it above init_and_link_pwq().
This patch is pure code reorganization and doesn't introduce any
functional changes.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 40
Rename @id argument of for_each_pool() to @pi so that it doesn't get
reused accidentally when for_each_pool() is used in combination with
other iterators.
This patch is purely cosmetic.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 16
1 file changed, 8 insertions(+), 8 del
Hello,
This patchset contains mostly cleanups and a fix for a bug in the new
unbound pools w/ attrs.
This patchset contains the following six patches.
0001-workqueue-relocate-pwq_set_max_active.patch
0002-workqueue-implement-and-use-pwq_adjust_max_active.patch
0003-workqueue-fix-max_active-ha
Ingo,
While testing my new code I stumbled upon this bug. This is a real
bug and has been in the kernel forever. Luckily, it's in a feature
that is seldom used. But it can cause a crash if the race is hit.
I based this off of my last pull request of tip/perf/urgent.
Thanks,
-- Steve
Please p
From: Daniel Kurtz
Use the kernel request_firmware API to allow a hotplug script to load new
firmware into CYAPA device. When request_firmware is called by a driver,
the kernel creates 'loading' and 'data' sysfs entries, and generates a
firmware udev event containing the name of a file ("cyapa.b
Add attributes to expose the product_id and firmware_version read
from the device firmware.
Signed-off-by: Dudley Du
Signed-off-by: Benson Leung
---
drivers/input/mouse/cyapa.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/input/mouse/cyapa.c b/drivers/in
Allow the name of the designated firmware to be passed as the
argument to update_fw from user space. This will allow user space
to specify which firmware to load.
Signed-off-by: Benson Leung
---
drivers/input/mouse/cyapa.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
Add a feature to update trackpad firmware via request_firmware to cyapa.
The last patch in the series adds sysfs attributses useful for version
and product identification that a user mode utility will need to
keep track of the current firmware on the device.
This is used today on Chromebook system
1 - 100 of 582 matches
Mail list logo
