* Borislav Petkov wrote:
> On Sat, Nov 12, 2016 at 12:06:49PM +0100, Ingo Molnar wrote:
> > Note that on recent kernels, with printk log timestamping enabled, this
> > looks
> > like:
> >
> > [ 206.721243] CR2: CR3: 00042ab75000 CR4:
> >
* Borislav Petkov wrote:
> On Sat, Nov 12, 2016 at 12:06:49PM +0100, Ingo Molnar wrote:
> > Note that on recent kernels, with printk log timestamping enabled, this
> > looks
> > like:
> >
> > [ 206.721243] CR2: CR3: 00042ab75000 CR4:
> > 001406e0
> > [
> > I suppose it could be, since family IDs are allocated in a 16-bit
> > range
> > anyway. But family IDs can also never actually be negative, so
> > having
> > an unsigned int in the struct makes sense too.
>
> All idr_* API's accept int, rather than unsigned int. This is my
> point.
Sure,
> > I suppose it could be, since family IDs are allocated in a 16-bit
> > range
> > anyway. But family IDs can also never actually be negative, so
> > having
> > an unsigned int in the struct makes sense too.
>
> All idr_* API's accept int, rather than unsigned int. This is my
> point.
Sure,
From: Noam Camus
Change log
---
V4 --> V5
Apply several comments made by Daneil Lezcano:
1) Add __init attribute to nps_get_timer_clk()
2) Fix return value of nps_get_timer_clk()
when failing to get clk rate
3) Change clocksource rate from 301 -> 300
V3 --> V4
Main changes
From: Noam Camus
Change log
---
V4 --> V5
Apply several comments made by Daneil Lezcano:
1) Add __init attribute to nps_get_timer_clk()
2) Fix return value of nps_get_timer_clk()
when failing to get clk rate
3) Change clocksource rate from 301 -> 300
V3 --> V4
Main changes are [Thanks for the
Hi Heiko, Jacob:
On 2016年11月13日 05:44, Heiko Stübner wrote:
Hi Jacob,
Am Sonntag, 13. November 2016, 01:41:21 schrieb 陈豪:
2016-11-03 20:34 GMT+08:00 Andy Yan :
Add basic support for rk1108 soc
Signed-off-by: Andy Yan
---
Hi Heiko, Jacob:
On 2016年11月13日 05:44, Heiko Stübner wrote:
Hi Jacob,
Am Sonntag, 13. November 2016, 01:41:21 schrieb 陈豪:
2016-11-03 20:34 GMT+08:00 Andy Yan :
Add basic support for rk1108 soc
Signed-off-by: Andy Yan
---
drivers/pinctrl/pinctrl-rockchip.c | 27
* Matt Fleming wrote:
> From: Ard Biesheuvel
>
> Invoke the EFI_RNG_PROTOCOL protocol in the context of the stub and
> install the Linux-specific RNG seed UEFI config table. This will be
> picked up by the EFI routines in the core kernel to
* Matt Fleming wrote:
> From: Ard Biesheuvel
>
> Invoke the EFI_RNG_PROTOCOL protocol in the context of the stub and
> install the Linux-specific RNG seed UEFI config table. This will be
> picked up by the EFI routines in the core kernel to seed the kernel
> entropy pool.
>
> Cc: Matt
Hi Lino,
[auto build test WARNING on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Lino-Sanfilippo/net-ethernet-slicoss-add-slicoss-gigabit-ethernet-driver/20161113-125131
config: alpha-allyesconfig (attached as .config)
compiler: alpha-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1
Hi Lino,
[auto build test WARNING on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Lino-Sanfilippo/net-ethernet-slicoss-add-slicoss-gigabit-ethernet-driver/20161113-125131
config: alpha-allyesconfig (attached as .config)
compiler: alpha-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1
On Sat, Nov 12, 2016 at 11:39 AM, Pali Rohár wrote:
> On Saturday 12 November 2016 20:15:45 Dmitry Torokhov wrote:
>> BYD automatic protocol detection is extremely unreliable and is often
>> triggers false positives on regular mice, Sentelic touchpads, and
>> other devices.
On Sat, Nov 12, 2016 at 11:39 AM, Pali Rohár wrote:
> On Saturday 12 November 2016 20:15:45 Dmitry Torokhov wrote:
>> BYD automatic protocol detection is extremely unreliable and is often
>> triggers false positives on regular mice, Sentelic touchpads, and
>> other devices. BYD has several
Hi Andrew,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: c60f169202c7643991a8b4bfeea60e06843d5b5a
arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h
Hi Andrew,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: c60f169202c7643991a8b4bfeea60e06843d5b5a
arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h
ti,charge-delay will be deprecated as it represents number of
clock cycles and the DT entries are done in assumption of 3MHz
TSCADC clock, but clock can be set upto 24MHz. So driver add
support for ti,charge-delay-ns and do not drop support for
ti,charge-delay to support old dtbs and it will be
ti,charge-delay will be deprecated as it represents number of
clock cycles and the DT entries are done in assumption of 3MHz
TSCADC clock, but clock can be set upto 24MHz. So driver add
support for ti,charge-delay-ns and do not drop support for
ti,charge-delay to support old dtbs and it will be
On Sat, Nov 12, 2016 at 1:37 PM, Johannes Berg
wrote:
> On Thu, 2016-11-10 at 09:11 -0800, Cong Wang wrote:
>> On Thu, Nov 10, 2016 at 7:57 AM, Colin King > > wrote:
>> >
>> > From: Colin Ian King
>> >
>> >
On Sat, Nov 12, 2016 at 1:37 PM, Johannes Berg
wrote:
> On Thu, 2016-11-10 at 09:11 -0800, Cong Wang wrote:
>> On Thu, Nov 10, 2016 at 7:57 AM, Colin King > > wrote:
>> >
>> > From: Colin Ian King
>> >
>> > family->id is unsigned, so the less than zero check for
>> > failure return from
Hi Joerg,
Thanks for your reviewing and great comments!
On 11/10/16 at 12:48pm, Joerg Roedel wrote:
> On Thu, Oct 20, 2016 at 07:37:18PM +0800, Baoquan He wrote:
> > prot = dir2prot(direction);
> > + if (translation_pre_enabled(iommu) && !dev_data->domain_updated) {
> > +
Hi Joerg,
Thanks for your reviewing and great comments!
On 11/10/16 at 12:48pm, Joerg Roedel wrote:
> On Thu, Oct 20, 2016 at 07:37:18PM +0800, Baoquan He wrote:
> > prot = dir2prot(direction);
> > + if (translation_pre_enabled(iommu) && !dev_data->domain_updated) {
> > +
On 11/10/16 at 12:52pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> thanks for working on this, really appreciated!
>
> On Thu, Oct 20, 2016 at 07:37:11PM +0800, Baoquan He wrote:
> > This is v6 post.
> >
> > The principle of the fix is similar to intel iommu. Just defer the
> > assignment
> > of
On 11/10/16 at 12:52pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> thanks for working on this, really appreciated!
>
> On Thu, Oct 20, 2016 at 07:37:11PM +0800, Baoquan He wrote:
> > This is v6 post.
> >
> > The principle of the fix is similar to intel iommu. Just defer the
> > assignment
> > of
In-flight DMA from 1st kernel could continue going in kdump kernel.
New io-page table has been created before bnx2 does reset at open stage.
We have to wait for the in-flight DMA to complete to avoid it look up
into the newly created io-page table at probe stage.
Suggested-by: Michael Chan
In-flight DMA from 1st kernel could continue going in kdump kernel.
New io-page table has been created before bnx2 does reset at open stage.
We have to wait for the in-flight DMA to complete to avoid it look up
into the newly created io-page table at probe stage.
Suggested-by: Michael Chan
This is v2 post.
In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
firmware requesting code was moved from open stage to probe stage.
The reason is in kdump kernel hardware iommu need device be reset in
driver probe stage, otherwise those in-flight DMA from 1st kernel
will
This reverts commit 3e1be7ad2d38c6bd6aeef96df9bd0a7822f4e51c.
When people build bnx2 driver into kernel, it will fail to detect
and load firmware because firmware is contained in initramfs and
initramfs has not been uncompressed yet during do_initcalls. So
revert commit 3e1be7a and work out a new
This is v2 post.
In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
firmware requesting code was moved from open stage to probe stage.
The reason is in kdump kernel hardware iommu need device be reset in
driver probe stage, otherwise those in-flight DMA from 1st kernel
will
This reverts commit 3e1be7ad2d38c6bd6aeef96df9bd0a7822f4e51c.
When people build bnx2 driver into kernel, it will fail to detect
and load firmware because firmware is contained in initramfs and
initramfs has not been uncompressed yet during do_initcalls. So
revert commit 3e1be7a and work out a new
On 11/12/16 at 11:40pm, David Miller wrote:
> From: Baoquan He
> Date: Sun, 13 Nov 2016 12:15:24 +0800
>
> > In-flight DMA from 1st kernel could continue going in kdump kernel.
> > New io-page table has been created before bnx2 does reset at open stage.
> > We have to wait for
On 11/12/16 at 11:40pm, David Miller wrote:
> From: Baoquan He
> Date: Sun, 13 Nov 2016 12:15:24 +0800
>
> > In-flight DMA from 1st kernel could continue going in kdump kernel.
> > New io-page table has been created before bnx2 does reset at open stage.
> > We have to wait for the in-flight DMA
Add myself as maintainer for the slicoss ethernet driver.
Signed-off-by: Lino Sanfilippo
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6781a3f..bb9af28 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -562,6 +562,11
Add myself as maintainer for the slicoss ethernet driver.
Signed-off-by: Lino Sanfilippo
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6781a3f..bb9af28 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -562,6 +562,11 @@ T: git
Hi,
this is a rework of the slicoss gigabit ethernet driver from Alacritech
that is currently part of the staging area. The driver is supposed to
support Mojave, Oasis and Kalahari cards, for both copper and fiber.
If this code is accepted the staging version can be removed (as Greg
told me
Hi,
this is a rework of the slicoss gigabit ethernet driver from Alacritech
that is currently part of the staging area. The driver is supposed to
support Mojave, Oasis and Kalahari cards, for both copper and fiber.
If this code is accepted the staging version can be removed (as Greg
told me
Add driver for Alacritech gigabit ethernet cards with SLIC (session-layer
interface control) technology. The driver provides basic support without
SLIC for the following devices:
- Mojave cards (single port PCI Gigabit) both copper and fiber
- Oasis cards (single and dual port PCI-x Gigabit)
Add driver for Alacritech gigabit ethernet cards with SLIC (session-layer
interface control) technology. The driver provides basic support without
SLIC for the following devices:
- Mojave cards (single port PCI Gigabit) both copper and fiber
- Oasis cards (single and dual port PCI-x Gigabit)
From: Pablo Neira Ayuso
Date: Thu, 10 Nov 2016 01:31:17 +0100
> I think I cannot help to address this conflict myself.
>
> 8fbfef7f505b is in my nf tree, while 489111e5c25b is in net-next. So
> you will hit this conflict by when you pull net into net-next.
>
> So please
From: Pablo Neira Ayuso
Date: Thu, 10 Nov 2016 01:31:17 +0100
> I think I cannot help to address this conflict myself.
>
> 8fbfef7f505b is in my nf tree, while 489111e5c25b is in net-next. So
> you will hit this conflict by when you pull net into net-next.
>
> So please keep this patch from
From: Baoquan He
Date: Sun, 13 Nov 2016 12:15:24 +0800
> In-flight DMA from 1st kernel could continue going in kdump kernel.
> New io-page table has been created before bnx2 does reset at open stage.
> We have to wait for the in-flight DMA to complete to avoid it look up
> into
From: Baoquan He
Date: Sun, 13 Nov 2016 12:15:24 +0800
> In-flight DMA from 1st kernel could continue going in kdump kernel.
> New io-page table has been created before bnx2 does reset at open stage.
> We have to wait for the in-flight DMA to complete to avoid it look up
> into the newly created
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
> The SoCs part of the sun5i family share the DTs, so we need consistant
> indices in order to still share the DTs.
>
> Signed-off-by: Maxime Ripard
> ---
>
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
> The SoCs part of the sun5i family share the DTs, so we need consistant
> indices in order to still share the DTs.
>
> Signed-off-by: Maxime Ripard
> ---
> include/dt-bindings/clock/sun5i-ccu.h | 126 +++-
>
Hi Dave,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new
lightweight SGL iterators
date: 6
Hi Dave,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new
lightweight SGL iterators
date: 6
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
> Signed-off-by: Maxime Ripard
> ---
> drivers/clk/sunxi-ng/ccu_mult.h | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
> Signed-off-by: Maxime Ripard
> ---
> drivers/clk/sunxi-ng/ccu_mult.h | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/clk/sunxi-ng/ccu_mult.h b/drivers/clk/sunxi-ng/ccu_mult.h
> index
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
> The multipliers we've seen so far all had an offset of one. However, on the
Explaining that the offset refers to the difference between the register value
and the actual multiplier/divider applied to the
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
> The multipliers we've seen so far all had an offset of one. However, on the
Explaining that the offset refers to the difference between the register value
and the actual multiplier/divider applied to the clock rate would be nice.
> earlier
In-flight DMA from 1st kernel could continue going in kdump kernel.
New io-page table has been created before bnx2 does reset at open stage.
We have to wait for the in-flight DMA to complete to avoid it look up
into the newly created io-page table at probe stage.
Suggested-by: Michael Chan
In-flight DMA from 1st kernel could continue going in kdump kernel.
New io-page table has been created before bnx2 does reset at open stage.
We have to wait for the in-flight DMA to complete to avoid it look up
into the newly created io-page table at probe stage.
Suggested-by: Michael Chan
Hi Linus,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on
UM
date: 3 months
Hi Linus,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on
UM
date: 3 months
Hi Michael,
On 11/11/16 at 09:37am, Michael Chan wrote:
> On Fri, Nov 11, 2016 at 6:02 AM, Baoquan He wrote:
> > On 11/11/16 at 09:46pm, Baoquan He wrote:
> >> Hi bnx2 experts,
> >>
> >> In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
> >> firmware
Hi Michael,
On 11/11/16 at 09:37am, Michael Chan wrote:
> On Fri, Nov 11, 2016 at 6:02 AM, Baoquan He wrote:
> > On 11/11/16 at 09:46pm, Baoquan He wrote:
> >> Hi bnx2 experts,
> >>
> >> In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
> >> firmware requesting code was
On Sun, Nov 13, 2016 at 11:48 AM, Chen-Yu Tsai wrote:
> On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
> wrote:
>
> It'd be better if you mentioned what clock needs this.
>
>> Signed-off-by: Maxime Ripard
>> ---
On Sun, Nov 13, 2016 at 11:48 AM, Chen-Yu Tsai wrote:
> On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
> wrote:
>
> It'd be better if you mentioned what clock needs this.
>
>> Signed-off-by: Maxime Ripard
>> ---
>> drivers/clk/sunxi-ng/ccu_nkm.c | 17 ++---
>>
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
It'd be better if you mentioned what clock needs this.
> Signed-off-by: Maxime Ripard
> ---
> drivers/clk/sunxi-ng/ccu_nkm.c | 17 ++---
>
On Wed, Nov 9, 2016 at 1:23 AM, Maxime Ripard
wrote:
It'd be better if you mentioned what clock needs this.
> Signed-off-by: Maxime Ripard
> ---
> drivers/clk/sunxi-ng/ccu_nkm.c | 17 ++---
> drivers/clk/sunxi-ng/ccu_nkm.h | 2 ++
> 2 files changed, 16 insertions(+), 3
+++ AKASHI Takahiro [21/10/16 10:13 +0900]:
The current "rodata=off" parameter disables read-only kernel mappings
under CONFIG_DEBUG_RODATA:
commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter
to disable read-only kernel mappings")
This patch is a logical extension to
+++ AKASHI Takahiro [21/10/16 10:13 +0900]:
The current "rodata=off" parameter disables read-only kernel mappings
under CONFIG_DEBUG_RODATA:
commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter
to disable read-only kernel mappings")
This patch is a logical extension to
Hi James,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of
vdso.lds
date: 5 weeks ago
config:
Hi James,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of
vdso.lds
date: 5 weeks ago
config:
From: Ivan Khoronzhuk
Date: Tue, 8 Nov 2016 15:16:05 +0200
> While create/destroy channel operation memory is not freed. It was
> supposed that memory is freed while driver remove. But a channel
> can be created and destroyed many times while changing number of
>
From: Ivan Khoronzhuk
Date: Tue, 8 Nov 2016 15:16:05 +0200
> While create/destroy channel operation memory is not freed. It was
> supposed that memory is freed while driver remove. But a channel
> can be created and destroyed many times while changing number of
> channels with ethtool.
>
>
From: Kast Bernd
Date: Fri, 4 Nov 2016 00:33:06 +0100
> This patch adds a module parameter in order to activate ASPM. By that
> the CPU can enter deep sleep modes (PC6) and power consumption can be
> reduced (for example from 13W to 8W on my notebook with a Haswell CPU).
>
From: Kast Bernd
Date: Fri, 4 Nov 2016 00:33:06 +0100
> This patch adds a module parameter in order to activate ASPM. By that
> the CPU can enter deep sleep modes (PC6) and power consumption can be
> reduced (for example from 13W to 8W on my notebook with a Haswell CPU).
> Basically, it
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error
with binutils 2.24 and earlier
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error
with binutils 2.24 and earlier
Make spelling correction for "regular"
Signed-off-by: Walt Feasel
---
drivers/staging/dgnc/digi.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/dgnc/digi.h b/drivers/staging/dgnc/digi.h
index 4e36573..bfd80ca 100644
---
Make spelling correction for "regular"
Signed-off-by: Walt Feasel
---
drivers/staging/dgnc/digi.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/dgnc/digi.h b/drivers/staging/dgnc/digi.h
index 4e36573..bfd80ca 100644
--- a/drivers/staging/dgnc/digi.h
+++
Made suggested modifications from checkpatch in reference
to WARNING: waitqueue_active without comment
Signed-off-by: Walt Feasel
---
drivers/staging/dgnc/dgnc_tty.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c
Made suggested modifications from checkpatch in reference
to WARNING: waitqueue_active without comment
Signed-off-by: Walt Feasel
---
drivers/staging/dgnc/dgnc_tty.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
index
Hi Alex,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation
of a VDSO
date: 1 year ago
config:
Hi Alex,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation
of a VDSO
date: 1 year ago
config:
Make block comment format changes to comply with
style guides
Signed-off-by: Walt Feasel
---
drivers/staging/dgnc/dgnc_tty.c | 166
1 file changed, 66 insertions(+), 100 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c
Make block comment format changes to comply with
style guides
Signed-off-by: Walt Feasel
---
drivers/staging/dgnc/dgnc_tty.c | 166
1 file changed, 66 insertions(+), 100 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c
Hi Russell,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: b2c0b2cbb282f0cf42518ffacbe197e6f2884168 nmi: create generic NMI
backtrace implementation
date: 1 year,
Hi Russell,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: b2c0b2cbb282f0cf42518ffacbe197e6f2884168 nmi: create generic NMI
backtrace implementation
date: 1 year,
Make spelling corrections for satisfy and
transitions
Signed-off-by: Walt Feasel
---
v2 resubmitted without behaviour
drivers/staging/dgnc/dgnc_tty.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c
Make spelling corrections for satisfy and
transitions
Signed-off-by: Walt Feasel
---
v2 resubmitted without behaviour
drivers/staging/dgnc/dgnc_tty.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
Hi Hannes,
On Sun, Nov 13, 2016 at 1:51 AM, Hannes Frederic Sowa
wrote:
> You probably need some combination of ipv6_chk_addr and/or
> ipv6_check_addr_and_flags (where dev can also be NULL). Be careful if a
> IFA_HOST or IFA_LINK address switches from one interface to
Hi Hannes,
On Sun, Nov 13, 2016 at 1:51 AM, Hannes Frederic Sowa
wrote:
> You probably need some combination of ipv6_chk_addr and/or
> ipv6_check_addr_and_flags (where dev can also be NULL). Be careful if a
> IFA_HOST or IFA_LINK address switches from one interface to another.
I can confirm
On Sun, Nov 13, 2016, at 01:43, Jason A. Donenfeld wrote:
> On Sat, Nov 12, 2016 at 8:08 PM, Jason A. Donenfeld
> wrote:
> >> Gotcha. I don't see any checks that the saddr is valid similar to what
> >> IPv4 does.
> >>
> >> I think the right place to add a check is in
On Sun, Nov 13, 2016 at 1:43 AM, Jason A. Donenfeld wrote:
> In perusing through the v6 FIB code, I don't even see an analog of
> __ip_dev_find... Hm?
Of all places, the iscsi code actually has a nice side-by-side
comparison. So far as I can see, the other protocols just omit
On Sun, Nov 13, 2016, at 01:43, Jason A. Donenfeld wrote:
> On Sat, Nov 12, 2016 at 8:08 PM, Jason A. Donenfeld
> wrote:
> >> Gotcha. I don't see any checks that the saddr is valid similar to what
> >> IPv4 does.
> >>
> >> I think the right place to add a check is in ip6_dst_lookup_tail():
> >>
On Sun, Nov 13, 2016 at 1:43 AM, Jason A. Donenfeld wrote:
> In perusing through the v6 FIB code, I don't even see an analog of
> __ip_dev_find... Hm?
Of all places, the iscsi code actually has a nice side-by-side
comparison. So far as I can see, the other protocols just omit this
check in the
On Sat, Nov 12, 2016 at 8:08 PM, Jason A. Donenfeld wrote:
>> Gotcha. I don't see any checks that the saddr is valid similar to what IPv4
>> does.
>>
>> I think the right place to add a check is in ip6_dst_lookup_tail():
>> if (!ipv6_addr_any(>saddr)) {
>> // saddr
On Sat, Nov 12, 2016 at 8:08 PM, Jason A. Donenfeld wrote:
>> Gotcha. I don't see any checks that the saddr is valid similar to what IPv4
>> does.
>>
>> I think the right place to add a check is in ip6_dst_lookup_tail():
>> if (!ipv6_addr_any(>saddr)) {
>> // saddr is valid for L3
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove
HAVE_LATENCYTOP_SUPPORT
date: 10 months ago
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove
HAVE_LATENCYTOP_SUPPORT
date: 10 months ago
Hi Pete,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for
Diamond 233L - Rev C processor variant
Hi Pete,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for
Diamond 233L - Rev C processor variant
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: b4214e41b7152b1964a3421a40251d202ae2d2c0 sh: add SMP support for J2
date: 3 months ago
config:
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 86e4ee760ef2f7571e233a3abf065ffd0bb4089d
commit: b4214e41b7152b1964a3421a40251d202ae2d2c0 sh: add SMP support for J2
date: 3 months ago
config:
On 11/12/16 15:53, Walt Feasel wrote:
> Made various spelling corrections in the comments
Make
>
> Signed-off-by: Walt Feasel
> ---
> drivers/staging/dgnc/dgnc_tty.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git
On 11/12/16 15:53, Walt Feasel wrote:
> Made various spelling corrections in the comments
Make
>
> Signed-off-by: Walt Feasel
> ---
> drivers/staging/dgnc/dgnc_tty.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/dgnc/dgnc_tty.c
On Wednesday 09 November 2016 11:54 PM, Rob Herring wrote:
> On Mon, Oct 31, 2016 at 03:45:35PM +0100, Bartosz Golaszewski wrote:
>> Create the driver for the da8xx master peripheral priority
>> configuration and implement support for writing to the three
>> Master Priority registers on da850
On Wednesday 09 November 2016 11:54 PM, Rob Herring wrote:
> On Mon, Oct 31, 2016 at 03:45:35PM +0100, Bartosz Golaszewski wrote:
>> Create the driver for the da8xx master peripheral priority
>> configuration and implement support for writing to the three
>> Master Priority registers on da850
1 - 100 of 604 matches
Mail list logo