On 11/26/2012 09:35 AM, Andrzej Pietrasiewicz wrote:
In some parts of the kernel (e.g. planned configfs integration into usb
gadget) there is a need to programmatically create config groups
(directories) but it would be preferable to disallow creating them by
the user. This is more or less what d
default_groups are no good for this.
Example:
$ echo 3> /cfg//mass_storage/luns
causes
/cfg/../mass_storage/lun0
/cfg/../mass_storage/lun1
/cfg/../mass_storage/lun2
On Mon, Nov 26 2012, Sebastian Andrzej Siewior wrote:
I though we did not want the luns file but instead use
mkdir /
On 11/26/2012 12:05 PM, Suzuki K. Poulose wrote:
diff --git a/arch/powerpc/include/asm/probes.h
b/arch/powerpc/include/asm/probes.h
index 5f1e15b..836e9b9 100644
--- a/arch/powerpc/include/asm/probes.h
+++ b/arch/powerpc/include/asm/probes.h
@@ -38,5 +38,34 @@ typedef u32 ppc_opcode_t;
#define
On Wed, Nov 21, 2012 at 02:04:26PM +, Alan Cox wrote:
> > I don't see any problems in my testcase.
>
> This looks fine to me as by the time we call tty_ldisc_release we have
> already set TTY_CLOSING on both sides.
Greg, can you push this into v3.7? This regression has been introduced in
v3.7
On 11/26/2012 06:54 PM, Michal Nazarewicz wrote:
On Mon, Nov 26 2012, Sebastian Andrzej Siewior wrote:
Wouldn't say that. It may adds complexity on another level. The target
subsystem has the same problem with adding luns and there seems nothing
wrong with having lun3 and 4 and leaving 0
On 11/27/2012 09:57 AM, Andrzej Pietrasiewicz wrote:
|mkdir -p $FABRIC/naa.6001405c3214b06a/tpgt_1
|mkdir $FABRIC/naa.6001405c3214b06a/tpgt_1/lun/lun_0
|mkdir $FABRIC/naa.6001405c3214b06a/tpgt_1/lun/lun_1
So you setup two luns without this patch. Would that work for you?
I think we _still_ nee
ks()
The code under tty_ldisc_kill() was executed earlier with the tty lock
taken so it is taken again.
I don't see any problems in my testcase.
Cc: sta...@vger.kernel.org #v3.7
Acked-by: Alan Cox
Signed-off-by: Sebastian Andrzej Siewior
---
Greg, here is the resend. I added Acked-By Alan C
On 11/27/2012 05:23 PM, Michal Nazarewicz wrote:
On Tue, Nov 27 2012, Sebastian Andrzej Siewior wrote:
I don't want to push python on anyone but the removal magic is simply
straight forward: unlink the disk ports, rmdir luns, tpgt,…
How should a generic tool know what kind of action
On 11/28/2012 09:10 AM, Andrzej Pietrasiewicz wrote:
Here I understand it. This is to some point a limitation of the gadget
framework. We do know the number of interface that will be available
before we bind. We simply don't know the endpoint number. There are two
exceptions to what I just wrote:
knowledge of the
functions. If there is no such mechanism, then it's a bad user
interface.
On Wed, Nov 28 2012, Sebastian Andrzej Siewior wrote:
Well. You need only to remove the directories you created.
My point is that there should be a way to write a script that is unaware
of th
On 11/28/2012 03:24 PM, Michal Nazarewicz wrote:
On Wed, Nov 28 2012, Sebastian Andrzej Siewior wrote:
-
/functions/acm-function/
instead of
/functions/function1/
+name
with attribute file named "name" which contains the name of th
as a child of the UDC node. The UDC
itself will appear once the hardware driver is loaded and can appear
later.
Signed-off-by: Sebastian Andrzej Siewior
---
fs/configfs/dir.c| 63 ++
include/linux/configfs.h |4 +++
2 files change
* Peter Hurley | 2013-03-05 17:20:29 [-0500]:
>> Not sure I understood. tty_hangup() is only called from within
>> gserial_disconnect() which calls right after usb_ep_disable(). After
>> usb_ep_disable() no further serial packets can be received until the
>> endpoints are re-enabled. This happens
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/cpufreq/cpufreq.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 1f93dbd..cd5acda 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
DEFINE_SRCU() and DEFINE_STATIC_SRCU() does the same thing except for
the "static" attribute. This patch moves the common pieces into
_DEFINE_SRCU() which is used by the the former macros either adding the
static attribute or not.
Signed-off-by: Sebastian Andrzej Siewior
---
inc
: Sebastian Andrzej Siewior
---
include/linux/notifier.h | 26 +-
include/linux/srcu.h |6 +++---
2 files changed, 24 insertions(+), 8 deletions(-)
diff --git a/include/linux/notifier.h b/include/linux/notifier.h
index d65746e..6bfd703 100644
--- a/include/linux/notifier.h
On 03/19/2013 05:22 PM, Joe Perches wrote:
>> +#define DEFINE_SRCU(name) _DEFINE_SRCU(name, )
>> +#define DEFINE_STATIC_SRCU(name)_DEFINE_SRCU(name, static)
>
> I think the use of an empty argument, even in
> a macro, unsightly.
__wait_event_lock_irq() => __wait_event_lock_irq() is
On 01/31/2013 06:21 AM, Namhyung Kim wrote:
>> diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
>> index e1f6860..3594e0c 100644
>> --- a/drivers/cpuidle/cpuidle.c
>> +++ b/drivers/cpuidle/cpuidle.c
>> @@ -23,6 +23,7 @@
>> #include "cpuidle.h"
>>
>> DEFINE_PER_CPU(struct cpuid
On 01/31/2013 03:12 AM, Michael Wang wrote:
> I'm not sure, but just concern about this case:
>
> group 0 cpu 0 cpu 1
> least idle 4 task
>
> group 1 cpu 2 cpu 3
> 1 task
On 01/28/2013 08:57 PM, John L. Males wrote:
> I was not suggesting you are responsible for the bug at all. On
Okay then :)
> I have no custom patches to the kernel.
okay.
> I looked at the RedHat bug 468794. The bug seems to indicate it
> was never fixed. The bug was reported against
> 2.6.27
The scheduler does not consider the power states CPUs while selecting
an idle one. So it might happen, that it puts load on a cpu which is
in a deeper power state than another idle one, which has higher
latency and power costs than pushing the load to the core which is not
in a deep power saving st
some kind of idle state. The larger the value, the deeper the idle
state.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/cpuidle/cpuidle.c | 13 -
include/linux/cpuidle.h |2 ++
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/cpuidle/cpuidle.c b
it is consider as a valid target.
Should there be no CPU in an idle state at disposal then the loadavg is
used as a fallback.
Signed-off-by: Sebastian Andrzej Siewior
---
include/linux/sched.h |1 +
kernel/sched/core.c |6 --
kernel/sched/fair.c | 24
3
On 01/17/2013 12:42 AM, John L. Males wrote:
> Hello,
Hi,
> I copied Sebastian in on the post my review of Changelogs suggests
> Sebastian is the one who will want to know about this kernel
> failure or will know who should be.
I did what? I reviewed patches since they went in this problem occur
On Fri, Jan 25, 2013 at 10:44:50AM +0800, fangxiaozhi 00110321 wrote:
> diff -uprN linux-3.8-rc4_orig/drivers/usb/storage/usual-tables.c
> linux-3.8-rc4/drivers/usb/storage/usual-tables.c
> --- linux-3.8-rc4_orig/drivers/usb/storage/usual-tables.c 2013-01-22
> 14:12:42.594238726 +0800
> +++ linux
On Fri, Jan 25, 2013 at 10:46:13AM +0800, fangxiaozhi 00110321 wrote:
> diff -uprN linux-3.8-rc4_orig/drivers/usb/storage/initializers.c
> linux-3.8-rc4/drivers/usb/storage/initializers.c
> --- linux-3.8-rc4_orig/drivers/usb/storage/initializers.c 2013-01-22
> 14:12:42.594238726 +0800
> +++ linux
On 02/20/2013 09:02 PM, Peter Hurley wrote:
> Sebastian, please re-test your g_nokia+dummy_hcd testcase with
> this series.
I've seen your first series but I did not have the time yet. I hope
this will change this weekend.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe lin
On 08/21/2012 10:19 AM, Andrzej Pietrasiewicz wrote:
@Joel:
However, I am wondering if it would make sense to get rid of the "connect"
(or "ready", if you will) attribute altogether and instead use symlinks:
when a user wants to make the gadget ready, they do an ln -s, when they want
to unbind th
aken).
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/include/asm/uprobes.h |2 ++
arch/x86/kernel/uprobes.c | 33 +++--
2 files changed, 33 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/uprobes.h b/arch/x86/include/asm/uprobes.h
i
alloc_uprobe() might return a NULL pointer, put_uprobe() can't deal with
this.
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/events/uprobes.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
index 7b3112c..30
On 08/29/2012 05:49 PM, Oleg Nesterov wrote:
That would help but would require a change in ptrace_attach() or
something in gdb/strace/…
Well, I still think you should not touch ptrace_attach() at all.
Okay.
One thing I just noticed: If I don't register a handler for SIGUSR1 and
send one to
breakpoint
hit" state. Once this limit is passed, no further task will be hold.
Cc: gdb-patc...@sourceware.org
Signed-off-by: Sebastian Andrzej Siewior
---
rfc..v1:
- removing pids from the exlude list once a task terminates
- skip_handler has been switched from int to struct uprobe *
'r' and ' ' is not supported according to current code.
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/trace/trace_uprobe.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
index 03003cd..
On 09/12/2012 08:02 PM, Cyril Chemparathy wrote:
-void __init early_init_dt_setup_initrd_arch(unsigned long start,
unsigned long end)
+void __init early_init_dt_setup_initrd_arch(u64 start, u64 end)
Why not phys_addr_t?
The rest of the memory specific bits of the device-tree code use u64 for
On 09/13/2012 12:08 AM, Rob Herring wrote:
Geert is right here. If it is a physical address, it should be
phys_addr_t.
While generally true, for the DT specific code I think it should be a
fixed u64. The size of the address is defined by the FDT, not the
kernel. It is very likely we could have
On Fri, Sep 14, 2012 at 08:52:58AM +0200, Rene Buergel wrote:
> > Git should show this as a move, not as a "add a file and remove a
> > file"
> > type patch. Are you generating it properly?
>
> Whats the proper way to do this? I did a git mv, git commit and than git diff
> on that commit hash.
On Fri, Sep 14, 2012 at 03:42:42PM +0400, Sergei Shtylyov wrote:
> >diff --git a/drivers/staging/usbip/stub_dev.c
> >b/drivers/staging/usbip/stub_dev.c
> >index 92ced35..f584af8 100644
> >--- a/drivers/staging/usbip/stub_dev.c
> >+++ b/drivers/staging/usbip/stub_dev.c
> >@@ -233,6 +230,13 @@ stati
On Fri, Sep 14, 2012 at 05:16:38PM +0300, Dan Carpenter wrote:
> I don't think this text is allowed on patches.
Oh Oh Oh Dan, I think you crossed a line here. You were not one of the
recipient and you reviewed and forwarded the email but you should have
deleted this email instead. Now legal action
On Mon, Oct 08, 2012 at 11:59:03PM +0300, Dmytro Milinevskyy wrote:
> Convert USB descriptor's fields to CPU byte order before using locally in USB
> NCM gadget driver.
> Tested on MIPS32 big-endian device.
>
> Signed-off-by: Dmytro Milinevskyy
> ---
> drivers/usb/gadget/f_ncm.c | 10 +-
On Wed, Oct 17, 2012 at 09:20:35PM +0200, Sebastian Andrzej Siewior wrote:
> With dummy_hcd and g_nokia (that is CONFIG_USB_GADGET=m,
> CONFIG_USB_DUMMY_HCD=m, CONFIG_USB_G_NOKIA=m) I see a lockdep complaing
> about a "circular locking dependency" after executing
ping? Or is
From: Sebastian Andrzej Siewior
Date: Wed, 24 Oct 2012 16:40:10 +0200
found by randconfig, Randy Dunlap and Stephen Rothwell:
|drivers/built-in.o: In function `fsg_setup':
|file_storage.c:(.text+0x24db7c): undefined reference to `usb_gadget_config_buf'
|file_storage.c:(.tex
On Wed, Oct 24, 2012 at 11:13:18AM -0400, Alan Stern wrote:
> Are you pinging yourself? That's what it looks like... :-)
Hehe. It seems that it got the job done :)
> Alan Stern
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to major
On Wed, Oct 24, 2012 at 07:30:42PM +0200, Michal Nazarewicz wrote:
> At first it looks strange as FSG does not use composite, but yeah:
Yeah. However, it should be removed in v3.8 anyway :)
> Acked-by: Michal Nazarewicz
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linu
On Wed, Sep 19, 2012 at 04:52:27PM +0200, Joerg Roedel wrote:
> Hi Sebastian,
Hi Joerg,
> > After browsing through the new functions in irq_remapping_modify_x86_ops() I
> > see that some of them test for "remap_ops" which is pointless because you
> > don't
> > call irq_remapping_modify_x86_ops()
the minor thingy I just mentioned,
Acked-by: Sebastian Andrzej Siewior
Sebastian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQkuuWAAoJEHuW6BYqjPXRnVwP/08DxdazUY4SOPIvBK4+gZh7
3VW5EdTLjBSYnaWEFccwhaqqq6FgJ5MfJ862sSXUpejjApDFQdOQPlZmIwfY5lF
enabled.
Signed-off-by: Sebastian Andrzej Siewior
---
include/linux/uprobes.h |2 ++
kernel/events/uprobes.c | 10 --
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/include/linux/uprobes.h b/include/linux/uprobes.h
index efe4b33..1be2d44 100644
--- a/include/linux
On 07/26/2012 05:20 PM, Sebastian Andrzej Siewior wrote:
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
index f935327..772eb3a 100644
--- a/kernel/events/uprobes.c
+++ b/kernel/events/uprobes.c
@@ -1528,7 +1528,10 @@ static void handle_swbp(struct pt_regs *regs)
utask
f the instruction on which we
placed the uprobe activates it?
But I am not sure about this patch...
On 07/26, Sebastian Andrzej Siewior wrote:
@@ -1528,7 +1528,10 @@ static void handle_swbp(struct pt_regs *regs)
utask->state = UTASK_SSTEP;
if (!pre_ssout(uprobe, regs,
On 07/30/2012 04:16 PM, Oleg Nesterov wrote:
I'd suggest you to make 2 patches:
- 1/2 creates arch_uprobe_*_step(...) __weak helpers in
kernel/events/uprobes.c which simply call
user_*_single_step() and updates the callers
Not strictly necessar
As Oleg pointed out in [0] utrace should not use the ptrace interface
for enabling/disabling single stepping.
[0] http://lkml.kernel.org/20120730141638.ga5...@redhat.com
Signed-off-by: Sebastian Andrzej Siewior
---
include/linux/uprobes.h |4
kernel/events/uprobes.c | 16
ore the BTF flag. In case the BTF flag is set, we should look at the
opcode and send SIGTRAP depending on the jump/flag status. For now we
wait for the next exception/jump to be taken.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/include/asm/uprobes.h |
On 07/31/2012 07:51 PM, Oleg Nesterov wrote:
However, honestly I do not like it. I think we should change this
step-by-step, that is why I suggested to use TIF_SINGLESTEP and
user_enable_single_step() like your initial patch did. With this
patch at least the debugger doesn't lose the control over
tem calls touching the configuration space.
So they realy don't have an Interrupt. I assumed that I was not good
enough reading the table and matching the entries to the HW.
>Signed-off-by: Florian Fainelli
Acked-by: Sebastian Andrzej Siewior
for patches 1-3
Sebastian
--
To unsubscrib
* Florian Fainelli | 2012-10-19 15:40:29 [+0200]:
>On Friday 19 October 2012 11:36:25 Fainelli wrote:
>> Sebastian Andrzej Siewior linutronix.de> writes:
>> >
>> > No. You do have a compatible entry. It first appeared on the ce4100
>> > CPU. If it happens
On Sun, Oct 28, 2012 at 06:30:02PM +0100, Dmytro Milinevskyy wrote:
> I was trying to keep 2 tabs but checkpatch didn't accept long line
> that's why I killed extra tab.
Then move them to the code section instead to initialize them in the
declaration section.
> >How does it work? Is the test on h
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/base/platform.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/platform.c b/drivers/base/platform.c
index 8727e9c..af1d47f 100644
--- a/drivers/base/platform.c
+++ b/drivers/base/platform.c
@@ -44,7 +44,7
Signed-off-by: Joel A Fernandes
Signed-off-by: Sebastian Andrzej Siewior
---
Could someone please pick this up?
v1..v2:
- s/edma@/dma-controller@/
arch/arm/boot/dts/am33xx.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot
On 08/26/2013 10:36 AM, Benoit Cousson wrote:
> I've just sent my previous email too soon...
np.
> Now the patch is different :-) I'll take that one.
Good, thanks.
>
> Thanks,
> Benoit
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messag
On 08/27/2013 10:13 AM, Stephen Rothwell wrote:
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/boot/dts/am335x-bone.dts between commit 97238b35d5bb
> ("usb: musb: dsps: use proper child nodes") from the tree and
> commit 63f6b2550aa0 ("ARM: dts: AM33XX: don't redefin
On 08/27/2013 03:24 PM, Benoit Cousson wrote:
> Hi Sebatian,
Hi Benoit,
> Yes. DT patches are an endless source of merge conflicts if they are
> merge throught different trees.
Usually there are small conflicts because two people added / changed a
node nearby. This patch turned the .dts file alm
On 08/27/2013 03:57 PM, Benoit Cousson wrote:
> + Kevin,
>
> On 27/08/2013 15:53, Sebastian Andrzej Siewior wrote:
>> What do we do now?
>
> Cannot you just merge the stable arm-soc/dt branch into your branch
> before applying your patches?
That is up to Greg. This cha
On 08/27/2013 04:05 PM, Benoit Cousson wrote:
> On 27/08/2013 16:02, Sebastian Andrzej Siewior wrote:
>> On 08/27/2013 03:57 PM, Benoit Cousson wrote:
>>> + Kevin,
>>>
>>> On 27/08/2013 15:53, Sebastian Andrzej Siewior wrote:
>>>> What do we do now?
On 08/27/2013 05:01 PM, Kevin Hilman wrote:
>>> What do we do now?
>>
>> Cannot you just merge the stable arm-soc/dt branch into your branch
>> before applying your patches?
>
> Unfortunately, the next/dt branch of arm-soc is not necessarily stable
> so should *not* be merged. In fact none of the
On 08/27/2013 06:12 PM, Olof Johansson wrote:
> No. Read that email again. What Benoit said was that if Felipe was fine
> with the change _HE_ would take it. Huge difference, and one that would have
> avoided this situation.
Yes, I'm sorry.
> The only way to solve these things in the future is to
On 08/27/2013 07:37 PM, Greg KH wrote:
> Nor will you, given that I am not the one to take these patches, Felipe
> is. I noticed now that you said "please route around Felipe", but
> sorry, no, I'm not going to do that unless there's a really good reason.
> Felipe seems to be around at the moment,
"triggered buffer" isn't selected so we end up with:
|ERROR: "iio_triggered_buffer_setup" [drivers/iio/adc/ti_am335x_adc.ko]
undefined!
Signed-off-by: Sebastian Andrzej Siewior
---
Please merge this into _this_ patch, it is still required.
drivers/iio/adc/Kconfig
* Zubair Lutfullah | 2013-08-25 23:45:23 [+0100]:
>diff --git a/drivers/input/touchscreen/ti_am335x_tsc.c
>b/drivers/input/touchscreen/ti_am335x_tsc.c
>index e1c5300..4124e580 100644
>--- a/drivers/input/touchscreen/ti_am335x_tsc.c
>+++ b/drivers/input/touchscreen/ti_am335x_tsc.c
>@@ -315,11 +321
* Zubair Lutfullah | 2013-08-25 23:45:24 [+0100]:
I am mostly happy with it. There are just two things I pointed out.
Besides that, it looks good from my side.
>diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
>index a952538..ae2202b 100644
>--- a/drivers/iio/adc/ti_
* Zubair Lutfullah | 2013-08-25 23:45:24 [+0100]:
>diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
>index a952538..ae2202b 100644
>--- a/drivers/iio/adc/ti_am335x_adc.c
>+++ b/drivers/iio/adc/ti_am335x_adc.c
…
>+static struct iio_trigger *tiadc_iio_allocate_trigger(
* Zubair Lutfullah | 2013-08-25 23:45:24 [+0100]:
>diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
>index a952538..ae2202b 100644
>--- a/drivers/iio/adc/ti_am335x_adc.c
>+++ b/drivers/iio/adc/ti_am335x_adc.c
>@@ -231,28 +406,56 @@ static int tiadc_probe(struct platfo
* Viresh Kumar | 2013-08-07 15:25:55 [+0530]:
>On 24 July 2013 14:47, Viresh Kumar wrote:
>> On 18 June 2013 10:21, Viresh Kumar wrote:
>
>> Hi Thomas,
>>
>> Do you still see some light of hope in this patch :) ?
>
>Ping!!
tglx, could you please take a look at this patch / thread?
Sebastian
--
* Thomas Meyer | 2013-09-16 23:10:50 [+0200]:
>Hi,
Hi Thomas,
>lockdep complains about this:
>
>[ 92.041513] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
>[ 92.090910] iwlwifi :02:00.0: Radio type=0x1-0x2-0x0
>
>[ 92.094779] =
>[ 92.094780] [ INFO: i
On 10/01/2013 01:44 AM, Ben Hutchings wrote:
> Right, but it looks quite strange to have this thread just for a
> (probably) quite rare event. Maybe some day someone will work out how
> to make Octeon's IRQ management less unusual and then you can use the
> simpler approach for RT...
We have thre
Dear RT folks!
I'm pleased to announce the v3.10.14-rt9 patch set.
Changes since v3.10.14-rt8
- the threshold module option of hwlat is no longer ignored. Path sent
by Mike Galbraith
- two patches from Kirill Tkhai to get basic RT compiled on Sparc.
- the ppc patch for the 5200 has been altere
On 07/07/2013 04:55 PM, Sergei Shtylyov wrote:
> Hello.
Hello Sergei,
> On 05-07-2013 20:12, Sebastian Andrzej Siewior wrote:
>
>> This is a first shot of the cppi41 DMA driver.
>
>Where have you been when I submitted my drivers back in 2009? :-)
Not here it seems :
On 07/08/2013 02:16 PM, Sergei Shtylyov wrote:
>> not using dmaengine and the network driver (cpsw) which is also using
>> cppi 3.1 is having its own implementation of the cppi-dma part. So I
>> think dma enggine implementation is a must here.
>
>Not at all. I'm not familiar with CPSW but DaVi
On 07/08/2013 12:43 PM, George Cherian wrote:
> This patch series adds phy support for AM335X platform.
> This patch series is based on Generic PHY framework [1].
>
>
> This series has
> - adds dual musb instances support for am335x platform (just for
> testing)
> - adds phy-am-
On 07/08/2013 10:34 PM, Ezequiel Garcia wrote:
> Hi,
Hi,
> On Mon, Jul 08, 2013 at 09:44:33PM +0200, Sebastian Andrzej Siewior wrote:
>
>> We need two nodes each one with a glue layer and a musb child node. The
>> instances crap in kernel has to vanish. Also that means
Dear RT Folks,
I'm pleased to announce the 3.8.13-rt14 release.
changes since v3.8.13-rt13:
- added a patch from Uwe Kleine-König to fix the UP breakage introduced by
the recent s/sbin spinlocks/raw_spin_lock/ change.
- added a fix for a livelock of workqueue vs ata-piix. Found by Carsten
Emd
Hi Zubair,
I have here am335x-evm board. The output of voltage4 (via `cat
/sys/bus/iio/devices/iio\:device0/in_voltage4_raw´) returns values in
the range 570…580. I tested the continuous sampling mdoe by executing
the following commands:
|echo 1 > /sys/bus/iio/devices/iio\:device0/scan_elements/i
On 10/07/2013 03:28 PM, Roger Quadros wrote:
> The generic PHY framewrok expects different properties than the
> old USB PHY framework. Supply those properties.
>
> Fixes USB OTG port on GAT04 and N900 after the Generic PHY framework was
> merged in greg/usb-next. [1]
Would it be much pain (and d
Dear RT folks!
I'm pleased to announce the v3.10.10-rt7 patch set.
Changes since v3.10.10-rt6
- hwlat compiles on 32bit (again). Reported by Fernando Lopez-Lezcano.
- bcache is disabled due to usage of anon semaphores. Anyone interrested
in using it?
- "genirq affinity callback" are fixed. Repo
On 08/30/2013 11:29 PM, Ben Hutchings wrote:
> Sebastian, I saw you came up with a fix for this but apparently without
> seeing my earlier message:
Yes Ben, I haven't seen it. If I was on Cc I very sorry for overlooking
it.
> On Thu, 2013-07-25 at 00:31 +0100, Ben Hutchings wrote:
>> Workqueue c
On 09/10/2013 11:02 PM, Matthias Kaehlcke wrote:
> The calculation of the old conversion timeout value was based on the number of
> channels used by this driver. This doesn't take into account that other
> channels
> can be used by the touchscreen driver. Adjust the timeout value to the maximum
>
On Sun, Sep 09, 2012 at 10:50:35AM +1000, Ben Minerds wrote:
> Removed 3 checkpatch.sh warnings and 1 error in
> drivers/usb/gadget/serial.c.
> -sizeof brackets x2
> -remove initialise to 0
> -pr_warning to pr_warn
I have a series pending which removes the last two chunks.
Sebastian
--
To unsubsc
* Oleg Nesterov | 2012-09-03 17:26:09 [+0200]:
>Afaics the usage of update_debugctlmsr() and TIF_BLOCKSTEP in
>step.c was always very wrong.
>
>1. update_debugctlmsr() was simply unneeded. The child sleeps
> TASK_TRACED, __switch_to_xtra(next_p => child) should notice
> TIF_BLOCKSTEP and set/c
On 09/03/2012 05:25 PM, Oleg Nesterov wrote:
Hello.
Hi Oleg,
Sebastian, I changed your patches a bit:
please let me know if you disagree.
Thank you very much. I'm fine with those. Just tested, looks good so
far.
Oleg.
Sebastian
--
To unsubscribe from this list: send the line "uns
On Tue, Nov 27, 2012 at 07:01:08PM +0100, Sebastian Andrzej Siewior wrote:
> Since commit 89c8d91e31f2 ("tty: localise the lock") I see a dead lock
> in one of my dummy_hcd + g_nokia test cases. The first run one was usually
> okay, the second often resulted in a splat by lockde
On Fri, Nov 30, 2012 at 09:21:43AM -0800, Greg Kroah-Hartman wrote:
> > Ping. Can you feed this to your tty tree? :)
>
> It's really late in the release cycle, I would like to have this get
> more testing in linux-next before I send it to Linus, so I was going to
> wait until after 3.8-rc1 is out
On Thu, Nov 01, 2012 at 09:21:16AM +0200, Felipe Balbi wrote:
> then we can merge to net tree and handle the conflicts when merging to
> Linus, that'd be fine by me as long as people know how to solve the
> conflict properly ;-)
Felipe please drop this patch. I don't like this VLAIS patch and its
On Mon, Dec 03, 2012 at 07:57:33PM +0100, Behan Webster wrote:
> However, in order to approximate what gcc is doing in code, obviously
> some math is required. The thought was that macros would hide the
> worst of it, trying not to obfuscate what was actually being done.
Why hide? The thing that i
sg_virt() on highmem pages won't work. This WARN_ON() should catch some
that still try.
Signed-off-by: Sebastian Andrzej Siewior
---
include/linux/scatterlist.h |3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/scatterlist.h b/include/linux/scatterlist.h
index 4b
On 12/03/2012 06:41 PM, Peter Hurley wrote:
The lock logic for tty_set_ldisc() is wrong. Despite existing code in
tty_set_ldisc() and tty_ldisc_hangup(), the ldisc_mutex does **not**
(and should not) play a role in acquiring or releasing ldisc references.
The only thing that needs to happen here
With dummy_hcd and g_nokia (that is CONFIG_USB_GADGET=m,
CONFIG_USB_DUMMY_HCD=m, CONFIG_USB_G_NOKIA=m) I see a lockdep complaing
about a "circular locking dependency" after executing
|modprobe dummy_hcd
|modprobe g_nokia
|cat /dev/ttyACM0 &
|sleep 1
|echo basilimi > /dev/ttyGS2
the first one goes
On 12/05/2012 10:46 PM, Andrew Morton wrote:
--- a/include/linux/scatterlist.h
+++ b/include/linux/scatterlist.h
@@ -198,6 +198,9 @@ static inline dma_addr_t sg_phys(struct scatterlist *sg)
**/
static inline void *sg_virt(struct scatterlist *sg)
{
+#ifdef CONFIG_DEBUG_SG
+ WARN_ON(Pa
From: Sebastian Andrzej Siewior
Since commit 89c8d91e31f2 ("tty: localise the lock") I see a dead lock
in one of my dummy_hcd + g_nokia test cases. The first run was usually
okay, the second often resulted in a splat by lockdep and the third was
usually a dead lock.
Lockdep complained
On Mon, Dec 17, 2012 at 06:21:16PM +0100, Armando Visconti wrote:
> >Besides that the patch looks fine :)
>
> Do you mean that 'inited' should be changed with 'initialized'?
Yes, I do.
> Oh ... my poor english... :(
Don't worry. Others, including myself, do this from time to time as well :)
>
>
On Tue, Dec 18, 2012 at 10:44:19AM +0800, fangxiaozhi 00110321 wrote:
> diff -uprN linux-3.7_bak/drivers/usb/storage/initializers.c
> linux-3.7/drivers/usb/storage/initializers.c
> --- linux-3.7_bak/drivers/usb/storage/initializers.c 2012-12-11
> 09:56:11.0 +0800
> +++ linux-3.7/drivers/
On Wed, Dec 19, 2012 at 03:13:32AM +, Fangxiaozhi (Franko) wrote:
> By the way, I found the kernel is updated to 3.7.1 today. So I have to
> update my patch based on 3.7.1, and resubmit it?
> Right?
You should rebase your patch on top of Greg's usb-next branch of his usb tree.
h
On 04/17/2013 06:25 PM, John Kacur wrote:
> Where did you fix these up? Can we have access?
I don't see reason why not. I just pushed my quilt queue to
git://git.kernel.org/pub/scm/linux/kernel/git/bigeasy/rt-v3.8-devel.git
Remember it is not a kernel tree, it is a quilt queue.
> Thanks
>
> Jo
1 - 100 of 3778 matches
Mail list logo
