From: "Yan, Zheng"
The uncore subsystem in Ivy Bridge-EP is similar to Sandy Bridge-EP.
There are some differences in config register encoding and pci device
IDs. The Ivy Bridge-EP uncore also supports a few new events.
Signed-off-by: Yan, Zheng
---
From: "Yan, Zheng"
The existing code assumes all Cbox and PCU events are using
filter, but actually the filter is event specific. Furthermore
the filter is sub-divided into multiple fields which are used
by different events.
Signed-off-by: Yan, Zheng
Reported-by: Stephane Eranian
---
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
block/blk-core.c between commit f79ea4161434 ("block: Refactor
blk_update_request()") from the block tree and commit "block, aio: batch
completion for bios/kiocbs" from the akpm tree.
I fixed it up (see below) and can carry
Hi Andrew,
Today's linux-next merge of the akpm tree got conflicts in
drivers/md/raid1.c and drivers/md/raid10.c between commit 9e882242c619
("block: Add submit_bio_wait(), remove from md") from the block tree and
commit "block: prep work for batch completion" from the akpm tree.
I fixed it up
On Mon, Mar 25, 2013 at 02:04:16PM +0100, Michal Hocko wrote:
> On Fri 22-03-13 16:23:50, Naoya Horiguchi wrote:
> [...]
> > @@ -523,6 +544,11 @@ static inline int check_pmd_range(struct
> > vm_area_struct *vma, pud_t *pud,
> > pmd = pmd_offset(pud, addr);
> > do {
> > next =
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
include/linux/blk_types.h between commit a38352e0ac02 ("block: Add an
explicit bio flag for bios that own their bvec") from the block tree and
commit "mm: make snapshotting pages for stable writes a per-bio
operation" from the
On Tue, 26 Mar 2013 13:57:09 +1030 Rusty Russell wrote:
> Alexandru Gheorghiu writes:
>
> > Used PTR_RET function instead of IS_ERR and PTR_ERR.
> > Patch found using coccinelle.
>
> WTF is PTR_RET? PTR_RET doesn't return anything. Why is it called
> that? It doesn't even make sense.
>
>
Alexandru Gheorghiu writes:
> Used PTR_RET function instead of IS_ERR and PTR_ERR.
> Patch found using coccinelle.
WTF is PTR_RET? PTR_RET doesn't return anything. Why is it called
that? It doesn't even make sense.
ZERO_OR_PTR_ERR() maybe.
But what problem are we solving? Insufficient
'data' is a pointer and hence use NULL instead of 0.
Silences the following warning:
drivers/mfd/max77686.c:49:50: warning: Using plain integer as NULL pointer
Signed-off-by: Sachin Kamat
Cc: Jonghwa Lee
---
drivers/mfd/max77686.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
On Thu, 2013-03-21 at 01:41 +, Ben Hutchings wrote:
> On Wed, 2013-03-20 at 21:43 +0100, Sebastian Gottschall (DD-WRT) wrote:
> > Am 20.03.2013 20:02, schrieb Sebastian Gottschall (DD-WRT):
> > > Hello
> > >
> > > The patch for sa_restorer will break mips builds, since sa_restorer
> > > isnt
Hi experts,
I didn't this patch merged to any git tree or maybe I missed.
Where is the right place for send X.509 patch?
Thanks a lot!
Joey Lee
於 四，2013-03-14 於 15:34 +0800，Lee, Chun-Yi 提到：
> From: Chun-Yi Lee
>
> Per X.509 spec in 4.2.1.1 section, the structure of Authority Key
>
On Mon, Mar 25 2013, Dave Chinner wrote:
> On Mon, Mar 25, 2013 at 05:39:13PM -0700, Greg Thelen wrote:
>> On Mon, Mar 25 2013, Dave Chinner wrote:
>> > On Mon, Mar 25, 2013 at 10:22:31AM -0700, Greg Thelen wrote:
>> >> Call cond_resched() from shrink_dentry_list() to preserve
>> >>
On Mon, Mar 25, 2013 at 01:31:28PM +0100, Michal Hocko wrote:
> On Fri 22-03-13 16:23:48, Naoya Horiguchi wrote:
> > Currently migrate_huge_page() takes a pointer to a hugepage to be
> > migrated as an argument, instead of taking a pointer to the list of
> > hugepages to be migrated. This behavior
Fix below build error:
CC drivers/clocksource/exynos_mct.o
drivers/clocksource/exynos_mct.c:557:1: error: expected '=', ',', ';', 'asm' or
'__attribute__' before '__unused'
drivers/clocksource/exynos_mct.c:558:1: error: expected '=', ',', ';', 'asm' or
'__attribute__' before '__unused'
On Mon, Mar 25, 2013 at 11:57:01AM +0100, Michal Hocko wrote:
> On Fri 22-03-13 16:23:47, Naoya Horiguchi wrote:
...
> > diff --git v3.9-rc3.orig/mm/hugetlb.c v3.9-rc3/mm/hugetlb.c
> > index 98a478e..a787c44 100644
> > --- v3.9-rc3.orig/mm/hugetlb.c
> > +++ v3.9-rc3/mm/hugetlb.c
> > @@ -48,7 +48,8
From: Len Brown
3e7fc708eb (ia64 idle: delete pm_idle) in 3.9-rc1
didn't finish the job, leaving an un-initialized
reference to (*idle)().
Reported-by: Lars-Peter Clausen
Signed-off-by: Len Brown
---
arch/ia64/kernel/process.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff
On Mon, Mar 25, 2013 at 11:13:40AM +0100, Michal Hocko wrote:
> On Fri 22-03-13 16:23:46, Naoya Horiguchi wrote:
> > When we have a page fault for the address which is backed by a hugepage
> > under migration, the kernel can't wait correctly until the migration
> > finishes. This is because
On 26 March 2013 07:30, Viresh Kumar wrote:
> On 25 March 2013 22:37, David Miller wrote:
>> From: Viresh Kumar
>> Date: Mon, 25 Mar 2013 22:24:44 +0530
>>
>>> This patch moves cpufreq driver of SPARK architecture to drivers/cpufreq.
>>
>> I don't know what spark is.
>
> :(
>
> s/spark/sparc
On 3/25/2013 7:38 PM, Eric W. Biederman wrote:
> Mike Travis writes:
>
>> This patch adds some significant KDB functions to be usable by
>> externally built and loadable KDB modules. All added functions
>> have been marked EXPORT_SYMBOL_GPL as that seems to be the norm.
>> No
(SSBI) driver") which added the Kconfig symbol MSM_SSBI (later changed to
just SSBI) which did not exist in the tree before. However,
MFD_PM8921_CORE depended on it and that selects MFD_PM8XXX which allows
the above file to build (and fail).
I have used the char-misc tree from next-20130325
On Mon, Mar 25, 2013 at 11:32:11AM +0100, Paul Bolle wrote:
> Commit c1fb6816fb1b78dd94b673b0fdaa9a7a16e97bd1 ("powerpc: Add
> relocation on exception vector handlers") added two lines of code that
> depend on the macro CONFIG_HVC_SCOM. That macro doesn't exist. Perhaps
> it was intended to use
On 03/25/2013 07:52 PM, 周洲仪 wrote:
> Thanks for reviewing
> Is it sounds good to add following line into section "Boot into System
> Kernel":
>
> The memory reserved for crash kernel should be no less than the unpacked
> init ram disk size
> that loaded with dump-capture kernel plus wired
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in
drivers/usb/serial/usb-serial.c between commit 6aad04f21374 ("TTY: add
tty_port_tty_wakeup helper") from the tty tree and commit d12e211d4484
("USB: serial: clean up debug info") from the usb tree.
I fixed it up (I just used the
From: Sahara
This fixes a number of sparse warnings like:
warning: incorrect type in argument 2 (different address spaces)
expected void volatile [noderef] *addr
got unsigned int *
warning: Using plain integer as NULL pointer
Additionally this fixes a warning from checkpatch.pl
> > - idle = pm_idle;
> > if (!idle)
>
> Hm, if I'm not mistaken idle will uninitialized at this point, so this
> could quite likely lead to a crash.
thanks,
will fix.
-Len
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 2013年03月26日 10:47, Nicolas Pitre wrote:
> On Tue, 26 Mar 2013, Chen Gang wrote:
>
>> a hacker may find something "valuable" with the aid of compiler ;-)
>>
>> maybe, it is a patch which is too minor to apply. I can understand :-)
>
> You should send such patches to Jiri Kosina .
>
> CONFIG_GENERIC_FIND_NEXT_BIT was removed in v3.0, but reappeared in two
> architectures. Remove it again.
>
> Signed-off-by: Paul Bolle
> ---
> 0) Untested.
>
> 1) See commit 63e424c84429903c92a0f1e9654c31ccaf6694d0 ("arch: remove
> CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT}") for the
On Tue, 26 Mar 2013, Chen Gang wrote:
> a hacker may find something "valuable" with the aid of compiler ;-)
>
> maybe, it is a patch which is too minor to apply. I can understand :-)
You should send such patches to Jiri Kosina .
Nicolas
--
To unsubscribe from this list: send the line
On 03/25/2013 10:31 PM, Mike Galbraith wrote:
[snip]
>>
>> Do you mean 1ms interval is still too big? and you prefer to have a 0
>> option?
>
> Not really, I just think a fixed interval may not be good enough without
> some idle time consideration. Once a single load gets going less
> balancing
When we do hot plug for pci devices that were injected aer errors, some newly
created child buses'
pci_ops will be assigned to pci_ops_aer. Aer_inject module will not track these
pci_ops_aer(not
list in pci_bus_ops_list),so we should clean all of these when rmmod aer_inject
module.
Rewrite pci_bus_ops_list release code for simplification, and clean
no used function pci_bus_ops_pop().
Reviewed-by: Huang Ying
Signed-off-by: Yijing Wang
---
drivers/pci/pcie/aer/aer_inject.c | 25 ++---
1 files changed, 6 insertions(+), 19 deletions(-)
diff --git
When we rmmod aer_inject module, there is a small race condition window between
pci_bus_ops_pop()
and pci_bus_set_ops() in aer_inject_exit, eg. pci_read_aer/pci_write_aer was
called between
them. So keep pci_bus_ops_list until pci_bus_set_ops complete, use
list_for_each_entry() instead of
When we injected aer errors to the pcie device by aer_inject module, pci_ops of
the pci
bus the device on will be assigned to pci_ops_aer.So if the target pci device
is a bridge, once we hot-remove and hot-add the bridge, the newly created child
bus's pci_ops
will be assigned to pci_ops_aer
When Inject aer errors to the target pci device, a pci_bus_ops will
be allocated for the pci device's pci bus.When the pci bus was removed,
we should also release the pci_bus_ops.
Signed-off-by: Yijing Wang
Reviewed-by: Sven Dietrich
---
drivers/pci/pcie/aer/aer_inject.c | 49
Hi Tony,
Can you pick up these bug fix patches into your ras tree? I sent them to PCI
subsystem maillist, but Bjorn does not seem
very interested in these aer_inject tool bug fix patches. Huang Ying
is the author of aer_inject tool.
And I had a long discussion with Huang Ying about these
On Mon, Mar 25, 2013 at 05:39:13PM -0700, Greg Thelen wrote:
> On Mon, Mar 25 2013, Dave Chinner wrote:
> > On Mon, Mar 25, 2013 at 10:22:31AM -0700, Greg Thelen wrote:
> >> Call cond_resched() from shrink_dentry_list() to preserve
> >> shrink_dcache_parent() interactivity.
> >>
> >> void
Mike Travis writes:
> This patch adds some significant KDB functions to be usable by
> externally built and loadable KDB modules. All added functions
> have been marked EXPORT_SYMBOL_GPL as that seems to be the norm.
> No 'EXPORT_SYMBOL's were changed from previous instances to avoid
>
--
I am Akilah Saeedi, i have 7.100,000.00 USD for you contact me on my provide
email for more details.
- Vidarebefordrat
--
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
On 2013年03月26日 09:48, Greg KH wrote:
> On Tue, Mar 26, 2013 at 09:22:57AM +0800, Chen Gang wrote:
>> On 2013年03月26日 07:32, Greg KH wrote:
>>> On Mon, Mar 25, 2013 at 10:36:22AM +0800, Chen Gang wrote:
better to let 'inline' in front of 'void'
>>>
>>> Why? What does this fix?
>>>
>>>
Adding support for supplied_from char * array. This is meant to store the
list of suppliers for a given supply, i.e. chargers for a battery. This
list can be populated through devicetree readily as well as passed
directly from the driver.
Signed-off-by: Rhyland Klein
---
v1:
- Changed from RFC
This property is meant to be used in device nodes which represent
power_supply devices that wish to provide a list of supplies which
provide them power, such as a battery listing its chargers.
Signed-off-by: Rhyland Klein
---
v1:
- changed from RFC v2 -> patch v1
- made poropery plural as it
This patch adds support for supplies to register a list of char *'s
which represent the list of supplies which supply them. This is the
opposite as the supplied_to list.
This change maintains support for supplied_to until all drivers which
make use of it already are converted.
Signed-off-by:
This series defines a common way for devicetree initialized
power_supplies to define their relationships between chargers and
supplicants.
This series adds a supplied_from array to complement the supplied_to
array and to allow supplies to define the list of supplies which
supply them.
Then once
On 03/25/2013 05:53 PM, John Stultz wrote:
> On 03/25/2013 03:36 PM, Arnd Bergmann wrote:
>> On Monday 25 March 2013, Rob Herring wrote:
>>> I count integrator-cp, realview, versatile and non-DT VExpress that do
>>> this (not surprisingly) and 25 platforms or timer implementations plus
>>> arm64
On 03/25/13 11:00, Mark Rutland wrote:
>
>>> I've spent the last few hours trying to get the dummy_timer driver working
>>> on
>>> tc2 with the sp804 as the broadcast source (with architected timer support
>>> disabled). It turns out that having dummy timer's rating so low means that
>>> it
>>>
The following changes since commit 3912a677f68f6084e0a7b6a1a29310ac1b083713:
Merge tag 'pinctrl-fixes-for-v3.9' of
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl (2013-03-24
10:11:29 -0700)
are available in the git repository at:
> From: Wei Yongjun
>
> sizeof() when applied to a pointer typed expression gives the size of the
> pointer,
> not that of the pointed data.
>
> Signed-off-by: Wei Yongjun
> ---
> drivers/mailbox/mailbox.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
drivers/md/raid5.c between commit e3620a3ad526 ("MD RAID5: Avoid
accessing gendisk or queue structs when not available") from Linus' tree
and commit 2f6db2a70734 ("raid5: use bio_reset()") from the block tree.
I fixed it up
On 25 March 2013 22:37, David Miller wrote:
> From: Viresh Kumar
> Date: Mon, 25 Mar 2013 22:24:44 +0530
>
>> This patch moves cpufreq driver of SPARK architecture to drivers/cpufreq.
>
> I don't know what spark is.
:(
s/spark/sparc ...
I will fix patch in V2..
--
To unsubscribe from this
On 03/25/2013 05:59:16 PM, Paul Bolle wrote:
Signed-off-by: Paul Bolle
---
Documentation/cgroups/memory.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Rob Landley
Rob--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 03/25/2013 03:55:28 PM, Matt Turner wrote:
On Mon, Mar 25, 2013 at 1:06 PM, Michael Cree
wrote:
> On 26/03/2013, at 4:09 AM, Tobias Klausmann wrote:
>>
>> On Mon, 25 Mar 2013, Will Deacon wrote:
>>>
>>> Any news on these? I've included an updated version of the first
patch,
>>> with
>>>
On Tue, Mar 26, 2013 at 09:22:57AM +0800, Chen Gang wrote:
> On 2013年03月26日 07:32, Greg KH wrote:
> > On Mon, Mar 25, 2013 at 10:36:22AM +0800, Chen Gang wrote:
> >>
> >> better to let 'inline' in front of 'void'
> >
> > Why? What does this fix?
> >
> >
> >
>
> when I am compiling with
On Tue, Mar 26, 2013 at 10:31:22AM +0900, Damian Hobson-Garcia wrote:
> Until recently uio_get_minor() returned 0 for success and
> a negative value on failure. This became non-negative for suceess and
> negative for failure. Restore the original return value spec so that we can
> successfully
Until recently uio_get_minor() returned 0 for success and
a negative value on failure. This became non-negative for suceess and
negative for failure. Restore the original return value spec so that we can
successfully initialize UIO devices with a non-zero minor device
number.
Signed-off-by:
On 2013年03月26日 07:32, Greg KH wrote:
> On Mon, Mar 25, 2013 at 10:36:22AM +0800, Chen Gang wrote:
>>
>> better to let 'inline' in front of 'void'
>
> Why? What does this fix?
>
>
>
when I am compiling with "EXTRA_FLAGS=-W", I get a warning:
make V=1 EXTRA_CFLAGS=-W ARCH=arm
On Mon, Mar 25 2013, Philip J. Kelleher wrote:
> From: Philip J Kelleher
>
> This patch removes dynamic allocation on the stack error.
>
> Signed-off-by: Philip J Kelleher
> ---
>
>
> diff -uprN -X
Hi John,
Today's linux-next merge of the wireless-next tree got a conflict in
net/mac80211/sta_info.c between commit 27a737ff7cb0 ("mac80211: always
synchronize_net() during station removal") from the wireless tree and
commits 3b8d9c290364 ("mac80211: remove underscores from some key
functions")
Allow threads other than the main thread to do introspection of files in
proc without relying on read permissions. proc_pid_follow_link() calls
proc_fd_access_allowed() which ultimately calls __ptrace_may_access().
Though this allows additional access to some proc files, we do not
believe
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/wireless/core.h between commit f9f475292dbb ("cfg80211: always check
for scan end on P2P device") from the wireless tree and commit
812569699119 ("cfg80211/mac80211: disconnect on suspend") from the
net-next tree.
I
On Mon, Mar 25, 2013 at 07:10:35PM +0100, Lars-Peter Clausen wrote:
> On 03/25/2013 06:59 PM, Sören Brinkmann wrote:
> > Hi,
> >
> > On Mon, Mar 25, 2013 at 06:19:11PM +0100, Lars-Peter Clausen wrote:
> >> On 03/25/2013 06:08 PM, Sören Brinkmann wrote:
> >>> Hi Lars,
> >>>
> >>> On Mon, Mar 25,
2013/3/25, Jaegeuk Kim :
> In the checkpoint flow, the f2fs investigates the total nat cache entries.
> Previously, if an entry has NULL_ADDR, f2fs drops the entry and adds the
> obsolete nid to the free nid list.
> However, this free nid will be reused sooner, resulting in its nat entry
> miss.
>
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/mac80211/sta_info.c between commit 27a737ff7cb0 ("mac80211: always
synchronize_net() during station removal") from the wireless tree and
commit 8d1f7ecd2af5 ("mac80211: defer tailroom counter manipulation when
roaming")
2013/3/25, Jaegeuk Kim :
> This patch removes data_version check flow during the fsync call.
> The original purpose for the use of data_version was to avoid writng inode
> pages redundantly by the fsync calls repeatedly.
Hi Jaegeuk.
> However, when user can modify file meta and then call fsync, we
On Mon, Mar 25 2013, Dave Chinner wrote:
> On Mon, Mar 25, 2013 at 10:22:31AM -0700, Greg Thelen wrote:
>> Call cond_resched() from shrink_dentry_list() to preserve
>> shrink_dcache_parent() interactivity.
>>
>> void shrink_dcache_parent(struct dentry * parent)
>> {
>> while ((found =
2013/3/25, Jaegeuk Kim :
> 2013-03-25 (월), 15:30 +0900, Namjae Jeon:
>> 2013/3/25, Jaegeuk Kim :
>> > We should handle errors during the recovery flow correctly.
>> > For example, if we get -ENOMEM, we should report a mount failure instead
>> > of
>> > conducting the remained mount procedure.
>> >
On 03/25/2013 05:16:24 AM, Paul Bolle wrote:
Signed-off-by: Paul Bolle
---
Documentation/kbuild/makefiles.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Acked-by: Rob Landley
Please send through the kbuild tree.
Rob
diff --git a/Documentation/kbuild/makefiles.txt
Hi Russell,
Russell King - ARM Linux writes:
> On Wed, Mar 20, 2013 at 05:01:58PM -0700, Kevin Hilman wrote:
>> Add ARM support for the context tracking subsystem by instrumenting
>> exception entry/exit points.
>>
>> Special thanks to Mats Liljegren for testing, collaboration and adding
>>
On 25-03-2013 14:22, Greg KH wrote:
On Tue, Mar 19, 2013 at 10:54:25AM -0400, Eduardo Valentin wrote:
This patch updates the documentation to remove
all warnings and errors reported by scripts/kernel-doc.
Most are missing arguments due to wrong format.
Cc: Nishanth Menon
Signed-off-by:
On 03/22/13 07:07, Thomas Meyer wrote:
> Am Samstag, den 16.03.2013, 10:38 -0700 schrieb Randy Dunlap:
>> On 03/16/13 08:08, Thomas Meyer wrote:
>>> Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
>>> Yes,
>>>
>>> so why not do this? As the text to EARLY_PRINTK explains?
>>
>> Yes,
On 03/21/13 19:02, zhangwei(Jovi) wrote:
> There don't have any EXPERT menu guard, and no config item is
> included in EXPERT menu, so change it as a config, not menu.
>
> This will make user more clear when they use 'make menuconfig'
> or 'make nconfig'.
>
> Signed-off-by: zhangwei(Jovi)
> Cc:
From: Magnus Damm
This patch is V3 of a GPIO driver for the R-Car series of
SoCs from Renesas. This driver is designed to be reusable
between multiple SoCs that share the same basic building block,
but so far it has only been used on R-Car H1 (r8a7779).
Each driver instance handles 32 GPIOs
On Fri, 15 Mar 2013, Nicolas Schichan wrote:
>
> Signed-off-by: Nicolas Schichan
> ---
> kernel/seccomp.c |2 ++
> 1 file changed, 2 insertions(+)
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next
--
James Morris
--
To unsubscribe from this list:
From: Lai Jiangshan
We're expanding wq->mutex to cover all fields specific to each
workqueue with the end goal of replacing pwq_lock which will make
locking simpler and easier to understand.
wq->nr_drainers and ->flags are specific to each workqueue. Protect
->nr_drainers and ->flags with
From: Lai Jiangshan
We're expanding wq->mutex to cover all fields specific to each
workqueue with the end goal of replacing pwq_lock which will make
locking simpler and easier to understand.
init_and_link_pwq() and pwq_unbound_release_workfn() already grab
wq->mutex when adding or removing a
From: Lai Jiangshan
To simplify locking, the previous patches expanded wq->mutex to
protect all fields of each workqueue instance including the pwqs list
leaving pwq_lock without any user. Remove the unused pwq_lock.
tj: Rebased on top of the current dev branch. Updated description.
From: Lai Jiangshan
We're expanding wq->mutex to cover all fields specific to each
workqueue with the end goal of replacing pwq_lock which will make
locking simpler and easier to understand.
This patch makes wq->saved_max_active protected by wq->mutex instead
of pwq_lock. As pwq_lock locking
From: Lai Jiangshan
wq->flush_mutex will be renamed to wq->mutex and cover all fields
specific to each workqueue and eventually replace pwq_lock, which will
make locking simpler and easier to understand.
Rename wq_mutex to wq_pool_mutex to avoid confusion with wq->mutex.
After the scheduled
Hello,
This patchset renames wq->flush_mutex to wq->mutex and expands it to
protect most fields which are specific to each workqueue instance.
This simplifies the locking and makes it easier to understand. The
mutex was already half there with multiple pool_workqueues support for
unbound
From: Lai Jiangshan
Currently pwq->flush_mutex protects many fields of a workqueue
including, especially, the pwqs list. We're going to expand this
mutex to protect most of a workqueue and eventually replace pwq_lock,
which will make locking simpler and easier to understand.
Drop the "flush_"
On Mon, Mar 25, 2013 at 05:29:33PM -0600, Stephen Warren wrote:
> On 03/22/2013 04:41 PM, Sören Brinkmann wrote:
> > Hi Lars,
> >
> > On Thu, Mar 21, 2013 at 07:32:52PM +0100, Lars-Peter Clausen wrote:
> >> On 03/21/2013 12:56 AM, Sören Brinkmann wrote:
> >>> Hi,
> >>>
> >>> I spent some time
On Mon, Mar 25, 2013 at 05:33:10PM -0600, Stephen Warren wrote:
> On 03/25/2013 12:27 PM, Sören Brinkmann wrote:
> > Hi Stephen,
> >
> > On Mon, Mar 25, 2013 at 12:13:08PM -0600, Stephen Warren wrote:
> >> On 03/20/2013 05:56 PM, Sören Brinkmann wrote:
> >>> Hi,
> >>>
> >>> I spent some time
2013/03/23 5:24, Toshi Kani wrote:
On Fri, 2013-03-22 at 10:53 +0900, Yasuaki Ishimatsu wrote:
acpi_memory_info has enabled bit and failed bit for controlling memory
hotplug. But we don't need to keep both bits.
The patch removes acpi_memory_info->failed bit.
Signed-off-by: yasuaki ishimatsu
From: Darrick J. Wong
The dm-cache writethrough strategy introduced by commit e2e74d617eadc15
("dm cache: fix race in writethrough implementation") issues a bio to
the origin device, remaps and then issues the bio to the cache device.
This more conservative in-series approach was selected to
On Mon, Mar 25, 2013 at 10:22:31AM -0700, Greg Thelen wrote:
> Call cond_resched() from shrink_dentry_list() to preserve
> shrink_dcache_parent() interactivity.
>
> void shrink_dcache_parent(struct dentry * parent)
> {
> while ((found = select_parent(parent, )) != 0)
>
On Tue, Mar 26, 2013 at 09:52:14AM +1000, Dave Airlie wrote:
> >>> Because it's the only way to get the PCI ROM in some cases, like on
> >>> pretty much all Apples with Radeons. Only using it if we have no other
> >>> options probably makes sense, though. Something like this (entirely
> >>>
>>> Because it's the only way to get the PCI ROM in some cases, like on
>>> pretty much all Apples with Radeons. Only using it if we have no other
>>> options probably makes sense, though. Something like this (entirely
>>> untested)?
>>
>> This looks reasonable. Mantas?
>
> It compiles, boots, and
Quoting Prashant Gaikwad (2013-03-20 05:00:34)
> Not all clocks are required to be decomposed into basic clock
> types but at the same time want to use the functionality
> provided by these basic clock types instead of duplicating.
>
> For example, Tegra SoC has ~100 clocks which can be
On Monday, March 25, 2013 7:15 PM, Mark Brown wrote:
>
> On Mon, Mar 25, 2013 at 02:12:21PM +0900, Jingoo Han wrote:
> > On Saturday, March 23, 2013 1:16 AM, Guennadi Liakhovetski wrote:
>
> > But, there is a typo in comment.
> > > + * At least one su2-auto-curr* must be specified iff
>
On 03/25/2013 12:27 PM, Sören Brinkmann wrote:
> Hi Stephen,
>
> On Mon, Mar 25, 2013 at 12:13:08PM -0600, Stephen Warren wrote:
>> On 03/20/2013 05:56 PM, Sören Brinkmann wrote:
>>> Hi,
>>>
>>> I spent some time working on this and incorporating feedback. Here's an
>>> updated proposal for a
On Mon, Mar 25, 2013 at 10:36:22AM +0800, Chen Gang wrote:
>
> better to let 'inline' in front of 'void'
Why? What does this fix?
--
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
Commit 90173882ed15a8034d6d162da5f343a2c7d87587 ("omap: add dsp platform
device") used CONFIG_BRIDGE_DVFS were it obviously meant
CONFIG_TIDSPBRIDGE_DVFS. Fix that.
Signed-off-by: Paul Bolle
---
Untested. As this typo has been in the tree since v2.6.37, this really
needs some testing.
On 03/22/2013 04:41 PM, Sören Brinkmann wrote:
> Hi Lars,
>
> On Thu, Mar 21, 2013 at 07:32:52PM +0100, Lars-Peter Clausen wrote:
>> On 03/21/2013 12:56 AM, Sören Brinkmann wrote:
>>> Hi,
>>>
>>> I spent some time working on this and incorporating feedback. Here's an
>>> updated proposal for a
Hi Boaz,
Fetching the osd tree
(git://git.open-osd.org/linux-open-osd.git#linux-next) produces a time
out and this error:
fatal: read error: Connection reset by peer
I will continue to use the last osd tree I fetched.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
Hector,
On Mon, Mar 25, 2013 at 4:31 PM, Fabio Estevam wrote:
> Hi Hector,
>
> On Mon, Mar 25, 2013 at 7:52 AM, Hector Palacios
> wrote:
>> Hello,
>>
>> I just tried recording audio on Freescale's MX28EVK that uses ASoC sgtl5000
>> (kernel v3.8) with:
>>
>> arecord -M -f cd sound.wav
On 26/03/13 09:40, Andrew Morton wrote:
> On Fri, 22 Mar 2013 17:15:49 +0100 Guennadi Liakhovetski
> wrote:
>
>> Add support for configuring AS3711 backlight driver from DT.
>>
>> Signed-off-by: Guennadi Liakhovetski
>> Reviwed-by: Mark Brown
>> ---
>> drivers/video/backlight/as3711_bl.c |
On Mon, 2013-03-25 at 23:29 +0100, Rafael J. Wysocki wrote:
> On Monday, March 25, 2013 02:45:36 PM Toshi Kani wrote:
> > On Fri, 2013-03-15 at 11:47 +0100, Vasilis Liaskovitis wrote:
> > > Hi,
> > >
> > > On Thu, Mar 14, 2013 at 06:16:30PM +0100, Rafael J. Wysocki wrote:
> > > > Sorry for the
On Mon, Mar 25, 2013 at 09:28:10PM +, Rob Herring wrote:
> On 03/25/2013 12:26 PM, Russell King - ARM Linux wrote:
> > On Thu, Mar 21, 2013 at 11:06:47AM +, Mark Rutland wrote:
> >> On TC2 this series leads to using the vexpress 24MHz clock as the sched
> >> clock
> >> in preference to
Hi Sakari,
On Sunday 24 March 2013 23:46:01 Sakari Ailus wrote:
> Pali Rohár wrote:
> > On Thursday 07 March 2013 23:18:27 Sakari Ailus wrote:
> >> On Wed, Mar 06, 2013 at 10:44:41PM +0100, Sebastian Reichel wrote:
> >>> On Wed, Mar 06, 2013 at 09:20:16PM +0100, Pali Rohár wrote:
> On
TI omap2 mcspi allows the slave devices to configure the behavior of
the SPI master. This patch adds device tree support to the existing
options.
Signed-off-by: Matthias Brugger
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 23
drivers/spi/spi-omap2-mcspi.c
Wei Yongjun writes:
> From: Wei Yongjun
>
> Fix to return a negative error code from the error handling
> case instead of 0, as returned elsewhere in this function.
>
> Signed-off-by: Wei Yongjun
Thanks, I've taken this for the moment in my pending queue.
Which brings the questionL Ohad, did
1 - 100 of 1182 matches
Mail list logo
