On Thu 2014-05-29 12:17:39, Tony Lindgren wrote:
> * Pavel Machek [140529 12:03]:
> > On Fri 2014-05-16 14:12:31, Tony Lindgren wrote:
> > > * Paul Bolle [140515 12:42]:
> > > > A check for CONFIG_SX1_OLD_FLASH was added in v2.6.24. But the related
> > > > Kconfig symbol was never part of the tre
On Thu, May 29, 2014 at 3:32 PM, Andy Lutomirski wrote:
> On Thu, May 29, 2014 at 12:17 PM, Paul Gortmaker
> wrote:
>> On Mon, May 5, 2014 at 6:25 PM, tip-bot for Andy Lutomirski
>> wrote:
>>> Commit-ID: 6f121e548f83674ab4920a4e60afb58d4f61b829
>>> Gitweb:
>>> http://git.kernel.org/tip/6f1
On 05/29/2014 12:32 PM, Andy Lutomirski wrote:
> On Thu, May 29, 2014 at 12:17 PM, Paul Gortmaker
> wrote:
>> On Mon, May 5, 2014 at 6:25 PM, tip-bot for Andy Lutomirski
>> wrote:
>>> Commit-ID: 6f121e548f83674ab4920a4e60afb58d4f61b829
>>> Gitweb:
>>> http://git.kernel.org/tip/6f121e548f836
On Tue, 2014-05-20 at 19:25 -0500, Kim Phillips wrote:
> From: Kim Phillips
>
> Needed by platform device drivers, such as the vfio-platform driver
> later in series, in order to bypass the existing OF, ACPI, id_table and
> name string matches, and successfully be able to be bound to any
> device
On 29 May 2014 16:04, Peter Zijlstra wrote:
> On Fri, May 23, 2014 at 05:53:04PM +0200, Vincent Guittot wrote:
>> @@ -7282,6 +7289,12 @@ static inline int nohz_kick_needed(struct rq *rq)
>>
>> if (nr_busy > 1)
>> goto need_kick_unlock;
>> +
>> + if (
On Thu, May 29, 2014 at 9:19 AM, Srinivas Kandagatla
wrote:
>> +++ b/drivers/mfd/qcom_rpm.c
[...]
>> +struct qcom_rpm {
>> + struct device *dev;
>> + struct completion ack;
>> + struct mutex lock;
>> +
>> + void __iomem *status_regs;
>> + void __iomem *ctrl_regs;
>>
On Thu, May 29, 2014 at 12:43 PM, H. Peter Anvin wrote:
> On 05/29/2014 12:32 PM, Andy Lutomirski wrote:
>> On Thu, May 29, 2014 at 12:17 PM, Paul Gortmaker
>> wrote:
>>> On Mon, May 5, 2014 at 6:25 PM, tip-bot for Andy Lutomirski
>>> wrote:
Commit-ID: 6f121e548f83674ab4920a4e60afb58d4f61b
On 29 May 2014 15:55, Peter Zijlstra wrote:
> On Fri, May 23, 2014 at 05:53:05PM +0200, Vincent Guittot wrote:
>> The scheduler tries to compute how many tasks a group of CPUs can handle by
>> assuming that a task's load is SCHED_LOAD_SCALE and a CPU capacity is
>> SCHED_POWER_SCALE.
>> We can now
V6->V7
- Remove /sysfs support and avoid the large cpumask definition.
V5->V6:
- Shepherd thread as a general worker thread. This means
that the general mechanism to control worker thread
cpu use by Frederic Weisbecker is necessary to
restrict the shepherd thread to the cpus not used
for
On Thu, 29 May 2014 10:43:21 -0400
Paul Gortmaker wrote:
> [[PATCH V2 3/3] init/calibrate.c: no prefix in logging] On 29/05/2014 (Thu
> 10:14) Fabian Frederick wrote:
>
> > define pr_fmt without prefix to avoid any default prefix update
>
> Again, it isn't clear to me what you are trying to ac
On 29 May 2014 16:02, Peter Zijlstra wrote:
> On Fri, May 23, 2014 at 05:53:05PM +0200, Vincent Guittot wrote:
>> @@ -6052,8 +6006,8 @@ static inline void update_sd_lb_stats(struct lb_env
>> *env, struct sd_lb_stats *sd
>>* with a large weight task outweighs the tasks on the syste
On Thu, May 29, 2014 at 9:35 PM, David Howells wrote:
> Sedat Dilek wrote:
>
>> # LC_ALL=C TEST_OVERLAYFS="1" ./run.sh
>> [ run.sh ] TEST_OVERLAYFS is 1
>> ***
>> *** ./run.sh open-plain.test
>> ***
>> [ mount_union.sh ] TEST_OVERLAYFS is 1
>> TEST100: Open O_RDONLY
>> - open_file -r /mnt/a/foo1
On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim wrote:
> Richard Yao reported a month ago that his system have a trouble
> with vmap_area_lock contention during performance analysis
> by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
> stressfully, but he didn't answer it.
>
>
On Thursday 29 May 2014 03:24 PM, Arnd Bergmann wrote:
> On Thursday 29 May 2014 10:08:10 Santosh Shilimkar wrote:
>> On Thursday 29 May 2014 10:01 AM, Linus Walleij wrote:
>>> On Wed, May 28, 2014 at 4:04 PM, Santosh Shilimkar
>>> wrote:
On Wednesday 28 May 2014 09:32 AM, Linus Walleij wrote
Implement and enable context tracking for arm64 (which is
a prerequisite for FULL_NOHZ support). This patchset
builds upon earlier work by Kevin Hilman and is based on
Will Deacon's tree.
Changes v5 to v6:
* Don't save far_el1 in x26 in el0_dbg path (not needed)
* TIF_NOHZ processes go through th
To implement the context tracker properly on arm64,
a function call needs to be made after debugging and
interrupts are turned on, but before the lr is changed
to point to ret_to_user(). If the function call
is made after the lr is changed the function will not
return to the correct place.
For sim
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc, el0_irq and all of the "error" paths).
These macros expand to function calls which will only work
properly if el0_sync and related code has been rearranged
(in a previous
As analyzed in https://bugzilla.kernel.org/show_bug.cgi?id=76331
we can have multiple DRHDs in a system and each may support different
guest address widths. We can add a device behind a less capable DRHD
to a domain so long as the lesser DRHD can map the existing domain
page table. We should neve
On Tue, May 27, 2014 at 08:47:36AM +0200, Jonas Bonn wrote:
> On 05/26/2014 10:52 PM, Geert Uytterhoeven wrote:
> > CC devicetree for the bindings
> >
> > On Mon, May 26, 2014 at 10:31 PM, Stefan Kristiansson
> > wrote:
> >> +++
> >> b/Documentation/devicetree/bindings/interrupt-controller/openc
Larry Bassel writes:
> Make calls to ct_user_enter when the kernel is exited
> and ct_user_exit when the kernel is entered (in el0_da,
> el0_ia, el0_svc, el0_irq and all of the "error" paths).
>
> These macros expand to function calls which will only work
> properly if el0_sync and related code h
On Wed, May 28, 2014 at 03:52:52PM +0900, Heesub Shin wrote:
> For aesthetics and readability, rename goto labels, remove
> useless code lines, and clarify function return type.
>
> Signed-off-by: Heesub Shin
> Reviewed-by: Mitchel Humpherys
> Tested-by: John Stultz
Not all of these would appl
On Wed, May 28, 2014 at 04:23:47PM -0700, Chaitanya Hazarey wrote:
> Fixed a misplaced brace in a function
>
> Signed-off-by: Chaitanya Hazarey
> ---
> drivers/staging/rtl8192u/r8192U_wx.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Where is patch 2/2 ?
--
To unsubscribe from thi
I have 1/5 through to 5/5. Will resend rightaway with slightly changed
subjects.
Chaitanya
On Thu, May 29, 2014 at 1:43 PM, Greg KH wrote:
> On Wed, May 28, 2014 at 04:23:47PM -0700, Chaitanya Hazarey wrote:
>> Fixed a misplaced brace in a function
>>
>> Signed-off-by: Chaitanya Hazarey
>> ---
On Thu, May 29, 2014 at 11:03 AM, Kumar Gala wrote:
> If we have a PCI config space specified in something like a ranges
> property we should treat it as memory type resource.
Config space should not be in ranges[1]. We have some cases that are,
but we don't want new ones.
>
> Signed-off-by: Kum
Removed dead code from the file.
Signed-off-by: Chaitanya Hazarey
---
drivers/staging/rtl8192u/r8192U_wx.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/staging/rtl8192u/r8192U_wx.c
b/drivers/staging/rtl8192u/r8192U_wx.c
index 09b1e81..ceb06d8 10
Removed dead code, commented out printks and DMESG.
Signed-off-by: Chaitanya Hazarey
---
drivers/staging/rtl8192u/r8192U_wx.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/staging/rtl8192u/r8192U_wx.c
b/drivers/staging/rtl8192u/r8192U_wx.c
index 675a12d..7dc2a96 100644
Added a space around '|' to address:
ERROR: need consistent spacing around '|' (ctx:VxW)
Signed-off-by: Chaitanya Hazarey
---
drivers/staging/rtl8192u/r8192U_wx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8192u/r8192U_wx.c
b/drivers/staging/rtl8192u
Fixed a misplaced brace in the r8192_wx_set_scan_type function.
Signed-off-by: Chaitanya Hazarey
---
drivers/staging/rtl8192u/r8192U_wx.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8192u/r8192U_wx.c
b/drivers/staging/rtl8192u/r8192U_wx.c
index 1af7c
To address the error -
ERROR: do not use C99 // comments
Removed all C99 comments.
Signed-off-by: Chaitanya Hazarey
---
drivers/staging/rtl8192u/r8192U_wx.c | 130 +--
1 file changed, 65 insertions(+), 65 deletions(-)
diff --git a/drivers/staging/rtl8192u/r8192
On Thu, May 29, 2014 at 2:03 AM, Dan Carpenter wrote:
> On Wed, May 28, 2014 at 08:26:53PM -0400, Alex Deucher wrote:
>> On Wed, May 28, 2014 at 7:49 PM, Ken Moffat wrote:
>> > On Wed, May 28, 2014 at 06:25:21PM +0100, Ken Moffat wrote:
>> >> Hi Daniel,
>> >>
>> >
>> > [ correcting details, conf
Local variable "box" gets assigned correct value when it is initialized.
There is no need to assign the same value again. Variable declarations
were reshuffled for better readability.
Signed-off-by: Giedrius Rekasius
---
Original patch was amended for better readability based on feedback from Wal
On Thu, 29 May 2014, Naoya Horiguchi wrote:
> On Wed, May 28, 2014 at 05:33:11PM -0700, Hugh Dickins wrote:
> > On Wed, 28 May 2014, Michael Ellerman wrote:
> > > Hey folks,
> > >
> > > Anyone seen this before? Trinity hit it just now:
> > >
> > > Linux Blade312-5 3.15.0-rc7 #306 SMP Wed May 28 1
On May 29, 2014, at 3:44 PM, Rob Herring wrote:
> On Thu, May 29, 2014 at 11:03 AM, Kumar Gala wrote:
>> If we have a PCI config space specified in something like a ranges
>> property we should treat it as memory type resource.
>
> Config space should not be in ranges[1]. We have some cases th
В Ср, 28/05/2014 в 22:26 +0200, Thomas Gleixner пишет:
> On Mon, 5 May 2014, Kirill Tkhai wrote:
> > В Сб, 03/05/2014 в 20:54 +0200, Thomas Gleixner пишет:
> > > Though exercising that code path as much as we can is not a bad thing
> > > either. So I'd like to see that made compile time conditional
On Thu, May 29, 2014 at 09:40:39AM +0300, Dan Carpenter wrote:
> On Thu, May 29, 2014 at 09:17:09AM +0900, DaeSeok Youn wrote:
> > Hi, Dan.
> >
> > 2014-05-28 19:11 GMT+09:00 Dan Carpenter :
> > > On Wed, May 28, 2014 at 06:29:38PM +0900, DaeSeok Youn wrote:
> > >> > In your patch it has:
> > >> >
On Thu, May 29, 2014 at 10:47 PM, Alex Deucher wrote:
> On Thu, May 29, 2014 at 2:03 AM, Dan Carpenter
> wrote:
>> On Wed, May 28, 2014 at 08:26:53PM -0400, Alex Deucher wrote:
>>> On Wed, May 28, 2014 at 7:49 PM, Ken Moffat wrote:
>>> > On Wed, May 28, 2014 at 06:25:21PM +0100, Ken Moffat wrot
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, May 29, 2014 at 01:43:01PM -0700, Chaitanya Hazarey wrote:
> I have 1/5 through to 5/5. Will resend rightaway with slightly changed
> subjects.
What does that have to do with patch 2/2 here?
Hello Jens,
This bug was originally reported against 3.10 and still exists in
3.15-rc5 [1] [2].
These changes were tested on-top of 3.15-rc5 with user-program that
opens a CD device, its media is removed, and then the program issues a
CDROMEJECT ioctl. Without this change, the kernel can crash
The blk-core dead queue checks introduce an error scenario to
blk_get_request that returns NULL if the request queue has been
shutdown. This affects the behavior for __GFP_WAIT callers, who should
verify the return value before dereferencing.
Signed-off-by: Joe Lawrence
Acked-by: Jiri Kosina [fo
The blk_get_request function may fail in low-memory conditions or during
device removal (even if __GFP_WAIT is set). To distinguish between these
errors, modify the blk_get_request call stack to return the appropriate
ERR_PTR. Verify that all callers check the return status and consider
IS_ERR inst
Sedat Dilek wrote:
> "Fixable" in your testsuite?
Done and pushed.
David
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at ht
On Wed, May 28, 2014 at 9:55 AM, Mark Brown wrote:
> On Tue, May 27, 2014 at 10:28:41AM -0700, Bjorn Andersson wrote:
>
>> +static int rpm_reg_set_voltage(struct regulator_dev *rdev,
>> +int min_uV, int max_uV,
>> +unsigned *selector)
>> +{
>
On Tue, 27 May 2014 22:23:51 +0200 Rickard Strandqvist
wrote:
> Removal of null pointer checks that could never happen
How do you know it never happens?
> --- a/fs/ocfs2/move_extents.c
> +++ b/fs/ocfs2/move_extents.c
> @@ -904,9 +904,6 @@ static int ocfs2_move_extents(struct
> ocfs2_move_exte
On Thu, 29 May 2014, Michael Ellerman wrote:
>
> Unfortunately I don't know our mm/hugetlb code well enough to give you a good
> answer. Ben had a quick look at our follow_huge_addr() and thought it looked
> "fishy". He suggested something like what we do in gup_pte_range() with
> page_cache_get_s
On Thu, May 29, 2014 at 1:03 AM, Mike Turquette wrote:
>
> Small number of user-visible regression fixes for clock drivers. There
> is a memory leak fix for an ST platform, an infinite Loop Of Doom fix
> for the recent changes to the basic clock divider (hopefully the last
> fix for those recent c
I am Mrs. Margaret Crawford, i write you this email to seek for your
Humanitarian help, i have decided to donate part of my inheritance to you for
humanitarian work and your personal use. As a result of my heart status. I need
you to contact my Attoney. Mark lawson. with this email for a better
On Thu, May 29, 2014 at 11:21:09AM -0700, Greg Kroah-Hartman wrote:
> On Thu, May 29, 2014 at 08:06:10AM -0700, Guenter Roeck wrote:
> > On 05/28/2014 09:32 PM, Greg Kroah-Hartman wrote:
> > >This is the start of the stable review cycle for the 3.14.5 release.
> > >There are 140 patches in this ser
On Thu, May 29, 2014 at 02:03:40PM -0700, Bjorn Andersson wrote:
Please fix your mailer to word wrap at less than 80 columns so quoted
text is legible.
> The hardware in this case is a "pmic" shared by all cpus in the system, so
> when
> we set the voltage, state or load of a regulator we merely
Right now if you've got earlyprintk enabled on exynos5420-peach-pit
then you'll get a hang on boot. Here's why:
1. The i2c-s3c2410 driver will probe at subsys_initcall. It will
enable its clock and disable it. This is the clock "i2c2".
2. The act of disabling "i2c2" will disable its parents.
This driver add partial support of the
maxim 1027/1029/1031. Differential mode is not
supported.
It was tested on armadeus apf27 board.
Signed-off-by: Philippe Reynes
---
.../devicetree/bindings/iio/adc/max1027-adc.txt| 22 +
drivers/iio/adc/Kconfig|9 +
dr
On Thu, 2014-05-29 at 13:05 -0700, Andrew Morton wrote:
> On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim wrote:
>
> > Richard Yao reported a month ago that his system have a trouble
> > with vmap_area_lock contention during performance analysis
> > by /proc/meminfo. Andrew asked why his analysis
On Thu, May 29, 2014 at 02:03:37PM -0700, Andrew Morton wrote:
> On Tue, 27 May 2014 22:23:51 +0200 Rickard Strandqvist
> wrote:
>
> > Removal of null pointer checks that could never happen
>
> How do you know it never happens?
>
> > --- a/fs/ocfs2/move_extents.c
> > +++ b/fs/ocfs2/mo
On 29.05.14 21:43, Alex Williamson wrote:
On Tue, 2014-05-20 at 19:25 -0500, Kim Phillips wrote:
From: Kim Phillips
Needed by platform device drivers, such as the vfio-platform driver
later in series, in order to bypass the existing OF, ACPI, id_table and
name string matches, and successfully
From: Siva Yerramreddy
Added an overview of mic bus and dma driver.
Reviewed-by: Ashutosh Dixit
Reviewed-by: Nikhil Rao
Reviewed-by: Sudeep Dutt
Signed-off-by: Siva Yerramreddy
---
Documentation/mic/mic_overview.txt | 67 +++---
1 file changed, 41 insertions(
From: Siva Yerramreddy
modprobe dma driver upon start and remove it upon unload.
Signed-off-by: Siva Yerramreddy
---
Documentation/mic/mpssd/mpss | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/mic/mpssd/mpss b/Documentation/mic/mpssd/mpss
index
ChangeLog:
=
v1 => v2:
a) MIC bus driver cleanups and device release callback fix in patch 2,
as per feedback from Greg Kroah-Hartman.
v1: Initial post @ https://lkml.org/lkml/2014/5/27/819
These patches are being sent to char-misc because there is a dependency
between the patches for
From: Siva Yerramreddy
This patch implements DMA Engine API for DMA controller on MIC X100
Coprocessors. DMA h/w is shared between host and card s/w.
Channels 0 to 3 are used by host and 4 to 7 are used by card.
Since the DMA device doesn't show up as PCIe device, a virtual bus called mic
bus is
From: Siva Yerramreddy
This patch adds a dma device on the mic virtual bus and uses this dmaengine
to transfer data for virtio devices
Reviewed-by: Nikhil Rao
Signed-off-by: Sudeep Dutt
Signed-off-by: Ashutosh Dixit
Signed-off-by: Siva Yerramreddy
---
drivers/misc/mic/Kconfig |
From: Siva Yerramreddy
This patch adds a dma device on the mic virtual bus
Reviewed-by: Nikhil Rao
Signed-off-by: Sudeep Dutt
Signed-off-by: Siva Yerramreddy
Signed-off-by: Ashutosh Dixit
---
drivers/misc/mic/Kconfig | 2 +-
drivers/misc/mic/card/mic_device.h | 8 --
drivers
On 29/05/14 19:38, Bjorn Andersson wrote:
On Thu, May 29, 2014 at 9:19 AM, Srinivas Kandagatla
wrote:
+- reg:
+ Usage: required
+ Value type:
+ Definition: two entries specifying the RPM's message ram and ipc
register
+
+- reg-names:
+ Usage: required
+ Value ty
From: Siva Yerramreddy
Add threaded irq support in mic_request_card_irq which will be used
for virtual devices added on mic bus.
Reviewed-by: Ashutosh Dixit
Reviewed-by: Nikhil Rao
Reviewed-by: Sudeep Dutt
Signed-off-by: Siva Yerramreddy
---
drivers/misc/mic/card/mic_device.c | 23 +
From: Siva Yerramreddy
Convert mic_request_irq to mic_request_threaded_irq to support threaded
irq for virtual devices on mic bus.
Reviewed-by: Ashutosh Dixit
Reviewed-by: Nikhil Rao
Reviewed-by: Sudeep Dutt
Signed-off-by: Siva Yerramreddy
---
drivers/misc/mic/host/mic_intr.c | 121 ++
This MIC virtual bus driver takes the responsibility of creating all
the virtual devices connected to the PCIe device on the host and the
platform device on the card. The MIC bus hardware operations provide
a way to abstract certain hardware details from the base physical devices.
Examples of devic
On Thu, May 29, 2014 at 2:07 PM, Guenter Roeck wrote:
> On Thu, May 29, 2014 at 11:21:09AM -0700, Greg Kroah-Hartman wrote:
>> On Thu, May 29, 2014 at 08:06:10AM -0700, Guenter Roeck wrote:
>> >
>> > alpha:defconfig - Fails with 'Inconsistent kallsyms
>> > data'. New failure;
Not involved in 8xx activities for years, update MAINTAINERS
to reflect it.
Signed-off-by: Marcelo Tosatti
diff --git a/MAINTAINERS b/MAINTAINERS
index c47d268..ed7b606 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5349,7 +5349,6 @@ F:arch/powerpc/*/*/*virtex*
LINUX FOR POWERPC EMBE
On the ARM Chromebook tps65090 has two masters: the AP (the main
processor running linux) and the EC (the embedded controller). The AP
is allowed to mess with FETs but the EC is in charge of charge control.
The tps65090 interupt line is routed to both the AP and the EC, which
can cause quite a he
On Thu, 29 May 2014 17:23:08 -0400 Dave Jones wrote:
> On Thu, May 29, 2014 at 02:03:37PM -0700, Andrew Morton wrote:
> > On Tue, 27 May 2014 22:23:51 +0200 Rickard Strandqvist
> wrote:
> >
> > > Removal of null pointer checks that could never happen
> >
> > How do you know it never happ
On 29/05/14 20:45, Bjorn Andersson wrote:
On Thu, May 29, 2014 at 9:19 AM, Srinivas Kandagatla
wrote:
+++ b/drivers/mfd/qcom_rpm.c
the line spacing looks bit odd.
I'll fix
+};
+
+#define RPM_STATUS_REG(rpm, i) ((rpm)->status_regs + (i) * 4)
+#define RPM_CTRL_REG(rpm, i) ((rpm)->ctrl
On Thu, May 29, 2014 at 02:00:51PM -0700, Greg KH wrote:
> On Thu, May 29, 2014 at 01:43:01PM -0700, Chaitanya Hazarey wrote:
> > I have 1/5 through to 5/5. Will resend rightaway with slightly changed
> > subjects.
>
> What does that have to do with patch 2/2 here? You sent a 1/2 patch, so
> obvi
To implement the context tracker properly on arm64,
a function call needs to be made after debugging and
interrupts are turned on, but before the lr is changed
to point to ret_to_user(). If the function call
is made after the lr is changed the function will not
return to the correct place.
For sim
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc, el0_irq and all of the "error" paths).
These macros expand to function calls which will only work
properly if el0_sync and related code has been rearranged
(in a previous
Implement and enable context tracking for arm64 (which is
a prerequisite for FULL_NOHZ support). This patchset
builds upon earlier work by Kevin Hilman and is based on
Will Deacon's tree.
Changes v5 to v6:
* Don't save far_el1 in x26 in el0_dbg path (not needed)
* TIF_NOHZ processes go through th
I have reviewed this patchset.
Reviewed-by: Dan Carpenter
Btw, I wish you would fold some of these patches together next time.
For example, patches 3-6 are very closely related and they should have
just been one thing.
Or the times where the change log says, "I am going to delete function
frob_
Adding Jason Gunthorpe...
On Thu, May 29, 2014 at 3:51 PM, Kumar Gala wrote:
>
> On May 29, 2014, at 3:44 PM, Rob Herring wrote:
>
>> On Thu, May 29, 2014 at 11:03 AM, Kumar Gala wrote:
>>> If we have a PCI config space specified in something like a ranges
>>> property we should treat it as mem
Ok will be quite for till the last ones get accepted.
Sorry for the bother !
Chaitanya
On Thu, May 29, 2014 at 2:41 PM, Dan Carpenter wrote:
> On Thu, May 29, 2014 at 02:00:51PM -0700, Greg KH wrote:
>> On Thu, May 29, 2014 at 01:43:01PM -0700, Chaitanya Hazarey wrote:
>> > I have 1/5 through t
Hi Matthew and Keith,
Thanks for the quick review.
The patch has been updated with the feedback from Keith and Jens. It's against
Jens' 3.16/core tree. You may use the nvmemq_wip_review branch at:
https://github.com/MatiasBjorling/linux-collab nvmemq_wip_review
Changes since v3:
* Added abort
This converts the current NVMe driver to utilize the blk-mq layer.
Contributions in this patch from:
Sam Bradshaw
Jens Axboe
Signed-off-by: Matias Bjørling
---
drivers/block/nvme-core.c | 1100 ++---
include/linux/nvme.h | 11 +-
2 files cha
This adds a macro GET(x) to convert x from big-endian to
little-endian. Hopefully I put it everywhere it needs to go and got
all the cases needed for everyone's linux/elf.h.
Signed-off-by: Andy Lutomirski
---
arch/x86/vdso/vdso2c.c | 15 +
arch/x86/vdso/vdso2c.h | 59 +++
Patch 1 causes make;make to behave similarly to make if vdso2c fails.
Patch 2 hopefully fixes x86 crossbuilds on big-endian machines. I don't
have a big-endian machine to test on, though.
Andy Lutomirski (2):
x86,vdso: When vdso2c fails, unlink the output
x86,vdso: Fix cross-compilation from
This avoids bizarre failures if make is run again.
Signed-off-by: Andy Lutomirski
---
arch/x86/vdso/vdso2c.c | 20 +++-
arch/x86/vdso/vdso2c.h | 10 +++---
2 files changed, 14 insertions(+), 16 deletions(-)
diff --git a/arch/x86/vdso/vdso2c.c b/arch/x86/vdso/vdso2c.c
index 8
On Fri, May 30, 2014 at 12:41:15AM +0300, Dan Carpenter wrote:
> On Thu, May 29, 2014 at 02:00:51PM -0700, Greg KH wrote:
> > On Thu, May 29, 2014 at 01:43:01PM -0700, Chaitanya Hazarey wrote:
> > > I have 1/5 through to 5/5. Will resend rightaway with slightly changed
> > > subjects.
> >
> > What
On Thu, May 29, 2014 at 2:18 PM, Mark Brown wrote:
> On Thu, May 29, 2014 at 02:03:40PM -0700, Bjorn Andersson wrote:
>
> Please fix your mailer to word wrap at less than 80 columns so quoted
> text is legible.
>
>> The hardware in this case is a "pmic" shared by all cpus in the system, so
>> whe
On 14-05-29 06:44 AM, Linus Walleij wrote:
On Tue, May 27, 2014 at 9:26 PM, wrote:
From: Eric Ernst
For Baytrail, you should never set a GPIO set to direct_irq
to output mode. When direct_irq_en is set for a GPIO, it is
tied directly to an APIC internally, and making the pad output
does no
On Thu, May 29, 2014 at 02:59:38PM -0700, Bjorn Andersson wrote:
> On Thu, May 29, 2014 at 2:18 PM, Mark Brown wrote:
> > No, this is awful and there's no way in hell that stuff like this should
> > be implemented in a driver since there's clearly nothing at all hardware
> > specific about it. T
On Thu, 29 May 2014, Naoya Horiguchi wrote:
>
> Curretly hugepage migration is available for all archs which support pmd-level
> hugepage, but testing is done only for x86_64 and there're bugs for other
> archs.
And even for x86_64 I think: the follow_huge_pmd() locking issue I
mentioned. But I
On Thu, May 29, 2014 at 2:41 PM, Srinivas Kandagatla
wrote:
>> Although we will not have more than one rpm in a system and therefore not
>> instatiate this driver multiple times I do not want to run it off the
>> global
>> state.
>>
> I agree.
>
> Why not make a separate data structure for the qco
On 05/29/2014 02:54 PM, abdoulaye berthe wrote:
Did you forget a changelog explaining why this is either needed, or even
a good idea? I joined the conversation late and don't know why you are
doing this.
Thanks,
David Daney
Signed-off-by: abdoulaye berthe
---
arch/arm/common/scoop.c
minor (Rafael usually fixes it up, but still):
$subject: PM / OPP:
On 05/27/2014 06:50 AM, Viresh Kumar wrote:
> When none of CONFIG_PM_OPP or CONFIG_OF is enabled we use the dummy
> implementation of of_init_opp_table() routine, which returns -EINVAL
> currently.
> -EINVAL can confuse the caller
On Fri, 23 May 2014 22:26:11 +0200 Fabian Frederick wrote:
> Remove obsolete simple_strtoul in ncp_getopt
Looks good to me.
>
> --- a/fs/ncpfs/getopt.c
> +++ b/fs/ncpfs/getopt.c
> @@ -53,15 +53,14 @@ int ncp_getopt(const char *caller, char **options, const
> struct ncp_option *opts
>
Quoting Doug Anderson (2014-05-29 14:21:36)
> Right now if you've got earlyprintk enabled on exynos5420-peach-pit
> then you'll get a hang on boot. Here's why:
>
> 1. The i2c-s3c2410 driver will probe at subsys_initcall. It will
>enable its clock and disable it. This is the clock "i2c2".
>
On 5/29/2014 11:24 AM, Bjorn Andersson wrote:
> On Wed, May 28, 2014 at 9:34 AM, Kumar Gala wrote:
>>
>> On May 27, 2014, at 12:28 PM, Bjorn Andersson
>> wrote:
>>
>>> Add binding for the Qualcomm Resource Power Manager (RPM) found in 8660,
>>> 8960
>>> and 8064 based devices. The binding curre
This avoids handling gpiochip remove error in device
remove handler.
Signed-off-by: abdoulaye berthe
---
drivers/gpio/gpiolib.c | 24 +++-
include/linux/gpio/driver.h | 2 +-
2 files changed, 8 insertions(+), 18 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/driver
On 05/27/2014 06:50 AM, Viresh Kumar wrote:
> All callers of of_init_opp_table() are required to take reference of
> dev->of_node, by initiating calls to of_node_{get|put}(), before and after
> calling of_init_opp_table().
>
> Its better to call these from within of_init_opp_table(), no fun adding
On 05/27/2014 06:50 AM, Viresh Kumar wrote:
> Enhance print messages for debugging purposes. Add a dev_err() whenever we
> fail
> to initialize OPP table due to some error in the table present in dts and add
> a
> dev_dbg() for success case.
>
> Signed-off-by: Viresh Kumar
> ---
> drivers/base
On Thu, 29 May 2014, Jens Axboe wrote:
On 2014-05-28 21:07, Keith Busch wrote:
Barring any bugs in the code, then yes, this should work. On the scsi-mq
side, extensive error injection and pulling has been done, and it seems to
hold up fine now. The ioctl path would need to be audited.
It's a
From: Linus Lüssing
Date: Sun, 25 May 2014 07:03:21 +0200
> Changes in v2:
I really need a bridging expert to review this series, thank you.
--
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 ht
On 05/29/2014 01:00 PM, Peter Zijlstra wrote:
> On Thu, May 29, 2014 at 06:50:57PM +0200, Peter Zijlstra wrote:
>> > On Thu, May 29, 2014 at 12:44:23PM -0400, Sasha Levin wrote:
>>> > > On 05/29/2014 11:07 AM, Peter Zijlstra wrote:
> > > On Thu, May 29, 2014 at 10:47:09AM -0400, Sasha Levin wr
Hi all!
First, I'm no expert on this code, but after a patch which I thought
was most accurate for the current code was written before, which was
rather something like the code below.
Then Jeff Liu that this was not something that could happen. So I send
a patch where the check was removed instead
On Thu, 29 May 2014 15:43:03 -0300 Marcelo Tosatti wrote:
>
> Zone specific allocations, such as GFP_DMA32, should not be restricted
> to cpusets allowed node list: the zones which such allocations demand
> might be contained in particular nodes outside the cpuset node list.
>
> Necessary for t
On 14-05-29 05:57 PM, Andy Lutomirski wrote:
> Patch 1 causes make;make to behave similarly to make if vdso2c fails.
> Patch 2 hopefully fixes x86 crossbuilds on big-endian machines. I don't
> have a big-endian machine to test on, though.
Since the x86 builds are unconditionally failing as-is now
601 - 700 of 908 matches
Mail list logo
