On Wed, Mar 26, 2014 at 01:03:00PM +0800, Jason Wang wrote:
> Current error handling of virtqueue_kick() was wrong in two places:
> - The skb were freed immediately when virtqueue_kick() fail during
> xmit. This may lead double free since the skb was not detached from
> the virtqueue.
> - try_f
(2014/03/22 9:49), Steven Rostedt wrote:
> On Wed, 05 Mar 2014 20:59:11 +0900
> Masami Hiramatsu wrote:
>
>
>>
>> diff --git a/Documentation/kprobes.txt b/Documentation/kprobes.txt
>> index 0cfb00f..7062631 100644
>> --- a/Documentation/kprobes.txt
>> +++ b/Documentation/kprobes.txt
>> @@ -22,8
On Wednesday, March 26, 2014 at 02:27:46 PM, Marek Vasut wrote:
> On Wednesday, March 26, 2014 at 06:56:34 AM, Yao Yuan wrote:
> > On Wednesday, March 26, 2014 at 11:43:27 AM, Marek Vasut wrote:
> > > On Wednesday, March 26, 2014 at 04:08:27 AM, Yao Yuan wrote:
> > >
> > > [...]
> > >
> > > > > > +
On Thu, 2014-01-16 at 13:47 +0800, hongbo.zh...@freescale.com wrote:
> From: Hongbo Zhang
>
> The usage of spin_lock_irqsave() is a stronger locking mechanism than is
> required throughout the driver. The minimum locking required should be used
> instead. Interrupts will be turned off and context
This patch modifies mfd driver to use regmap for handling interrupts.
It allows to simplify irq handling process. This modifications needed
to make small changes in function drivers, which use interrupts.
Signed-off-by: Robert Baldyga
---
drivers/mfd/Kconfig |2 +-
drivers/m
Hi Lee,
>From: Lee Jones [mailto:lee.jo...@linaro.org]
>Obtain IRQ number and request IRQ resource via the usual methods. We're
>also registering an IRQ handler to inform us of any completed tasks.
>Notice that we're starting to make use of the device struct that we
>defined before. In keeping wit
On Tue, Mar 25, 2014 at 06:42:13PM -0400, Mikulas Patocka wrote:
>
>
> On Mon, 24 Mar 2014, Daniel Vetter wrote:
>
> > >> Like I've said the entire teardown sequence for legacy drm drivers is
> > >> terminally busted, so the only hope we have is to reapply this missing
> > >> duct-tape which mad
>From: Lee Jones [mailto:lee.jo...@linaro.org]
>
>Add support for clocks when, and only when, they are supplied. It is
>not yet compulsory to provide the BCH and EMI clocks, as Common Clk isn't
>supported Mainline yet. Until an implementation lands upstream all clocks
>located on STM boards default
Hi Surendra,
> To fix the sparse warning "cast to restricted __le32" marked
> "rom_version" to __le32 instead of unsigned int in "struct ath3k_version"
> and added cpu_to_le32() for the expression assigning int value to
> "rom_version".
> Successfully built the module without warnings and errors
> -Original Message-
> From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
> Behalf Of Peter Wu
> Sent: Sunday, March 23, 2014 6:00 AM
> To: Gleb Natapov
> Cc: Venkatesh Srinivas; Peter Zijlstra; Ingo Molnar; Andi Kleen; Linux Kernel
> Developers List; H. Peter Anvin; k.
On Wednesday, March 26, 2014 at 08:08:28 AM, Yao Yuan wrote:
> On Wednesday, March 26, 2014 at 02:27:46 PM, Marek Vasut wrote:
> > On Wednesday, March 26, 2014 at 06:56:34 AM, Yao Yuan wrote:
> > > On Wednesday, March 26, 2014 at 11:43:27 AM, Marek Vasut wrote:
> > > > On Wednesday, March 26, 2014
On Tue, Mar 25, 2014 at 07:00:45PM -0300, Ezequiel Garcia wrote:
> After taking a quick glance at the whole driver I noticed you have something
> strange going on. AFAIK, the typical NAND driver probe() should be one of
> these two:
>
> * Call nand_scan() which calls nand_scan_ident() + nand_scan_
On Tue, Mar 11, 2014 at 01:31:26AM -0300, Erico Nunes wrote:
> Mention to CONFIG_MTD_ECC_BCH in the warning message can be confusing as this
> doesn't match the exact name of the configuration option.
> This warning showed up once to me when I was starting to set up BCH. After
> checking my .config
On Wed, 2014-03-26 at 08:10 +0100, Robert Baldyga wrote:
> This patch modifies mfd driver to use regmap for handling interrupts.
> It allows to simplify irq handling process. This modifications needed
> to make small changes in function drivers, which use interrupts.
>
> Signed-off-by: Robert Bald
fix a sparse warning.
drivers/staging/vt6655/iwctl.c:1846:35: warning: cast from restricted
gfp_t
drivers/staging/vt6655/iwctl.c:1846:35: warning: incorrect type in
argument 2 (different base types)
drivers/staging/vt6655/iwctl.c:1846:35:expected restricted gfp_t
[usertype] flags
drivers/stagin
> This patch modifies mfd driver to use regmap for handling interrupts.
> It allows to simplify irq handling process. This modifications needed
> to make small changes in function drivers, which use interrupts.
>
> Signed-off-by: Robert Baldyga
> ---
> drivers/mfd/Kconfig |2
Below is the list of build error/warning regressions/improvements in
v3.14-rc8[1] compared to v3.13[2].
Summarized:
- build errors: +10/-30
- build warnings: +93/-79
JFYI, when comparing v3.14-rc8[1] to v3.14-rc7[3], the summaries are:
- build errors: +6/-1
- build warnings: +19/-15
As
> I realise that you and Alessandro are very busy (I have not often seen
> Alessandro do any posting in the past fortnight), but a couple of weeks
> ago I sent an RTC patch set with register.h changes ...
>
> >> From: Opensource [Steve Twiss]
> >>
> >> Add the RTC driver for DA9063.
>
> >> The
On Wed, Mar 26, 2014 at 8:47 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v3.14-rc8[1] to v3.14-rc7[3], the summaries are:
> - build errors: +6/-1
+ /scratch/kisskb/src/arch/powerpc/include/asm/io.h: error:
'virt_phys_offset' undeclared (first use in this function): =>
814:16, 807:1
于 2014/3/26 0:25, Satoru Takeuchi 写道:
> At Tue, 25 Mar 2014 16:58:58 +0800,
> Liu hua wrote:
>>
>> 于 2014/3/24 4:50, Satoru Takeuchi 写道:
>>> At Sun, 23 Mar 2014 15:54:04 +0800,
>>> Liu Hua wrote:
As sysctl_hung_task_timeout_sec is unsigned long, when this value is
larger then LONG_MA
For tsc deadline mode, when we shut down clockevent we should disarm
local-APIC timer like count-down mode.
Signed-off-by: wang, biao
Signed-off-by: Zhang Di
---
arch/x86/kernel/apic/apic.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/apic/apic.c b
This patch modifies mfd driver to use regmap for handling interrupts.
It allows to simplify irq handling process. This modifications needed
to make small changes in function drivers, which use interrupts.
Signed-off-by: Robert Baldyga
Reviewed-by: Krzysztof Kozlowski
---
Changelog:
v2:
- fix n
> This patch modifies mfd driver to use regmap for handling interrupts.
> It allows to simplify irq handling process. This modifications needed
> to make small changes in function drivers, which use interrupts.
>
> Signed-off-by: Robert Baldyga
> Reviewed-by: Krzysztof Kozlowski
> ---
>
> Chang
>> I realise that you and Alessandro are very busy (I have not often seen
>> Alessandro do any posting in the past fortnight), but a couple of weeks
>> ago I sent an RTC patch set with register.h changes ...
>>
>> >> From: Opensource [Steve Twiss]
>> >>
>> >> Add the RTC driver for DA9063.
>>
>>
fix an bug related to extension list.
there was the potential bug in set_cold_files function, namei.c.
Signed-off-by: Dongho Sim
---
mkfs/f2fs_format.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
index 9dbdc1d..d485808 1006
On Tue, Mar 25, 2014 at 07:01:10PM +0100, Sam Ravnborg wrote:
> >
> > There are two things that don't work too well with this. First this
> > causes the build to break if the build machine doesn't have the new
> > public header (include/uapi/linux/dma-buf.h) installed yet. So the only
> > way to m
On 26 March 2014 02:29, micky wrote:
> Hi Ulf,
>
> On 03/25/2014 06:44 PM, Ulf Hansson wrote:
>>
>> On 25 March 2014 10:47, wrote:
>>>
>>> From: Micky Ching
>>>
>>> Add new command type(R1 without CRC) handle, without this
>>> patch mmc card initialize will be failed.
>>>
>>> Using a more caref
On Thu, Feb 13, 2014 at 10:15 PM, Paul Gortmaker
wrote:
> While copy_to/from_user_page() users are uncommon, there is one in
> drivers/staging/lustre/lustre/libcfs/linux/linux-curproc.c which leads
> to the following:
>
> ERROR: "sparc32_cachetlb_ops"
> [drivers/staging/lustre/lustre/libcfs/libcf
On Sat, Jan 25, 2014 at 4:23 AM, Oleg Drokin wrote:
> On Jan 24, 2014, at 3:55 AM, Geert Uytterhoeven wrote:
>> On Fri, Jan 24, 2014 at 6:51 AM, Oleg Drokin wrote:
+STAGING - LUSTRE
+M: Andreas Dilger
+M: Oleg Drokin
+M: Peng Tao .
+L: hpdd-discuss
+S: O
Hi,
Huang Shijie wrote:
> On Fri, Mar 21, 2014 at 11:50:17AM +0100, Lothar Waßmann wrote:
> > With a flash-based BBT there is no reason to move the Factory Bad
> > Block Marker from the data area buffer (to where it is mapped by the
> > GPMI NAND controller) to the OOB buffer. Thus, make this feat
(cc akpm, who still uses these scripts, while the rest of the world
moved to git ;-)
On Wed, Mar 26, 2014 at 12:49 AM, Mitchel Humpherys
wrote:
> The link to the tarball for Andrew Morton's patch scripts is dead. These
> scripts don't seem to be used for kernel development these days anyways
> so
On Tue, Mar 18, 2014 at 10:25:27AM -0400, Wang, Xiaoming wrote:
> 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 ==
>
On Tue, 25 Mar, at 03:40:30PM, Roy Franz wrote:
> Add the efi_early_call() macro to invoke functions in the efi_early
> structure. Using a macro for these invocations allows the arm32/arm64
> architectures to define the macro differently so that they can directly
> invoke the boot services function
On Wed, Mar 26, 2014 at 09:44:08AM +0100, Geert Uytterhoeven wrote:
> Ping?
>
> We got a new "fix" for this in due to https://lkml.org/lkml/2014/2/13/479
Given that lustre maintainers aren't willing to fix even the worst crap
like this we really should drop it from the staging tree.
--
To unsubs
On Tue, Mar 25, 2014 at 06:19:24PM +, j...@ringle.org wrote:
> From: Jon Ringle
>
> This patch adds the devicetree documentation for the NXP SC16IS7XX UARTs.
>
> Signed-off-by: Jon Ringle
> ---
> .../devicetree/bindings/serial/nxp,sc16is7xx.txt | 35
> ++
> 1 file ch
On Tue, 25 Mar, at 03:47:23PM, Roy Franz wrote:
>
> I have sent a patch (attempted to reply using git-send-email) that
> adds the macro for x86 and updates efi-stub-helper.c. If you could
> add this to your series for 3.15 that would be great, as then we would
> not have any x86 changes in the AR
Hi Lee,
>From: Lee Jones [mailto:lee.jo...@linaro.org]
>
>Fetch platform specific data from Device Tree. Any functions which
>are useful to other STM NAND Controllers have been separated into a
>separate file so they can be easily referenced by them as they
>appear.
>
>Signed-off-by: Lee Jones
>-
It was impossible to enumerate on a SuperSpeed (XHCI) host
with alternate setting = 1 due to the wrongly set 'bMaxBurst'
field in the SuperSpeed Endpoint Companion descriptor.
Testcase:
modprobe -r usbtest; modprobe usbtest alt=1
modprobe g_zero
plug device to SuperSpeed port on the host.
Witho
Hi Jason,
On 26/03/2014 01:30, Jason Cooper wrote:
> On Tue, Mar 25, 2014 at 11:48:18PM +0100, Gregory CLEMENT wrote:
>> The initial binding for PMSU were wrong. It didn't take into account
>> all the registers from the PMSU and moreover it referred to registers
>> which are not part of PMSU.
>>
>
Il 26/03/2014 08:23, Wu, Feng ha scritto:
Is there a solution for this issue right now? I also met this GPF crash.
Can you attach your .config?
Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
During system resume, if the event buffers are not setup before
the gadget controller starts then we start with invalid context
and this can lead to bus access errors. This is especially true for
platforms that loose the controller context during system suspend.
e.g. AM437x.
The following backtrac
From: Cody P Schafer
> On 03/25/2014 03:43 AM, Anton Blanchard wrote:
> >
> > Hi Cody,
> >
> > hv-24x7: could not obtain capabilities, error 0x
> fffe, not enabling
> > hv-gpci: could not obtain capabilities, error 0x
> fffe, not enabling
> >
> >> + pr_info("could n
This is another one I'd like to send off to James ASAP, can I get some
reviews?
On Mon, Mar 17, 2014 at 06:28:01AM -0700, Christoph Hellwig wrote:
> Instead of letting the ULD play games with the prep_fn move back to
> the model of a central prep_fn with a callback to the ULD. This
> already clea
On 03/26/2014 10:33 AM, Gregory CLEMENT wrote:
On 26/03/2014 01:30, Jason Cooper wrote:
On Tue, Mar 25, 2014 at 11:48:18PM +0100, Gregory CLEMENT wrote:
The initial binding for PMSU were wrong. It didn't take into account
all the registers from the PMSU and moreover it referred to registers
whi
On 26/03/2014 01:42, Jason Cooper wrote:
> Gregory,
>
> On Tue, Mar 25, 2014 at 11:48:11PM +0100, Gregory CLEMENT wrote:
> ...
>> The first patch should go through ARM subsystem and should be taken by
>> Russell King. I made few change on it following Lorenzo advice and
>> now it will reuse the cp
Grant Grundler [mailto:grund...@google.com]
> Sent: Wednesday, March 26, 2014 4:12 AM
[...]
> Hayes,
> I believe this patch was dropped after the series was split.
> Can you please repost this patch by itself?
There is no problem for current behavior, and I don't get the
issue of tx timeout, yet
On 2014/03/26 03:43 AM, Chase Southwood wrote:
> There were just a handful of more while loops in this file that needed
> timeouts, and this patch takes care of them. One new callback is
> introduced, and all of the proper comedi_timeout() calls are then used.
>
> Signed-off-by: Chase Southwood
This patch adds IRQ line specification for the MAX8997 chip and necessary
pinctrl group to configure pull-up and driver strength of the pin.
It's needed for proper handling of IRQs coming from MAX8997 multifunction
device (IRQs are used by PMIC, MUIC and RTC).
Signed-off-by: Robert Baldyga
Review
On Wed, 2014-03-26 at 12:56 +0900, SeongJae Park wrote:
> Fix following trivial build warning:
>
> drivers/net/xen-netback/netback.c: In function ‘xenvif_tx_dealloc_action’:
> drivers/net/xen-netback/netback.c:1585:8: warning:
> format ‘%x’ expects argument of type
> ‘unsigned int’, but argument
In older kernels (before v3.10) ipc_rcu_hdr->refcount was non-atomic int.
There was possuble double-free bug: do_msgsnd() calls ipc_rcu_putref() under
msq->q_perm->lock and RCU, while freequeue() calls it while it holds only
'rw_mutex', so there is no sinchronization between them. Two function
decr
Russell,
Thanks for the reply!
On Mar 26, Russell King - ARM Linux wrote:
> On Tue, Mar 25, 2014 at 07:45:55PM -0300, Ezequiel Garcia wrote:
> >
> > Without this patch we got the heartbeat's reboot_notifier called twice while
> > testing the recent hibernation patches, which was unexpected and p
On Tue, Mar 25, 2014 at 10:12:14PM +, Tanmay Inamdar wrote:
> Hello Liviu,
>
> Thanks for taking a look. Please see inline.
>
> On Tue, Mar 25, 2014 at 7:02 AM, Liviu Dudau wrote:
> > On Wed, Mar 19, 2014 at 11:12:39PM +, Tanmay Inamdar wrote:
> >> This patch adds the AppliedMicro X-Gene
Hi Lee,
>From: Lee Jones [mailto:lee.jo...@linaro.org]
>
>Use DMA to read and/or write a single page of data.
>
>Signed-off-by: Lee Jones
>---
> drivers/mtd/nand/stm_nand_bch.c | 119
> 1 file changed, 119 insertions(+)
>
>diff --git a/drivers/mtd/nand/stm_
Hi Lee,
>From: Lee Jones [mailto:lee.jo...@linaro.org]
missing commit log :-)
Though $subject is self-explanatory, but you can add more description about
assumption and hardware caveats about the controller, and its use.
>
>Signed-off-by: Lee Jones
>---
> drivers/mtd/nand/stm_nand_bch.c | 56 +++
Hi Gregory,
On Mar 25, Gregory CLEMENT wrote:
> @@ -285,4 +290,21 @@ static struct notifier_block
> armada_370_xp_cpu_pm_notifier = {
> .notifier_call = armada_370_xp_cpu_pm_notify,
> };
>
> +int __init armada_370_xp_cpu_pm_init(void)
> +{
> + if (!((of_find_compatible_node(NULL, NUL
Hi Lee,
>From: Lee Jones [mailto:lee.jo...@linaro.org]
>
>Helper function for bch_mtd_read() and bch_mtd_write() to handle
>multi-page or non-aligned reads and writes respectively.
>
>Signed-off-by: Lee Jones
>---
I think below code is duplicate of nand_do_read_ops() and nand_do_write_ops()
in n
Dear Gregory CLEMENT,
On Tue, 25 Mar 2014 23:48:25 +0100, Gregory CLEMENT wrote:
> +int __init armada_370_xp_cpu_pm_init(void)
> +{
> + if (!((of_find_compatible_node(NULL, NULL,
> "marvell,armada-370-xp-pmsu") ||
> + of_find_compatible_node(NULL, NULL,
> "marvel
Hi Alexandre,
Am Mittwoch, den 26.03.2014, 15:33 +0900 schrieb Alexandre Courbot:
> Hi Lucas,
>
> On Mon, Mar 24, 2014 at 10:19 PM, Lucas Stach wrote:
> > Hi Alexandre,
> >
> > Am Montag, den 24.03.2014, 17:42 +0900 schrieb Alexandre Courbot:
> >> Hi everyone,
> > [...]
> >>
> >> A few lines of
Thank you for let me know kindly :)
On Wed, Mar 26, 2014 at 7:09 PM, Ian Campbell wrote:
> On Wed, 2014-03-26 at 12:56 +0900, SeongJae Park wrote:
>> Fix following trivial build warning:
>>
>> drivers/net/xen-netback/netback.c: In function ‘xenvif_tx_dealloc_action’:
>> drivers/net/xen-netback/ne
On 01/08/2014 02:39 AM, Tony Lindgren wrote:
> * Taras Kondratiuk [131223 10:20]:
>> On 23 December 2013 20:10, Taras Kondratiuk
>> wrote:
>>> This series does trivial replacement of __raw_xxx functions with xxx_relaxed
>>> endian-neutral variants in 'mach-omap2' and 'plat-omap' directories.
>>>
On 26/03/2014 11:31, Thomas Petazzoni wrote:
> Dear Gregory CLEMENT,
>
> On Tue, 25 Mar 2014 23:48:25 +0100, Gregory CLEMENT wrote:
>
>> +int __init armada_370_xp_cpu_pm_init(void)
>> +{
>> +if (!((of_find_compatible_node(NULL, NULL,
>> "marvell,armada-370-xp-pmsu") ||
>> +
I don't know if it is a valid idea, but maybe it would be ok to process
events after resume in general, and only throw away events on those
platforms that continue to log events while in standby (Samsung 5/7/9)?
But after all, it would be better to find the command to tell the EC to
stop recording
于 2014年03月26日 16:51, Lothar Waßmann 写道:
I don't see why this should not be supported on i.MX28 (i.MX23 doesn't
do byteswapping anyway, so this wouldn't change anything for i.MX23).
The partitions used by Linux need not necessarily be accessible for the
Boot ROM code (and vice versa).
But the fir
On 03/26/2014 10:28 AM, Roger Quadros wrote:
> Bug was introduced by commit cf9a08ae in v3.9
I'm sorry for the trouble.
Acked-by: Sebastian Andrzej Siewior
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
On 24/03/14 09:26, Ian Campbell wrote:
On Fri, 2014-03-21 at 17:23 +, Zoltan Kiss wrote:
This reverts commit e9275f5e2df1b2098a8cc405d87b88b9affd73e6. This commit is the
last in the netback grant mapping series, and it tries to do more aggressive
aggreagtion of unmap operations. However prac
On Wed, Mar 26, 2014 at 07:12:27AM -0300, Ezequiel Garcia wrote:
> On Mar 26, Russell King - ARM Linux wrote:
> > On Tue, Mar 25, 2014 at 07:45:55PM -0300, Ezequiel Garcia wrote:
> > >
> > > Without this patch we got the heartbeat's reboot_notifier called twice
> > > while
> > > testing the recen
Paul,
You have been awfully silent for this whole thread while this is a regression
caused by a patch of you
(ca2f09f2b2c6c25047cfc545d057c4edfcfe561c as clearly stated much earlier in
this thread).
The commit messages states:
"net_rx_action() is the place where we could do with an accurate
hrtimer_set_expires_range() and hrtimer_set_expires_range_ns() have almost same
implementations and so we can call hrtimer_set_expires_range() from
hrtimer_set_expires_range_ns() internally, instead of duplicating code.
Signed-off-by: Viresh Kumar
---
include/linux/hrtimer.h | 3 +--
1 file chan
Hi Thomas,
I am going through this piece of code to complete my 'cpusets.quiesce' work.
While going through code I accumulated these patches which are mostly code
cleanups and shouldn't have much functional change.
Thanks for applying yesterdays cleanups :)
Viresh Kumar (14):
hrtimer: replace
retrigger_next_event() is defined within #ifdef CONFIG_HIGH_RES_TIMERS and we
already have pointer to base available. So it makes more sense to simply use
base->hres_active instead of doing this by calling hrtimer_hres_active():
__this_cpu_read(hrtimer_bases.hres_active)
Signed-off-by: Vi
In init_timers() we need to call init_timers_cpu() for boot CPU. For this,
currently we are emulating a call to hotplug notifier. Probably this was done
initially to get rid of code redundancy. But this sequence always called a
single routine, i.e. init_timers_cpu(), and so calling that routine dir
Caller of hrtimer_switch_to_hres(), i.e. hrtimer_run_pending(), has already
verified this by calling hrtimer_hres_active() and so we don't need to do it
again in hrtimer_switch_to_hres().
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kerne
clock_was_set_delayed() is called from only hrtimer.c and so should be marked
static. Along with that its declaration and dummy definition must be removed
from hrtimer.h.
Signed-off-by: Viresh Kumar
---
include/linux/hrtimer.h | 5 -
kernel/hrtimer.c| 3 ++-
2 files changed, 2 insert
We have just checked that expires_next.tv64 == cpu_base->expires_next.tv64, and
in this case we shouldn't rewrite the same value again. Rewrite code to fix
this.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/hrti
Currently we are returning notifier_from_errno() from CPU_UP_PREPARE notifier
when we detect an error while calling init_timers_cpu(). notifier_from_errno()
already has enough checks within to do something similar. And so we can call it
directly without checking if there was an error or not.
Signe
High Resolution feature can be enabled/disabled from bootargs if we have a
string 'highres=' followed by 'on' or 'off'. The default value of this variable
is '1'. When 'on' is passed as bootarg, we don't have to overwrite this
variable by '1'.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c |
Active_bases field of struct hrtimer_cpu_base is used at only one place, i.e.
hrtimer_interrupt() and at that place too we can easily use timerqueue_getnext()
instead to achieve the same result. I don't think this will have any performance
degradation issues and so removing this field.
Signed-off-
In hrtimers_init() we need to call init_hrtimers_cpu() for boot CPU. For this,
currently we are emulating a call to hotplug notifier. Probably this was done
initially to get rid of code redundancy. But this sequence always called a
single routine, i.e. init_hrtimers_cpu(), and so calling that routi
hrtimer_force_reprogram() is only called from parts of kernel which are defined
within #ifdef CONFIG_HIGH_RES_TIMERS and so its empty definition is never used.
Remove it.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/hrtimer.c b/kern
Currently we have a 'tab' here instead of 'space' after 'comma'. Replace it with
'space'.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index d55092c..a1120a0 100644
--- a/kernel/hrtimer.c
Breaking format fragments into multiple lines hits readability of code. Even if
it goes over 80 column width, its better to keep them together.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtim
In switch_hrtimer_base() we have created a local variable basenum which is set
to base->index. This variable is used at only one place. It makes code more
readable if we remove this variable use base->index directly.
Signed-off-by: Viresh Kumar
---
kernel/hrtimer.c | 3 +--
1 file changed, 1 ins
On 03/26/2014 09:26 AM, Preeti U Murthy wrote:
> Its possible that the tick_broadcast_force_mask contains cpus which are not
> in cpu_online_mask when a broadcast tick occurs. This could happen under the
> following circumstance assuming CPU1 is among the CPUs waiting for broadcast.
>
> CPU0
On 03/26/2014 04:51 PM, Viresh Kumar wrote:
> In switch_hrtimer_base() we have created a local variable basenum which is set
> to base->index. This variable is used at only one place. It makes code more
> readable if we remove this variable use base->index directly.
>
No, this doesn't look right.
On 03/25/2014 11:48 PM, Gregory CLEMENT wrote:
ll_set_cpu_coherent is always used on the current CPU, so instead of
passing the CPU id as argument, ll_set_cpu_coherent() can find it by
itself.
Signed-off-by: Gregory CLEMENT
Acked-by: Thomas Petazzoni
---
[...]
diff --git a/arch/arm/mach-mveb
It's quite cricial to clear error flags because SAI might hang if getting
FIFO underrun during playback (I haven't confirmed the same issue on Rx
overflow though).
So this patch enables those irq and adds isr() to clear the flags so as to
keep playback entirely safe.
Signed-off-by: Nicolin Chen
The Hardware Locality (hwloc) team is pleased to announce the release
of v1.9:
http://www.open-mpi.org/projects/hwloc/
v1.9 is a major new release series.
It adds a couple enhanced API functions, many object attributes for
better representing CPU and I/O device characteristics, and more.
* AP
On 26/03/2014 12:52, Sebastian Hesselbarth wrote:
> On 03/25/2014 11:48 PM, Gregory CLEMENT wrote:
>> ll_set_cpu_coherent is always used on the current CPU, so instead of
>> passing the CPU id as argument, ll_set_cpu_coherent() can find it by
>> itself.
>>
>> Signed-off-by: Gregory CLEMENT
>> Acke
Hi,
Huang Shijie wrote:
> 于 2014年03月26日 16:51, Lothar Waßmann 写道:
> > I don't see why this should not be supported on i.MX28 (i.MX23 doesn't
> > do byteswapping anyway, so this wouldn't change anything for i.MX23).
> > The partitions used by Linux need not necessarily be accessible for the
> > Boo
On 03/25/2014 11:48 PM, Gregory CLEMENT wrote:
The initial binding for PMSU were wrong. It didn't take into account
all the registers from the PMSU and moreover it referred to registers
which are not part of PMSU.
The Power Management Unit Service block also controls the Coherency
Fabric subsyst
From: Nicolin Chen
> It's quite cricial to clear error flags because SAI might hang if getting
> FIFO underrun during playback (I haven't confirmed the same issue on Rx
> overflow though).
>
> So this patch enables those irq and adds isr() to clear the flags so as to
> keep playback entirely safe.
On 26/03/2014 13:04, Sebastian Hesselbarth wrote:
> On 03/25/2014 11:48 PM, Gregory CLEMENT wrote:
>> The initial binding for PMSU were wrong. It didn't take into account
>> all the registers from the PMSU and moreover it referred to registers
>> which are not part of PMSU.
>>
>> The Power Manageme
On Wed, Mar 26, 2014 at 12:42:43AM -0700, Jimmy Li wrote:
> fix a sparse warning.
> drivers/staging/vt6655/iwctl.c:1846:35: warning: cast from restricted
> gfp_t
> drivers/staging/vt6655/iwctl.c:1846:35: warning: incorrect type in
> argument 2 (different base types)
> drivers/staging/vt6655/iwctl.c
Hi,
Currently APEI depends on x86 architecture. It is because of many x86
specific features like "IA-32 Architecture Corrected Machine Check
" error source or NMI hardware error notification. However, many other
features like "PCI Express Device AER Structure" or GHES via external
interrupt ca
On Wed, Mar 26, 2014 at 02:58:50PM +0900, SeongJae Park wrote:
> bp_proc_create() be called only when BP_PROC_SUPPORT defined but its
> definition live outside of #ifdef BP_PROC_SUPPORT and cause following
> trivial build warning:
> drivers/staging/silicom/bpctl_mod.c:6786:12: warning:
> ‘bp_proc_c
I apologize in advance if I'm posting this to the wrong list. Also, I've attempted to post in plain text; I hope
Thunderbird behaves.
I have set up a ipsec tunnel between Server-A and Server-B using public IP addresses and configured the ip xfrm state
and ip xfrm policy database to use marks.
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, March 25, 2014 11:50 PM
> To: Haiyang Zhang
> Cc: David Miller; o...@aepfle.de; net...@vger.kernel.org;
> jasow...@redhat.com; driverdev-de...@linuxdriverproject.org; linux-
> ker...@vger.kernel.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm announcing the release of the 3.12.15 kernel.
All users of the 3.12 kernel series must upgrade.
The updated 3.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.12.y
and can be bro
On Wed, Mar 26, 2014 at 9:27 PM, Greg KH wrote:
> On Wed, Mar 26, 2014 at 02:58:50PM +0900, SeongJae Park wrote:
>> bp_proc_create() be called only when BP_PROC_SUPPORT defined but its
>> definition live outside of #ifdef BP_PROC_SUPPORT and cause following
>> trivial build warning:
>> drivers/sta
On 03/26/2014 04:51 PM, Viresh Kumar wrote:
> In hrtimers_init() we need to call init_hrtimers_cpu() for boot CPU. For this,
> currently we are emulating a call to hotplug notifier. Probably this was done
> initially to get rid of code redundancy. But this sequence always called a
> single routine,
1 - 100 of 502 matches
Mail list logo
