> -Original Message-
> From: Ruxandra Ioana Radulescu
> Sent: Wednesday, November 02, 2016 9:50 AM
> To: Stuart Yoder ; gre...@linuxfoundation.org
> Cc: German Rivera ; de...@driverdev.osuosl.org;
> linux-kernel@vger.kernel.org;
>
> -Original Message-
> From: Ruxandra Ioana Radulescu
> Sent: Wednesday, November 02, 2016 9:50 AM
> To: Stuart Yoder ; gre...@linuxfoundation.org
> Cc: German Rivera ; de...@driverdev.osuosl.org;
> linux-kernel@vger.kernel.org;
> ag...@suse.de; a...@arndb.de; Leo Li ; Roy Pledge
> ;
On 2016.11.04 at 15:24 +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-04 07:37:02 [-0400], Austin S. Hemmelgarn wrote:
> > > clued enough to have known better. Reassigning bug reports in question
> > > from gcc-6 to linux is beyond stupid; Balint is either being deliberately
> > > obtuse,
On 2016.11.04 at 15:24 +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-04 07:37:02 [-0400], Austin S. Hemmelgarn wrote:
> > > clued enough to have known better. Reassigning bug reports in question
> > > from gcc-6 to linux is beyond stupid; Balint is either being deliberately
> > > obtuse,
On Thu, Nov 03, 2016 at 03:50:07PM +0100, Sebastian Andrzej Siewior wrote:
> @@ -1084,20 +1079,13 @@ static int smp_add_present_cpu(int cpu)
> rc = sysfs_create_group(>kobj, _common_attr_group);
> if (rc)
> goto out_cpu;
> - if (cpu_online(cpu)) {
> - rc =
On Thu, Nov 03, 2016 at 03:50:07PM +0100, Sebastian Andrzej Siewior wrote:
> @@ -1084,20 +1079,13 @@ static int smp_add_present_cpu(int cpu)
> rc = sysfs_create_group(>kobj, _common_attr_group);
> if (rc)
> goto out_cpu;
> - if (cpu_online(cpu)) {
> - rc =
On Oct 27 2016 or thereabouts, Bastien Nocera wrote:
> This adds support for the THQ uDraw tablet for the PS3, as
> 4 separate device nodes, so that user-space can easily consume
> events coming from the hardware.
>
> Note that the touchpad two-finger support is fairly unreliable,
> and a
On Oct 27 2016 or thereabouts, Bastien Nocera wrote:
> This adds support for the THQ uDraw tablet for the PS3, as
> 4 separate device nodes, so that user-space can easily consume
> events coming from the hardware.
>
> Note that the touchpad two-finger support is fairly unreliable,
> and a
On 2016-11-04 07:37:02 [-0400], Austin S. Hemmelgarn wrote:
> > clued enough to have known better. Reassigning bug reports in question
> > from gcc-6 to linux is beyond stupid; Balint is either being deliberately
> > obtuse, or geniunely unable to imagine that somebody might be using the
> >
On 2016-11-04 07:37:02 [-0400], Austin S. Hemmelgarn wrote:
> > clued enough to have known better. Reassigning bug reports in question
> > from gcc-6 to linux is beyond stupid; Balint is either being deliberately
> > obtuse, or geniunely unable to imagine that somebody might be using the
> >
On Thu, Nov 03, 2016 at 03:50:06PM +0100, Sebastian Andrzej Siewior wrote:
> From: Thomas Gleixner
>
> There is no reason to remove the sysfs cpu files when the CPU is dead, they
> can be removed when the cpu is prepared to go down. Doing it at
> DOWN_PREPARE allows us to
On Thu, Nov 03, 2016 at 03:50:06PM +0100, Sebastian Andrzej Siewior wrote:
> From: Thomas Gleixner
>
> There is no reason to remove the sysfs cpu files when the CPU is dead, they
> can be removed when the cpu is prepared to go down. Doing it at
> DOWN_PREPARE allows us to convert it to a
On Fri, Nov 4, 2016 at 6:14 AM, Christopher Covington
wrote:
> Applications such as Just-In-Time (JIT) compilers, Checkpoint/Restore In
> Userspace (CRIU), and User Mode Linux (UML) need to know the highest
> virtual address, TASK_SIZE, to implement pointer tagging or make a
On Fri, Nov 4, 2016 at 6:14 AM, Christopher Covington
wrote:
> Applications such as Just-In-Time (JIT) compilers, Checkpoint/Restore In
> Userspace (CRIU), and User Mode Linux (UML) need to know the highest
> virtual address, TASK_SIZE, to implement pointer tagging or make a first
> educated
On 04/11/16 11:24, Eric Auger wrote:
> The function populates the list of reserved regions with the
> PCI host bridge windows and the MSI IOVA range.
>
> At the moment an arbitray MSI IOVA window is set at 0x800
> of size 1MB.
>
> Signed-off-by: Eric Auger
>
> ---
>
On 04/11/16 11:24, Eric Auger wrote:
> The function populates the list of reserved regions with the
> PCI host bridge windows and the MSI IOVA range.
>
> At the moment an arbitray MSI IOVA window is set at 0x800
> of size 1MB.
>
> Signed-off-by: Eric Auger
>
> ---
>
> RFC v1 -> v2: use
Casey Schaufler wrote:
> On 11/1/2016 5:53 AM, Tetsuo Handa wrote:
> > I didn't check past discussion, but how do you handle
> > security_delete_hooks()
> > case (I mean, "selinux" will remain there when reading
> > /sys/kernel/security/lsm
> > even after it is disabled at runtime)?
>
> Paul
Casey Schaufler wrote:
> On 11/1/2016 5:53 AM, Tetsuo Handa wrote:
> > I didn't check past discussion, but how do you handle
> > security_delete_hooks()
> > case (I mean, "selinux" will remain there when reading
> > /sys/kernel/security/lsm
> > even after it is disabled at runtime)?
>
> Paul
On Fri, 2016-11-04 at 09:58 +0100, Pavel Machek wrote:
> On Fri 2016-11-04 09:38:49, Pavel Machek wrote:
> >
> >
[...]
> > What is worse, they go to low frequency even with "performance"
> governor on v4.8-rc1?!
>
> pavel@duo:/sys/devices/system/cpu/cpu0/cpufreq$ sudo cat
>
On Fri, 2016-11-04 at 09:58 +0100, Pavel Machek wrote:
> On Fri 2016-11-04 09:38:49, Pavel Machek wrote:
> >
> >
[...]
> > What is worse, they go to low frequency even with "performance"
> governor on v4.8-rc1?!
>
> pavel@duo:/sys/devices/system/cpu/cpu0/cpufreq$ sudo cat
>
Joe Perches writes:
> On Sun, 2016-10-30 at 19:02 -0400, Jes Sorensen wrote:
>> Code is 80 characters wide, and comments are /* */ never the ugly C++
>> crap.
>
> You might look at the recent Linus Torvalds authored commit
> 5e467652ffef (?printk: re-organize log_output() to be
Joe Perches writes:
> On Sun, 2016-10-30 at 19:02 -0400, Jes Sorensen wrote:
>> Code is 80 characters wide, and comments are /* */ never the ugly C++
>> crap.
>
> You might look at the recent Linus Torvalds authored commit
> 5e467652ffef (?printk: re-organize log_output() to be more legible")
>
On Nov 03 2016 or thereabouts, Ooi, Joyce wrote:
> User is unable to access to input-X-yyy and feature-X-yyy where
> X is a hex value and more than 9 (e.g. input-a-yyy, feature-b-yyy) in HID
> sensor custom sysfs interface.
> This is because when creating the attribute, the attribute index is
>
On Nov 03 2016 or thereabouts, Ooi, Joyce wrote:
> User is unable to access to input-X-yyy and feature-X-yyy where
> X is a hex value and more than 9 (e.g. input-a-yyy, feature-b-yyy) in HID
> sensor custom sysfs interface.
> This is because when creating the attribute, the attribute index is
>
Adding additional steps required specific to q6v56 based on version check
along with some trivial changes in name of local functions.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 137 ++---
1 file
Encapsulate resources specific to each version of hexagon chip to
device node to avoid conditional check for manipulation of those
resources in driver code.
Signed-off-by: Avaneesh Kumar Dwivedi
---
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 1 +
Adding additional steps required specific to q6v56 based on version check
along with some trivial changes in name of local functions.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 137 ++---
1 file changed, 98 insertions(+), 39
Encapsulate resources specific to each version of hexagon chip to
device node to avoid conditional check for manipulation of those
resources in driver code.
Signed-off-by: Avaneesh Kumar Dwivedi
---
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 1 +
drivers/remoteproc/qcom_q6v5_pil.c
Handling of clock and regulator resources as well as reset register
programing differe depending upon version of hexagon chip version as
number of resource to program differ and parameters to program also
differ, hence it is needed to make these functions version independent.
Signed-off-by:
Handling of clock and regulator resources as well as reset register
programing differe depending upon version of hexagon chip version as
number of resource to program differ and parameters to program also
differ, hence it is needed to make these functions version independent.
Signed-off-by:
Hi Eric,
Thanks for posting this new series - the bottom-up approach is a lot
easier to reason about :)
On 04/11/16 11:24, Eric Auger wrote:
> Introduce a new iommu_reserved_region struct. This embodies
> an IOVA reserved region that cannot be used along with the IOMMU
> API. The list is
Hi Eric,
Thanks for posting this new series - the bottom-up approach is a lot
easier to reason about :)
On 04/11/16 11:24, Eric Auger wrote:
> Introduce a new iommu_reserved_region struct. This embodies
> an IOVA reserved region that cannot be used along with the IOMMU
> API. The list is
Yeah, the device or driver is definitely getting confused with rx_desc
structures.
I added code to check for unlikely rx_desc values, and it found this for
starters:
rx_desc: 00480801 00480401 00480001 0048fc00 0048f800 0048f400 pkt_len=2045
rx_data: 00 f0 48 00 00 ec 48 00 00 e8 48 00 00 e4
Yeah, the device or driver is definitely getting confused with rx_desc
structures.
I added code to check for unlikely rx_desc values, and it found this for
starters:
rx_desc: 00480801 00480401 00480001 0048fc00 0048f800 0048f400 pkt_len=2045
rx_data: 00 f0 48 00 00 ec 48 00 00 e8 48 00 00 e4
>>> You could define an xprintf() macro that checks if the return value
>>> is < 0 and simply calls perror() and exit(1) in such case.
>> Does such a macro belong to any general header file from the Linux
>> software library?
> No.
Would you like to add it?
How do you think about to reuse it in
>>> You could define an xprintf() macro that checks if the return value
>>> is < 0 and simply calls perror() and exit(1) in such case.
>> Does such a macro belong to any general header file from the Linux
>> software library?
> No.
Would you like to add it?
How do you think about to reuse it in
Hi David,
the series have some Acked-by, do you prefer a new
series (I can rebase them if you ask me) or you can keep
this one? Or you have some advice or issue to warn?
Regards,
peppe
On 10/26/2016 8:56 AM, Giuseppe Cavallaro wrote:
This subset of patches aim to fix the PTP support
for the
Hi David,
the series have some Acked-by, do you prefer a new
series (I can rebase them if you ask me) or you can keep
this one? Or you have some advice or issue to warn?
Regards,
peppe
On 10/26/2016 8:56 AM, Giuseppe Cavallaro wrote:
This subset of patches aim to fix the PTP support
for the
On Fri, Nov 4, 2016 at 10:29 AM, Amir Goldstein wrote:
> You did not address my comment about the 'stack' allocation overflow
> in ovl_lookup
> I believe the (possible) overflow is demonstrated by the following debug
> patch:
Oops, missed that. Good spotting!
And there's
On Fri, Nov 4, 2016 at 10:29 AM, Amir Goldstein wrote:
> You did not address my comment about the 'stack' allocation overflow
> in ovl_lookup
> I believe the (possible) overflow is demonstrated by the following debug
> patch:
Oops, missed that. Good spotting!
And there's more shit that
Maciej Rozycki writes:
> On Tue, 1 Nov 2016, Guenter Roeck wrote:
>
> > > > Some toolchains fail to build mips images with the following build
> error.
> > > >
> > > > arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires
> '-mfp32'
> > > >
> > > > This is
Maciej Rozycki writes:
> On Tue, 1 Nov 2016, Guenter Roeck wrote:
>
> > > > Some toolchains fail to build mips images with the following build
> error.
> > > >
> > > > arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires
> '-mfp32'
> > > >
> > > > This is seen, for example, with the
> -Original Message-
> From: Stuart Yoder [mailto:stuart.yo...@nxp.com]
> Sent: Friday, October 21, 2016 9:02 AM
> To: gre...@linuxfoundation.org
> Cc: German Rivera ; de...@driverdev.osuosl.org;
> linux-kernel@vger.kernel.org; ag...@suse.de; a...@arndb.de; Leo Li
>
> -Original Message-
> From: Stuart Yoder [mailto:stuart.yo...@nxp.com]
> Sent: Friday, October 21, 2016 9:02 AM
> To: gre...@linuxfoundation.org
> Cc: German Rivera ; de...@driverdev.osuosl.org;
> linux-kernel@vger.kernel.org; ag...@suse.de; a...@arndb.de; Leo Li
> ; Roy Pledge ; Stuart
On Fri, Nov 4, 2016 at 3:55 PM, Christopher Covington
wrote:
> - } else
> + } else {
> seq_puts(m, " 0 0 0 0 0 0 0");
> + }
Oh, come on, people.
On Fri, Nov 4, 2016 at 3:55 PM, Christopher Covington
wrote:
> - } else
> + } else {
> seq_puts(m, " 0 0 0 0 0 0 0");
> + }
Oh, come on, people.
On Fri, Nov 04, 2016 at 09:50:56PM +0900, Masahiro Yamada wrote:
> Hi Russell,
>
> 2016-11-04 21:23 GMT+09:00 Russell King - ARM Linux :
> > On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro Yamada wrote:
> >> Documentation/CodingStyle recommends to use label names which
On Fri, Nov 04, 2016 at 09:50:56PM +0900, Masahiro Yamada wrote:
> Hi Russell,
>
> 2016-11-04 21:23 GMT+09:00 Russell King - ARM Linux :
> > On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro Yamada wrote:
> >> Documentation/CodingStyle recommends to use label names which say
> >> what the goto
Hello.
On 11/4/2016 8:11 AM, Jon Mason wrote:
Add support for the AMAC ethernet to the Broadcom Northstar2 SoC device
tree
Signed-off-by: Jon Mason
---
arch/arm64/boot/dts/broadcom/ns2-svk.dts | 5 +
arch/arm64/boot/dts/broadcom/ns2.dtsi| 12
2
Hello.
On 11/4/2016 8:11 AM, Jon Mason wrote:
Add support for the AMAC ethernet to the Broadcom Northstar2 SoC device
tree
Signed-off-by: Jon Mason
---
arch/arm64/boot/dts/broadcom/ns2-svk.dts | 5 +
arch/arm64/boot/dts/broadcom/ns2.dtsi| 12
2 files changed, 17
On Fri, 4 Nov 2016, Kai-Heng Feng wrote:
> Sometimes cdc_mbim failed to probe if runtime pm is enabled:
> [9.305626] cdc_mbim: probe of 2-2:1.12 failed with error -22
>
> This can be solved by increase its pm usage counter.
This should not be needed. The USB core increments the PM usage
On Fri, 4 Nov 2016, Kai-Heng Feng wrote:
> Sometimes cdc_mbim failed to probe if runtime pm is enabled:
> [9.305626] cdc_mbim: probe of 2-2:1.12 failed with error -22
>
> This can be solved by increase its pm usage counter.
This should not be needed. The USB core increments the PM usage
Hi,
On 04-11-16 13:30, Paul Burton wrote:
Hi Hans,
On Friday, 4 November 2016 13:11:34 GMT Hans de Goede wrote:
Hi All,
While booting 4.9-rc# for the first time on an Allwinner A33 tablet,
I noticed that after u-boot the LCD display stayed black. It turns out
that there was an issue which
Hi,
On 04-11-16 13:30, Paul Burton wrote:
Hi Hans,
On Friday, 4 November 2016 13:11:34 GMT Hans de Goede wrote:
Hi All,
While booting 4.9-rc# for the first time on an Allwinner A33 tablet,
I noticed that after u-boot the LCD display stayed black. It turns out
that there was an issue which
Applications such as Just-In-Time (JIT) compilers, Checkpoint/Restore In
Userspace (CRIU), and User Mode Linux (UML) need to know the highest
virtual address, TASK_SIZE, to implement pointer tagging or make a first
educated guess at where to find a large, unused region of memory.
Unfortunately the
Applications such as Just-In-Time (JIT) compilers, Checkpoint/Restore In
Userspace (CRIU), and User Mode Linux (UML) need to know the highest
virtual address, TASK_SIZE, to implement pointer tagging or make a first
educated guess at where to find a large, unused region of memory.
Unfortunately the
On 02.11.2016 04:30, Lu Baolu wrote:
xhci->addr_dev is used for the completion of both address device
and enable slot commands. It's shared by enumerations of all USB
devices connected to an xhci host. Hence, it's just a source for
possible races. Since we've introduced command structure and the
On 02.11.2016 04:30, Lu Baolu wrote:
xhci->addr_dev is used for the completion of both address device
and enable slot commands. It's shared by enumerations of all USB
devices connected to an xhci host. Hence, it's just a source for
possible races. Since we've introduced command structure and the
On Fri, Nov 04, 2016 at 08:59:58AM -0400, Neil Horman wrote:
> On Thu, Nov 03, 2016 at 04:35:33PM -0200, Marcelo Ricardo Leitner wrote:
> > On Thu, Nov 03, 2016 at 07:02:47PM +0100, Andrey Konovalov wrote:
> > > On Thu, Nov 3, 2016 at 6:52 PM, Marcelo Ricardo Leitner
> > >
On Fri, Nov 04, 2016 at 08:59:58AM -0400, Neil Horman wrote:
> On Thu, Nov 03, 2016 at 04:35:33PM -0200, Marcelo Ricardo Leitner wrote:
> > On Thu, Nov 03, 2016 at 07:02:47PM +0100, Andrey Konovalov wrote:
> > > On Thu, Nov 3, 2016 at 6:52 PM, Marcelo Ricardo Leitner
> > > wrote:
> > > > On Thu,
This patch adds support to pm clocks via device tree, so that the clocks
can be turned on and off during runtime pm. This patch is required for
Qualcomm msm8996 pcie controller which sits on a bus with its own
power-domain and clocks.
Without this patch the clock associated with the bus are never
This patch adds support to pm clocks via device tree, so that the clocks
can be turned on and off during runtime pm. This patch is required for
Qualcomm msm8996 pcie controller which sits on a bus with its own
power-domain and clocks.
Without this patch the clock associated with the bus are never
Hi Linus,
here is a bunch of GPIO fixes for the v4.9 series.
The most prominent thing is the largeish file descriptor leak fix,
and the regression fix for multiple-instance chips is pretty important
too.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit
This patch is required when the pcie controller sits on a bus with
its own power domain and clocks which are controlled via a bus driver
like simple pm bus. As these bus driver have runtime pm enabled, it makes
sense to update the usage counter so that the runtime pm does not suspend
the clks or
On Fri, Nov 04, 2016 at 02:06:00PM +0200, Jani Nikula wrote:
> On Fri, 04 Nov 2016, Jarkko Sakkinen wrote:
> > In order too make Documentation root directory cleaner move the tpm
> > directory under Documentation/security.
>
> FWIW I like this.
Thx. I just
This patch is required when the pcie controller sits on a bus with
its own power domain and clocks which are controlled via a bus driver
like simple pm bus. As these bus driver have runtime pm enabled, it makes
sense to update the usage counter so that the runtime pm does not suspend
the clks or
On Fri, Nov 04, 2016 at 02:06:00PM +0200, Jani Nikula wrote:
> On Fri, 04 Nov 2016, Jarkko Sakkinen wrote:
> > In order too make Documentation root directory cleaner move the tpm
> > directory under Documentation/security.
>
> FWIW I like this.
Thx. I just realized that I should have CC'd to
Hi Linus,
here is a bunch of GPIO fixes for the v4.9 series.
The most prominent thing is the largeish file descriptor leak fix,
and the regression fix for multiple-instance chips is pretty important
too.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit
This patchset adds support to msm8996 pcie controller. I tested this patch on
v4.9-rc2 along with phy driver patch [1] and
"PCI: designware: check for iATU unroll support after initializing host"
fix [2] on DB820c APQ8096 board on port B and port C using sata and
ethernet controller.
Changes
On Thu, Nov 03, 2016 at 04:35:33PM -0200, Marcelo Ricardo Leitner wrote:
> On Thu, Nov 03, 2016 at 07:02:47PM +0100, Andrey Konovalov wrote:
> > On Thu, Nov 3, 2016 at 6:52 PM, Marcelo Ricardo Leitner
> > wrote:
> > > On Thu, Nov 03, 2016 at 06:11:01PM +0100, Andrey
On Thu, Nov 03, 2016 at 04:35:33PM -0200, Marcelo Ricardo Leitner wrote:
> On Thu, Nov 03, 2016 at 07:02:47PM +0100, Andrey Konovalov wrote:
> > On Thu, Nov 3, 2016 at 6:52 PM, Marcelo Ricardo Leitner
> > wrote:
> > > On Thu, Nov 03, 2016 at 06:11:01PM +0100, Andrey Konovalov wrote:
> > >> On
This patchset adds support to msm8996 pcie controller. I tested this patch on
v4.9-rc2 along with phy driver patch [1] and
"PCI: designware: check for iATU unroll support after initializing host"
fix [2] on DB820c APQ8096 board on port B and port C using sata and
ethernet controller.
Changes
This patch adds support to msm8996/apq8096 pcie, MSM8996 supports
Gen 1/2, One lane, 3 pcie root-complex with support to MSI and
legacy interrupts and it conforms to PCI Express Base 2.1 specification.
This patch adds post_init callback to qcom_pcie_ops, as this is pcie
pipe clocks are only setup
This patch adds support to msm8996/apq8096 pcie, MSM8996 supports
Gen 1/2, One lane, 3 pcie root-complex with support to MSI and
legacy interrupts and it conforms to PCI Express Base 2.1 specification.
This patch adds post_init callback to qcom_pcie_ops, as this is pcie
pipe clocks are only setup
On Fri, Nov 04, 2016 at 08:40:47PM +0900, Norbert Preining wrote:
> Dear all,
>
> since 4.9-rc series started I see heavy redraw problems on i915. Starting
> or resizing for example the digikam window messes up completely the content.
>
> I have seen this at least since rc2 (I often wait till
On Fri, Nov 04, 2016 at 08:40:47PM +0900, Norbert Preining wrote:
> Dear all,
>
> since 4.9-rc series started I see heavy redraw problems on i915. Starting
> or resizing for example the digikam window messes up completely the content.
>
> I have seen this at least since rc2 (I often wait till
As suggested by Documentation/CodingStyle right before section 3.1: Spaces,
use braces on all branches of a conditional statement if they are used on
any branch. No functional changes.
Signed-off-by: Christopher Covington
---
fs/proc/array.c | 3 ++-
1 file changed, 2
As suggested by Documentation/CodingStyle right before section 3.1: Spaces,
use braces on all branches of a conditional statement if they are used on
any branch. No functional changes.
Signed-off-by: Christopher Covington
---
fs/proc/array.c | 3 ++-
1 file changed, 2 insertions(+), 1
On Tue, 1 Nov 2016, Guenter Roeck wrote:
> > > Some toolchains fail to build mips images with the following build error.
> > >
> > > arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32'
> > >
> > > This is seen, for example, with the 'mipsel-linux-gnu-gcc (Debian 6.1.1-9)
On Tue, 1 Nov 2016, Guenter Roeck wrote:
> > > Some toolchains fail to build mips images with the following build error.
> > >
> > > arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32'
> > >
> > > This is seen, for example, with the 'mipsel-linux-gnu-gcc (Debian 6.1.1-9)
Make alignment and tab usage consistent across file. No functional changes.
Signed-off-by: Christopher Covington
---
include/uapi/linux/auxvec.h | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/include/uapi/linux/auxvec.h
Make alignment and tab usage consistent across file. No functional changes.
Signed-off-by: Christopher Covington
---
include/uapi/linux/auxvec.h | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/include/uapi/linux/auxvec.h b/include/uapi/linux/auxvec.h
index
Hi Russell,
2016-11-04 21:23 GMT+09:00 Russell King - ARM Linux :
> On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro Yamada wrote:
>> Documentation/CodingStyle recommends to use label names which say
>> what the goto does or why the goto exists.
>>
>> Just in case, split
Hi Russell,
2016-11-04 21:23 GMT+09:00 Russell King - ARM Linux :
> On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro Yamada wrote:
>> Documentation/CodingStyle recommends to use label names which say
>> what the goto does or why the goto exists.
>>
>> Just in case, split it up into three labels
On Thu, Nov 03, 2016 at 08:38:44PM +0200, Laurent Pinchart wrote:
Hi Chris,
On Thursday 03 Nov 2016 10:47:03 Chris Mason wrote:
On Thu, Nov 03, 2016 at 06:06:35PM +0200, Laurent Pinchart wrote:
> On Thursday 03 Nov 2016 11:39:51 Steven Rostedt wrote:
>> The TAB elections are now complete.
On Thu, Nov 03, 2016 at 08:38:44PM +0200, Laurent Pinchart wrote:
Hi Chris,
On Thursday 03 Nov 2016 10:47:03 Chris Mason wrote:
On Thu, Nov 03, 2016 at 06:06:35PM +0200, Laurent Pinchart wrote:
> On Thursday 03 Nov 2016 11:39:51 Steven Rostedt wrote:
>> The TAB elections are now complete.
Hi Chris,
On mer., oct. 26 2016, Chris Packham wrote:
> The actual frequency was updated in commit ae142bd99765 ("ARM: mvebu:
> Fix the main PLL frequency on Armada 375, 38x and 39x SoCs") but the
> comment was not updated. Update it now.
>
> Signed-off-by:
Hi Chris,
On mer., oct. 26 2016, Chris Packham wrote:
> The actual frequency was updated in commit ae142bd99765 ("ARM: mvebu:
> Fix the main PLL frequency on Armada 375, 38x and 39x SoCs") but the
> comment was not updated. Update it now.
>
> Signed-off-by: Chris Packham
Applied on mvebu/dt
On Fri, Nov 04, 2016 at 01:16:14PM +0100, Fabian Mewes wrote:
> Add Qualcomm QCA tagging introduced in cafdc45c9 to the
> list of supported protocols.
>
> Signed-off-by: Fabian Mewes
Thanks
Reviewed-by: Andrew Lunn
Andrew
On Fri, Nov 04, 2016 at 01:16:14PM +0100, Fabian Mewes wrote:
> Add Qualcomm QCA tagging introduced in cafdc45c9 to the
> list of supported protocols.
>
> Signed-off-by: Fabian Mewes
Thanks
Reviewed-by: Andrew Lunn
Andrew
Hi Hans,
On Friday, 4 November 2016 13:11:34 GMT Hans de Goede wrote:
> Hi All,
>
> While booting 4.9-rc# for the first time on an Allwinner A33 tablet,
> I noticed that after u-boot the LCD display stayed black. It turns out
> that there was an issue which caused X to never get up, and all
Hi Hans,
On Friday, 4 November 2016 13:11:34 GMT Hans de Goede wrote:
> Hi All,
>
> While booting 4.9-rc# for the first time on an Allwinner A33 tablet,
> I noticed that after u-boot the LCD display stayed black. It turns out
> that there was an issue which caused X to never get up, and all
On Tue, Nov 1, 2016 at 4:57 PM, Andrey Smirnov wrote:
> None of the OF match table entries contain any compatiblity strings that
> could not be matched against using i2c_device_id table above and
> of_modalias_node. Besides that entries in OF match table do not cary
>
On Tue, Nov 1, 2016 at 4:57 PM, Andrey Smirnov wrote:
> None of the OF match table entries contain any compatiblity strings that
> could not be matched against using i2c_device_id table above and
> of_modalias_node. Besides that entries in OF match table do not cary
> proper device variant
Add Qualcomm QCA tagging introduced in cafdc45c9 to the
list of supported protocols.
Signed-off-by: Fabian Mewes
---
Documentation/networking/dsa/dsa.txt |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/networking/dsa/dsa.txt
Add Qualcomm QCA tagging introduced in cafdc45c9 to the
list of supported protocols.
Signed-off-by: Fabian Mewes
---
Documentation/networking/dsa/dsa.txt |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/networking/dsa/dsa.txt
On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro Yamada wrote:
> Documentation/CodingStyle recommends to use label names which say
> what the goto does or why the goto exists.
>
> Just in case, split it up into three labels because the CodingStyle
> says "one err bugs" is a common type of bug
On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro Yamada wrote:
> Documentation/CodingStyle recommends to use label names which say
> what the goto does or why the goto exists.
>
> Just in case, split it up into three labels because the CodingStyle
> says "one err bugs" is a common type of bug
On 11/03/2016 01:47 PM, Sebastian Andrzej Siewior wrote:
On 2016-11-02 18:47:49 [-0400], Charles (Chas) Williams wrote:
I don't this this is a race. Here is some debugging from the two CPU VM
(2 sockets, 1 core per socket). In identify_cpu() we have:
/* The boot/hotplug time
On 11/03/2016 01:47 PM, Sebastian Andrzej Siewior wrote:
On 2016-11-02 18:47:49 [-0400], Charles (Chas) Williams wrote:
I don't this this is a race. Here is some debugging from the two CPU VM
(2 sockets, 1 core per socket). In identify_cpu() we have:
/* The boot/hotplug time
601 - 700 of 996 matches
Mail list logo