Hyper-V VMBUS driver can be a module; handle this case correctly. Please apply.
Signed-off-by: K. Y. Srinivasan
---
arch/x86/kernel/irq.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
index 42805fa..283a76a 100644
---
Hi Linus,
On 03/31/2014 10:22 AM, Linus Walleij wrote:
> On Sat, Mar 29, 2014 at 5:44 AM, Harini Katakam
> wrote:
>> On Sat, Mar 29, 2014 at 3:20 AM, Linus Walleij
>> wrote:
>>> On Thu, Mar 27, 2014 at 4:25 PM, Harini Katakam wrote:
>
+/* Read/Write access to the GPIO PS registers */
On Fri, Mar 28, 2014 at 09:48:58AM +0100, Lothar Waßmann wrote:
> Change the pwm chip driver registration, so that a chip driver that
> supports polarity inversion can still be used with DTBs that don't
> provide the 'PWM_POLARITY' flag.
>
> This is done to provide polarity inversion support for
Hi Linus,
I would like to ask You for pulling fixes for dma-mapping subsystem for
ARM for v3.15.
The following changes since commit cfbf8d4857c26a8a307fb7cd258074c9dcd8c691:
Linux 3.14-rc4 (2014-02-23 17:40:03 -0800)
are available in the git repository at:
As Namhyung reported(https://lkml.org/lkml/2014/4/1/89),
current perf-probe -L option doesn't handle errors in line-range
searching correctly. It causes a SEGV if an error occured in the
line-range searching.
$ perf probe -x ./perf -v -L map__load
Open Debuginfo file:
On 04/02/2014 02:32 AM, Guenter Roeck wrote:
> On 04/01/2014 04:20 AM, Michal Simek wrote:
>> Hi Guenter,
>>
+/**
+ * struct cdns_wdt - Watchdog device structure
+ * @regs: baseaddress of device
+ * @rst: reset flag
+ * @clk: struct clk * of a clock source
+ *
Hi Lothar,
On Fri, Mar 28, 2014 at 09:49:00AM +0100, Lothar Waßmann wrote:
> static struct pwm_ops imx_pwm_ops = {
> .enable = imx_pwm_enable,
> .disable = imx_pwm_disable,
> @@ -210,6 +228,7 @@ struct imx_pwm_data {
> int (*config)(struct pwm_chip *chip,
> struct
I should have a qemu image running before the end of the week based on
the latest Archlinux 64 packages. Then, I'll install the 3.14 kernel
and see what I'll get.
By the way, since kernel 3.14 is now available, it has been pushed to
Arch's repository. It will be deployed soon on many systems
Hi,
>> > USB patches for 3.15-rc1
>> >
>> > Here's the big USB pull request for 3.15-rc1.
>>
>> Hmm. I'm getting this when testing:
>>
>> warning: (AHCI_XGENE) selects PHY_XGENE which has unmet direct
>> dependencies (HAS_IOMEM && OF && (ARM64 || COMPILE_TEST))
>>
>> which looks like AHCI_XGENE
On 28 March 2014 17:11, Viresh Kumar wrote:
> diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
> @@ -887,25 +887,22 @@ static void __remove_hrtimer(struct hrtimer *timer,
> struct hrtimer_clock_base *base,
> unsigned long newstate, int
On Tue, Apr 01, 2014 at 09:37:44AM -0700, Greg KH wrote:
> On Tue, Apr 01, 2014 at 04:23:12PM +0200, Sylwester Nawrocki wrote:
> > On 01/04/14 15:19, Ben Dooks wrote:
> > > On 31/03/14 21:06, Greg KH wrote:
> > >> > On Mon, Mar 31, 2014 at 06:41:56PM +0200, Sylwester Nawrocki wrote:
> > [...]
> >
Are you in any financial problem? Do you need quick loans or to clear your
debts and get back to business. If so do contact us for more details for loan
application. contact us only on this email>latmanl...@gmail.com
All your responses should be send to our private Email:
On Wed, 2014-04-02 at 10:34 +1100, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> This time around, the powerpc merges are going to be a little bit
> more complicated than usual.
Looks like I sent this one twice, one with "merge" and one with "next"
in the subject. They are otherwise identical
The following changes since commit 33807f4f0daec3b00565c2932d95f614f5833adf:
Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 (2014-03-11
11:53:42 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
On 2 April 2014 06:55, Josh Boyer wrote:
> Hi All,
>
> When running make listnewconfig/oldconfig on the config below with
> Linus' latest tree, I keep seeing this error message spit out:
>
> drivers/cpufreq/Kconfig:57:warning: choice value used outside its choice group
>
On Mon, Mar 31, 2014 at 9:47 PM, Jovi Zhangwei wrote:
> Hi Alexei,
>
> On Tue, Apr 1, 2014 at 5:29 AM, Alexei Starovoitov wrote:
>> On Mon, Mar 31, 2014 at 3:01 AM, Jovi Zhangwei
>> wrote:
>>> Hi Ingo,
>>>
>>> On Mon, Mar 31, 2014 at 3:17 PM, Ingo Molnar wrote:
* Jovi Zhangwei
It turns out all Haswell processors (including the Desktop variant)
support RAPL DRAM readings in addition to package, pp0, and pp1.
I've confirmed RAPL DRAM readings on my model 60 Haswell desktop.
See the 4th-gen-core-family-desktop-vol-2-datasheet.pdf
available from the Intel website for
On Tuesday 25 March 2014 11:20 PM, Dave Hansen wrote:
> On 03/25/2014 10:36 AM, Kirill A. Shutemov wrote:
+/*
+ * Fault around order is a control knob to decide the fault around pages.
+ * Default value is set to 0UL (disabled), but the arch can override it as
+ * desired.
Earlier commit:
commit 652ed95d5fa6074b3c4ea245deb0691f1acb6656
Author: Viresh Kumar
Date: Thu Jan 9 20:38:43 2014 +0530
cpufreq: introduce cpufreq_generic_get() routine
did some changes to driver and by mistake made cpuclk as a 'static' local
variable,
you are going to find both camps (and everything in between) as well as people
who see nothing wrong with proprietary software involved with any open/free
software project. The bigger the project, the more variation you will see.
The kernel is GPLv2, so there are not big discussions about it
On Tuesday, April 01, 2014 9:46 PM, Konrad Rzeszutek Wilk wrote:
> On Tue, Apr 01, 2014 at 10:51:58AM +0900, Jungseok Lee wrote:
> > This patch corrects kernel command line handler when io_tlb_nslabs is
> > set to 0.
> >
> > A current implementation allocates default size memory (64MB) when
> > 0
Hi Laurent,
On Tue, 2014-04-01 at 15:49 +0200, Laurent Pinchart wrote:
> Hi Olivier,
>
> On Sunday 30 March 2014 00:23:01 Olivier Langlois wrote:
> > Hi Laurent,
> >
> > > > Yes. ffmpeg uses wall clock time to create timestamps for audio packets
> > > > from ALSA device.
> > >
> > > OK. I
On Wed, 2014-04-02 at 00:03 +0200, Rafael J. Wysocki wrote:
> > Rafael, are you going to take these or should I send them to Linus ?
> >
> > (I'd rather you take them :-)
>
> I can do that, but the timing is pretty bad. How urgent are they?
To be honest pretty urgent. It's a new drop-in driver
On 04/01/2014 04:01 PM, Dave Hansen wrote:
> On 04/01/2014 02:35 PM, H. Peter Anvin wrote:
>> On 04/01/2014 02:21 PM, Johannes Weiner wrote:
>>> Either way, optimistic volatile pointers are nowhere near as
>>> transparent to the application as the above description suggests,
>>> which makes this
On 04/01/2014 09:03 PM, John Stultz wrote:
>
> So, maybe its best to ignore the fact that folks want to do semi-crazy
> user-space faulting via SIGBUS. At least to start with. Lets look at the
> semantic for the "normal" mark volatile, never touch the pages until you
> mark non-volatile -
On 04/01/2014 02:21 PM, Johannes Weiner wrote:
> [ I tried to bring this up during LSFMM but it got drowned out.
> Trying again :) ]
>
> On Fri, Mar 21, 2014 at 02:17:30PM -0700, John Stultz wrote:
>> Optimistic method:
>> 1) Userland marks a large range of data as volatile
>> 2) Userland
Section D7.2.83 TCR_EL1, Translation Control Register (EL1) of the
latest ARM Architecture Reference Manual, ARMv8, for ARMv8-A states
that TCR_EL1 TG1 (bits [31:30]) should be set to 11 for a 64KB
TTBR1_EL1 granule size. The mainline 3.14 kernel incorrectly sets
those bits to 01 (which is a 16KB
Compared source code of rtc-lib.c::rtc_year_days() with
efirtc.c::rtc_year_days(), found the code in rtc-efi decreases value
of day twice when it computing year days. The tc-lib.c::rtc_year_days()
has already decrease day and return the year days from 0 to 365.
Signed-off-by: Lee, Chun-Yi
---
Return -EINVAL unless all of user-given strings are correctly
NUL-terminated.
Signed-off-by: YOSHIFUJI Hideaki
---
drivers/isdn/isdnloop/isdnloop.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/isdn/isdnloop/isdnloop.c b/drivers/isdn/isdnloop/isdnloop.c
index
In document numa_memory_policy.txt, the following examples for flag
MPOL_F_RELATIVE_NODES are incorrect.
For example, consider a task that is attached to a cpuset with
mems 2-5 that sets an Interleave policy over the same set with
MPOL_F_RELATIVE_NODES. If the cpuset's
In the f2fs_wait_on_page_writeback, io->bio should be covered by io_rwsem.
Otherwise, the bio pointer can become a dangling pointer due to data races.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/segment.c
On 04/02/2014 06:13 AM, Michael Neuling wrote:
> Anshuman Khandual wrote:
>> > This patch adds few more ptrace request macros expanding
>> > the existing capability. These ptrace requests macros can
>> > be classified into two categories.
> Why is this only an RFC?
>
Looking for comments,
During the testing, we encounter below WARN followed by Oops:
WARNING: at kernel/sched/core.c:6218
...
NIP [c0101660] .build_sched_domains+0x11d0/0x1200
LR [c0101358] .build_sched_domains+0xec8/0x1200
PACATMSCRATCH [8000f032]
On Wed, 2 Apr 2014, Rafael J. Wysocki wrote:
> On Friday, March 28, 2014 01:29:53 PM Daniel Lezcano wrote:
> > The following patchset provides an interaction between cpuidle and the
> > scheduler.
> >
> > The first patch encapsulate the needed information for the scheduler in a
> > separate
> Subject: Re: [PATCH] regmap: mmio: Fix the bug of 'offset' value parsing.
>
> On Mon, Mar 31, 2014 at 02:33:31PM +0800, Xiubo Li wrote:
> > 'offset = *(u32 *)reg;', this will be okey for 32/64-bit register, but
> > for 8/16-bit register, the 'offset' value will overflow.
>
> This doesn't apply
On Fri, 28 Mar 2014, Daniel Lezcano wrote:
> As we know in which idle state the cpu is, we can investigate the following:
>
> 1. when did the cpu entered the idle state ? the longer the cpu is idle, the
> deeper it is idle
> 2. what exit latency is ? the greater the exit latency is, the deeper
'offset = *(u32 *)reg;'
This will be okey for 32/64-bits register device, but for 8/16-bits
register ones, the 'offset' value will overflow, for example:
The IMX2 Watchdog, whose registers and values are all 16-bits:
If the IO base virtual address is ctx->regs = 0x888c, and the now
doing the
On Wed, Apr 02, 2014 at 12:35:04AM +, Mathieu Desnoyers wrote:
> - Original Message -
> > From: "Paul E. McKenney"
> > To: "Mathieu Desnoyers"
> > Cc: fweis...@gmail.com, pet...@infradead.org, linux-kernel@vger.kernel.org
> > Sent: Monday, March 31, 2014 1:23:19 PM
> > Subject: Re:
On 2014-04-01 20:43, Linus Torvalds wrote:
On Tue, Apr 1, 2014 at 12:05 PM, Jens Axboe wrote:
- Cleanup of the IPI usage from the block layer, and associated helper
code. From Frederic Weisbecker and Jan Kara.
So I absolutely *hate* how this was done.
Why the hell was it mixed in with
bond_open is not setting the inactive flag correctly for some modes (alb and
tlb), resulting in error behavior if the bond has been administratively set
down and then back up. This effect should not occur when slaves are added while
the bond is up; it's something that only happens after a down/up
On Wed, Apr 02, 2014 at 01:03:13PM +1100, Andrew Stephenson wrote:
> Ah, so there is a Free Software camp and an Open Source camp within
> the Linux Kernel Mailing List.
There is a strong consensus that the Linux kernel should remain GPLv2,
and many senior kernel developers (including Linus) have
make allyesconfig give the following build error on tile:
tilegx-linux-gcc: error: arch/tile/kernel/vdso/vgettimeofday32.o: No such file
or directory
tilegx-linux-objcopy: 'arch/tile/kernel/vdso/vdso32.so.dbg': No such file or
directory
In case with CONFIG_MODVERSIONS, cmd_cc_o_c generate
On Tue, Apr 1, 2014 at 12:05 PM, Jens Axboe wrote:
>
> - Cleanup of the IPI usage from the block layer, and associated helper
> code. From Frederic Weisbecker and Jan Kara.
So I absolutely *hate* how this was done.
Why the hell was it mixed in with the block layer code? It's not even
in some
On Tue, Apr 01, 2014 at 05:28:19PM -0700, Linus Torvalds wrote:
> On Tue, Apr 1, 2014 at 11:49 AM, Greg KH wrote:
> >
> > USB patches for 3.15-rc1
> >
> > Here's the big USB pull request for 3.15-rc1.
>
> Hmm. I'm getting this when testing:
>
> warning: (AHCI_XGENE) selects PHY_XGENE which
On Tue, Apr 01, 2014 at 05:42:54PM +0100, Mark Brown wrote:
> On Tue, Apr 01, 2014 at 09:21:57PM +0800, Nicolin Chen wrote:
>
> > Sir, I just rebased my for-next branch again and found that it's missing
> > two applied patches: "ASoC: fsl_sai: Add isr to deal with error flag" and
> > "ASoC:
On Tue, Apr 01 2014, Kamezawa Hiroyuki wrote:
>> On Tue, Apr 01 2014, Davidlohr Bueso wrote:
>>
>>> On Tue, 2014-04-01 at 19:56 -0400, KOSAKI Motohiro wrote:
>>> Ah-hah, that's interesting info.
>>>
>>> Let's make the default 64GB?
>>
>> 64GB is infinity at that time, but
Add support for CCU policy engine control, and also for setting the
mask bits for bus clocks that require a policy change to get
activated. This includes adding validity checking framework for
CCUs, to validate the policy fields if defined.
Signed-off-by: Alex Elder
---
Don't let a failure of ccu_wait_bit() go unnoticed.
Signed-off-by: Alex Elder
---
drivers/clk/bcm/clk-kona.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/clk/bcm/clk-kona.c b/drivers/clk/bcm/clk-kona.c
index e3d339e..c01d810 100644
--- a/drivers/clk/bcm/clk-kona.c
+++
Rather than "manually" setting up each CCU's clock entries at run
time, define a flexible array of generic Kona clock structures
within the CCU structure itself. Each of these entries contains
generic kona clock information (like its CCU pointer and clock
framework initialization data). Each
As I developed the bcm281xx clock code I understood there were
restrictions on device tree "compatible" strings names, and as a
result "bcm11351" was used in places despite the part family being
more properly called "bcm281xx". This can be a little confusing.
In some cases I went to far and
Add support for clock gate hysteresis control. For now, if it's
defined for a clock, it's enabled.
Signed-off-by: Alex Elder
---
drivers/clk/bcm/clk-kona-setup.c | 30 ++
drivers/clk/bcm/clk-kona.c | 33 +
We know up front how many CCU's we'll support, so there's no need to
allocate their data structures dynamically. Define a macro
KONA_CCU_COMMON() to simplify the initialization of many of the
fields in a ccu_data structure. Pass the address of a statically
defined CCU structure to
Use the init_data.name field to hold the name of a Kona clock rather
than duplicating it.
Signed-off-by: Alex Elder
---
drivers/clk/bcm/clk-kona-setup.c |6 +++---
drivers/clk/bcm/clk-kona.c | 17 ++---
drivers/clk/bcm/clk-kona.h |3 +--
3 files changed, 14
Add support for clock gate hysteresis control. For now, if it's
defined for a clock, it's enabled.
Signed-off-by: Alex Elder
---
drivers/clk/bcm/clk-kona-setup.c | 30 ++
drivers/clk/bcm/clk-kona.c | 33 +
This series includes updates for the bcm281xx clock code for 3.15.
It is dependent on the following code, already queued for 3.15:
https://github.com/broadcom/mach-bcm/
Branch armsoc/for-3.15/drivers
clk: bcm281xx: don't disable unused peripheral clocks
clk: bcm281xx: add
Ah, so there is a Free Software camp and an Open Source camp within the Linux
Kernel Mailing List.
> On 2 Apr 2014, at 11:45 am, David Lang wrote:
>
> There is no concensus, some people are working hard to do so, others love
> GPLv3
>
> David Lang
>
>> On Wed, 2 Apr 2014, Andrew Stephenson
(2014/04/02 10:08), Greg Thelen wrote:
>
> On Tue, Apr 01 2014, Davidlohr Bueso wrote:
>
>> On Tue, 2014-04-01 at 19:56 -0400, KOSAKI Motohiro wrote:
>> Ah-hah, that's interesting info.
>>
>> Let's make the default 64GB?
>
> 64GB is infinity at that time, but it no longer
Hi all,
On Tue, 25 Feb 2014 17:09:44 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the staging tree got a conflict in
> arch/arm/boot/dts/imx53-qsb.dts between commit d5eb195f26fa ("ARM: dts:
> i.MX53: move common QSB nodes to new file") from the arm-soc tree and
> commit
On Mon, Mar 31, 2014 at 9:13 PM, Andi Kleen wrote:
> On Mon, Mar 31, 2014 at 10:01:04AM +0800, Jovi Zhangwei wrote:
>> On Sun, Mar 30, 2014 at 8:58 AM, Andi Kleen wrote:
>> >> Maybe in future, after ktap support "include" or "require" to
>> >> import user defined library in userspace.
>> >
>> >
On Tue, 2014-04-01 at 21:32 -0400, Bandan Das wrote:
> While using the new_id interface, the user can unintentionally feed
> incorrect values if the driver static table has a matching entry.
> This is possible since only the device and vendor fields are
> mandatory and the rest are optional. As a
On 2014/4/1 22:41, Chris Mason wrote:
>
> Hello everyone,
>
> During last week's Collab summit, Jon Corbet suggested we use the power
> of social media to improve the Linux kernel patch review process.
>
> We thought this was a great idea, and have been experimenting with a new
> Facebook group
While using the new_id interface, the user can unintentionally feed
incorrect values if the driver static table has a matching entry.
This is possible since only the device and vendor fields are
mandatory and the rest are optional. As a result, store_new_id
will fill in default values that are
On Tue, Apr 01 2014, Vladimir Davydov wrote:
> We have only a few places where we actually want to charge kmem so
> instead of intruding into the general page allocation path with
> __GFP_KMEMCG it's better to explictly charge kmem there. All kmem
> charges will be easier to follow that way.
>
On Tue, Apr 01 2014, Davidlohr Bueso wrote:
> On Tue, 2014-04-01 at 19:56 -0400, KOSAKI Motohiro wrote:
>> >> > Ah-hah, that's interesting info.
>> >> >
>> >> > Let's make the default 64GB?
>> >>
>> >> 64GB is infinity at that time, but it no longer near infinity today. I
>> >> like
>> >> very
(2014/04/02 4:19), Andrew Morton wrote:
On Tue, 01 Apr 2014 15:29:05 +0900 Kamezawa Hiroyuki
wrote:
So their system will act as if they had set SHMMAX=enormous. What
problems could that cause?
Look. The 32M thing is causing problems. Arbitrarily increasing the
arbitrary 32M to an
2014-04-01 16:55 GMT-07:00 Alexander Holler :
> Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
> changed the initialization of the mv643xx_eth driver to use phy_init_hw()
> to reset the PHY. Unfortunately the initialization for the 88E1116R PHY
> was broken such, that it
Move kmem_cache_free out of spinlock protection region for better performance.
Change log from v1:
o remove spinlock protection for kmem_cache_free in destroy_node_manager
suggested by Jaegeuk Kim.
Signed-off-by: Chao Yu
---
fs/f2fs/checkpoint.c | 27 +--
On Tue, Apr 01 2014, Vladimir Davydov wrote:
> Currently to allocate a page that should be charged to kmemcg (e.g.
> threadinfo), we pass __GFP_KMEMCG flag to the page allocator. The page
> allocated is then to be freed by free_memcg_kmem_pages. Apart from
> looking asymmetrical, this also
Hi Kim,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Tuesday, April 01, 2014 8:04 PM
> To: Chao Yu
> Cc: linux-f2fs-de...@lists.sourceforge.net; linux-fsde...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs:
On 2014-04-01 15:32, Michael Kerrisk (man-pages) wrote:
> Richard,
>
> On 04/01/2014 08:25 PM, Richard Hansen wrote:
>> For the flags parameter, POSIX says "Either MS_ASYNC or MS_SYNC shall
>> be specified, but not both." [1] There was already a test for the
>> "both" condition. Add a test to
Hi all,
On Thu, 20 Mar 2014 14:36:03 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the tip tree got a conflict in
> arch/arm/mach-imx/pm-imx6q.c between commit 9cdde7217e92 ("ARM: imx6:
> rename pm-imx6q.c to pm-imx6.c") from the arm-soc tree and commit
> 8435cf757632 ("arm:
On Tue, Apr 1, 2014 at 5:29 PM, Marcelo Tosatti wrote:
> On Tue, Apr 01, 2014 at 12:17:16PM -0700, Andy Lutomirski wrote:
>> On Tue, Apr 1, 2014 at 11:01 AM, Marcelo Tosatti wrote:
>> > On Mon, Mar 31, 2014 at 10:33:41PM -0700, Andy Lutomirski wrote:
>> >> On Mar 31, 2014 8:45 PM, "Marcelo
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-3.15-rc1-2
to receive more ACPI and power management updates for v3.15-rc1 with
top-most commit 7b5c39389c86063e86fe8f2e0093c7197ddfa60a
Merge branch 'pm-runtime'
on top of commit
Fix checkpatch.pl issues with missing blank line after declarations.
Signed-off-by: Toby Smith
---
drivers/staging/netlogic/xlr_net.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/netlogic/xlr_net.c
b/drivers/staging/netlogic/xlr_net.c
index c83e337..75d7c63 100644
---
Anshuman Khandual wrote:
> This patch adds few more ptrace request macros expanding
> the existing capability. These ptrace requests macros can
> be classified into two categories.
Why is this only an RFC?
Also, please share the test case that you wrote for this.
Mikey
>
> (1)
On Tue, 2014-04-01 at 19:56 -0400, KOSAKI Motohiro wrote:
> >> > Ah-hah, that's interesting info.
> >> >
> >> > Let's make the default 64GB?
> >>
> >> 64GB is infinity at that time, but it no longer near infinity today. I like
> >> very large or total memory proportional number.
> >
> > So I still
On Tue, Apr 1, 2014 at 3:29 PM, Matthew Dempsky wrote:
> Revised patch below. Unfortunately, I just realized I don't have my
> test machine handy, so I won't be able to test it until tomorrow.
Quick update: Julien helped me setup a VM to test this, and the patch
still passes my test case
On Tue, Apr 01, 2014 at 11:15:40AM -0600, Alex Williamson wrote:
> On Tue, 2014-04-01 at 09:47 -0700, Greg KH wrote:
> > On Tue, Apr 01, 2014 at 10:28:54AM -0600, Alex Williamson wrote:
> > > The driver_override field allows us to specify the driver for a device
> > > rather than relying on the
At 2014-04-02 02:27:56,"Jesse Gross" wrote:
>On Tue, Apr 1, 2014 at 8:24 AM, wei zhang wrote:
>> At 2014-04-01 08:49:53,"Jesse Gross" wrote:
>>>On Sun, Mar 30, 2014 at 5:12 AM, wei zhang wrote:
At 2014-03-29 06:02:25,"Jesse Gross" wrote:
>>
Maybe I misunderstand something? I think
On Tue, Apr 1, 2014 at 5:03 PM, Andi Kleen wrote:
>
> Remove the left over extern __visible Linus objected too.
> They should be useless, as we only need the visible
> on the actual definitions.
Ack. I'm going to assume that I'll get this together with the other
__visibility patches in some LTO
- Original Message -
> From: "Paul E. McKenney"
> To: "Mathieu Desnoyers"
> Cc: fweis...@gmail.com, pet...@infradead.org, linux-kernel@vger.kernel.org
> Sent: Monday, March 31, 2014 1:23:19 PM
> Subject: Re: Promela/spin model for NO_HZ_FULL_SYSIDLE code
>
> On Mon, Mar 31, 2014 at
On Tue, Apr 1, 2014 at 5:01 PM, Steven Rostedt wrote:
>
> Why would they break tracing? I remember there was a issue with compat
> calls, are these related to that?
They "break" tracing by being invisible to syscall tracing. As you
really should know ;)
The syscall tracing feature depends on
On 04/01/2014 04:20 AM, Michal Simek wrote:
Hi Guenter,
+/**
+ * struct cdns_wdt - Watchdog device structure
+ * @regs: baseaddress of device
+ * @rst: reset flag
+ * @clk: struct clk * of a clock source
+ * @prescaler: for saving prescaler value
+ * @ctrl_clksel: counter clock prescaler
On Tue, Apr 1, 2014 at 11:49 AM, Greg KH wrote:
>
> USB patches for 3.15-rc1
>
> Here's the big USB pull request for 3.15-rc1.
Hmm. I'm getting this when testing:
warning: (AHCI_XGENE) selects PHY_XGENE which has unmet direct
dependencies (HAS_IOMEM && OF && (ARM64 || COMPILE_TEST))
which
What is the consensus on replacing GNU with software that won't become GPLv3 in
the future, with the latest gcc for example.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
2014-03-08 11:55 GMT+08:00 Axel Lin :
> The is_enabled implementation is wrong in some cases:
> e.g. for pbias_mmc_omap5: enable_mask is : BIT(27) | BIT(25) | BIT(26)
> However, pbias_regulator_enable() only sets BIT(27) | BIT(26) bits.
> So is_enabled callback will always return false in this
On Tue, Apr 01, 2014 at 06:52:12PM -0500, Kim Phillips wrote:
> On Tue, 01 Apr 2014 10:28:54 -0600
> Alex Williamson wrote:
>
> > The driver_override field allows us to specify the driver for a device
> > rather than relying on the driver to provide a positive match of the
> > device. This
On Tue, Apr 1, 2014 at 5:12 PM, Marcelo Tosatti wrote:
> On Tue, Apr 01, 2014 at 12:17:16PM -0700, Andy Lutomirski wrote:
>> On Tue, Apr 1, 2014 at 11:01 AM, Marcelo Tosatti wrote:
>> > On Mon, Mar 31, 2014 at 10:33:41PM -0700, Andy Lutomirski wrote:
>> >> On Mar 31, 2014 8:45 PM, "Marcelo
On 04/01/2014 10:25 AM, Chris Mason wrote:
Hi Linus,
We still have some corruption fixes and other patches coming in for the
merge window, but this batch is tested and ready to go.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git master
Tsutomu noticed
On 03/31/2014 07:46 AM, Christoph Hellwig wrote:
> This series adds support for sharing tags (and thus requests) between
> multiple request_queues. We'll need this for SCSI, and I think Martin
> also wants something similar for nvme.
>
> Besides the mess with request contructors/destructors the
(2014/04/02 5:15), KOSAKI Motohiro wrote:
Our middleware engineers has been complaining about this sysctl limit.
System administrator need to calculate required sysctl value by making sum
of all planned middlewares, and middleware provider needs to write "please
calculate systcl param by."
On Tue, Apr 01, 2014 at 12:17:16PM -0700, Andy Lutomirski wrote:
> On Tue, Apr 1, 2014 at 11:01 AM, Marcelo Tosatti wrote:
> > On Mon, Mar 31, 2014 at 10:33:41PM -0700, Andy Lutomirski wrote:
> >> On Mar 31, 2014 8:45 PM, "Marcelo Tosatti" wrote:
> >> >
> >> > On Mon, Mar 31, 2014 at 10:52:25AM
>> > Ah-hah, that's interesting info.
>> >
>> > Let's make the default 64GB?
>>
>> 64GB is infinity at that time, but it no longer near infinity today. I like
>> very large or total memory proportional number.
>
> So I still like 0 for unlimited. Nice, clean and much easier to look at
> than
Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
changed the initialization of the mv643xx_eth driver to use phy_init_hw()
to reset the PHY. Unfortunately the initialization for the 88E1116R PHY
was broken such, that it used mdelay() instead of really waiting for a
reset to
On 03/31/2014 09:07 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.86 release.
There are 6 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Tue, Apr 01, 2014 at 07:31:30PM -0400, Dave Jones wrote:
> On Tue, Apr 01, 2014 at 04:18:22PM -0700, Paul E. McKenney wrote:
>
> > > # entries-in-buffer/entries-written: 7/7 #P:4
> > > #
> > > # _-=> irqs-off
> > > # / _=>
On 03/31/2014 09:08 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.36 release.
There are 9 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
2014-04-01 16:55 GMT-07:00 Alexander Holler :
> Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
Please specify the commit message in parenthesis.
> changed the initialization of the mv643xx_eth driver to use phy_init_hw()
> to reset the PHY. Unfortunately the
On Tue, 01 Apr 2014 11:54:23 -0700
"H. Peter Anvin" wrote:
> On 03/31/2014 05:33 PM, Linus Torvalds wrote:
> >
> > I notice that there seems to be a handful of x86 system calls that
> > don't use the SYSCALL_DEFINEx() macros to define the system call, some
> > grepping finds at least ioperm(),
On Tue, Apr 01, 2014 at 04:57:24PM -0700, Paul E. McKenney wrote:
> > [ 917.790265] INFO: rcu_preempt detected stalls on CPUs/tasks:
> > [ 917.791189] (detected by 0, t=6502 jiffies, g=21390, c=21389, q=0)
>
> But the hang didn't happen until grace period #21390. Sigh! That means
>
1 - 100 of 1722 matches
Mail list logo
