Am Samstag, 24. Mai 2014, 05:10:07 schrieb Herbert Xu:
Hi Herbert,
> Stephan Mueller wrote:
> > + memset(_algs[i], 0, sizeof(struct crypto_alg));
> > + if (pr) {
> > + memcpy(drbg_algs[i].cra_name, "drbg(pr(", 8);
> > +
Hi Daniel,
Today's linux-next merge of the clockevents tree got a conflict in
arch/arm/boot/dts/vf610.dtsi between commit 0517fe6aa880 ("ARM: dts:
vf610-twr: Add support for sdhc1") from the arm-soc tree and commit
07513e1330a9 ("ARM: dts: vf610: Add Freescale FlexTimer Module timer
node") from
Am Samstag, 24. Mai 2014, 05:14:59 schrieb Herbert Xu:
Hi Herbert,
> Stephan Mueller wrote:
> > Hi,
> >
> > the following set of patches implements the deterministic random bit
> > generator (DRBG) specified by SP800-90A.
> >
> > The DRBG implementation offers the following:
> >* All
On Sun, May 25, 2014 at 03:44:01PM +0530, Himangi Saraogi wrote:
> This patch moves most data allocated in the probe function from
> unmanaged interfaces to managed interfaces. The kfrees and error
> handling code is done away with. The unnecesary labels are
> removed. Also, linux/device.h is
On Sat, May 24, 2014 at 05:47:09PM +0530, Himangi Saraogi wrote:
> This patch moves most data allocated in the probe function from
> unmanaged interfaces to managed interfaces. The kfrees and error
> handling code is done away with. Also, the unnecesary labels are
> removed and the function
On 05/26/2014 12:23 PM, Tejun Heo wrote:
> On Thu, May 22, 2014 at 10:21:25PM +0800, Lai Jiangshan wrote:
>> On Thu, May 22, 2014 at 9:47 PM, Tejun Heo wrote:
>> This is not busy wait, the retry and numa_pwq_tbl() guarantee that
>> the retry will get a new pwq (even without cpu_relax()) as the
On Fri, May 23, 2014 at 12:37:46PM -0400, Yufeng Shen wrote:
> On Thu, May 22, 2014 at 10:29 AM, Nick Dyer wrote:
> >
> > Dmitry Torokhov wrote:
> > > On Thu, Jul 18, 2013 at 07:17:44PM +0200, rydb...@euromail.se wrote:
> > >>> From: Yufeng Shen
> > >>> This is the preparation for supporting the
2014-05-26 7:19 GMT+03:00 Dave Chinner :
> On Mon, May 26, 2014 at 11:19:04AM +1000, Dave Chinner wrote:
>> On Mon, May 26, 2014 at 10:08:13AM +1000, Dave Chinner wrote:
>> > On Sun, May 25, 2014 at 01:04:09PM -0700, Linus Torvalds wrote:
>> > > On Mon, May 5, 2014 at 11:34 AM, Plamen Petrov
>>
On Mon, 2014-05-26 at 11:04 +0800, Libo Chen wrote:
> hi,
> my box has 16 cpu (E5-2658,8 core, 2 thread per core), i did a test on
> 3.4.24stable, startup 50 same process, every process is sample:
>
> #include
>
> int main()
> {
> for (;;)
> {
>> During task switch, all of CS.DPL, CS.RPL, SS.DPL must match (in addition
>> to all the other requirements) and will be the new CPL. So far this
>> worked by carefully setting the CS selector and flag before doing the
>
> s/flag/EFLAGS/
>
>> task switch; however, this will not work once we get
On Sun, 2014-05-25 at 21:58 -0700, Chaitanya Hazarey wrote:
> Added a blank line after declarations in many places to fix
> the following warning issued by checkpatch.pl:
Unrelated trivial note:
> diff --git a/drivers/staging/silicom/bpctl_mod.c
> b/drivers/staging/silicom/bpctl_mod.c
> @@
Hi Grant,
After merging the devicetree tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/of/base.c: In function 'of_update_property':
drivers/of/base.c:1906:10: error: 'found' undeclared (first use in this
function)
return found ? 0 : -ENODEV;
^
Hi Chanwoo,
On 26 May 2014 10:27, Chanwoo Choi wrote:
> This patch add IRQF_NO_SUSPEND flag before requesting interrupt handler
> if button->wakeup is true. If ther interrupt of gpio-keys hasn't included
> IRQF_NO_SUSPEND, wouldn't wake-up from freeze state when pressing button.
Please refer
Added a blank line after declarations in many places to fix
the following warning issued by checkpatch.pl:
WARNING: Missing a blank line after declarations
Signed-off-by: Chaitanya Hazarey
---
drivers/staging/silicom/bpctl_mod.c| 88 +++-
On its way.
Chaitanya
On Sun, May 25, 2014 at 5:51 PM, Greg KH wrote:
> On Sun, May 25, 2014 at 05:36:58PM -0700, Chaitanya Hazarey wrote:
>> Added a blank line after declarations in many places to fix the following
>> warning issued by checkpatch.pl:
>
> Always wrap your lines at 72 columns,
This patch add IRQF_NO_SUSPEND flag before requesting interrupt handler
if button->wakeup is true. If ther interrupt of gpio-keys hasn't included
IRQF_NO_SUSPEND, wouldn't wake-up from freeze state when pressing button.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
Cc: Dmitry Torokhov
Hi Tejun,
You are the implementor of CMWQ workqueues and I am working on device drivers.
In this new workqueues, worker threads are created like:
kworker/u4:0
kworker/0:0
OK, with the help of ftrace, we are able to know on which cpu id, it is
created. Can we read not from u4:0 or 0:0, the
On Mon, May 26, 2014 at 2:48 AM, Maxime Ripard
wrote:
> On Fri, May 23, 2014 at 03:51:06PM +0800, Chen-Yu Tsai wrote:
>> PLL6 is used by some important but undocumented module, most likely
>> memory related, such as mbus or the actual memory controller. As we
>> do not have a driver for that, add
From: Joe Perches
Date: Sun, 25 May 2014 10:58:52 -0700
> On Sun, 2014-05-25 at 19:32 +0200, Manuel Schölling wrote:
>> To be future-proof and for better readability the time comparisons are
>> modified to use time_before() instead of plain, error-prone math.
>
> Sensible change, but it seems
On 19 May 2014 11:10, Chander Kashyap wrote:
> Hi Daniel/Kgene,
>
> On 16 May 2014 13:33, Chander Kashyap wrote:
>> Exynos5420 is a big-little Soc from Samsung. It has 4 A15 and 4 A7 cores.
>>
>> This patchset adds cpuidle support for Exynos5420 SoC based on
>> generic big.little cpuidle driver.
On Mon, May 26, 2014 at 3:14 AM, Maxime Ripard
wrote:
> On Fri, May 23, 2014 at 03:51:20PM +0800, Chen-Yu Tsai wrote:
>> The Allwinner A23 SoC has a PRCM unit like the previous A31 SoC.
>> The differences are the AR100 clock can no longer be modified,
>> and the APB0 clock has different divisors.
On Thu, May 22, 2014 at 10:21:25PM +0800, Lai Jiangshan wrote:
> On Thu, May 22, 2014 at 9:47 PM, Tejun Heo wrote:
> This is not busy wait, the retry and numa_pwq_tbl() guarantee that
> the retry will get a new pwq (even without cpu_relax()) as the comments says,
Yes, *eventually*. It's not
On Mon, May 26, 2014 at 3:39 AM, Maxime Ripard
wrote:
> On Fri, May 23, 2014 at 03:51:25PM +0800, Chen-Yu Tsai wrote:
>> The Ippo-q8h is a tablet circiut board commonly found in cheap Android
>> tablets with A23 SoCs. There are at least 2 versions of the board, with
>> different peripherals, such
On Mon, May 26, 2014 at 11:19:04AM +1000, Dave Chinner wrote:
> On Mon, May 26, 2014 at 10:08:13AM +1000, Dave Chinner wrote:
> > On Sun, May 25, 2014 at 01:04:09PM -0700, Linus Torvalds wrote:
> > > On Mon, May 5, 2014 at 11:34 AM, Plamen Petrov
> > > wrote:
> > > >
> > > > The story short: on
Hi Chris,
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/mmc/host/sdhci-s3c.c: In function 'sdhci_s3c_notify_change':
drivers/mmc/host/sdhci-s3c.c:402:25: error: 'struct sdhci_host' has no member
named 'card_tasklet'
Caused by commit
On 24 May 2014 18:29, Pavel Machek wrote:
> On Fri 2014-05-23 10:03:27, Viresh Kumar wrote:
>> On 22 May 2014 20:22, Eduardo Valentin wrote:
>> > However, on CPUs that needs thermal managment, it makes sense to have
>> > such dependency, from functional perspective. Mainly because scaling
>> >
On Mon, May 26, 2014 at 3:38 AM, Maxime Ripard
wrote:
> On Fri, May 23, 2014 at 03:51:24PM +0800, Chen-Yu Tsai wrote:
>> The Allwinner A23 is a tablet oriented SoC with 2 Cortex-A7 cores
>> and a Mali-400MP2 GPU.
>>
>> Signed-off-by: Chen-Yu Tsai
>> ---
>> arch/arm/boot/dts/sun8i-a23.dtsi | 524
On 23 May 2014 21:26, Stephen Warren wrote:
> Oh OK, I guess the "notify" value is static then, and driver defined, so
> this is fine.
Correct!! Can you reply on the tegra patch also? So that we can close this
thread ASAP?
--
To unsubscribe from this list: send the line "unsubscribe
On Mon, May 26, 2014 at 3:26 AM, Maxime Ripard
wrote:
> On Fri, May 23, 2014 at 03:51:23PM +0800, Chen-Yu Tsai wrote:
>> The A23 is a dual Cortex-A7. Add the logic to use the IPs used to
>> control the CPU configuration and the CPU power so that we can
>> bring up secondary CPUs at boot.
>>
>>
Hi,
On Mon, May 26, 2014 at 2:56 AM, Maxime Ripard
wrote:
> On Fri, May 23, 2014 at 03:51:12PM +0800, Chen-Yu Tsai wrote:
>> Some clock modules on the A31 use PLL6x2 as one of their inputs.
>> This patch changes the PLL6 implementation for A31 to a divs clock,
>> i.e. clock with multiple outputs
Paolo Bonzini wrote on 2014-05-23:
> When Hyper-V enlightenments are in effect, Windows prefers to issue an
> Hyper-V MSR write to issue an EOI rather than an x2apic MSR write.
> The Hyper-V MSR write is not handled by the processor, and besides
> being slower, this also causes bugs with APIC
Hi,
On 05/23/2014 04:46 AM, Rickard Strandqvist wrote:
> There is otherwise a risk of a possible null pointer dereference.
>
> Was largely found by using a static code analysis program called cppcheck.
>
> Signed-off-by: Rickard Strandqvist
> ---
> fs/ocfs2/move_extents.c |4 +++-
> 1
EXYNOS5410 is SoC in Samsung's Exynos5 SoC series.
Add initial support for this SoC.
Signed-off-by: Tarek Dakhran
Signed-off-by: Vyacheslav Tyrtov
---
arch/arm/mach-exynos/Kconfig |5 +
arch/arm/mach-exynos/common.h | 12 ++--
2 files changed, 15 insertions(+), 2
The EXYNOS5410 clocks are statically listed and registered
using the Samsung specific common clock helper functions.
Signed-off-by: Tarek Dakhran
Signed-off-by: Vyacheslav Tyrtov
---
.../devicetree/bindings/clock/exynos5410-clock.txt | 45 +
drivers/clk/samsung/Makefile
The series of patches represent support of Exynos 5410 SoC
The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture
Patches add new platform description, support of clock controller and device
tree for Exynos 5410.
Has been build on Samsung Linux Kernel
(branch: for-next,
Add initial device tree nodes for EXYNOS5410 SoC and SMDK5410 board.
Signed-off-by: Tarek Dakhran
Signed-off-by: Vyacheslav Tyrtov
Reviewed-by: Tomasz Figa
---
arch/arm/boot/dts/Makefile|1 +
arch/arm/boot/dts/exynos5410-smdk5410.dts | 82
On 05/22/2014 10:21 PM, Lai Jiangshan wrote:
> On Thu, May 22, 2014 at 9:47 PM, Tejun Heo wrote:
>> On Thu, May 22, 2014 at 04:44:16PM +0800, Lai Jiangshan wrote:
>>> When pwq->refcnt == 0, the retrying is guaranteed to make forward-progress.
>>> The comment above the code explains it well:
>>>
hi,
my box has 16 cpu (E5-2658,8 core, 2 thread per core), i did a test on
3.4.24stable, startup 50 same process, every process is sample:
#include
int main()
{
for (;;)
{
unsigned int i = 0;
On Fri, 23 May 2014 11:11:13 -0700, Andi Kleen wrote:
>> > diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
>> > index 1a2d7fc..e6d8ed0 100644
>> > --- a/tools/perf/builtin-report.c
>> > +++ b/tools/perf/builtin-report.c
>> > @@ -315,8 +315,9 @@ static int
On 05/26/2014 10:43 AM, f...@marvell.com wrote:
From: Fan Wu
What the patch did:
1.To call pinmux_disable_setting ahead of pinmux_enable_setting in each time of
calling pinctrl_select_state
2.Remove the HW disable operation in in pinmux_disable_setting function.
The reason why to do this
Hi Andi,
On Fri, 23 May 2014 14:35:03 -0700, Andi Kleen wrote:
> On Mon, May 19, 2014 at 05:21:15PM +0900, Namhyung Kim wrote:
>> This is gone with 540476de74c9 ("perf tools: Remove
>> symbol_conf.use_callchain check").
>
> The patchkit applies to tip/perf/core.
The commit 540476de74c9 is also
From: Fan Wu
What the patch did:
1.To call pinmux_disable_setting ahead of pinmux_enable_setting in each time of
calling pinctrl_select_state
2.Remove the HW disable operation in in pinmux_disable_setting function.
The reason why to do this is that:
1.To avoid duplicated calling
On Fri, May 23, 2014 at 05:57:58PM -0700, Laura Abbott wrote:
> On 5/12/2014 10:04 AM, Laura Abbott wrote:
> >
> > I'm going to see about running this through tests internally for comparison.
> > Hopefully I'll get useful results in a day or so.
> >
> > Thanks,
> > Laura
> >
>
> We ran some
On Sun, May 25, 2014 at 05:11:30PM -0400, Theodore Ts'o wrote:
> On Sun, May 25, 2014 at 01:04:09PM -0700, Linus Torvalds wrote:
> >
> > The fact is, I think xfs is just buggy. Returning 38 (ENOSYS) is
> > totally insane. "No such system call"? Somebody is on some bad bad
> > drugs. Not that the
For cheap seek, when we scan the region between si->lowset_bit
and scan_base, if san_base is greater than si->highest_bit, the
scan operation between si->highest_bit and scan_base is not
unnecessary.
This patch can be used to avoid scanning invalidated region for
cheap seek.
Signed-off-by: Chen
Thanks for CC-ing me.
Here are some comments.
- I have no objection about the 0:0 char-dev whiteout, but you don't
have to have the inode for each whiteout. The hardlink is better.
In this version, you have now. How about creating a "base"
whiteout under workdir at the mount-time? Maybe
On Thu, May 22, 2014 at 08:07:35PM +0200, Geert Uytterhoeven wrote:
> The calculation of the bit rate divider used a standard C division, which
> rounds down the quotient. This may lead to a higher bitrate than requested.
> Round up to avoid this.
>
> E.g. on Koelsch, the SPI flash (configured
On Mon, May 26, 2014 at 10:08:13AM +1000, Dave Chinner wrote:
> On Sun, May 25, 2014 at 01:04:09PM -0700, Linus Torvalds wrote:
> > On Mon, May 5, 2014 at 11:34 AM, Plamen Petrov
> > wrote:
> > >
> > > The story short: on systems with btrfs root I have a kernel .config with
> > > ext4,
> > >
Hi Bruce,
After merging the nfsd tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/nfsd/nfs4proc.c: In function 'warn_on_nonidempotent_op':
fs/nfsd/nfs4proc.c:1861:3: error: implicit declaration of function
'nfsd4_op_name' [-Werror=implicit-function-declaration]
On Sun, May 25, 2014 at 05:36:58PM -0700, Chaitanya Hazarey wrote:
> Added a blank line after declarations in many places to fix the following
> warning issued by checkpatch.pl:
Always wrap your lines at 72 columns, like git asks you to when you type
in the commit message.
> WARNING: Missing a
Hi all,
On Mon, 26 May 2014 10:17:41 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the samsung tree got a conflict in
> arch/arm/Kconfig.debug between commit 7098cff2a3f4 ("ARM: debug: qcom:
> make UART address selection configuration option") from the arm-soc
> tree and commit
Added a blank line after declarations in many places to fix the following
warning issued by checkpatch.pl:
WARNING: Missing a blank line after declarations
The reason why it was not applying clean against Greg's tree was that
bpctl_mod.c had changed in the functions which are a part of this
[ For the benefit of those watching at home ]
Linus pulled this and it was included in v3.15-rc6.
Thanks Linus, Geert and a cast of 1000s.
On Tue, May 13, 2014 at 04:42:04PM +0900, Simon Horman wrote:
> Hi Linus,
>
> Please consider this SH Driver Update for v3.15.
>
> It consists of a single
On Mon, May 26, 2014 at 12:57:39AM +0100, Masaru Nomura wrote:
> > What _branch_ of that git tree did you make it against?
> >
>
> I did my work against
>
> commit 4b660a7f5c8099d88d1a43d8ae138965112592c7
That is a commit, not a branch.
Please work against the staging-next branch, not master.
On Mon, May 19, 2014 at 9:38 AM, Christoph Hellwig wrote:
> On Mon, May 19, 2014 at 05:35:40PM +0300, Kirill A. Shutemov wrote:
>> >From functional POV, emulation *should* be identical to original
>> remap_file_pages(), but slower. It would be nice, if you test it early.
>>
>> It's not clear yet
Hi Kukjin,
Today's linux-next merge of the samsung tree got a conflict in
arch/arm/Kconfig.debug between commit 7098cff2a3f4 ("ARM: debug: qcom:
make UART address selection configuration option") from the arm-soc
tree and commit 1899de289497 ("ARM: S3C24XX: use generic
DEBUG_UART_PHY/_VIRT in
OK sure, will do Dan.
Greg, the patch has some issues, I did sync to your staging-next
branch and am having issues applying it.
Will send an update when i am able to do it.
Thanks,
Chaitanya
On Sun, May 25, 2014 at 3:30 PM, Dan Carpenter wrote:
> Since you're redoing this one anyway, please
On Sun, May 25, 2014 at 01:04:09PM -0700, Linus Torvalds wrote:
> On Mon, May 5, 2014 at 11:34 AM, Plamen Petrov wrote:
> >
> > The story short: on systems with btrfs root I have a kernel .config with
> > ext4,
> > xfs and btrfs built-in which works fine with 3.13.x, but 3.14.x panics.
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Manfred,
On 05/25/2014 11:01 PM, Manfred Spraul wrote:
> Hi Marian,
>
> On 05/22/2014 03:01 PM, Marian Marinov wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 05/05/2014 10:59 PM, Marian Marinov wrote:
>>>
>>> In my tests it
> What _branch_ of that git tree did you make it against?
>
I did my work against
commit 4b660a7f5c8099d88d1a43d8ae138965112592c7
Thank you,
Masaru
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
On Mon, May 26, 2014 at 1:40 AM, abdoulaye berthe wrote:
> Well, ignoring the return value as it is done in gpio-bt8xx makes the
> compiler complain and display a warning message. The problem with
> false warning is that it might distract you.
Isn't the warning due to the __must_check in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/24/2014 03:34 PM, Richard Weinberger wrote:
> Am 24.05.2014 09:52, schrieb Michael Kerrisk (man-pages):
>> On 04/21/2014 10:42 AM, Richard Weinberger wrote:
>>> Am 21.04.2014 09:24, schrieb Michael Kerrisk:
> Does recursive monitoring even
On 5/23/2014 6:08 PM, Lee Jones wrote:
>
> Why are you re-sending this?
>
Hi,
My mail server reported that it failed to send [PATCH v2 1/4] to LKML,
so I resent the whole series, only to get it properly archived.
Sorry for the confusion.
Best Regards
Lejun
--
To unsubscribe from this list:
.. and with this, I'm back on my usual Sunday schedule.
It's just a few days after -rc6, but as expected, there were some
pending stuff for when I got back home, so you should think of this as
being the "normal" release, and rc6 just having been oddly delayed by
my travel.
The bulk of this is
On Sun, May 25, 2014 at 11:50:03PM +0100, Masaru Nomura wrote:
>
>
>
> 2014-05-25 23:37 GMT+01:00 Greg KH :
>
> On Sun, May 25, 2014 at 11:24:12PM +0100, Masaru Nomura wrote:
> > Remove prohibited space between function name and
> > open parenthesis to meet kernel coding style.
>
On Thu, 2014-05-22 at 17:47 +0100, Will Deacon wrote:
> Hi all,
>
> This is version 2 of the series I originally posted here:
>
> https://lkml.org/lkml/2014/4/17/269
>
> Changes since v1 include:
>
> - Added relevant acks from arch maintainers
> - Fixed potential compiler re-ordering issue
--
Von Dr. David Sidwell
Global Equity Forschung
London Regional Office-
UBS Investment Bank in London.
1-Fins begraben Avenue, London EC2M 2PP
Mein lieber Freund,
Mein Name ist Dr. David Sidwell von Harlesden North west London. Ich
arbeite mit UBS Investment Bank Großbritannien. Ich möchte
> CS.RPL is not equal to the CPL in the few instructions between
> setting CR0.PE and reloading CS. And CS.DPL is also not equal
> to the CPL for conforming code segments.
Out of my curiousity, could you elaborate the problem of this
CPL gap window, such as breaking any VMs or tests? From Linux
On Sun, May 25, 2014 at 08:47:51PM +0400, Konstantin Khlebnikov wrote:
> scripts/kconfig/menu.c: In function ‘get_symbol_str’:
> scripts/kconfig/menu.c:590:18: warning: ‘jump’ may be used uninitialized in
> this function [-Wmaybe-uninitialized]
> jump->offset = strlen(r->s);
>
On Sat, May 24, 2014 at 1:12 PM, Wei Huang wrote:
> Table 7-1 of the SDM mentions a check that the code segment's
> DPL must match the selector's RPL. This was not done by KVM,
> fix it.
>
> Signed-off-by: Paolo Bonzini
> ---
> arch/x86/kvm/emulate.c | 31 +--
> 1
Hi all,
On Sun, 25 May 2014 15:12:35 -0700 Greg Kroah-Hartman
wrote:
>
> On Sun, May 25, 2014 at 11:54:14PM +0200, Vincent Stehlé wrote:
> > Commit f9b0e251dfbf 'drm: make mode_valid callback optional' left variable
> > ret
> > unused; remove it.
> >
> > This fixes the following compilation
Hi all,
On Sun, 25 May 2014 23:54:35 +0100 Russell King - ARM Linux
wrote:
>
> On Sun, May 25, 2014 at 02:08:48PM +0200, David Herrmann wrote:
> >
> > On Sat, May 24, 2014 at 11:05 PM, Vincent Stehlé
> > wrote:
> > > The dma_buf_export function was updated in commit 4bcec44ffaf9 'dma-buf:
>
> Not needed anymore now that the CPL is computed directly
> by the task switch code.
Given the current form, looks OK to me.
Reviewed-by: Wei Huang
>
> Signed-off-by: Paolo Bonzini
> ---
> arch/x86/include/asm/kvm_emulate.h | 1 -
> arch/x86/kvm/x86.c | 6 --
> 2 files
> Another day, another CPL patch...
>
> It turns out that the simple approach of getting CPL from SS.DPL
> broke x86/taskswitch2.flat. To fix that, already "imagine" that the
> CPL is CS.RPL, or 3 for VM86 tasks, while loading segment descriptors
> during task switches. This removes the hack
On Sun, May 25, 2014 at 02:08:48PM +0200, David Herrmann wrote:
> Hi
>
> On Sat, May 24, 2014 at 11:05 PM, Vincent Stehlé
> wrote:
> > The dma_buf_export function was updated in commit 4bcec44ffaf9 'dma-buf: use
> > reservation objects' to take a reservation object parameter; update Armada
> >
Philippe Reynes schrieb:
> This driver add partial support of the
> maxim 1027/1029/1031. Differential mode is not
> supported.
>
> It was tested on armadeus apf27 board.
>
> Signed-off-by: Philippe Reynes
> ---
> .../devicetree/bindings/iio/adc/max1027-adc.txt| 21 +
>
On Sun, May 25, 2014 at 11:24:12PM +0100, Masaru Nomura wrote:
> Remove prohibited space between function name and
> open parenthesis to meet kernel coding style.
> Also fix indenting due to changes to keep readability.
>
> -since v2:
> None. This is the resend of v2 as v2 failed to apply
This
Since you're redoing this one anyway, please use a more specific subject
like:
[PATCH] Staging: Silicom: bpctl_mod.c & bypass.c: add blank lines
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
This patch adds documentation for Device-Tree bindings for sunxi IR
controller.
Signed-off-by: Alexander Bersenev
Signed-off-by: Alexsey Shestacov
---
.../devicetree/bindings/media/sunxi-ir.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644
This patch adds driver for sunxi IR controller.
It is based on Alexsey Shestacov's work based on the original driver
supplied by Allwinner.
Signed-off-by: Alexander Bersenev
Signed-off-by: Alexsey Shestacov
---
drivers/media/rc/Kconfig | 10 ++
drivers/media/rc/Makefile| 1 +
This patch adds IR controller in A20 Device-Tree:
- Two IR devices found in A20 user manual
- Pins for two devices
- One IR device physically found on Cubieboard 2
- One IR device physically found on Cubietruck
Signed-off-by: Alexander Bersenev
Signed-off-by: Alexsey Shestacov
---
This patch introduces Consumer IR(CIR) support for sunxi boards.
This is based on Alexsey Shestacov's work based on the original driver
supplied by Allwinner.
Signed-off-by: Alexander Bersenev
Signed-off-by: Alexsey Shestacov
---
Changes since version 1:
- Fix timer memory leaks
- Fix
Quoting James Bottomley (james.bottom...@hansenpartnership.com):
> On Sat, 2014-05-24 at 22:25 +, Serge Hallyn wrote:
> > Quoting James Bottomley (james.bottom...@hansenpartnership.com):
> > > On Fri, 2014-05-23 at 11:20 +0300, Marian Marinov wrote:
> > > > On 05/20/2014 05:19 PM, Serge Hallyn
Remove prohibited space between function name and
open parenthesis to meet kernel coding style.
Also fix indenting due to changes to keep readability.
-since v2:
None. This is the resend of v2 as v2 failed to apply
Signed-off-by: Masaru Nomura
---
Len field is already set to zero, but not the from field which is sent as
0xfe00. This makes no sense, and may cause confuse server
implementations doing sanity checks (qemu-nbd is an example.)
Signed-off-by: Hani Benhabiles
---
Compared to v1:
* Zero the request structure instead
On Sun, May 25, 2014 at 11:59:08AM -0700, Chaitanya Hazarey wrote:
> Added a blank line after declarations in many places to fix the following
> warning issued by checkpatch.pl:
>
> WARNING: Missing a blank line after declarations
>
> Lets see if this works now, this patch is prepared against
On Sun, May 25, 2014 at 11:54:14PM +0200, Vincent Stehlé wrote:
> Commit f9b0e251dfbf 'drm: make mode_valid callback optional' left variable ret
> unused; remove it.
>
> This fixes the following compilation warning:
>
> drivers/staging/imx-drm/imx-tve.c: In function
>
On Sun, May 25, 2014 at 11:13:05PM +0200, Vincent Stehlé wrote:
> Add missing specification of efm32_uart_exit as module_exit.
>
> This fixes the following compilation warning:
>
> drivers/tty/serial/efm32-uart.c:840:123: warning: ‘efm32_uart_exit’ defined
> but not used [-Wunused-function]
Commit f9b0e251dfbf 'drm: make mode_valid callback optional' left variable ret
unused; remove it.
This fixes the following compilation warning:
drivers/staging/imx-drm/imx-tve.c: In function ‘imx_tve_connector_mode_valid’:
drivers/staging/imx-drm/imx-tve.c:252:6: warning: unused variable
On Sun, May 25, 2014 at 02:11:13PM -0400, Paul Clements wrote:
> On Sun, May 25, 2014 at 6:18 AM, Hani Benhabiles wrote:
> > On Sun, May 18, 2014 at 10:11:13AM +0100, Hani Benhabiles wrote:
> >> On Fri, May 16, 2014 at 10:56:33PM -0400, Paul Clements wrote:
> >> > Agreed. But better yet, the
On Thu, 2014-05-22 at 17:47 +0100, Will Deacon wrote:
> A corollary to this is that mmiowb() probably needs rethinking. As it
> currently
> stands, an mmiowb() is required to order MMIO writes to a device from multiple
> CPUs, even if that device is protected by a lock. However, this isn't often
Add missing specification of efm32_uart_exit as module_exit.
This fixes the following compilation warning:
drivers/tty/serial/efm32-uart.c:840:123: warning: ‘efm32_uart_exit’ defined
but not used [-Wunused-function]
Signed-off-by: Vincent Stehlé
Cc: Uwe Kleine-König
Cc: Greg Kroah-Hartman
On Sun, May 25, 2014 at 01:04:09PM -0700, Linus Torvalds wrote:
>
> The fact is, I think xfs is just buggy. Returning 38 (ENOSYS) is
> totally insane. "No such system call"? Somebody is on some bad bad
> drugs. Not that the mount_block_root() loop and error handling might
> not be a good thing to
Hi Nadia,
You added a patch that adds dynamic scaling of MSGMNI (f7bf3df8).
The description begins with:
On large systems we'd like to allow a larger number of message queues. In
some cases up to 32K. However simply setting MSGMNI to a larger value may
cause problems for smaller systems.
On 05/24/14 06:15, Tomasz Figa wrote:
Hi Tarek,
On 23.05.2014 12:35, Tarek Dakhran wrote:
Add initial device tree nodes for EXYNOS5410 SoC and SMDK5410 board.
Signed-off-by: Tarek Dakhran
Signed-off-by: Vyacheslav Tyrtov
---
arch/arm/boot/dts/Makefile|1 +
MOV CR/DR instructions ignore the mod field (in the ModR/M byte). As the SDM
states: "The 2 bits in the mod field are ignored". Accordingly, the second
operand of these instructions is always a general purpose register.
The current emulator implementation does not do so. If the mod bits do not
On Mon, May 5, 2014 at 11:34 AM, Plamen Petrov wrote:
>
> The story short: on systems with btrfs root I have a kernel .config with ext4,
> xfs and btrfs built-in which works fine with 3.13.x, but 3.14.x panics. After
> inserting some debug printks, I got this info from mount_block_root:
>
> --->
Hi Marian,
On 05/22/2014 03:01 PM, Marian Marinov wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/05/2014 10:59 PM, Marian Marinov wrote:
In my tests it worked exactly as expected. Here is an example:
[root@sp2 ~]# sysctl -a|grep shmmax kernel.shmmax = 68719476736 [root@sp2 ~]#
Tried yesterdays git v3.15-rc6-190-g1ee1cea on Sun Fire T2000 (32-thread
sparc64) and got reproducibly stuck on boot with ext journal replay like
below. Booting Debian 3.14.2-1 replayed the log and mounted FS fine.
After that, my test kernel works fine too. SO I can not reproduce it any
more
On Fri, May 23, 2014 at 03:51:09PM +0800, Chen-Yu Tsai wrote:
> The PLLs on newer Allwinner SoC's, such as the A31 and A23, have a
> N multiplier factor that starts from 1, not 0.
>
> This patch adds an option to the clock driver's config data structures
> to define the difference.
>
>
1 - 100 of 382 matches
Mail list logo
