On Tuesday, March 18, 2014 2:04 PM, Joel Pelaez Jorge wrote:
>
> This patch fixes the following checkpatch.pl issues caused by the new
> function: ether_addr_copy
>
> Signed-off-by: Joel Pelaez Jorge
> ---
> drivers/staging/slicoss/slicoss.c | 20 ++--
> 1 file changed, 10
Inki Dae wrote:
>
> Applied.
>
> Thanks,
> Inki Dae
>
> 2014-03-17 12:28 GMT+09:00 Daniel Kurtz :
> > The following commit [0] fixed a use-after-free, but left the subdrv
> open
> > in the error path.
> >
> > [0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
> > drm/exynos: Fix freeing issues
On Sat, Mar 15, 2014 at 2:33 AM, wrote:
> From: Dirk Brandewie
>
> Change to use ->stop() callback to do clean up during CPU
> hotplug. The requested P state for an offline core will be used by the
> hardware coordination function to select the package P state. If the
> core is under load when
On Sat, Mar 15, 2014 at 7:34 AM, Rafael J. Wysocki wrote:
> On Friday, March 14, 2014 02:03:56 PM dirk.brande...@gmail.com wrote:
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -1338,6 +1338,9 @@ static int __cpufreq_remove_dev_prepare(struct device
>> *dev,
>> }
>> }
>>
>> +
This patch removes the IRQF_DISABLED flag from FRV architecture
code. It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
arch/frv/kernel/irq-mb93091.c | 8
arch/frv/kernel/irq-mb93093.c | 1 -
arch/frv/kernel/irq-mb93493.c | 4 ++--
Hi,
On 03/05/2014 06:45 AM, Michael Opdenacker wrote:
> This patch removes the use of the IRQF_DISABLED flag
> in several drivers in drivers/scsi/
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
> ---
> drivers/scsi/dtc.c| 2 +-
Hi Mark,
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Monday, March 17, 2014 11:45 PM
> To: Josh Cartwright
> Cc: Harini Katakam; robh...@kernel.org; pawel.m...@arm.com;
> mark.rutl...@arm.com; ijc+devicet...@hellion.org.uk;
> ga...@codeaurora.org;
Hi Mark,
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Monday, March 17, 2014 11:00 PM
> To: Harini Katakam
> Cc: robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com;
> ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; r...@landley.net;
>
On Sat, Mar 15, 2014 at 7:29 AM, Rafael J. Wysocki wrote:
> I honestly don't think that ->target drivers will ever do anything like it,
> because they need the governor to "exit" before. So we are talking about the
> only two ->setpolicy drivers in the tree here.
I don't have a example platform
Hi,
It was a long weekend in India due to some holidays and so couldn't reply.
On Fri, Mar 14, 2014 at 11:59 PM, Dirk Brandewie
wrote:
> On 03/14/2014 10:07 AM, Viresh Kumar wrote:
> Suspend and hotplug are two very different things and if we start
> crossing those wires bad things are going to
This patch fixes the following checkpatch.pl issues caused by the new
function: ether_addr_copy
Signed-off-by: Joel Pelaez Jorge
---
drivers/staging/slicoss/slicoss.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/staging/slicoss/slicoss.c
Applied.
Thanks,
Inki Dae
2014-03-17 12:28 GMT+09:00 Daniel Kurtz :
> The following commit [0] fixed a use-after-free, but left the subdrv open
> in the error path.
>
> [0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
> drm/exynos: Fix freeing issues in exynos_drm_drv.c
>
> Change-Id:
On Tue, Mar 18, 2014 at 1:19 PM, Namhyung Kim wrote:
> It's because thread__find_addr_map() clears al->filtered, so filtering
> with -d option won't work. Maybe we can move initialization of the
> al->filtered upto this function.
Oh, I meant the -c/--comms option actually :)
Thanks,
Namhyung
hi, linux kernel 3.4.83 cross reference is added into www.xrefs.info.
check it out... Thx. xrefs.info admin
--
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 Tue, Mar 18, 2014 at 5:08 AM, Arnaldo Carvalho de Melo
wrote:
> Em Mon, Mar 10, 2014 at 04:43:53PM +0900, Namhyung Kim escreveu:
>> @@ -749,9 +750,6 @@ int perf_event__preprocess_sample(const union perf_event
>> *event,
>> if (thread == NULL)
>> return -1;
>>
>> - if
Hi Eric,
Today's linux-next merge of the audit tree got conflicts in
arch/mips/include/asm/syscall.h and arch/mips/kernel/ptrace.c between
commits cdda64d4d01f ("MIPS: asm: syscall: Define syscall_get_arch"),
d74c2862 ("MIPS: ptrace: Move away from secure_computing_strict") and
f5179287b016
CC maintainer improves patch aerodynamics.
On Mon, 2014-03-17 at 19:05 -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> If the sched_clock time starts at a large value, the kernel will spin
> in sched_avg_update for a long time while rq->age_stamp catches up
> with rq->clock.
>
> The
On Mon, Mar 17, 2014 at 6:41 PM, David Miller wrote:
> From: Ben Chan
> Date: Mon, 17 Mar 2014 17:46:27 -0700
>
>> Thanks again for the review and tip. I've submitted patch v2 to
>> address the le16_to_cpu conversion.
>
> When you update a patch from a series, you should repost the entire
>
This patch adds the MBIM extended functional descriptor structure
defined in "Universal Serial Bus Communications Class Subclass
Specification for Mobile Broadband Interface Model, Revision 1.0,
Errata-1" published by USB-IF.
Signed-off-by: Ben Chan
---
No changes from patch v1.
According to "Universal Serial Bus Communications Class Subclass
Specification for Mobile Broadband Interface Model, Revision 1.0,
Errata-1" published by USB-IF, the wMTU field of the MBIM extended
functional descriptor indicates the operator preferred MTU for IP data
streams.
This patch modifies
On 2014/3/14 3:50, Tejun Heo wrote:
> Hello,
>
> The planned unified hierarchy is just around the corner. We're gonna
> repurpose the dummy hierarchy to serve as the default unified
> hierarchy. Controllers which aren't attached to other hierarchies are
> already automatically bound to the
On Tue, 2014-03-18 at 12:38 +0900, Jingoo Han wrote:
> In addition to this, there are the same cases like this,
> in this file as below. Please search other same cases.
> For instance, 'grep' will be a good way to find it.
[]
> static void slic_adapter_set_hwaddr(struct adapter *adapter)
> {
>
On Mon, 2014-03-17 at 16:36 -0700, H. Peter Anvin wrote:
> Add predicate functions for having arch_get_random[_seed]*(). The
> only current use is to avoid the loop in arch_random_refill() when
> arch_get_random_seed_long() is unavailable.
Paul, I think our HW rng on P7+ and later would qualify
On Tuesday, March 18, 2014 12:18 PM, Joel Pelaez Jorge wrote:
>
> This patch fixes the following checkpatch.pl issues caused by the new
> function: ether_addr_copy
>
> Signed-off-by: Joel Pelaez Jorge
> ---
> diff --git a/drivers/staging/slicoss/slicoss.c
> b/drivers/staging/slicoss/slicoss.c
>
ame for function dgap_do_bios_load
patch generated against: next-20140317
Signed-off-by: Masood Mehmood
---
drivers/staging/dgap/dgap.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/dgap/dgap.c b/drivers/staging/dgap/dgap.c
index bfafe7e..bbacbba 100
On Tue, 2014-03-18 at 11:28 +1100, Finn Thain wrote:
> This patch series addresses several issues with NCR5380 drivers:
[]
> 3. Broken debugging code.
My preference would be to change dprintk to scsi_dbg
Seems sensible otherwise.
--
To unsubscribe from this list: send the line "unsubscribe
This patch fixes the following checkpatch.pl issues caused by the new
function: ether_addr_copy
Signed-off-by: Joel Pelaez Jorge
---
diff --git a/drivers/staging/slicoss/slicoss.c
b/drivers/staging/slicoss/slicoss.c
index 12aafe3..4ff39aa 100644
--- a/drivers/staging/slicoss/slicoss.c
+++
On Mon, Mar 17, 2014 at 06:30:38PM +0100, Peter Zijlstra wrote:
> On Mon, Mar 17, 2014 at 09:48:15AM -0700, Paul E. McKenney wrote:
> > Good point, this barrier is a bit obsure. Here you go:
> >
> > /*
> > * Make sure this load happens before the purportedly
> > * time-consuming
Signed-off-by: Wenyou Yang
---
arch/arm/mach-at91/pm_slowclock.S | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-at91/pm_slowclock.S
b/arch/arm/mach-at91/pm_slowclock.S
index 2001877..842ddaf 100644
--- a/arch/arm/mach-at91/pm_slowclock.S
+++
Due to enable CONFIG_AT91_SLOW_CLOCK
Signed-off-by: Wenyou Yang
---
arch/arm/configs/sama5_defconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/sama5_defconfig b/arch/arm/configs/sama5_defconfig
index dc3881e..a15879c 100644
--- a/arch/arm/configs/sama5_defconfig
Hi Nicolas,
The patches is to add support to enter standby mode for ARMv7,
then enabling the feature to disable main oscillator
when suspending to memory for sama5d3x.
The patches is based on branch, for-next and at91/cleanup
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
Best
socs: at91sam9x5, at91sam9n12, sama5d3
Signed-off-by: Wenyou Yang
---
arch/arm/mach-at91/pm.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c
index 8bda1ce..7280d09 100644
--- a/arch/arm/mach-at91/pm.c
+++
Now kmemcheck_pagealloc_alloc() is only called by __alloc_pages_slowpath().
__alloc_pages_nodemask()
__alloc_pages_slowpath()
kmemcheck_pagealloc_alloc()
And the page will not be tracked by kmemcheck in the following path.
__alloc_pages_nodemask()
Hi Antoine,
On Mon, 17 Mar 2014 08:06:26 -0700
Antoine Ténart wrote:
> Adds initial support for the Marvell Armada 1500 pro (BG2Q) SoC (Berlin
> family). The SoC has nodes for cpu, l2 cache controller, interrupt
> controllers, local timer, apb timers and uarts for now.
>
> Signed-off-by:
On Mon, Mar 17, 2014 at 06:14:34PM +0100, Peter Zijlstra wrote:
> On Mon, Mar 17, 2014 at 09:58:07AM -0700, Paul E. McKenney wrote:
> > @@ -4111,6 +4115,7 @@ int __sched __cond_resched_softirq(void)
> > {
> > BUG_ON(!in_softirq());
> >
> > + rcu_cond_resched();
>
> Don't you have to
On 03/17/2014 11:24 AM, Alex Shi wrote:
> On 03/13/2014 01:57 PM, Alex Shi wrote:
>> In the cpu_load decay usage, we mixed the long term, short term load with
>> balance bias, randomly pick a big/small value from them according to balance
>> destination or source. This mix is wrong, the balance
By the way, I tried to get the error message, but my display had gone
in standby mode before it completed and it wouldn't wake up. I'll have
to test with an earlier 3.14 kernel (rc1 or rc2), when it was answering
to my wake up signal. Even though my display doesn't wake up with rc6,
it is
From: Micky Ching
Using non-DMA dump-regs, which would be more exactly for DMA transfer failed.
More careful handle when cmd/data timeout, add stop(CMD12) cmd before go to
finish request when multi-rw timeout.
Remove some static checher warings.
on commit:
From: Micky Ching
commit a27fbf2f067b0cd6f172c8b696b9a44c58bfaa7a
produced a cmd.flags unhandled in realtek pci host driver.
This will make MMC card failed initialize, this patch is
used to handle the new cmd.flags condition and MMC card can be used.
Signed-off-by: Micky Ching
---
From: Micky Ching
Add new command type(R1 without CRC) handle, without this patch mmc card
initialize will be failed.
Using a more careful handle in request timeout, and debug info is printed
using non DMA mode. Smatch warning was removed.
Micky Ching (2):
mmc: rtsx: add R1-no-CRC mmc
From: Ben Chan
Date: Mon, 17 Mar 2014 17:46:27 -0700
> Thanks again for the review and tip. I've submitted patch v2 to
> address the le16_to_cpu conversion.
When you update a patch from a series, you should repost the entire
patch set, rather than just the patch which changes.
This avoids any
This patch fixes the following checkpatch.pl issues caused by the new
function: ether_addr_copy
Signed-off-by: Joel Pelaez Jorge
---
diff --git a/drivers/staging/slicoss/slicoss.c
b/drivers/staging/slicoss/slicoss.c
index 12aafe3..4ff39aa 100644
--- a/drivers/staging/slicoss/slicoss.c
+++
Hi,
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. Wysocki
> Sent: Tuesday, March 18, 2014 9:13 AM
>
> On Tuesday, March 18, 2014 12:31:54 AM Zheng, Lv wrote:
> > Hi, Rafael
> >
> > > From: Wysocki, Rafael J
> > > Sent: Monday, March
Hi,
On 03/18/2014 09:38 AM, s...@ring0.de wrote:
> Hi,
>
> On Mon, Mar 17, 2014 at 09:43:43PM +0900, Chanwoo Choi wrote:
>> This patchset add DT helper function to get power-supply device from
>> devicetree.
>> - of_power_supply_get_dev(struct device *dev, enum power_supply_dev_type
>> type,
From: Richard Cochran
Date: Sun, 16 Mar 2014 14:29:22 +0100
> + /* Check to see if any other pin previously had this function. */
> + if (mutex_lock_interruptible(>pincfg_mux))
> + return -ERESTARTSYS;
> + for (i = 0; i < info->n_pins; i++) {
> + if
Thanks Gerald for reviewing and sorry for not elaborated it in the e-mail.
Firstly, I think you can't call module_put after fail try_module_get
Secondly, there exists duplicate module_put on the program path (the last
one is before return 0)
On Mon, Mar 17, 2014 at 9:28 PM, Gerald Schaefer
Previously 'background_gc={on***,off***}' is being parsed as correct option,
with this patch we cloud fix the trivial bug in mount process.
Change log from v1:
o need to check length of parameter suggested by Jaegeuk Kim.
Signed-off-by: Chao Yu
---
fs/f2fs/super.c |4 ++--
1 file changed,
Hi,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Tuesday, March 18, 2014 8:33 AM
> To: Chao Yu
> Cc: linux-f2fs-de...@lists.sourceforge.net; linux-fsde...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [f2fs-dev] [PATCH] f2fs: fix
On Tuesday, March 18, 2014 12:31:54 AM Zheng, Lv wrote:
> Hi, Rafael
>
> > From: Wysocki, Rafael J
> > Sent: Monday, March 17, 2014 8:09 PM
> >
> > On 3/17/2014 5:14 AM, Lv Zheng wrote:
> > > This feature enabled by the following commit is still under development.
> > >
> > >Commit:
Hi, Sabrina and Valdis
Could you give this patch a try to see if this patch is working?
Thanks and best regards
-Lv
> From: Zheng, Lv
> Sent: Monday, March 17, 2014 12:15 PM
>
> From: Robert Moore
>
> It is reported that the auto-serialization mechanism has broken some
> machine. This patch
Only the NCR5380_dprint() macro should invoke the NCR5380_print() function.
That's why NCR5380.c only defines the function #if NDEBUG. Use the standard
macro.
Signed-off-by: Finn Thain
---
drivers/scsi/sun3_scsi.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
Index:
HOSTS_C is always undefined. There is no hosts.c anymore.
Signed-off-by: Finn Thain
---
drivers/scsi/g_NCR5380.h |3 ---
drivers/scsi/mac_scsi.h |3 ---
drivers/scsi/pas16.h |3 ---
drivers/scsi/sun3_scsi.h |3 ---
drivers/scsi/t128.h |3 ---
5 files changed, 15
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c |2 --
drivers/scsi/NCR5380.h |4
drivers/scsi/g_NCR5380.c |4
drivers/scsi/g_NCR5380.h |4
drivers/scsi/mac_scsi.c |4
drivers/scsi/mac_scsi.h |4
drivers/scsi/sun3_scsi.c |4
The mkret() change a value of error from positive to
negative. This patch is modified to return negative value
when it failed. It doesn't need to call with function
for changing from positive to negative.
Signed-off-by: Daeseok Youn
---
v2: fix a typo in subject
this patch is rebased in
On Mon, Mar 17, 2014 at 2:27 PM, Bjørn Mork wrote:
>
> This sounds all reasonable to me. Thanks for taking the time to explain
> it in such detail. I did know that some vendors set wMaxSegmentSize too
> low, but had no idea that vendors were using the extended descriptor
> instead of
There are three implementations of the core NCR5380 driver and three sets
of debugging macro definitions. And all three implementations use the
NCR5380.h header as well.
Two of the definitions of the dprintk macro accept a variable argument list
whereas the third does not. Standardize on the
All NCR5380 drivers already include the NCR5380.h header. Better to
adopt those macros rather than have three variations on them.
Moreover, the macros in NCR5380.h are preferable because the atari_NCR5380
and sun3_NCR5380 versions are inflexible. For example, they can't accomodate
Remove the unused (and divergent) debugging macro definitions from
the sun3_NCR5380 and atari_NCR5380 drivers. These drivers have been
converted to use the common macros in NCR5380.h.
Signed-off-by: Finn Thain
---
drivers/scsi/atari_scsi.h | 93 ---
All NCR5380 drivers already include the NCR5380.h header. Better to
adopt those macros rather than have three variations on them.
Moreover, the macros in NCR5380.h are preferable anyway: the atari_NCR5380
and sun3_NCR5380 versions are inflexible. For example, they can't accomodate
The sun3 drivers suffer from a whole bunch of duplicated code. Fix this
by following the g_NCR5380_mmio example. (Notionally, sun3_scsi relates to
sun3_scsi_vme in the same way that g_NCR5380 relates to g_NCR5380_mmio.)
Dead code is also removed: we now have working debug macros so
Move the #include "NCR5380.h" out of the sun3_scsi.h header file and into
the driver .c files, like all the other NCR5380 drivers in the tree.
This improves uniformity and reduces the depth of nested includes. The
sequence of #include's, #define's and #if's no longer does my head in.
All three NCR5380 core driver implementations share the same NCR5380.h
header file so they need to agree on certain macro definitions.
The flag bit used by the NDEBUG_MERGING macro in atari_NCR5380 and
sun3_NCR5380 collides with the bit used by NDEBUG_LISTS.
Moreover, NDEBUG_ABORT appears in
BOARD_NORMAL is completely unused and BOARD_NCR53C400 is used only by
g_NCR5380 internally. Remove the unused definitions.
Signed-off-by: Finn Thain
---
drivers/scsi/arm/cumana_1.c |3 ---
drivers/scsi/arm/oak.c |3 ---
drivers/scsi/mac_scsi.h |3 ---
(Second attempt... sorry for the earlier spam.)
This patch series addresses several issues with NCR5380 drivers:
1. The complex network of #include directives.
2. Three inconsistent implementations of the core driver all attempting
to share the same macro definitions in NCR5380.h.
3.
The change from cmd->target to cmd->device->id was apparently the purpose of
commit a7f251228390e87d86c5e3846f99a455517fdd8e in
kernel/git/tglx/history.git but some instances have been missed.
Also fix the "NDEBUG_LAST_WRITE_SENT" and "NDEBUG_ALL" typo's.
Also fix some format strings (%ul
Hi,
On Mon, Mar 17, 2014 at 09:43:43PM +0900, Chanwoo Choi wrote:
> This patchset add DT helper function to get power-supply device from
> devicetree.
> - of_power_supply_get_dev(struct device *dev, enum power_supply_dev_type type,
> int index)
> Power-supply class
On 03/17/2014 02:43 AM, Jan Kara wrote:
> On Mon 17-03-14 10:21:18, Jan Kara wrote:
>> On Fri 14-03-14 11:33:31, John Stultz wrote:
>>> + for (;;) {
>>> + unsigned long new_flags;
>>> + pgoff_t pgoff;
>>> + unsigned long tmp;
>>> +
>>> + if (!vma)
>>> +
On Tue, Mar 18, 2014 at 09:26:07AM +0900, DaeSeok Youn wrote:
> I think vmalloc/kmalloc in uislib_malloc() can be removed and just use
> vmalloc/kmalloc directly.
Yes. Actually, just use kmalloc, I don't knwo why vmalloc is being
used, but cc: the driver maintainers just to be sure.
>
Hi,
2014-03-17 (월), 17:40 +0800, Chao Yu:
> Previously 'background_gc={on***,off***}' is being parsed as correct option,
> with this patch we cloud fix the trivial bug in mount process.
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/super.c |4 ++--
> 1 file changed, 2 insertions(+), 2
Hi, Rafael
> From: Wysocki, Rafael J
> Sent: Monday, March 17, 2014 8:09 PM
>
> On 3/17/2014 5:14 AM, Lv Zheng wrote:
> > This feature enabled by the following commit is still under development.
> >
> >Commit: cd52379678785b02d7a357988cfba214fdaf92f4
> >Subject: ACPICA: Add global option
On Fri, Mar 14, 2014 at 09:48:35AM +0800, Ming Lei wrote:
> On Fri, Mar 14, 2014 at 12:08 AM, Bjorn Helgaas wrote:
> > On Thu, Mar 13, 2014 at 2:51 AM, Ming Lei wrote:
> >> Hi Bjorn,
> >>
> >> I found this patch broke virtio-pci devices.
> >
> > Thanks a lot for testing this.
> >
> >> On Thu,
I think vmalloc/kmalloc in uislib_malloc() can be removed and just use
vmalloc/kmalloc directly.
(UISMALLOC() macro is also removed.)
And uislib_malloc() is renamed to "uislib_trace_buffer_status()" which
is just tracing buffer status(Malloc_FailuresAlloc, Malloc_BytesInUse
...) for
On Mon, 2014-03-17 at 18:21 -0400, Tejun Heo wrote:
> So, looked at the failed code. The only necessary change seems to be
> calling device_remove_file_self() in dump_ack_store() and then doing
> kobject_put() directly afterwards, which would have been completely
> fine as a merge fix patch.
Ok.
Hi all,
Today's linux-next merge of the mvebu tree got a conflict in
arch/arm/boot/dts/Makefile between commit 8fc1b0f87d9f ("ARM: qcom: Split
Qualcomm support into legacy and multiplatform") from the arm-soc tree
and commits 97623e934388 ("Merge branch 'mvebu/dt' into for-next") and
54cab10f63f2
On Thu, 2013-12-19 at 11:51 -0800, tip-bot for Len Brown wrote:
> Commit-ID: 40e2d7f9b5dae048789c64672bf3027fbb663ffa
> Gitweb: http://git.kernel.org/tip/40e2d7f9b5dae048789c64672bf3027fbb663ffa
> Author: Len Brown
> AuthorDate: Wed, 18 Dec 2013 16:44:57 -0500
> Committer: H. Peter
pcmd->parmbuf->pbuf has been allocated if command is
GEN_CMD_CODE(_Set_Drv_Extra),
and it enqueued by rtw_enqueue_cmd. rtw_cmd_thread dequeue pcmd by
rtw_dequeue_cmd.
The memory leak happened on this branch "if( _FAIL == rtw_cmd_filter(pcmdpriv,
pcmd) )"
which goto post_process directly against
On Mon, 2014-03-17 at 14:56 -0700, Greg KH wrote:
> No you can't, sorry.
>
> And this seems like a huge abuse of sysfs, you better be using binary
> sysfs files for your log data...
>
> Do you have a pointer to where you document this sysfs api in
> Documentation/ABI/ ?
Yes, the patch adds the
Tejun Heo writes:
> On Mon, Mar 17, 2014 at 06:05:54PM -0400, Tejun Heo wrote:
>> I think this is being blown out of proportion. It was a rarely used
>> API and converting to the new one is mostly trivial which can be
>
> So, looked at the failed code. The only necessary change seems to be
>
From: Corey Minyard
If the sched_clock time starts at a large value, the kernel will spin
in sched_avg_update for a long time while rq->age_stamp catches up
with rq->clock.
The comment in kernel/sched/clock.c says that there is no strict promise
that it starts at zero. So initialize
Hi all,
Given that 3.14 will be out in a few days, it's time to close my trees
for new patches until 3.15-rc1 is out.
Please feel free to send me patches for these trees, but note that I'll
be ignoring them until 3.15-rc1 is out, at which point in time I'll
start reviewing them again and
Greg KH writes:
> On Tue, Mar 18, 2014 at 07:33:30AM +1100, Benjamin Herrenschmidt wrote:
>> On Mon, 2014-03-17 at 11:33 -0700, Greg KH wrote:
>>
>> > There were only 3 (or 4), users of this api, and no new ones had been
>> > added in _years_, it's a very obscure thing, and odds are, it wouldn't
According to "Universal Serial Bus Communications Class Subclass
Specification for Mobile Broadband Interface Model, Revision 1.0,
Errata-1" published by USB-IF, the wMTU field of the MBIM extended
functional descriptor indicates the operator preferred MTU for IP data
streams.
This patch modifies
On Tue, Mar 11, 2014 at 02:36:09PM -0400, David Long wrote:
> git://git.linaro.org/people/dave.long/linux.git uprobes-v7
>
> for you to fetch changes up to e55c35236b8adf79453a998506ec6081833b9484:
>
> ARM: add uprobes support (2014-03-11 11:40:29 -0400)
I pulled this a week ago into my
[+cc Daniel, Dave, Yinghai, Guo, Aaron, LKML]
On Sat, Mar 15, 2014 at 02:32:22PM +0200, Jouni Mettälä wrote:
> Hi. I can't start xsession without iommu=remap=2 kernel parameter.
>
> Kernel bisect lead to this commit
>
The crypto algorithm modules utilizing the crypto daemon could
be used early when the system start up. Using module_init
does not guarantee that the daemon's work queue is initialized
when the cypto alorithm depending on crypto_wq starts. It is necessary
to initialize the crypto work queue
Hi Ohad,
On 03/17/2014 02:47 PM, Ohad Ben-Cohen wrote:
> Hi Suman,
>
> On Mon, Mar 17, 2014 at 9:10 PM, Suman Anna wrote:
>> base_id would be a property (if added) of the hwspinlock controller node,
>> and from DT perspective, we will be using the phandle for the controller
>> anyway. So, using
Hi Philipp,
On Friday 14 March 2014 13:19:39 Philipp Zabel wrote:
> Am Donnerstag, den 13.03.2014, 18:13 +0100 schrieb Laurent Pinchart:
> > On Thursday 13 March 2014 12:08:16 Philipp Zabel wrote:
> > > Am Montag, den 10.03.2014, 14:37 + schrieb Grant Likely:
> > > > > > Nak. I made comments
Upcoming Intel silicon adds a new RDSEED instruction, which is similar
to RDRAND but provides a stronger guarantee: unlike RDRAND, RDSEED
will always reseed the PRNG from the true random number source between
each read. Thus, the output of RDSEED is guaranteed to be 100%
entropic, unlike RDRAND
Add predicate functions for having arch_get_random[_seed]*(). The
only current use is to avoid the loop in arch_random_refill() when
arch_get_random_seed_long() is unavailable.
Signed-off-by: H. Peter Anvin
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
---
Use arch_get_random_seed*() in two places in the Linux random
driver (drivers/char/random.c):
1. During entropy pool initialization, use RDSEED in favor of RDRAND,
with a fallback to the latter. Entropy exhaustion is unlikely to
happen there on physical hardware as the machine is
If we have arch_get_random_seed*(), try to use it for emergency refill
of the entropy pool before giving up and blocking on /dev/random. It
may or may not work in the moment, but if it does work, it will give
the user better service than blocking will.
Reviewed-by: Ingo Molnar
Signed-off-by: H.
Upcoming Intel silicon adds a new RDSEED instruction. Whereas RDRAND
returns output from a PRNG, the RDSEED instruction returns fully
conditioned entropy that is suitable for use as seeds to a PRNG.
This patchset adds support for RDSEED in the Linux kernel in three
places:
1. During bootup, use
t mm/mlock.c:512!
[ 1753.914387] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 1753.914387] Dumping ftrace buffer:
[ 1753.914387](ftrace buffer empty)
[ 1753.914387] Modules linked in:
[ 1753.914387] CPU: 26 PID: 36822 Comm: trinity-c337 Tainted: G
W 3.14.0-rc6-next-20140317-s
Hi Robert,
On Friday 14 March 2014 08:05:05 Robert Schwebel wrote:
> On Thu, Mar 13, 2014 at 04:13:08PM +0100, Sylwester Nawrocki wrote:
> > My experience and feelings are similar, I started to treat mainline
> > kernel much less seriously after similar DT related blocking issues.
>
> So how do
Ok. I will rebase this patch in staging-next branch and send it again.
Thanks.
Daeseok Youn.
2014-03-18 6:23 GMT+09:00 Greg KH :
> On Mon, Mar 10, 2014 at 08:54:18AM +0900, Daeseok Youn wrote:
>>
>> The mkret() change a value of error from positive to
>> negative. This patch is modified to
On Wed, Mar 12, 2014 at 10:24:21AM +0900, Nobuhiro Iwamatsu wrote:
> Register for the device are mapped in uio_mmap_physical().
> In this case, it might not be the same as the size of VMA always.
Why wouldn't this be the case?
> This uses PAGE_ALIGN to memory size, fix the check of the memory
> Root cause time: it's wrong for the oom-killer to use SIGKILL. In fact
It has to use SIGKILL anything else might be caught and grow the user
stack a page..
> it's basically always wrong to send signals from in-kernel. Signals
> are a userspace IPC mechanism and using them in-kernel a) makes
On Mon, 17 Mar 2014 16:00:05 +0100 Ralph Mueck wrote:
> This patch introduces a consistency check feature for level-1 RAID
> arrays that have been created with the md driver.
> When enabled, every read request is duplicated and initiated for each
> member of the RAID array. All read blocks are
On Sat, Mar 15, 2014 at 11:49:09PM -0700, Ben Chan wrote:
> This patch adds the MBIM extended functional descriptor structure
> defined in "Universal Serial Bus Communications Class Subclass
> Specification for Mobile Broadband Interface Model, Revision 1.0,
> Errata-1" published by USB-IF.
>
>
On Mon, Mar 17, 2014 at 04:04:04PM -0700, Greg KH wrote:
> On Mon, Mar 10, 2014 at 09:33:37AM +0100, Robert Baldyga wrote:
> > This patch adds missing spin_unlock and mutex_unlock calls in
> > error handling code.
> >
> > Signed-off-by: Robert Baldyga
> > Acked-by: Michal Nazarewicz
> >
1 - 100 of 1248 matches
Mail list logo