Hi Linus:
This push fixes a build error on ARM that was introduced in 3.13-rc1.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
or
master.kernel.org:/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
Krzysztof Hałasa (1):
crypto: ixp4xx - Fix kernel
On Tue, Dec 31, 2013 at 11:51:16AM +0100, Krzysztof Hałasa wrote:
> drivers/crypto/ixp4xx_crypto.c: In function 'ixp_module_init':
> drivers/crypto/ixp4xx_crypto.c:1419:2: error: 'dev' undeclared (first use in
> this function)
>
> Now builds. Not tested on real hw.
>
> Signed-off-by: Krzysztof
On some architectures, in certain CPU deep idle states the local timers stop.
An external clock device is used to wakeup these CPUs. The kernel support for
the
wakeup of these CPUs is provided by the tick broadcast framework by using the
external clock device as the wakeup source.
However not
On Wed, 2014-01-01 at 14:34 +0900, Tetsuo Handa wrote:
> I think we want formatting directive support because we have users shown
> below.
>
> fs/afs/internal.h: printk("[%-6.6s] "FMT"\n", current->comm
> ,##__VA_ARGS__)
> fs/cachefiles/internal.h: printk(KERN_DEBUG "[%-6.6s]
Joe Perches wrote:
> > Please describe your format and rules (e.g. what byte starts a built-in
> > token;
> > what bytes are used for representing variable name, what separates flags,
> > field
> > width and precision options from variable name if these options are
> > specified,
> > what byte
The nfmsg variable is not used (except in sizeof operator which does
not care about its value) between the first and second time it is
assigned the value. Furthermore, nlmsg_data has no side effects, so
the assignment can be safely removed.
Signed-off-by: Michal Nazarewicz
Cc: Patrick McHardy
[commit 8185554d: fix incorrect inode acl reset] introduced a dead
code by adding a condition which can never be true to an else
branch. The condition can never be true because it is already
checked by a previous if statement which causes function to return.
Signed-off-by: Michal Nazarewicz
Hi Vincent,
On 12/18/2013 06:43 PM, Vincent Guittot wrote:
> This patch applies on top of the two patches [1][2] that have been proposed by
> Peter for creating a new way to initialize sched_domain. It includes some
> minor
> compilation fixes and a trial of using this new method on ARM
Hi Jens,
On Wed, Jan 1, 2014 at 12:38 AM, Jens Axboe wrote:
> On Thu, Dec 26 2013, Ming Lei wrote:
>> One problem is that request->start_time/start_time_ns could be
>> set as wrong.
>>
>> Also it is normal to intialize one data structure just after its
>> allocation.
>>
>> So move the
In PVH the shared grant frame is the PFN and not MFN,
hence its mapped via the same code path as HVM.
The allocation of the grant frame is done differently - we
do not use the early platform-pci driver and have an
ioremap area - instead we use balloon memory and stitch
all of the non-contingous
From: Mukesh Rathor
Most of the functions in page.h are prefaced with
if (xen_feature(XENFEAT_auto_translated_physmap))
return mfn;
Except the mfn_to_local_pfn. At a first sight, the function
should work without this patch - as the 'mfn_to_mfn' has
a similar check. But
The revector and copying of the P2M only happens when
!auto-xlat and on 64-bit builds. It is not obvious from
the code, so lets have seperate 32 and 64-bit functions.
We also invert the check for auto-xlat to make the code
flow simpler.
Suggested-by: Stefano Stabellini
Signed-off-by: Konrad
From: Mukesh Rathor
In xen_add_extra_mem() we can skip updating P2M as it's managed
by Xen. PVH maps the entire IO space, but only RAM pages need
to be repopulated.
Signed-off-by: Mukesh Rathor
Signed-off-by: Konrad Rzeszutek Wilk
---
arch/x86/xen/setup.c | 23 ---
1 file
From: Mukesh Rathor
The VCPU bringup protocol follows the PV with certain twists.
>From xen/include/public/arch-x86/xen.h:
Also note that when calling DOMCTL_setvcpucontext and VCPU_initialise
for HVM and PVH guests, not all information in this structure is updated:
- For HVM guests, the
We have this odd scenario of where for PV paths we take a shortcut
but for the HVM paths we first ioremap xen_hvm_resume_frames, then
assign it to gnttab_shared.addr. This is needed because gnttab_map
uses gnttab_shared.addr.
Instead of having:
if (pv)
return gnttab_map
From: Mukesh Rathor
PVH is a PV guest with a twist - there are certain things
that work in it like HVM and some like PV. There is
a similar mode - PVHVM where we run in HVM mode with
PV code enabled - and this patch explores that.
The most notable PV interfaces are the XenBus and event
The patches, also available at
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/pvh.v12
implements the neccessary functionality to boot a PV guest in PVH mode.
This blog has a great description of what PVH is:
From: Mukesh Rathor
As we do not have yet a mechanism for that.
This also impacts the ARM/ARM64 code (which does not have
hotplug support yet).
Signed-off-by: Mukesh Rathor
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/cpu_hotplug.c | 4 +++-
1 file changed, 3 insertions(+), 1
From: Mukesh Rathor
.. which are surprinsingly small compared to the amount for PV code.
PVH uses mostly native mmu ops, we leave the generic (native_*) for
the majority and just overwrite the baremetal with the ones we need.
We also optimize one - the TLB flush. The native operation would
From: Mukesh Rathor
In the bootup code for PVH we can trap cpuid via vmexit, so don't
need to use emulated prefix call. We also check for vector callback
early on, as it is a required feature. PVH also runs at default kernel
IOPL.
Finally, pure PV settings are moved to a separate function that
From: Mukesh Rathor
PVH allows PV linux guest to utilize hardware extended capabilities,
such as running MMU updates in a HVM container.
The Xen side defines PVH as (from docs/misc/pvh-readme.txt,
with modifications):
"* the guest uses auto translate:
- p2m is managed by Xen
- pagetables are
From: Mukesh Rathor
Which is a PV guest with auto page translation enabled
and with vector callback. It is a cross between PVHVM and PV.
The Xen side defines PVH as (from docs/misc/pvh-readme.txt,
with modifications):
"* the guest uses auto translate:
- p2m is managed by Xen
- pagetables are
The 'xen_hvm_resume_frames' used to be an 'unsigned long'
and contain the virtual address of the grants. That was OK
for most architectures (PVHVM, ARM) were the grants are contingous
in memory. That however is not the case for PVH - in which case
we will have to do a lookup for each virtual
From: Mukesh Rathor
PVH is a PV guest with a twist - there are certain things
that work in it like HVM and some like PV. For the XenBus
mechanism we want to use the PVHVM mechanism.
Signed-off-by: Mukesh Rathor
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/xenbus/xenbus_client.c | 3
P2M is not available for PVH. Fortunatly for us the
P2M code already has mostly the support for auto-xlat guest thanks to
commit 3d24bbd7dddbea54358a9795abaf051b0f18973c
"grant-table: call set_phys_to_machine after mapping grant refs"
which: "
introduces set_phys_to_machine calls for
From: Mukesh Rathor
For PVHVM the shared_info structure is provided via the same way
as for normal PV guests (see include/xen/interface/xen.h).
That is during bootup we get 'xen_start_info' via the %esi register
in startup_xen. Then later we extract the 'shared_info' from said
structure (in
The function gnttab_max_grant_frames() returns the maximum amount
of frames (pages) of grants we can have. Unfortunatly it was
dependent on gnttab_init() having been run before to initialize
the boot max value (boot_max_nr_grant_frames).
This meant that users of gnttab_max_grant_frames would
From: Mukesh Rathor
During early bootup we start life using the Xen provided
GDT, which means that we are running with %cs segment set
to FLAT_KERNEL_CS (FLAT_RING3_CS64 0xe033, GDT index 261).
But for PVH we want to be use HVM type mechanism for
segment operations. As such we need to switch to
On 12/30/13 09:26, Martin Schwidefsky wrote:
On Mon, 30 Dec 2013 16:11:10 +0100
Oleg Nesterov wrote:
Not sure I understand... except that timekeeping_resume() does
__timekeeping_inject_sleeptime().
Hmm, you are right. The sleeptime is added to the monotonic boottime.
So the first value of
I set the in-reply-to to try to put my new patch here, but failed.
I need to figure it out.
From: Joe Xue
The LED pattern trigger allows LEDs blink in user defined pattern.
v2: Change the pattern memory from fixed static to malloc
Change the timer schedule way to save cpu time
Add the
From: Joe Xue
The LED pattern trigger allows LEDs blink in user defined pattern.
v2: Change the pattern memory from fixed static to malloc
Change the timer schedule way to save cpu time
Add the mutex to protect the pattern operation
new file:
On 01/01/14 00:55, Ilia Mirkin wrote:
On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce wrote:
On 31/12/13 10:36, Ilia Mirkin wrote:
On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce
wrote:
System x86_64 with openSUSE 13.1.
X.Org version: 1.14.99.905
openSUSE 12.2 kernels boot successfully into a
On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce wrote:
> On 31/12/13 10:36, Ilia Mirkin wrote:
>>
>> On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce
>> wrote:
>>>
>>> System x86_64 with openSUSE 13.1.
>>> X.Org version: 1.14.99.905
>>>
>>> openSUSE 12.2 kernels boot successfully into a graphical screen,
On 12/19/2013 09:41 PM, joeyli wrote:
>>
>> What platform do you have that has TAD support? I am wondering how this
>> was tested.
>>
>
> It's a testing platform that's only support get/set time functions of
> ACPI TAD.
>
It would be really, really good to get this into Qemu (either SeaBIOS or
On 31/12/13 10:36, Ilia Mirkin wrote:
On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce wrote:
System x86_64 with openSUSE 13.1.
X.Org version: 1.14.99.905
openSUSE 12.2 kernels boot successfully into a graphical screen, login to
KDE4, etc. all normal.
3.13-rc kernels boot fully with X running but
min_free_kbytes may be updated during thp's initialization. Sometimes,
this will change the value being set by user. Showing message will
clarify this confusion.
Signed-off-by: Han Pingtian
---
mm/huge_memory.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git
On Mon, Dec 30, 2013 at 4:45 PM, Kees Cook wrote:
>
> NAK. If you have selected CONFIG_CC_STACKPROTECTOR_STRONG, the build
> the fail hard. Without this, it means you'll end up with kernels that
> build and show a stackprotector option in their config, which is
> false.
What we really really
Hi Pavel,
>>> +static struct task_struct *h4p_thread;
>>
>> Can’t this be done using a work queue. You are looking at a 3.14
>> kernel the earliest. We have way better primitives these days.
>
> I tried to convert it to work queue, but was not too
> succesfull. Workqueue is not really good
On Tue, Dec 31, 2013 at 10:12:31AM -0200, Henrique de Moraes Holschuh wrote:
> On Tue, 31 Dec 2013, Julian Andres Klode wrote:
> > We might be able to work around this by simple setting stop = start
> > if a new write causes the stop threshold to be below the start
> > threshold. But this also
On 12/31/2013 11:21 AM, Konrad Rzeszutek Wilk wrote:
>
> So, I am wondering if this is related to " x86/fpu: CR0.TS should be set
> before trap
> into PV guest's #NM exception handle" which does have a similar pattern - you
> do enough of the task switches and the FPU is screwed.
>
> See
>
On Tuesday 31 December 2013, Gene Heskett wrote:
>On Tuesday 31 December 2013, Roger Heflin wrote:
>>rescue boot it, change the /boot mount line in /etc/fstab to add
>>noauto (like noauto,defaults...or whatever else you already have) and
>>change the last column to 0 to disable fsck on it.
>>
>>It
Hi!
> > +static struct task_struct *h4p_thread;
>
> Can’t this be done using a work queue. You are looking at a 3.14
> kernel the earliest. We have way better primitives these days.
I tried to convert it to work queue, but was not too
succesfull. Workqueue is not really good match for what this
On 13-12-31 03:40 PM, walt wrote:
> On 12/18/2013 01:11 PM, Greg Kroah-Hartman wrote:
>> 3.12-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: David Laight
>>
>> commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e upstream.
>>
>> Section
From: Thadeu Lima de Souza Cascardo
Date: Mon, 23 Dec 2013 15:34:29 -0200
> Since commit 52367a763d8046190754ab43743e42638564a2d1
> ("cxgb4/cxgb4vf: Code cleanup to enable T4 Configuration File support"),
> we have failures like this during cxgb4 probe:
>
> cxgb4 :01:00.4: bad SGE FL page
__u32 is only useful for kernel-user interface, u32 should be enough
for kernel. Formatting was very confusing around __get_free_pages().
Signed-off-by: Pavel Machek
diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
index 936093e..1387208 100644
--- a/drivers/hv/connection.c
+++
From: Ding Tianhong
Date: Mon, 30 Dec 2013 15:40:25 +0800
> This is the second patchset for slight optimization of address compare,
> mainly for net tree, just following the Joe's opinion, it will help review
> the code for maintainers and supports.
>
> v2: Change some style for patch 2.
>
This change turns on debugfs support for the BCM281xx watchdog driver.
Signed-off-by: Markus Mayer
---
arch/arm/configs/bcm_defconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/bcm_defconfig b/arch/arm/configs/bcm_defconfig
index 10d1392..d4d0083 100644
---
This change introduces debugfs support for the BCM281xx watchdog driver.
Signed-off-by: Markus Mayer
---
drivers/watchdog/Kconfig| 10
drivers/watchdog/bcm_kona_wdt.c | 116 +--
2 files changed, 122 insertions(+), 4 deletions(-)
diff --git
This series adds debugfs support to the bcm281xx watchdog driver. Most
of the code submitted here was already included as part of v5 of the
original driver submission. See
http://www.spinics.net/lists/linux-watchdog/msg03328.html
However, the debugfs code has since been broken out of the original
A Happy new year to all :)
Just wondering whether anyone has any ideas on how I could force the
TSC to resync?
Starting to get a bit desperate. The motherboard manufacturers support
is useless They keep telling me to install Windows *groan*. I dont
think there is any easy way to expose
On 12/31/2013 08:37 PM, Mike Turquette wrote:
Quoting Mike Turquette (2013-12-19 00:07:29)
Quoting Sylwester Nawrocki (2013-12-16 14:14:37)
Hi Mike,
Laurent has already taken this patch into his tree, could you apply
the remaining ones to your clk tree so this series has enough exposure
in
On 12/30/2013 09:58 PM, rui wang wrote:
> On 12/30/13, Prarit Bhargava wrote:
>>
>>
>> On 12/30/2013 07:56 AM, rui wang wrote:
>>
> ...
>> Okay, so the big issue is that we need to do the calculation without this
>> cpu,
>
>>
>> int check_irq_vectors_for_cpu_disable(void)
>> {
>>int
On Monday, December 30, 2013 12:00:56 PM Daniel Lezcano wrote:
> Hi Rafael,
>
> this pull request provides a single fix for the calxeda cpuidle driver.
> It is based on v3.13-rc6.
>
> * Andre Przywara fixed a compilation warning due to the driver probe
> function prototype mismatch for the
From: Rafael J. Wysocki
The changes in the ACPI-based PCI hotplug (ACPIPHP) subsystem made
during the 3.12 development cycle uncovered a problem with VGA
switcheroo that on some systems, when the device-specific method
(ATPX in the radeon case, _DSM in the nouveau case) is used to turn
off the
On Tuesday, December 31, 2013 10:45:46 AM Yinghai Lu wrote:
> On Mon, Dec 30, 2013 at 5:15 AM, Rafael J. Wysocki wrote:
> > On Monday, December 30, 2013 01:51:28 PM Rafael J. Wysocki wrote:
> >> > We have patches that need to stop ioapic and iommu between
> >> > pci_stop_root_bus and
On 12/18/2013 01:11 PM, Greg Kroah-Hartman wrote:
> 3.12-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: David Laight
>
> commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e upstream.
>
> Section 4.11.7.1 of rev 1.0 of the xhci
On 12/31/2013 11:40 AM, Randy Dunlap wrote:
> arch/x86/lguest/Kconfig:1:error: recursive dependency detected!
> arch/x86/lguest/Kconfig:1:symbol LGUEST_GUEST depends on VIRTUALIZATION
> arch/x86/Kconfig.virt:2: symbol VIRTUALIZATION is selected by
> LGUEST_GUEST
> warning: (X86_VSMP)
On Tue, 2013-12-31 at 14:00 -0500, David Miller wrote:
> From: Neil Horman
> Date: Mon, 23 Dec 2013 08:29:41 -0500
>
> > The SCTP protocol has several deprecation warnings in its setsockopt path
> > that
> > can be triggered by unprivlidged users. Since these are not ratelimited,
> > we can
>
On 12/31/2013 11:26 AM, Randy Dunlap wrote:
> On 12/30/13 10:40, Dave Hansen wrote:
>> From: Dave Hansen
>> This removes another 4 lines from the default x86 menu. Note
>> that I slightly changed the MTRR prompt text since PAT is
>> hidden under here. This makes PAT easier to find since it
>>
On 12/31/2013 11:26 AM, Randy Dunlap wrote:
> On 12/30/13 10:40, Dave Hansen wrote:
>> From: Dave Hansen
>>
>> This takes the relatively obscure (NUMA-Q anyone?) platforms
>> (both 32 and 64-bit) and sticks them in their own menu.
>> Virtually nobody needs to set these, and those that do know how
You can add there are SCSI targets out there employing this feature as well.
=;^)
-Original Message-
From: linux-scsi-ow...@vger.kernel.org
[mailto:linux-scsi-ow...@vger.kernel.org] On Behalf Of Martin K. Petersen
Sent: Monday, December 23, 2013 8:35 AM
To: Christoph Hellwig
Cc: Jens
On 12/31/2013 02:41 PM, Dominique Martinet wrote:
> Hi,
Thanks for the fast reply.
> Richard Yao wrote on Tue, Dec 31, 2013 :
>> #!/bin/bash
>> cat <<-EOF
>> EOF
>>
>> Running this causes bash to fork via clone(), set fd=0 to point to an
>> empty file in /tmp, unlink it and then execve cat.
Hi,
Richard Yao wrote on Tue, Dec 31, 2013 :
> #!/bin/bash
> cat <<-EOF
> EOF
>
> Running this causes bash to fork via clone(), set fd=0 to point to an
> empty file in /tmp, unlink it and then execve cat. Specifically,
> something like this;
>
> [pid 3699] open("/tmp/sh-thd-1388524249",
>
On 12/30/13 10:40, Dave Hansen wrote:
> The x86 "Processor type and features" menu has really been
> letting itself go over the years. It needs to be put on a
> diet as a new-year's resolution.
Applying all 12 patches in order provokes kconfig:
arch/x86/lguest/Kconfig:1:error: recursive
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/cros_ec_keyb.c | 80 ---
1 file changed, 45 insertions(+), 35 deletions(-)
diff --git a/drivers/input/keyboard/cros_ec_keyb.c
b/drivers/input/keyboard/cros_ec_keyb.c
index d44c5d4..03cb960 100644
---
u8 is proper in-kernel type for unsigned byte data.
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/cros_ec_keyb.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/input/keyboard/cros_ec_keyb.c
b/drivers/input/keyboard/cros_ec_keyb.c
On 12/31/2013 04:56 AM, Mark Cave-Ayland wrote:
Hi Larry,
Could it be that you don't see the issue the locally because you've got
different compiler optimisation settings? I've seen a similar bug recently on
another project where the "may be used uninitialized" warning appears with -O0
and -O1
On 12/30/13 10:40, Dave Hansen wrote:
> From: Dave Hansen
>
> This removes another 4 lines from the default x86 menu. Note
> that I slightly changed the MTRR prompt text since PAT is
> hidden under here. This makes PAT easier to find since it
> "depends on MTRR" anyway.
I would have put
On 12/30/13 10:40, Dave Hansen wrote:
> From: Dave Hansen
>
> This takes the relatively obscure (NUMA-Q anyone?) platforms
> (both 32 and 64-bit) and sticks them in their own menu.
> Virtually nobody needs to set these, and those that do know how
> to find them the hard way.
I'd sorta prefer to
On Tuesday 31 December 2013 17:32:14 jjhib...@traphandler.com wrote:
>
> + ethernet@3000 {
> + compatible = "davicom,dm9000";
> + reg = <0x3000 0x2 0x3004 0x2>;
> +
On Tue, Dec 31, 2013 at 10:42:47AM -0800, H. Peter Anvin wrote:
> On 12/30/2013 07:52 AM, halfdog wrote:
> >>
> >> Still in VirtualBox?
> >
> > Yes, again: after comparing the results from initrd on real hardware
> > with Vbox, I'm getting to understand the timing problem involved and why
> >
I have a small shell script:
#!/bin/bash
cat <<-EOF
EOF
Running this causes bash to fork via clone(), set fd=0 to point to an
empty file in /tmp, unlink it and then execve cat. Specifically,
something like this;
[pid 3699] open("/tmp/sh-thd-1388524249",
O_WRONLY|O_CREAT|O_EXCL|O_TRUNC, 0600) =
On Tuesday 31 December 2013, Roger Heflin wrote:
>rescue boot it, change the /boot mount line in /etc/fstab to add
>noauto (like noauto,defaults...or whatever else you already have) and
>change the last column to 0 to disable fsck on it.
>
>It should boot then, and you have the machine fully up
Quoting Mark Brown (2013-12-31 08:09:16)
> On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
>
> > Commit 1b1ccee1e821 "mfd: s2mps11: Fix build after regmap field rename
> > in sec-core.c" is also touching this file, which is in Mark's tree
> > right now. If I rebase
>
> It's been
Hi Linus,
Happy New Year!
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get a fix for panic
in gpio-keys
On Tue 2013-12-31 13:29:21, Richard Weinberger wrote:
> On Tue, Dec 31, 2013 at 12:33 PM, Pavel Machek wrote:
> > On Tue 2013-12-31 00:00:39, Joe Xue wrote:
> >> > What about something like this?
> >> >
> >> > Not shcheduling timer when nothing changed should save a bit of
> >> > power/cpu...
>
From: Neil Horman
Date: Mon, 23 Dec 2013 08:29:41 -0500
> The SCTP protocol has several deprecation warnings in its setsockopt path that
> can be triggered by unprivlidged users. Since these are not ratelimited, we
> can
> spam the logs quite easily here. Since these are all deprecation
> > --- a/drivers/xen/xenbus/xenbus_client.c
> > +++ b/drivers/xen/xenbus/xenbus_client.c
> > @@ -45,6 +45,7 @@
> > #include
> > #include
> > #include
> > +#include
> >
> > #include "xenbus_probe.h"
> >
> > @@ -743,7 +744,7 @@ static const struct xenbus_ring_ops ring_ops_hvm = {
> >
Hi Henrik,
On Tue, Dec 31, 2013 at 10:26:31AM +0100, Henrik Rydberg wrote:
> Hi Felipe,
>
> > Adds a helper function to send end touch events for active tracking ids.
> > And also implements it in egalax driver.
>
> What problematic scenario is this supposed to solve?
>
> The 'release on
>> + * Based on Richard Purdie's ledtrig-timer.c and Atsushi Nemoto's
>> + * ledtrig-heartbeat.c and Shuah Khan's ledtrig-transient.c
>
> I stil think this belongs in user space except for platforms with hardware
> acceleration for it.
This can free the user space application from loop or thread.
On Mon, Dec 30, 2013 at 5:15 AM, Rafael J. Wysocki wrote:
> On Monday, December 30, 2013 01:51:28 PM Rafael J. Wysocki wrote:
>> > We have patches that need to stop ioapic and iommu between
>> > pci_stop_root_bus and pci_remove_root_bus.
>
> BTW, what *exactly* do they need to be stopped between?
rescue boot it, change the /boot mount line in /etc/fstab to add
noauto (like noauto,defaults...or whatever else you already have) and
change the last column to 0 to disable fsck on it.
It should boot then, and you have the machine fully up were you can do
better debugging.
ie mount /boot may
On 12/30/2013 07:52 AM, halfdog wrote:
>>
>> Still in VirtualBox?
>
> Yes, again: after comparing the results from initrd on real hardware
> with Vbox, I'm getting to understand the timing problem involved and why
> timing in VBox is different: The test program usually OOPSes when
> touching FPU
Please get rid of your Mail-Followup-To: header:
Mail-Followup-To: Krzysztof Hałasa ,
lkml ,
linux-arm-ker...@lists.infradead.org,
Russell King ,
On 31/12/2013 17:32, jjhib...@traphandler.com wrote:
From: jean-jacques hiblot
The EBI/SMC external interface is used to access external peripherals (NAND
and Ethernet controller in the case of sam9261ek). Different configurations and
timings are required for those peripherals. This bus
Greetings;
I can't build a bootable 3.12.6 kernel, it seems to die quite fast with a
trace blaming binfmt-some-hex-number. Or fail well into the boot waiting
for / to come available. But if I choose a shell at that failure, it
isn't / that is not shown in a blkid report, it is /boot, named
Hi Wim,
Thanks for your comments. I addressed them and will be sending out the
resulting patches shortly.
> Questions/remarks I still have:
> 1) *debugfs is defined in the bcm_kona_wdt struct, but busy_count isn't.
>Seems odd to me. What's the reason?
secure_register_read() only took a void
On 12/31/13 05:48, Gerhard Sittig wrote:
> On Tue, Dec 31, 2013 at 11:51 +0100, Krzysztof Hałasa wrote:
>>
>> drivers/crypto/ixp4xx_crypto.c: In function 'ixp_module_init':
>> drivers/crypto/ixp4xx_crypto.c:1419:2: error: 'dev' undeclared (first use in
>> this function)
>>
>> Now builds. Not
Hello Jean-Jacques
On 31/12/2013 17:32, jjhib...@traphandler.com wrote:
From: Jean-Jacques Hiblot
Hi Nicolas,
This patch set aims at bringing a basic device tree support for the sam9261.
It's mostly based on the sam9263 stuff.
The only new thing here is the smc bus driver. It's a very simple
On Tue, 31 Dec 2013 16:55:33 +
Mark Brown wrote:
> On Thu, Dec 12, 2013 at 06:59:17PM +0100, Jean-Francois Moine wrote:
>
> > This patch renders optional the CODEC name / OF node on sound card register,
> > as it is done for the CPU side, in the case the CODEC DAI name is unique.
>
> >
Hi Magnus,
On Wednesday 18 December 2013 07:26:15 Magnus Damm wrote:
> On Wed, Dec 18, 2013 at 1:08 AM, Laurent Pinchart wrote:
> > On Tuesday 17 December 2013 11:38:23 Magnus Damm wrote:
> >> From: Magnus Damm
> >>
> >> Add support for SCIF functions SCK, TXD, RXD, CTS and RTS to the
> >>
Hello Jean-Jacques,
On 31/12/2013 17:33, jjhib...@traphandler.com wrote:
From: jean-jacques hiblot
The test (pdev->resource[1].flags != IORESOURCE_IRQ) is broken because the flags
value may contain not only the information IORESSOURCE_IRQ but also the IRQ type
(IORESOURCE_IRQ_HIGHLEVEL for
On Wed, Jan 01, 2014 at 01:00:44AM +0800, Axel Lin wrote:
> I just found this commit after pull regulator updates.
> So why to use 'platform' prefix in MODULE_ALIAS for i2c driver?
> Does it really work?
No, it shouldn't work - I'll drop that commit for now. Sorry, such a
mistake didn't occur
On 12/31/2013 05:28 PM, Peter Zijlstra wrote:
On Mon, Dec 30, 2013 at 02:44:46PM +0100, Daniel Lezcano wrote:
This patchset does a cleanup on the parameters passed from the function
'trigger_load_balance' to the underneath functions.
Doesn't actually apply right.. will maybe spend more time
On Mon, Dec 23, 2013 at 03:25:38PM +0800, Xiubo Li wrote:
> Try to get the device's module clock if the dt has no clocks and
> system-clock-frequency properties.
Applied, thanks.
signature.asc
Description: Digital signature
Hi,
I just found this commit after pull regulator updates.
So why to use 'platform' prefix in MODULE_ALIAS for i2c driver?
Does it really work?
Regards,
Axel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Mon, Dec 30, 2013 at 03:52:31PM +0100, Michael Gunselmann wrote:
> From: Martin Hofmann
>
> The file 80211hdr.h contained 4 macros (in both little and big endain fashion)
> that were not used in the driver. Thus, this patch removes them.
>
Better to leave them in. They are useful as
On Thu, Dec 12, 2013 at 06:59:17PM +0100, Jean-Francois Moine wrote:
> This patch renders optional the CODEC name / OF node on sound card register,
> as it is done for the CPU side, in the case the CODEC DAI name is unique.
> This simplifies the definition of CODECs with multiple DAIs,
On Mon, Dec 30, 2013 at 03:52:34PM +0100, Michael Gunselmann wrote:
> wpa2.h: Checkpatch does no longer complain about anything
>
> wpa2.c: Checkpatch complains about some lines that are longer than
> 80 characters. Breaking them would deteriorate the readability
> so these lines were
Sent from my iPad
> On 30 dec. 2013, at 19:14, Julia Lawall wrote:
>
> From: Julia Lawall
>
> Ether_addr_equal_64bits is more efficient than ether_addr_equal, and can be
> used when each argument is an array within a structure that contains at
> least two bytes of data beyond the array.
>
1 - 100 of 408 matches
Mail list logo
