Hi Alexandru,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on v4.18-rc6 next-20180724]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Alexandru,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on v4.18-rc6 next-20180724]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Dear Jyothi, Please find attached docs for proceeding transfer. Kindly advise the container and truck details for proceeding. Thanks & Regards, T. FrancisLogistics Manager Gulf Worldwide Distribution FZEMO 0253, PO Box 261619Jebel Ali Free ZoneDUBAI - UAETel: +9714 8814100Fax: +97148814343
Dear Jyothi, Please find attached docs for proceeding transfer. Kindly advise the container and truck details for proceeding. Thanks & Regards, T. FrancisLogistics Manager Gulf Worldwide Distribution FZEMO 0253, PO Box 261619Jebel Ali Free ZoneDUBAI - UAETel: +9714 8814100Fax: +97148814343
Hi friend I am a banker in ADB BANK. I want to transfer an abandoned
$15.5Million to your Bank account. 40/percent will be your share.
For more details contanct me urgently. Yours Mrs. Lisa Banneth.
Hi friend I am a banker in ADB BANK. I want to transfer an abandoned
$15.5Million to your Bank account. 40/percent will be your share.
For more details contanct me urgently. Yours Mrs. Lisa Banneth.
From: Roman Kiryanov
The driver never mutates this variable - no benefits of
keeping it mutable.
Signed-off-by: Roman Kiryanov
---
Changes in v2:
- Replaced "const u32" with "#define".
drivers/tty/goldfish.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
From: Roman Kiryanov
The driver never mutates this variable - no benefits of
keeping it mutable.
Signed-off-by: Roman Kiryanov
---
Changes in v2:
- Replaced "const u32" with "#define".
drivers/tty/goldfish.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
From: Roman Kiryanov
enums produce better compilation errors than defines.
Signed-off-by: Roman Kiryanov
---
Changes in v2:
- Added the enum types (goldfish_tty_reg and goldfish_tty_cmd).
drivers/tty/goldfish.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
From: Roman Kiryanov
checkpatch.pl complained about missing blank lines
(between variable definitions and executable code)
and using just "unsigned" instead of "unsigned int".
Signed-off-by: Roman Kiryanov
---
Changes in v2:
- Updated the commit message.
drivers/tty/goldfish.c | 6 --
1
From: Roman Kiryanov
enums produce better compilation errors than defines.
Signed-off-by: Roman Kiryanov
---
Changes in v2:
- Added the enum types (goldfish_tty_reg and goldfish_tty_cmd).
drivers/tty/goldfish.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
From: Roman Kiryanov
checkpatch.pl complained about missing blank lines
(between variable definitions and executable code)
and using just "unsigned" instead of "unsigned int".
Signed-off-by: Roman Kiryanov
---
Changes in v2:
- Updated the commit message.
drivers/tty/goldfish.c | 6 --
1
> clocks.
> > >
> >
> > This patch causes a regression when running a qemu emulation with
> > arm:integratorcp.
>
> Thank you for the report. I will study it.
>
> >
> > ...
> > Console: colour dummy device 80x30
> > ----[ cut he
> clocks.
> > >
> >
> > This patch causes a regression when running a qemu emulation with
> > arm:integratorcp.
>
> Thank you for the report. I will study it.
>
> >
> > ...
> > Console: colour dummy device 80x30
> > ----[ cut he
On Tue, 2018-07-24 at 14:56 -0700, pher...@codeaurora.org wrote:
> A reminder to review a few patches I had sent last week. Below are the
> links for the patches.
>
> https://lkml.org/lkml/2018/7/5/798
I have no fundamental object to this one, but
the 80 column use is unnecessary and should be
On Tue, 2018-07-24 at 14:56 -0700, pher...@codeaurora.org wrote:
> A reminder to review a few patches I had sent last week. Below are the
> links for the patches.
>
> https://lkml.org/lkml/2018/7/5/798
I have no fundamental object to this one, but
the 80 column use is unnecessary and should be
Hi,
> On Tue, Jul 24, 2018 at 09:11:37AM +0800, jiang.bi...@zte.com.cn wrote:
>
>> >> Signed-off-by: Cheng Lin
>> >> Signed-off-by: Tan Hu
>> >> Signed-off-by: Jiang Biao
>> >
>> >This SoB chain is invalid.
>
>> Mm, we don't quite understand what the *Signed-off-by* precisely means,
>> Does it
Hi,
> On Tue, Jul 24, 2018 at 09:11:37AM +0800, jiang.bi...@zte.com.cn wrote:
>
>> >> Signed-off-by: Cheng Lin
>> >> Signed-off-by: Tan Hu
>> >> Signed-off-by: Jiang Biao
>> >
>> >This SoB chain is invalid.
>
>> Mm, we don't quite understand what the *Signed-off-by* precisely means,
>> Does it
2018-07-12 21:50 GMT+09:00 Ville Syrjala :
> From: Ville Syrjälä
>
> Make it possible to answer "m or y" or "y or m" to
> oldconfig so that scripted kernel builds can easily
> enable new features not present in the existing .config.
>
> The particular use case I have in mind is continuous
2018-07-12 21:50 GMT+09:00 Ville Syrjala :
> From: Ville Syrjälä
>
> Make it possible to answer "m or y" or "y or m" to
> oldconfig so that scripted kernel builds can easily
> enable new features not present in the existing .config.
>
> The particular use case I have in mind is continuous
memmap_init is sometimes a macro sometimes a function based on
__HAVE_ARCH_MEMMAP_INIT. It is only a function on ia64. Make
memmap_init a weak function instead, and let ia64 redefine it.
Signed-off-by: Pavel Tatashin
---
arch/ia64/include/asm/pgtable.h | 1 -
mm/page_alloc.c | 9
memmap_init is sometimes a macro sometimes a function based on
__HAVE_ARCH_MEMMAP_INIT. It is only a function on ia64. Make
memmap_init a weak function instead, and let ia64 redefine it.
Signed-off-by: Pavel Tatashin
---
arch/ia64/include/asm/pgtable.h | 1 -
mm/page_alloc.c | 9
update_defer_init() should be called only when struct page is about to be
initialized. Because it counts number of initialized struct pages, but
there we may skip struct pages if there is some mirrored memory.
So move, update_defer_init() after checking for mirrored memory.
Also, rename
update_defer_init() should be called only when struct page is about to be
initialized. Because it counts number of initialized struct pages, but
there we may skip struct pages if there is some mirrored memory.
So move, update_defer_init() after checking for mirrored memory.
Also, rename
On Wed, 25 Jul 2018, Tetsuo Handa wrote:
> > If exit_mmap() gets preempted indefinitely before it can free any memory,
> > we are better off oom killing another process. The purpose of the timeout
> > is to give an oom victim an amount of time to free its memory and exit
> > before selecting
On Wed, 25 Jul 2018, Tetsuo Handa wrote:
> > If exit_mmap() gets preempted indefinitely before it can free any memory,
> > we are better off oom killing another process. The purpose of the timeout
> > is to give an oom victim an amount of time to free its memory and exit
> > before selecting
On Tue, Jul 24, 2018 at 04:46:34PM -0700, Matthias Kaehlcke wrote:
> There are three thermal stages defined in the PMIC:
>
> stage 1: warning
> stage 2: system should shut down
> stage 3: emergency shut down
>
> By default the PMIC assumes that the OS isn't doing anything and thus
> at stage 2
On Tue, Jul 24, 2018 at 04:46:34PM -0700, Matthias Kaehlcke wrote:
> There are three thermal stages defined in the PMIC:
>
> stage 1: warning
> stage 2: system should shut down
> stage 3: emergency shut down
>
> By default the PMIC assumes that the OS isn't doing anything and thus
> at stage 2
The field 'prev_stage' in struct qpnp_tm_chip is not used, remove it.
Signed-off-by: Matthias Kaehlcke
---
drivers/thermal/qcom-spmi-temp-alarm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/thermal/qcom-spmi-temp-alarm.c
b/drivers/thermal/qcom-spmi-temp-alarm.c
index
The field 'prev_stage' in struct qpnp_tm_chip is not used, remove it.
Signed-off-by: Matthias Kaehlcke
---
drivers/thermal/qcom-spmi-temp-alarm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/thermal/qcom-spmi-temp-alarm.c
b/drivers/thermal/qcom-spmi-temp-alarm.c
index
memmap_init_zone, is getting complex, because it is called from different
contexts: hotplug, and during boot, and also because it must handle some
architecture quirks. One of them is mirroed memory.
Move the code that decides whether to skip mirrored memory outside of
memmap_init_zone, into a
memmap_init_zone, is getting complex, because it is called from different
contexts: hotplug, and during boot, and also because it must handle some
architecture quirks. One of them is mirroed memory.
Move the code that decides whether to skip mirrored memory outside of
memmap_init_zone, into a
Three small patches that improve memmap_init_zone() and also fix a small
deferred pages bug.
The improvements include reducing number of ifdefs and making code more
modular.
The bug is the deferred_init_update() should be called after the mirrored
memory skipping is taken into account.
Pavel
Three small patches that improve memmap_init_zone() and also fix a small
deferred pages bug.
The improvements include reducing number of ifdefs and making code more
modular.
The bug is the deferred_init_update() should be called after the mirrored
memory skipping is taken into account.
Pavel
The documentation claims that the 'reg' property consists of two values,
the SPMI address and the length of the controller's registers. However
the SPMI bus to which it is added specifies "#size-cells = <0>;". Remove
the controller register length from the documentation of the field and the
The documentation claims that the 'reg' property consists of two values,
the SPMI address and the length of the controller's registers. However
the SPMI bus to which it is added specifies "#size-cells = <0>;". Remove
the controller register length from the documentation of the field and the
The current example for a thermal zone isn't very useful as reference
since it would result in a hardware shutdown at 145°C, instead of
allowing the system to try to shutdown gracefully. Without an ADC
channel a maximum of two trip points is useful in practice for this
sensor, with temperatures
The current example for a thermal zone isn't very useful as reference
since it would result in a hardware shutdown at 145°C, instead of
allowing the system to try to shutdown gracefully. Without an ADC
channel a maximum of two trip points is useful in practice for this
sensor, with temperatures
There are three thermal stages defined in the PMIC:
stage 1: warning
stage 2: system should shut down
stage 3: emergency shut down
By default the PMIC assumes that the OS isn't doing anything and thus
at stage 2 it does a partial PMIC shutdown and at stage 3 it kills
all power. When switching
This adds the spmi-temp-alarm node to pm8998 based on the examples in the
bindings.
Signed-off-by: Matthias Kaehlcke
Reviewed-by: Douglas Anderson
---
Changes in v5:
- added tag 'Reviewed-by: Douglas Anderson '
Changes in v4:
- none
Changes in v3:
- changed node name from
There are three thermal stages defined in the PMIC:
stage 1: warning
stage 2: system should shut down
stage 3: emergency shut down
By default the PMIC assumes that the OS isn't doing anything and thus
at stage 2 it does a partial PMIC shutdown and at stage 3 it kills
all power. When switching
This adds the spmi-temp-alarm node to pm8998 based on the examples in the
bindings.
Signed-off-by: Matthias Kaehlcke
Reviewed-by: Douglas Anderson
---
Changes in v5:
- added tag 'Reviewed-by: Douglas Anderson '
Changes in v4:
- none
Changes in v3:
- changed node name from
The thermal zone uses spmi-temp-alarm as sensor, the trip points
correspond to the PMIC thermal stages 1 and 2. The critical trip
point at 125°C disables the partial PMIC shutdown at stage 2.
Without an IIO input the sensor only reports a limited number of
temperatures:
- 37°C for temperatures
The thermal zone uses spmi-temp-alarm as sensor, the trip points
correspond to the PMIC thermal stages 1 and 2. The critical trip
point at 125°C disables the partial PMIC shutdown at stage 2.
Without an IIO input the sensor only reports a limited number of
temperatures:
- 37°C for temperatures
On Sat, 21 Jul 2018 11:31:27 -0700 Davidlohr Bueso wrote:
> On Sat, 21 Jul 2018, Peter Zijlstra wrote:
>
> >On Sat, Jul 21, 2018 at 10:21:20AM -0700, Davidlohr Bueso wrote:
> >> On Fri, 20 Jul 2018, Andrew Morton wrote:
> >>
> >> > We could open-code it locally. Add a couple of
> >> >
On Sat, 21 Jul 2018 11:31:27 -0700 Davidlohr Bueso wrote:
> On Sat, 21 Jul 2018, Peter Zijlstra wrote:
>
> >On Sat, Jul 21, 2018 at 10:21:20AM -0700, Davidlohr Bueso wrote:
> >> On Fri, 20 Jul 2018, Andrew Morton wrote:
> >>
> >> > We could open-code it locally. Add a couple of
> >> >
On Sat, Jul 21, 2018 at 01:06:26PM +0200, Paul Cercueil wrote:
> The driver is now compatible with four SoCs: JZ4780, JZ4770, JZ4725B and
> JZ4740.
What the driver supports is irrelevant to the binding.
>
> Besides, it now expects the devicetree to supply a second memory
> resource. This resource
On Sat, Jul 21, 2018 at 01:06:26PM +0200, Paul Cercueil wrote:
> The driver is now compatible with four SoCs: JZ4780, JZ4770, JZ4725B and
> JZ4740.
What the driver supports is irrelevant to the binding.
>
> Besides, it now expects the devicetree to supply a second memory
> resource. This resource
On Thu, Jul 12, 2018 at 09:12:43PM +, Yixun Lan wrote:
> Document the MMC sub clock controller driver, the potential consumer
> of this driver is MMC or NAND. Also add three clock bindings IDs which
> provided by this driver.
>
> Signed-off-by: Yixun Lan
> ---
>
On Thu, Jul 12, 2018 at 09:12:43PM +, Yixun Lan wrote:
> Document the MMC sub clock controller driver, the potential consumer
> of this driver is MMC or NAND. Also add three clock bindings IDs which
> provided by this driver.
>
> Signed-off-by: Yixun Lan
> ---
>
On Tue, Jul 24, 2018 at 11:31:22AM +, Denis OSTERLAND wrote:
> From: Denis Osterland
>
> The devicetree documentation for the ISL1219 device tree
> binding is added with an short example. It is not a trivial
> device, because it supports two interrupt sources.
>
> Signed-off-by: Denis
On Tue, Jul 24, 2018 at 11:31:22AM +, Denis OSTERLAND wrote:
> From: Denis Osterland
>
> The devicetree documentation for the ISL1219 device tree
> binding is added with an short example. It is not a trivial
> device, because it supports two interrupt sources.
>
> Signed-off-by: Denis
On Tue, 24 Jul 2018 17:30:08 -0400
Steven Rostedt wrote:
> I don't see where ->reg() would return anything but 1 on success. Maybe
> I'm missing something. I'll look some more, but I'm thinking of changing
> ->reg() to return zero on all success, and negative on all errors and
> just check
On Tue, 24 Jul 2018 17:30:08 -0400
Steven Rostedt wrote:
> I don't see where ->reg() would return anything but 1 on success. Maybe
> I'm missing something. I'll look some more, but I'm thinking of changing
> ->reg() to return zero on all success, and negative on all errors and
> just check
Dirk Gouders reported that two consecutive "make" invocations on an
already compiled tree will show alternating behaviors:
$ make
CALLscripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
DATAREL arch/x86/boot/compressed/vmlinux
Kernel: arch/x86/boot/bzImage is
Dirk Gouders reported that two consecutive "make" invocations on an
already compiled tree will show alternating behaviors:
$ make
CALLscripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
DATAREL arch/x86/boot/compressed/vmlinux
Kernel: arch/x86/boot/bzImage is
On 2018/07/25 7:51, David Rientjes wrote:
> On Wed, 25 Jul 2018, Tetsuo Handa wrote:
>
You might worry about situations where __oom_reap_task_mm() is a no-op.
But that is not always true. There is no point with emitting
pr_info("oom_reaper: unable to reap pid:%d (%s)\n",
On 2018/07/25 7:51, David Rientjes wrote:
> On Wed, 25 Jul 2018, Tetsuo Handa wrote:
>
You might worry about situations where __oom_reap_task_mm() is a no-op.
But that is not always true. There is no point with emitting
pr_info("oom_reaper: unable to reap pid:%d (%s)\n",
On Wed, 25 Jul 2018, Tetsuo Handa wrote:
> >> You might worry about situations where __oom_reap_task_mm() is a no-op.
> >> But that is not always true. There is no point with emitting
> >>
> >> pr_info("oom_reaper: unable to reap pid:%d (%s)\n", ...);
> >> debug_show_all_locks();
> >>
> >>
On Wed, 25 Jul 2018, Tetsuo Handa wrote:
> >> You might worry about situations where __oom_reap_task_mm() is a no-op.
> >> But that is not always true. There is no point with emitting
> >>
> >> pr_info("oom_reaper: unable to reap pid:%d (%s)\n", ...);
> >> debug_show_all_locks();
> >>
> >>
Currently cgroup-v1's memcg_stat_show traverses the memcg tree ~17 times
to collect the stats while cgroup-v2's memory_stat_show traverses the
memcg tree thrice. On a large machine, a couple thousand memcgs is very
normal and if the churn is high and memcgs stick around during to
several reasons,
Currently cgroup-v1's memcg_stat_show traverses the memcg tree ~17 times
to collect the stats while cgroup-v2's memory_stat_show traverses the
memcg tree thrice. On a large machine, a couple thousand memcgs is very
normal and if the churn is high and memcgs stick around during to
several reasons,
Hello,
Previously patches were sent with wrong cover format, please ignore.
I am sending four patches which trying to resolve TODO list requirements
no 45 about octeon-usb.
There are SPDX licence additions on c and header files.
Checkpatch warnings are resolved,also a notice about
On Tue, 24 Jul 2018 15:07:18 -0700
Kees Cook wrote:
> Adding Steven (maintainer) and Al (fs) to CC...
Thanks, first I've seen of this.
>
> On Tue, Jul 24, 2018 at 1:02 PM, Zubin Mithra wrote:
> > tracefs_ops is initialized inside tracefs_create_instance_dir and not
> > modified after.
On Tue, 24 Jul 2018 15:07:18 -0700
Kees Cook wrote:
> Adding Steven (maintainer) and Al (fs) to CC...
Thanks, first I've seen of this.
>
> On Tue, Jul 24, 2018 at 1:02 PM, Zubin Mithra wrote:
> > tracefs_ops is initialized inside tracefs_create_instance_dir and not
> > modified after.
Hello,
Previously patches were sent with wrong cover format, please ignore.
I am sending four patches which trying to resolve TODO list requirements
no 45 about octeon-usb.
There are SPDX licence additions on c and header files.
Checkpatch warnings are resolved,also a notice about
Changes coding style and encapsulate into parentheses timeout_usec.
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 44 +
1 file changed, 23 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
b/drivers/staging/octeon-usb/octeon-hcd.c
index cded30f145aa..cff5e790b196 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.c
Changes coding style and encapsulate into parentheses timeout_usec.
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 44 +
1 file changed, 23 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
b/drivers/staging/octeon-usb/octeon-hcd.c
index cded30f145aa..cff5e790b196 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.c
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.h
b/drivers/staging/octeon-usb/octeon-hcd.h
index 3353aefe662e..769c36cf6614 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.h
This patch resolves the warnings as its refereed to TODO list.
There are also a code style issues that could be resolved via breaking
down cvmx_usb_poll_channel().
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 10 ++
1 file changed, 6 insertions(+), 4
This patch resolves the warnings as its refereed to TODO list.
There are also a code style issues that could be resolved via breaking
down cvmx_usb_poll_channel().
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 10 ++
1 file changed, 6 insertions(+), 4
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.h
b/drivers/staging/octeon-usb/octeon-hcd.h
index 3353aefe662e..769c36cf6614 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.h
On Mon, 4 Jun 2018 22:47:27 +0530 Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
>
On Mon, 4 Jun 2018 22:47:27 +0530 Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
>
On 2018/07/25 6:45, David Rientjes wrote:
> On Sat, 21 Jul 2018, Tetsuo Handa wrote:
>
>> You can't apply "[patch v4] mm, oom: fix unnecessary killing of additional
>> processes"
>> because Michal's patch which removes oom_lock serialization was added to -mm
>> tree.
>>
>
> I've rebased the
On 2018/07/25 6:45, David Rientjes wrote:
> On Sat, 21 Jul 2018, Tetsuo Handa wrote:
>
>> You can't apply "[patch v4] mm, oom: fix unnecessary killing of additional
>> processes"
>> because Michal's patch which removes oom_lock serialization was added to -mm
>> tree.
>>
>
> I've rebased the
Changes coding style and encapsulate into parentheses timeout_usec.
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 44 +
1 file changed, 23 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
Hi Stephen,
2018-07-25 0:01 GMT+02:00 Stephen Rothwell :
> Hi all,
>
> Commit
>
> b6fbc2f6a686 ("GFS2: Fix recovery issues for spectators")
>
> is missing a Signed-off-by from its committer. It was rebased.
thanks, I've fixed it now but this is getting rather annoying -- and
it must happen to
Changes coding style and encapsulate into parentheses timeout_usec.
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 44 +
1 file changed, 23 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
Hi Stephen,
2018-07-25 0:01 GMT+02:00 Stephen Rothwell :
> Hi all,
>
> Commit
>
> b6fbc2f6a686 ("GFS2: Fix recovery issues for spectators")
>
> is missing a Signed-off-by from its committer. It was rebased.
thanks, I've fixed it now but this is getting rather annoying -- and
it must happen to
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.h
b/drivers/staging/octeon-usb/octeon-hcd.h
index 3353aefe662e..769c36cf6614 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.h
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.h
b/drivers/staging/octeon-usb/octeon-hcd.h
index 3353aefe662e..769c36cf6614 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.h
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
b/drivers/staging/octeon-usb/octeon-hcd.c
index cded30f145aa..cff5e790b196 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.c
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.h
b/drivers/staging/octeon-usb/octeon-hcd.h
index 3353aefe662e..769c36cf6614 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.h
This patch resolves the warnings as its refereed to TODO list.
There are also a code style issues that could be resolved via breaking
down cvmx_usb_poll_channel().
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 10 ++
1 file changed, 6 insertions(+), 4
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
b/drivers/staging/octeon-usb/octeon-hcd.c
index cded30f145aa..cff5e790b196 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.c
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/octeon-usb/octeon-hcd.h
b/drivers/staging/octeon-usb/octeon-hcd.h
index 3353aefe662e..769c36cf6614 100644
--- a/drivers/staging/octeon-usb/octeon-hcd.h
This patch resolves the warnings as its refereed to TODO list.
There are also a code style issues that could be resolved via breaking
down cvmx_usb_poll_channel().
Signed-off-by: Georgios Tsotsos
---
drivers/staging/octeon-usb/octeon-hcd.c | 10 ++
1 file changed, 6 insertions(+), 4
Date: Wed, 25 Jul 2018 01:18:58 +0300
Subject: [PATCH 0/4] Staging: octeon-usb: Fixes and Coding style applied.
Hello,
I am sending four patches which trying to resolve TODO list requirements
no 45 about octeon-usb.
There are SPDX licence additions on c and header files.
Checkpatch warnings
Date: Wed, 25 Jul 2018 01:18:58 +0300
Subject: [PATCH 0/4] Staging: octeon-usb: Fixes and Coding style applied.
Hello,
I am sending four patches which trying to resolve TODO list requirements
no 45 about octeon-usb.
There are SPDX licence additions on c and header files.
Checkpatch warnings
Am 22.07.2018 um 23:19 schrieb Andreas Färber:
> From: Ian Pozella
>
> The mmc block in Pistachio allows 1 to 8 data bits to be used.
> Marduk uses 4 bits allowing the upper 4 bits to be allocated
> to the Mikrobus ports. However these bits are still connected
> internally meaning the mmc block
Am 22.07.2018 um 23:19 schrieb Andreas Färber:
> From: Ian Pozella
>
> The mmc block in Pistachio allows 1 to 8 data bits to be used.
> Marduk uses 4 bits allowing the upper 4 bits to be allocated
> to the Mikrobus ports. However these bits are still connected
> internally meaning the mmc block
I would like to speak with the person that managing photos for your
company?
We provide image editing like – photos cutting out and retouching.
Enhancing your images is just a part of what we can do for your business.
Whether you’re an ecommerce
store or portrait photographer, real estate
I would like to speak with the person that managing photos for your
company?
We provide image editing like – photos cutting out and retouching.
Enhancing your images is just a part of what we can do for your business.
Whether you’re an ecommerce
store or portrait photographer, real estate
On Wed, 2018-07-18 at 18:26 -0400, Calvin Walton wrote:
> Based on the documentation provided in AMD's Open-Source
> Register Reference For AMD Family 17h Processors:
> https://support.amd.com/TechDocs/56255_OSRR.pdf
>
> I've added support for reading Cores and Package energy usage from
> AMD's
>
On Wed, 2018-07-18 at 18:26 -0400, Calvin Walton wrote:
> Based on the documentation provided in AMD's Open-Source
> Register Reference For AMD Family 17h Processors:
> https://support.amd.com/TechDocs/56255_OSRR.pdf
>
> I've added support for reading Cores and Package energy usage from
> AMD's
>
Adding Steven (maintainer) and Al (fs) to CC...
On Tue, Jul 24, 2018 at 1:02 PM, Zubin Mithra wrote:
> tracefs_ops is initialized inside tracefs_create_instance_dir and not
> modified after. tracefs_create_instance_dir allows for initialization
> only once, and is called from
Adding Steven (maintainer) and Al (fs) to CC...
On Tue, Jul 24, 2018 at 1:02 PM, Zubin Mithra wrote:
> tracefs_ops is initialized inside tracefs_create_instance_dir and not
> modified after. tracefs_create_instance_dir allows for initialization
> only once, and is called from
201 - 300 of 1482 matches
Mail list logo
