No. Fixing one bootloader is almost impossible. Fixing them all is a
Sisiphyean task.
Yinghai Lu wrote:
>On Mon, Apr 15, 2013 at 7:36 PM, H. Peter Anvin wrote:
>> On 04/15/2013 03:00 PM, Yinghai Lu wrote:
>>>
>>> looks you are trying redo the work for bootloader to pick loaded
>phys addr.
Hi,
I am working with an embedded system, using the Intel Atom CPU,
and the usual motherboard components:
# lspci
00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI
Bridge (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor
From: "Yan, Zheng"
The uncore subsystem in Ivy Bridge-EP is similar to Sandy Bridge-EP.
There are some differences in config register encoding and pci device
IDs. The Ivy Bridge-EP uncore also supports a few new events.
Signed-off-by: Yan, Zheng
---
From: "Yan, Zheng"
The existing code assumes all Cbox and PCU events are using
filter, but actually the filter is event specific. Furthermore
the filter is sub-divided into multiple fields which are used
by different events.
Signed-off-by: Yan, Zheng
Reported-by: Stephane Eranian
---
From: "Yan, Zheng"
On -rt kfree() can schedule, but CPU_{STARTING,DYING} should be
atomic. So use a list to defer kfree until CPU_{ONLINE,DEAD}.
Signed-off-by: Yan, Zheng
---
arch/x86/kernel/cpu/perf_event_intel_uncore.c | 28 ---
1 file changed, 25 insertions(+), 3
From: "Yan, Zheng"
I sent these 3 patches to the mailing list some time ago, but got no response.
Patch 1 and patch 2 are bug fixes, patch 3 adds Ivy Bridge-EP support.
Regards
Yan, Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 04/16/2013 05:12 AM, Ingo Molnar wrote:
* Waiman Long wrote:
[...]
Patches 2 improves the mutex spinning process by reducing contention among the
spinners when competing for the mutex. This is done by using a MCS lock to put
the spinners in a queue so that only the first spinner will try
From: Ludovic Desroches
The BUG_ON() directive is triggered probably due to a latency modification
following inclusion of c10d736 (softirq: reduce latencies).
This condition has not been met before 3.9-rc1 and doesn't trigger without
this patch.
We now make sure that DMA channel is idle before
Argh. Taking a step back helped clear my head.
For the -stable releases, I agree we should just go with your
revert-plus-hlist_del_init_rcu patch. I will give it a test
when I am in the office.
For the v3.10 release, we should work on making this more
correct and completely documented.
Robin
On 16-04-2013 15:10, Prabhakar lad wrote:
From: Lad, Prabhakar
with recent commit with id 068a0df76023926af958a336a78bef60468d2033
Please also specify the summary line of that commit in parens (or however
you like).
which adds add length check for mmap, the application were failing
Hello.
On 16-04-2013 14:54, Prabhakar lad wrote:
From: Lad, Prabhakar
with recent commit with id 068a0df76023926af958a336a78bef60468d2033
Please also specify the summary line of that commit in parens (or however
you like).
which adds add length check for mmap, the application were
On Tue, Apr 16, 2013 at 01:31:40PM +0200, Thomas Petazzoni wrote:
> Dear Jason Cooper,
>
> On Tue, 16 Apr 2013 07:29:51 -0400, Jason Cooper wrote:
>
> > > Do not send this series upstream (or even in -next) until it has been at
> > > least build-tested and acked by the affected architectures.
On Tue, Apr 9, 2013 at 10:36 PM, wrote:
>
> + /* Found it! return success */
I'm pretty sure this comment is in the wrong place.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
* Borislav Petkov wrote:
> Hi,
>
> here it is.
>
> Original tip:x86/cpu tree state is this:
>
> 3019653a5758 x86/fpu: Fix FPU initialization
> 042c16f14161 x86, CPU, AMD: Drop useless label
> 982f33db626e x86, AMD: Correct {rd,wr}msr_amd_safe warnings
> e277a4938574 x86: Fold-in trivial
* Borislav Petkov wrote:
> On Tue, Apr 16, 2013 at 11:25:28AM +0200, Ingo Molnar wrote:
> > I've got limited extra capacity right now - but if Peter rebases
> > tip:x86/cpu or you send a pullable update of tip:x86/cpu I can stick
> > it into -tip testing and yell if it goes wrong.
> >
>
> Ok,
* Robin Holt wrote:
> We recently noticed that reboot of a 1024 cpu machine takes approx 16
> minutes of just stopping the cpus. The slowdown was tracked to commit
> f96972f.
>
> The current implementation does all the work of hot removing the cpus
> before halting the system. We are
Dear Jason Cooper,
On Tue, 16 Apr 2013 07:29:51 -0400, Jason Cooper wrote:
> > Do not send this series upstream (or even in -next) until it has been at
> > least build-tested and acked by the affected architectures. AFAIK it
> > breaks microblaze build (simple missing #include) and isn't yet
On Tue, Apr 16, 2013 at 4:50 PM, Mark Brown wrote:
> On Mon, Apr 15, 2013 at 02:10:27PM +0530, Girish K S wrote:
>> From: Girish K S
>>
>> The 64xx spi driver supports partial polling mode.
>> Only the last chunk of the transfer length is transferred
>> or recieved in polling mode.
>
> I'm
Hi Linus,
please pull this fix for a missing dependency when generating
scripts/mod/devicetable-offsets.h. This dependency got introduced in
v3.9-rc1.
Thanks,
Michal
The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
Linux 3.9-rc1 (2013-03-03 15:11:05 -0800)
are
On Tue, Apr 16, 2013 at 06:26:36PM +0800, Xiao Guangrong wrote:
> On 04/16/2013 05:31 PM, Robin Holt wrote:
> > On Tue, Apr 16, 2013 at 02:39:49PM +0800, Xiao Guangrong wrote:
> >> The commit 751efd8610d3 (mmu_notifier_unregister NULL Pointer deref
> >> and multiple ->release()) breaks the fix:
>
On Wed, Apr 10, 2013 at 02:46:20PM +0800, Axel Lin wrote:
> We can save a register read operation in some case if read
> expand_register first.
> If info->expand_register.voltage_mask bit is set, no need to read
> voltage_reg.
Applied, thanks.
signature.asc
Description: Digital signature
15.04.2013 13:59, l...@tigusoft.pl пишет:
> There are 2 hard drives (normal, magnetic) in software raid 1
> on 3.2.41 kernel.
>
> When I write into them e.g. using dd from /dev/zero to a local file
> (ext4 on default settings), running 2 dd at once (writing two files) it
> starves all other
On Sat, Apr 13, 2013 at 01:25:38AM +0800, Axel Lin wrote:
> The *dev and *mfd of struct rc5t583_regulator_info are not used after convert
> to use regmap, remove them.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Apr 15, 2013 at 02:10:27PM +0530, Girish K S wrote:
> From: Girish K S
>
> The 64xx spi driver supports partial polling mode.
> Only the last chunk of the transfer length is transferred
> or recieved in polling mode.
I'm missing patch 1 of this series.
signature.asc
Description:
On 2013/4/6 9:21, Tejun Heo wrote:
> Hello, guys.
>
> Status-quo
> ==
>
> It's been about a year since I wrote up a summary on cgroup status quo
> and future plans. We're not there yet but much closer than we were
> before. At least the locking and object life-time management aren't
Hi Prabhakar,
(CC'ing Marek)
On Tuesday 16 April 2013 16:24:30 Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> with recent commit with id 068a0df76023926af958a336a78bef60468d2033
> which adds add length check for mmap, the application were failing to
> mmap the buffers.
>
> This patch aligns
This patch adds support for UserModeHelper tracker in a container.
The reason for this is that the only containerised tracker ("nfsdcld") is
going to be removed in 3.10 kernel, thus at least one more tracker have to be
containerised to replace the deprecated one.
UMH tracker looks more preferable
On 04/10/2013 08:46 AM, Axel Lin wrote:
We can save a register read operation in some case if read
expand_register first.
If info->expand_register.voltage_mask bit is set, no need to read
voltage_reg.
Signed-off-by: Axel Lin
Looks good.
Acked-by: Bengt Jonsson
---
From: Lad, Prabhakar
with recent commit with id 068a0df76023926af958a336a78bef60468d2033
which adds add length check for mmap, the application were failing to
mmap the buffers.
This patch aligns the the buffer size to page size boundary for both
capture and display driver so the it pass the
On Thu, Apr 11, 2013 at 11:47:37AM -0700, Dave Hansen wrote:
> On 04/11/2013 12:45 AM, Stanislaw Gruszka wrote:
> > On Mon, Apr 08, 2013 at 08:57:16AM -0700, Dave Hansen wrote:
> >> On 04/04/2013 04:41 PM, Frederic Weisbecker wrote:
> >>> Does this patch fix the issue for you?
> >>>
Hi list,
On a power7 system, we have installed 3.9-rc7 and crash 6.1.6. If I run
something like "make -j 64" to compile linux kernel from source, sooner
or latter, oom-killer will be triggered. Before that, when I trying to
analyse the live system with crash, some processes' %MEM and RSS looks
On 08:19 Tue 16 Apr , Dan Carpenter wrote:
> On Mon, Apr 15, 2013 at 04:11:18PM -0700, David Rientjes wrote:
> > On Mon, 15 Apr 2013, Greg Kroah-Hartman wrote:
> >
> > > > The positive numbers are used to return information on the remaining
> > > > cache size (again, see the comment I pasted
On 04/10/2013 08:40 AM, Axel Lin wrote:
When setting voltage for AB8540_LDO_AUX3, current code only updates one of
info->voltage_reg and info->expand_register registers which is wrong.
To ensure we set to correct voltage, it always needs to clear or set
expand_register.voltage_mask bit of
Hi Hans,
On Tue, Apr 16, 2013 at 4:24 PM, Prabhakar lad
wrote:
> From: Lad, Prabhakar
>
> with recent commit with id 068a0df76023926af958a336a78bef60468d2033
> which adds add length check for mmap, the application were failing to
> mmap the buffers.
>
> This patch aligns the the buffer size to
From: Lad, Prabhakar
with recent commit with id 068a0df76023926af958a336a78bef60468d2033
which adds add length check for mmap, the application were failing to
mmap the buffers.
This patch aligns the the buffer size to page size boundary for both
capture and display driver so the it pass the
From: Lad, Prabhakar
with recent commit with id 068a0df76023926af958a336a78bef60468d2033
which adds add length check for mmap, the application were failing to
mmap the buffers.
This patch aligns the the buffer size to page size boundary for both
capture and display driver so the it pass the
From: Grant Likely
I've taken a full time position with Linaro and so I'll be using my
Linaro email address from this point on. It has also been many years
since I've touched any of the Xilinx related code so mark those items as
unmaintained.
In addition, Mark Brown is taking the lead on SPI
On Sat, Apr 13, 2013 at 11:44:54AM -0700, Linus Torvalds wrote:
> PS. This is the "Make sure 'total' fits in 32 bits first" version. Not
> really tested, but it's just changing the order of operations a bit.
>
> /* We know one of the values has a bit set in the high 32 bits */
> for (;;)
On 2013年04月16日 18:25, Chen Gang wrote:
> On 2013年04月12日 17:42, Chen Gang wrote:
>> On 2013年04月11日 12:10, Chen Gang wrote:
>>> On 2013年04月11日 05:19, Eric Paris wrote:
- Original Message -
>> b. has an new issue for AUDIT_DIR:
>>after AUDIT_DIR succeed, it will
On 04/16/2013 05:31 PM, Robin Holt wrote:
> On Tue, Apr 16, 2013 at 02:39:49PM +0800, Xiao Guangrong wrote:
>> The commit 751efd8610d3 (mmu_notifier_unregister NULL Pointer deref
>> and multiple ->release()) breaks the fix:
>> 3ad3d901bbcfb15a5e4690e55350db0899095a68
>> (mm: mmu_notifier:
(Adding Ben back to the CC list; not sure how his email was dropped)
On Thu, Apr 11, 2013 at 10:12:56AM +0100, Luis Henriques wrote:
> On Wed, Apr 10, 2013 at 03:57:12PM +, Seiji Aguchi wrote:
> >
> >
> > > -Original Message-
> > > From: Luis Henriques
> -Original Message-
> From: Randy Dunlap [mailto:rdun...@infradead.org]
> Sent: 12 April 2013 21:02
> To: Opensource [Anthony Olech]
> Cc: Dmitry Torokhov; Mark Brown; Samuel Ortiz; Ashish Jangam; Eric
> Andersson; Andrew Jones; linux-in...@vger.kernel.org; LKML; David Dajun Chen
>
Hi,
thanks for the submission.
On Thu, Apr 04, 2013 at 09:52:01PM -0700, Naveen Krishna Chatradhi wrote:
> From: Naveen Krishna Chatradhi
>
> Adds support for High Speed I2C driver found in Exynos5 and
> later SoCs from Samsung.
> This driver currently supports Auto mode.
Either explain the
On 2013年04月12日 17:42, Chen Gang wrote:
> On 2013年04月11日 12:10, Chen Gang wrote:
>> On 2013年04月11日 05:19, Eric Paris wrote:
>>> - Original Message -
>>>
> b. has an new issue for AUDIT_DIR:
>after AUDIT_DIR succeed, it will set rule->tree.
>next, the other case
On Mon, Apr 15, 2013 at 06:41:17PM -0400, Neil Horman wrote:
> +#ifdef CONFIG_IRQ_REMAP
> +static void __init intel_remapping_check(int num, int slot, int func)
> +{
> + u8 revision;
> +
> + revision = read_pci_config_byte(num, slot, func, PCI_REVISION_ID);
> +
> + /*
> + *
On Tue, Apr 16, 2013 at 08:22:19AM +0800, Alex Shi wrote:
> testing has a little variation, but the power data is quite accurate.
> I may change to packing tasks per cpu capacity than current cpu
> weight. that should has better power efficient value.
Yeah, this probably needs careful measuring -
On Mon, 15 Apr 2013 20:42:57 -0700, Doug Anderson wrote:
> From: Thomas Abraham
>
> With device core now able to setup the default pin configuration,
> the pin configuration code based on the deprecated Samsung specific
> gpio bindings is removed.
>
> Signed-off-by: Thomas Abraham
>
The pci_process_bridge_OF_ranges function, used to parse the "ranges"
property of a PCI host device, is found in both Microblaze and PowerPC
architectures. These implementations are nearly identical. This patch
moves this common code to a common place.
Signed-off-by: Andrew Murray
Signed-off-by:
On Tue, Apr 16, 2013 at 09:18:41AM +, Opensource [Anthony Olech] wrote:
> The reason why they are separate is that they are probed with different data
> structures and they use a different wrapper to access the "regmap" API.
> However, that is not a blocking issue, but it would mean
This patch converts the pci_load_of_ranges function to use the new common
of_pci_range_parser.
Signed-off-by: Andrew Murray
Signed-off-by: Liviu Dudau
Reviewed-by: Rob Herring
---
arch/mips/pci/pci.c | 50 --
1 files changed, 16 insertions(+),
This patchset factors out duplicated code associated with parsing PCI
DT "ranges" properties across the architectures and introduces a
"ranges" parser. This parser "of_pci_range_parser" can be used directly
by ARM host bridge drivers enabling them to obtain ranges from device
trees.
I've included
This patch factors out common implementation patterns to reduce overall kernel
code and provide a means for host bridge drivers to directly obtain struct
resources from the DT's ranges property without relying on architecture specific
DT handling. This will make it easier to write archiecture
Hi,
On Tuesday 16 April 2013 01:20 AM, Grant Likely wrote:
On Mon, 15 Apr 2013 17:56:10 +0530, Kishon Vijay Abraham I
wrote:
Hi,
On Monday 15 April 2013 05:04 PM, Grant Likely wrote:
On Wed, 20 Mar 2013 14:42:00 +0530, Kishon Vijay Abraham I
wrote:
The PHY framework provides a set of
Line discipline locking was performed with a combination of
a mutex, a status bit, a count, and a waitqueue -- basically,
a rw semaphore.
Replace the existing combination with an ld_semaphore.
Fixes:
1) the 'reference acquire after ldisc locked' bug
2) the over-complicated halt mechanism
3)
The hangup may already have happened; check for that state also.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
index 9ace119..84ba790 100644
---
Just as the tty pair must be locked in a stable sequence
(ie, independent of which is consider the 'other' tty), so must
the ldisc pair be locked in a stable sequence as well.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 87 +
1 file
The semantics of a rw semaphore are almost ideally suited
for tty line discipline lifetime management; multiple active
threads obtain "references" (read locks) while performing i/o
to prevent the loss or change of the current line discipline
(write lock).
Unfortunately, the existing rw_semaphore
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
index 9725c94..ba49c0e 100644
--- a/drivers/tty/tty_ldisc.c
+++ b/drivers/tty/tty_ldisc.c
@@
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
index 84ba790..9725c94 100644
--- a/drivers/tty/tty_ldisc.c
+++ b/drivers/tty/tty_ldisc.c
@@ -567,13 +567,15 @@
Rename o_ldisc to avoid confusion with the ldisc of the
'other' tty.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
index a150f95..9ace119 100644
---
On 15/04/13 21:09, Matthew Garrett wrote:
> Identical to V5, except with the UCS2 helper functions included this time.
Thanks these looks good to me. I've applied all three patches to the
'urgent' branch.
--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list:
On 16/04/13 10:56, joeyli wrote:
> I think I just got the same situation on my side with Acer machine. I am
> trying Matthew's new patchset hope can avoid this situation:
>
> https://lkml.org/lkml/2013/4/15/473
Please do let us know whether the patches work for you.
--
To unsubscribe from this
Hi,
here it is.
Original tip:x86/cpu tree state is this:
3019653a5758 x86/fpu: Fix FPU initialization
042c16f14161 x86, CPU, AMD: Drop useless label
982f33db626e x86, AMD: Correct {rd,wr}msr_amd_safe warnings
e277a4938574 x86: Fold-in trivial check_config function
c70293d0e3fe x86: Get rid of
On Mon, Apr 15, 2013 at 03:37:59PM +0100, Waiman Long wrote:
> If it is confirmed that all the supported architectures can allow a
> negative mutex count without incorrect behavior, we can then back
> out the architecture specific change and allow the mutex count to
> go to any negative number.
Moving the reboot=s<##> parameter for x86 to a kernel parameter
proper. I did not find any other arch that was specifying the
reboot cpu.
I left a compatibility mode in there. The new parameter always
takes precedence. I also fixed up the current code to support
up to cpuid's up to the current
I did allow the remaining 81 character line behind. It did not seem
like it was worth changing. Otherwise, it now passes checkpatch.pl.
Signed-off-by: Robin Holt
To: Ingo Molnar
To: Russ Anderson
Cc: Shawn Guo
Cc: Oleg Nesterov
Cc: Andrew Morton
Cc: "H. Peter Anvin"
Cc: Lai Jiangshan
This patch is preparatory. It moves reboot related syscall, etc
functions from kernel/sys.c to kernel/reboot.c.
Signed-off-by: Robin Holt
To: Ingo Molnar
To: Russ Anderson
Cc: Shawn Guo
Cc: Oleg Nesterov
Cc: Andrew Morton
Cc: "H. Peter Anvin"
Cc: Lai Jiangshan
Cc: Linus Torvalds
Cc:
We recently noticed that reboot of a 1024 cpu machine takes approx 16
minutes of just stopping the cpus. The slowdown was tracked to commit
f96972f.
The current implementation does all the work of hot removing the cpus
before halting the system. We are switching to just migrating to the
boot
Hi Jiri,
於 日，2013-04-14 於 23:25 +0200，Jiri Slaby 提到：
> Hi,
>
> after update to 3.8, every update of the kernel ends up in an unbootable
> machine. It is due to the following commit:
> commit 68d929862e29a8b52a7f2f2f86a0600423b093cd
> Author: Matthew Garrett
> Date: Sat Mar 2 19:40:17 2013
We recently noticed that reboot of a 1024 cpu machine takes approx 16
minutes of just stopping the cpus. The slowdown was tracked to commit
f96972f.
The current implementation does all the work of hot removing the cpus
before halting the system. We are switching to just migrating to the
On Wed, Apr 10, 2013 at 10:02:12AM -0700, Guenter Roeck wrote:
> On Mon, Apr 08, 2013 at 10:15:19AM -0700, Kevin Strasser wrote:
> > From: Michael Brunner
> >
> > Add i2c support for the on-board PLD found on some Kontron embedded
> > modules.
> >
> > Signed-off-by: Michael Brunner
> >
On Tue, Apr 16, 2013 at 11:25:28AM +0200, Ingo Molnar wrote:
> I've got limited extra capacity right now - but if Peter rebases
> tip:x86/cpu or you send a pullable update of tip:x86/cpu I can stick
> it into -tip testing and yell if it goes wrong.
>
Ok, I'll do that in a second.
Btw, another
> "Wolfram" == Wolfram Sang writes:
Hi,
>> +- their-claim-gpios: The GPIOs that the other sides use the claim the bus.
>> + Note that some implementations may only support a single other master.
Wolfram> Stronger? "Currently, only one other master is supported"?
Also there's a typo:
On Mon, Apr 15, 2013 at 10:45:38AM -0700, Joe Perches wrote:
> On Mon, 2013-04-15 at 12:16 -0500, Robin Holt wrote:
> > I did allow the remaining 81 character line behind. It did not seem
> > like it was worth changing. Otherwise, it now passes checkpatch.pl.
>
> trivia:
>
> I'd make these
* Robin Holt wrote:
> I have the patches sort-of finished. The patch set starts by
> moving the halt/shutdown/reboot functions over to a new
> kernel/reboot.c, next patch gets a checkpatch.pl cleanup to
> work, third patch is essentially the below patch against the
> new file, and the fourth
Doug,
On Tue, Apr 09, 2013 at 02:34:28PM -0700, Doug Anderson wrote:
> The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme
> where masters need to claim the bus with a GPIO before they can start
> a transcation. This should generally only be used when standard I2C
>
* Jacob Shin wrote:
> On Tue, Apr 09, 2013 at 12:21:48PM -0500, Jacob Shin wrote:
> > The following patchset adds address masks to existing perf hardware
> > breakpoint mechanism to allow trapping on an address range (currently
> > only single address) on supported architectures.
> >
> > perf
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: 12 April 2013 14:27
> To: Opensource [Anthony Olech]
> Cc: Liam Girdwood; Guenter Roeck; Jean Delvare; Randy Dunlap; LKML; David
> Dajun Chen
> Subject: Re: [NEW DRIVER V4 7/7] DA9058 REGULATOR driver
> On Fri, Apr
On Tue, Apr 16, 2013 at 02:39:49PM +0800, Xiao Guangrong wrote:
> The commit 751efd8610d3 (mmu_notifier_unregister NULL Pointer deref
> and multiple ->release()) breaks the fix:
> 3ad3d901bbcfb15a5e4690e55350db0899095a68
> (mm: mmu_notifier: fix freed page still mapped in secondary MMU)
On Tuesday, April 16, 2013, Doug Anderson
> Seungwon,
>
> On Mon, Apr 15, 2013 at 5:14 AM, Seungwon Jeon wrote:
> >> + MMC_CAP_8_BIT_DATA | MMC_CAP_CMD23 | MMC_CAP_SDIO_IRQ,
> >> + MMC_CAP_CMD23 | MMC_CAP_SDIO_IRQ,
> > This line for [1]
> >> + MMC_CAP_CMD23 |
This patch adds dts support for the sata controller
Signed-off-by: Girish K S
---
arch/arm/boot/dts/exynos5440.dtsi |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5440.dtsi
b/arch/arm/boot/dts/exynos5440.dtsi
index 7c5dc38..2dc4ffa
* Robin Holt wrote:
> On Tue, Apr 16, 2013 at 11:01:09AM +0200, Ingo Molnar wrote:
> >
> > * Robin Holt wrote:
> >
> > > On Mon, Apr 15, 2013 at 10:47:49AM -0700, H. Peter Anvin wrote:
> > > > We usually don't break working user setups as a matter if policy. Only
> > > > if it can't be
This patch adds the compatible string of the exynos5440 sata controller
compliant with the ahci 1.3 and sata 3.0 specification.
Signed-off-by: Girish K S
changes in v2:
changed the compatible string by adding the actual IP
owners name instead of the SoC vendor name.
---
On Tue, Apr 16, 2013 at 2:43 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Apr 16, 2013 at 02:40:04PM +0530, Girish K S wrote:
>> This patch adds the compatible string of the exynos5440 sata controller
>> compliant with the ahci 1.3 and sata 3.0 specification.
>>
>> Signed-off-by: Girish K S
>> ---
* Borislav Petkov wrote:
> On Mon, Apr 15, 2013 at 05:54:15PM +0200, Borislav Petkov wrote:
> > On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
> > > It was tip:master with x86/cpu merged in freshly.
> >
> > Ok, some more observations. I can trigger some oops similar yours (I
> >
On Tue, Apr 16, 2013 at 11:01:09AM +0200, Ingo Molnar wrote:
>
> * Robin Holt wrote:
>
> > On Mon, Apr 15, 2013 at 10:47:49AM -0700, H. Peter Anvin wrote:
> > > We usually don't break working user setups as a matter if policy. Only
> > > if it can't be avoided.
> > >
> > > Robin Holt wrote:
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 12 April 2013 19:07
> To: Opensource [Anthony Olech]
> Cc: LKML; Alessandro Zummo
> Subject: Re: [NEW DRIVER V4 0/7] DA9058 PMIC - please comment on this new
> driver
> On Friday, April 12, 2013
> -Original Message-
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: 15 April 2013 18:46
> To: Opensource [Anthony Olech]
> Cc: LKML
> Subject: Re: [NEW DRIVER V4 7/7] DA9058 REGULATOR driver
>
> On Mon, Apr 15, 2013 at 05:29:13PM +, Opensource [Anthony Olech]
> wrote:
> > >
* libin wrote:
> On 2013/4/15 22:15, Jonghwan Choi wrote:
> > From: libin
> >
> > This patch looks like it should be in the 3.8-stable tree, should we apply
> > it?
> >
>
> yes, I think this patch should be applied to the 3.8-stable tree. Thanks.
> Libin
Since this is a debug interface
Em Mon, 15 Apr 2013 20:10:49 -0700 (PDT)
David Rientjes escreveu:
> On Tue, 9 Apr 2013, Antti Palosaari wrote:
>
> > On 04/08/2013 08:47 PM, Randy Dunlap wrote:
> > > From: Randy Dunlap
> > >
> > > Fix randconfig error when USB is not enabled:
> > >
> > > ERROR: "usb_control_msg"
Hi,
On Tue, Apr 16, 2013 at 02:40:04PM +0530, Girish K S wrote:
> This patch adds the compatible string of the exynos5440 sata controller
> compliant with the ahci 1.3 and sata 3.0 specification.
>
> Signed-off-by: Girish K S
> ---
> drivers/ata/ahci_platform.c |1 +
> 1 files changed, 1
* Waiman Long wrote:
> [...]
>
> Patches 2 improves the mutex spinning process by reducing contention among
> the
> spinners when competing for the mutex. This is done by using a MCS lock to
> put
> the spinners in a queue so that only the first spinner will try to acquire
> the
> mutex
On 16.4.2013 10:21, Michal Marek wrote:
> On 15.4.2013 23:54, Yann E. MORIN wrote:
>> So, unless Michal really wants to pull this one and push it to Linus
>> before he cuts v3.9 final, I'll merge this later in my -for-next branch.
>
> That's fine with me.
BTW, in you are going to rebase the
* Waiman Long wrote:
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -3021,9 +3021,6 @@ static inline bool owner_running(struct mutex *lock,
> struct task_struct *owner)
> */
> int mutex_spin_on_owner(struct mutex *lock, struct task_struct *owner)
> {
> - if
This patch adds the compatible string of the exynos5440 sata controller
compliant with the ahci 1.3 and sata 3.0 specification.
Signed-off-by: Girish K S
---
drivers/ata/ahci_platform.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/ata/ahci_platform.c
On Mon, Apr 15, 2013 at 8:17 PM, Al Viro wrote:
> On Mon, Apr 15, 2013 at 05:30:41PM +0200, Miklos Szeredi wrote:
>> On Mon, Apr 15, 2013 at 5:08 PM, Miklos Szeredi wrote:
>> > For example doing a readlink() on a magic symlink under /proc
>> > shouldn't result in a synchronous call to a fuse
* Oleg Nesterov wrote:
> Ingo, please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
>
> Mostly uretprobes. "perf probe -x file sym%return" works like kretprobes.
> TODO: longjmp() is not supported, currently we assume that the probed
> function returns,
16.04.2013 06:03, Eric Dumazet пишет:
From: Eric Dumazet
On Mon, 2013-04-15 at 17:37 -0700, Eric Dumazet wrote:
On Mon, 2013-04-15 at 16:57 +0300, Vitaly V. Bursov wrote:
Hello,
I have a bonding device (mode=802.3ad xmit_hash_policy=layer2+3 miimon=300) and
for kernels <3.7 forwarded IPv4
* Robin Holt wrote:
> On Mon, Apr 15, 2013 at 10:47:49AM -0700, H. Peter Anvin wrote:
> > We usually don't break working user setups as a matter if policy. Only if
> > it can't be avoided.
> >
> > Robin Holt wrote:
> >
> > >On Mon, Apr 15, 2013 at 10:18:31AM -0700, H. Peter Anvin wrote:
>
This patch adds dts support for the sata controller
Signed-off-by: Girish K S
---
arch/arm/boot/dts/exynos5440.dtsi |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5440.dtsi
b/arch/arm/boot/dts/exynos5440.dtsi
index 7c5dc38..2dc4ffa
401 - 500 of 1154 matches
Mail list logo
