Hi Srinivas,
I have 3 questions about the nvmem sybsystem.
Please correct me if something is missing from my thought.
(Q1) How to allocate struct nvmem_config?
I see 3 ways in allocating struct nvmem_config.
What is a good / bad practice?
(A) Allocate statically in .data section
On Fri, Sep 08, 2017 at 05:46:24PM +0900, Byungchul Park wrote:
> To peter,
>
> Does it work?
>
> Chagnes from v1
> - Add a completion initialization function with a lockdep map
> - Enhance readability of the workqueue code
Do not you like it becasue it introduces another
On 08/09/17 22:48, Krishna Reddy wrote:
> SDHCI controllers on Tegra186 support 40 bit addressing.
> IOVA addresses are 48-bit wide on Tegra186.
> SDHCI host common code sets dma mask as either 32-bit or 64-bit.
> To avoid access issues when SMMU is enabled, disable 64-bit dma.
>
> Signed-off-by:
On Fri, Sep 08, 2017 at 01:59:00PM -0700, h...@zytor.com wrote:
> On September 8, 2017 2:45:10 AM PDT, Gary Lin wrote:
> >On Thu, Sep 07, 2017 at 02:16:21PM -0700, h...@zytor.com wrote:
> >> On September 7, 2017 2:44:51 AM PDT, Gary Lin wrote:
> >> >On Thu, Jun 01,
On 10/09/17 5:48 PM, "Christos Gkekas" wrote:
>Pointers bnx2i_cmd are set but never used, so they can be removed.
>
>Signed-off-by: Christos Gkekas
>---
> drivers/scsi/bnx2i/bnx2i_hwi.c | 10 --
> 1 file changed, 10 deletions(-)
>
>diff
* Andy Lutomirski wrote:
> On Fri, Sep 8, 2017 at 12:59 AM, Jiri Kosina wrote:
> > On Thu, 7 Sep 2017, Andy Lutomirski wrote:
> >
> >> Jiri reported a resume-from-hibernation failure triggered by PCID.
> >> The root cause appears to be rather odd. The
On Sun, Sep 10, 2017 at 8:49 PM, Gabriel C wrote:
>
> Yes 81f95076281f is to blame.. After reverting it all is fine again.
>
> 15 resume cycles on the one laptop , 10 on the other without to hit the
> trace.
Yeah, I think that disable/enable_firmware in the suspend/resume
Hi Linus,
>> Yes 81f95076281f is to blame.. After reverting it all is fine again.
>>
>> 15 resume cycles on the one laptop , 10 on the other without to hit the
>> trace.
>
> Yeah, I think that disable/enable_firmware in the suspend/resume path
> is basically just completely random code. There
On Fri, 2017-09-08 at 18:38 -0400, Theodore Ts'o wrote:
> On Fri, Sep 08, 2017 at 02:48:51PM +1000, James Morris wrote:
> >
> > Mimi and Christoph worked together on this over several iterations -- I'll
> > let them respond.
>
> Mimi --- we should chat next week in LA. I've been working on a
>
Since:
commit c5a94a618e7ac86b20f53d947f68d7cee6a4c6bc
Author: Peter Zijlstra
Date: Wed Aug 23 13:58:44 2017 +0200
workqueue: Use TASK_IDLE
all worker threads are in D state. They all show up when using "magic
SysRq w". In htop they all have big fat red 'D' in
This patchset primarily adds Broadcom FlexRM reset module for
VFIO platform driver.
The patches are based on Linux-4.13-rc3 and can also be
found at flexrm-vfio-v8 branch of
https://github.com/Broadcom/arm64-linux.git
Changes since v8:
- Add missing "ring_num++" in
This patch adds Broadcom FlexRM low-level reset for
VFIO platform.
It will do the following:
1. Disable/Deactivate each FlexRM ring
2. Flush each FlexRM ring
The cleanup sequence for FlexRM rings is adapted from
Broadcom FlexRM mailbox driver.
Signed-off-by: Anup Patel
From: Stephen Hemminger
This extends existing vmbus related sysfs structure to provide per-channel
state information. This is useful when diagnosing issues with multiple
queues in networking and storage.
The existing sysfs only displayed information about the primary
On 2017-09-09 21:56, Harinath Nampally wrote:
> This driver supports multiple devices like mma8653,
> mma8652, mma8452, mma8453 and fxls8471. Almost all
> these devices have more than one event.
>
> Current driver design hardcodes the event specific
> information, so only one
Lockdep is needed for proving the spinlocks and rwlocks work fine on our
platform. It also requires calling the trace_hardirqs_off() and
trace_hardirqs_on() pair of routines when entering and exiting an
interrupt.
For OpenRISC the interrupt stack frame does not support frame pointers,
so to call
For lockdep support a reliable stack trace mechanism is needed. This
patch adds support in OpenRISC for the stacktrace framework, implemented
by a simple unwinder api. The unwinder api supports both framepointer
and basic stack tracing.
The unwinder is now used to replace the stack_dump()
In case timers are not in sync when cpus start (i.e. hot plug / offset
resets) we need to synchronize the secondary cpus internal timer with
the main cpu. This is needed as in OpenRISC SMP there is only one
clocksource registered which reads from the same ttcr register on each
cpu.
This
Currently we do a spin on secondary cpus when waiting to boot. This
theoretically causes issues with power consumption and does cause issues
with qemu cycle burning (it starves cpu 0 from actually being able to
boot.)
This change puts each secondary cpu to sleep if they have a power
management
From: Jan Henrik Weinstock
On OpenRISC the icache does not snoop data stores. This can cause
aliasing as reported by Jan. This patch fixes the issue to ensure icache
is properly synchronized when code is written to memory. It supports both
SMP and UP flushing.
OpenRISC only supports hardware instructions that perform 4 byte atomic
operations. For enabling qrwlocks for upcoming SMP support 1 and 2 byte
implementations are needed. To do this we leverage the 4 byte atomic
operations and shift/mask the 1 and 2 byte areas as needed.
This heavily borrows
During SMP testing we were getting the below warning after booting the
secondary cpu:
[0.06] BUG: scheduling while atomic: swapper/1/0/0x
This change follows similar patterns from other architectures to start
the schduler with preempt disabled.
Signed-off-by: Stafford Horne
void foo(int a)
switch (a) {
case 'h':
fun1();
exit(1);
default:
}
creates a warning
Possible switch case/default not preceded by break
or fallthrough comment
exit( should be treated like return.
Signed-off-by: Heinrich Schuchardt
Logging without newlines are still prone to interleaving.
Add newlines where necessary.
Miscellanea:
o Coalesce formats
o Realign arguments
o Fix a couple misindented lines with the above logging changes
Signed-off-by: Joe Perches
---
drivers/staging/ccree/ssi_aead.c
From: Stefan Kristiansson
This patch introduces the SMP support for the OpenRISC architecture.
The SMP architecture requires cores which have multicore features which
have been introduced a few years back including:
- New SPRS SPR_COREID SPR_NUMCORES
-
Enable OpenRISC to use qspinlocks and qrwlocks for upcoming SMP support.
Signed-off-by: Stafford Horne
---
arch/openrisc/Kconfig | 2 ++
arch/openrisc/include/asm/Kbuild | 4
arch/openrisc/include/asm/spinlock.h | 12 +++-
From: Stefan Kristiansson
IPI driver for the Open Multi-Processor Interrupt Controller (ompic) as
described in the Multicore support section of the OpenRISC 1.2
proposed architecture specification:
From: Stefan Kristiansson
Previously, the area between 0x0-0x100 have been used as a "scratch"
memory area to temporarily store regs during exception entry. In a
multi-core environment, this will not work.
This change is to use shadow registers for nested
While working on SMP for OpenRISC I found this is needed for qrwlocks to
work correctly. OpenRISC is big endian so this should have been here
already.
Signed-off-by: Stafford Horne
---
arch/openrisc/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git
Hello Again,
This series adds SMP support for OpenRISC. The OpenRISC multicore platform
and SMP linux support is based on the work that Stefan Kristiansson did
around 2012 implemented in Verilog and run on FPGAs. I have been working
to upstream this work. I have additionally tested this on
From: Stefan Kristiansson
Simple enough to be compatible with simulation environments,
such as verilated systems, QEMU and other targets supporting OpenRISC
SMP. This also supports our base FPGA SoC's if the cpu frequency is
upped to 50Mhz.
Signed-off-by:
Add OpenRISC.io to vendor prefixes. This is reserved for softcores
developed by the OpenRISC community. The OpenRISC community has
separated from OpenCores.org requiring a new prefix.
Signed-off-by: Stafford Horne
---
Changes since v1
- New patch
On 09/11/2017, 05:11 AM, Jibin Xu wrote:
...
> --- a/drivers/tty/sysrq.c
> +++ b/drivers/tty/sysrq.c
> @@ -245,8 +245,10 @@ static void sysrq_handle_showallcpus(int key)
>* architecture has no support for it:
>*/
> if (!trigger_all_cpu_backtrace()) {
> - struct
From: Stephen Hemminger
When investigating performance, it is useful to be able to look at
the number of host and guest events per-channel. This is equivalent
to per-device interrupt statistics.
Signed-off-by: Stephen Hemminger
Signed-off-by:
From: Dexuan Cui
Due to commit 54a66265d675 ("Drivers: hv: vmbus: Fix rescind handling"),
we need this patch to resolve the below deadlock:
after we get the mutex in vmbus_hvsock_device_unregister() and call
vmbus_device_unregister() -> device_unregister() -> ... ->
From: Olaf Hering
Till recently the expected length of bytes read by the
daemon did depend on the context. It was either hv_start_fcopy or
hv_do_fcopy. The daemon had a buffer size of two pages, which was much
larger than needed.
Now the expected length of bytes read by the
From: Dexuan Cui
hv_sock driver is automatically loaded when an application creates an
AF_VSOCK socket, so we don't really need to trigger uevents to the user
space udevd.
And hv_sock devices can appear and disappear frequency, e.g. 100 per
second, so triggering the
On Thu, 2017-09-07 at 11:19 -0700, Linus Torvalds wrote:
> On Mon, Sep 4, 2017 at 3:29 AM, James Morris wrote:
> >
> > IMA:
> > - A new integrity_read file operation method, avoids races when
> > calculating file hashes
>
> Honestly, this seems really odd.
>
> It
Dear Linux folks,
With Linux built from commit 4dfc2788033d (Merge tag
'iommu-updates-v4.14' of
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu), I get the
warning below on a Lenovo X60t with a 32-bit CPU.
```
$ dmesg
[0.00] Linux version 4.13.0+ (root@d44d03a193d6) (gcc
On Sun, 10 Sep 2017 08:36:43 +0200
Martin Kepplinger wrote:
> On 2017-09-09 21:56, Harinath Nampally wrote:
> > This driver supports multiple devices like mma8653,
> > mma8652, mma8452, mma8453 and fxls8471. Almost all
> > these devices have more than one event.
>
I've been staring at the word PCID too long.
Fixes: f13c8e8c58ba ("x86/mm: Reinitialize TLB state on hotplug and resume")
Reported-by: Dan Carpenter
Signed-off-by: Andy Lutomirski
---
arch/x86/mm/tlb.c | 2 +-
1 file changed, 1 insertion(+), 1
Hi folks,
I'm getting lots of warnings from dtc about unit address format errors:
For example in imx6q.dtsi:
ocram: sram@0090 {
The node name's address part has leading zeros which dtc doesn't like.
It doesn't seem to have a big influence (yet ?), but I'd guess this
warning is there
On Sun, Sep 10, 2017 at 03:57:21AM +0100, Al Viro wrote:
> On Sat, Sep 09, 2017 at 09:07:56PM -0400, Dave Jones wrote:
>
> > With this in place, I'm still seeing -EBUSY from
> > invalidate_inode_pages2_range
> > which doesn't end well...
>
> Different issue, and I'm not sure why that
Am 10.09.2017 um 17:17 schrieb Guenter Roeck:
> On 09/04/2017 04:16 PM, Andreas Färber wrote:
>> Add a watchdog driver for the Realtek RTD1295 SoC.
>>
>> Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_watchdog.c code and
>> mach-rtk119x/driver/dc2vo/fpga/include/iso_reg.h register defines.
>>
>>
From: Randy Dunlap
Fix kernel-doc warning ('*' in Sphinx doc means "emphasis"):
../kernel/sched/fair.c:7584: WARNING: Inline emphasis start-string without
end-string.
Signed-off-by: Randy Dunlap
---
kernel/sched/fair.c |2 +-
1 file changed,
Use spaces around most binary operators
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
Space required after ','
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
Remove space between function name and open parenthesis '('
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
Follow linux-kernel code style for conditional statements
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 63 +
1 file changed, 19 insertions(+), 44 deletions(-)
diff --git
On Sun, 10 Sep 2017 09:21:11 -0700, Dmitry Torokhov wrote:
> On Sun, Sep 10, 2017 at 12:03:38AM +0200, Jakub Kicinski wrote:
> > On Sat, 09 Sep 2017 13:59:25 -0700, Dmitry Torokhov wrote:
> > > On September 9, 2017 1:17:26 PM PDT, Jakub Kicinski
> > > wrote:
> > > >On Sat, 9
Return value of request_module() does not handled,
so it is possible to use shorter try_then_request_module().
Signed-off-by: Ivan Safonov
---
.../staging/rtl8192u/ieee80211/ieee80211_softmac.c | 27 +++---
drivers/staging/rtl8192u/ieee80211/ieee80211_wx.c
On Wed, 6 Sep 2017 18:16:33 +0200
Fabrice Gasnier wrote:
> On 09/06/2017 02:56 PM, Arnd Bergmann wrote:
> > The ADC driver can trigger on either the timer or the lptim
> > trigger, but it only uses a Kconfig 'select' statement
> > to ensure that the first of the two is
On Sun, Sep 10, 2017 at 12:03:38AM +0200, Jakub Kicinski wrote:
> On Sat, 09 Sep 2017 13:59:25 -0700, Dmitry Torokhov wrote:
> > On September 9, 2017 1:17:26 PM PDT, Jakub Kicinski wrote:
> > >On Sat, 9 Sep 2017 12:55:51 -0700, Dmitry Torokhov wrote:
> > >> On Sat, Sep 9, 2017
> Alright, I didn't test it but I kind of like it now. The one minor
> naming issue I had pointed out before is mentioned below. But if that's
> no issue for Jon:
> Reviewed-by: Martin Kepplinger
Martin, Thanks a lot for the review.
> btw, Harianath: Would you point me to the
No spaces at the start of a line
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
Use spaces between concatenated strings
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 50 ++---
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
Remove space before ';', '++', ','
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel wrote:
> Dear Linux folks,
>
>
> With Linux built from commit 4dfc2788033d (Merge tag 'iommu-updates-v4.14'
> of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu), I get the
> warning below on a Lenovo X60t with a 32-bit
Blank lines aren't necessary after an open brace and before a close brace
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
On September 10, 2017 11:00:10 AM PDT, Jakub Kicinski wrote:
>On Sun, 10 Sep 2017 09:21:11 -0700, Dmitry Torokhov wrote:
>> On Sun, Sep 10, 2017 at 12:03:38AM +0200, Jakub Kicinski wrote:
>> > On Sat, 09 Sep 2017 13:59:25 -0700, Dmitry Torokhov wrote:
>> > > On September 9, 2017
On Sun, Sep 10, 2017 at 1:06 PM, Enrico Weigelt, metux IT consult
wrote:
> Hi folks,
>
>
> I'm getting lots of warnings from dtc about unit address format errors:
>
> For example in imx6q.dtsi:
>
> ocram: sram@0090 {
>
> The node name's address part has leading zeros which
> I stripped the version change stuff from the commit message - they
> should have been below the --- Useful during review, but generally
> not worth retaining once we have accepted it.
I didn't know that, thanks for letting me know.
Next time I will keep that in mind.
Thanks,
Hari
On Sun, Sep
Current design will lose recovery process when check_curseg_offset is OK.
Signed-off-by: Yunlong Song
---
fsck/fsck.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index cb341ba..56a47be 100644
--- a/fsck/fsck.c
On Sun, Sep 10, 2017 at 6:58 AM, Masahiro Yamada
wrote:
>
> "is_reserved_word()" sounds like a boolean function
> that returns 1 or 0.
> Maybe, the choice of the function name was not nice.
Yeah, not great name. That's the old name, though - I didn't change
that
loop-AES changes since previous release:
- Worked around kernel interface changes on 4.13 kernels.
- Added second util-linux patch to work around gpg 2 pinentry-mode bug.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.7l.tar.bz2
md5sum
Hi,
On Sun, Sep 10, 2017 at 6:40 AM, kernel test robot
wrote:
>
> Greeting,
>
> FYI, we noticed a -11.3% regression of netperf.Throughput_tps due to commit:
>
>
> commit: 6d46bd3d970382b83554b56a34f231d5d1dd ("sched/fair: Improve the
> behavior of sync flag")
> url:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4dfc2788033d30dfccfd4268e06dd73ce2c654ed
commit: 39358a033b2e4432052265c1fa0f36f572d8cfb5 objtool, x86: Add facility for
asm code to provide unwind hints
date: 8 weeks ago
config:
On Sun, 2017-09-10 at 17:46 +0200, Heinrich Schuchardt wrote:
> void foo(int a)
> switch (a) {
> case 'h':
> fun1();
> exit(1);
> default:
> }
>
> creates a warning
> Possible switch case/default not preceded by break
> or fallthrough comment
>
>
On Sat, 2017-09-09 at 18:04 +0900, Stafford Horne wrote:
> Currently running checkpatch on a directory with a cover-letter.patch
> file reports the following error:
>
> -
> patches/smp-v2/v2--cover-letter.patch
>
Hi,
xtensa:allmodconfig fails to build in mainline with compiler errors
as follows.
drivers/staging/rtl8723bs/core/rtw_ap.c: In function ‘expire_timeout_chk’:
drivers/staging/rtl8723bs/core/rtw_ap.c:442:1: internal compiler error:
in change_address_1, at emit-rtl.c:2126
On Mon, 4 Sep 2017 23:06:37 -0400
harinath Nampally wrote:
> > I agree with your understanding. It's a rising threshold, just that the
> > input
> > will only reflect high frequency changes in the signal.
> Thank you for the clarification. I am hoping this gets merged
stm32_spi_prepare_mbr() is returning an error value when div is less
than SPI_MBR_DIV_MIN *and* greater than SPI_MBR_DIV_MAX, which always
evaluates to false. This should change to use *or*.
Signed-off-by: Christos Gkekas
---
drivers/spi/spi-stm32.c | 4 ++--
1 file
Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron :
>On Mon, 4 Sep 2017 23:06:37 -0400
>harinath Nampally wrote:
>
>> > I agree with your understanding. It's a rising threshold, just
>that the input
>> > will only reflect high frequency
Hi Linus,
2017-09-09 6:38 GMT+09:00 Linus Torvalds :
> On Fri, Sep 8, 2017 at 11:39 AM, Linus Torvalds
> wrote:
>>
>> Strange. Does anybody see what the pattern to the failure is?
>
> Found it. Stupid special case for 'typeof()' that
On 09/09/2017 02:47 PM, Ben Hutchings wrote:
This is the start of the stable review cycle for the 3.16.48 release.
There are 233 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10.09.2017 11:09, mtx wrote:
it tries to open the initial console, before even attempt to mount the > root fs, which obviously is doomed to fail. (directly passing root=>
via cmdline - no initrd etc)
Solved it. For the record: the uart2 node was still disabled, so the
kernel did allocate a
Use one space around (on each side of) '=' operator
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
On 09/04/2017 04:16 PM, Andreas Färber wrote:
Add a binding for the Realtek RTD1295 watchdog.
Acked-by: Rob Herring
Signed-off-by: Andreas Färber
Reviewed-by: Guenter Roeck
---
v1 -> v2: Unchanged
On 09/04/2017 04:16 PM, Andreas Färber wrote:
Add a watchdog driver for the Realtek RTD1295 SoC.
Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_watchdog.c code and
mach-rtk119x/driver/dc2vo/fpga/include/iso_reg.h register defines.
Signed-off-by: Andreas Färber
On 09/04/2017 04:16 PM, Andreas Färber wrote:
Add the watchdog node to the RTD1295 Device Tree.
Acked-by: Rob Herring
Signed-off-by: Andreas Färber
Acked-by: Guenter Roeck
---
Depends on the pending clock nodes patch.
v1 ->
Use one space around most binary operators
Signed-off-by: Harsha Sharma
---
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
An off-by-one error in loop terminantion conditions in
create_setup_data_nodes will lead to memory leak when
create_setup_data_node return error.
Signed-off-by: Sean Fu
---
arch/x86/kernel/ksysfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
void foo(int a)
switch (a) {
case 'h':
fun1();
exit(1);
default:
}
creates a warning
Possible switch case/default not preceded by break
or fallthrough comment
exit( should be treated like return.
Signed-off-by: Heinrich Schuchardt
On Sun, Sep 10, 2017 at 12:55 PM, Geert Uytterhoeven
wrote:
55e285a upstream.
>
>> --- a/include/linux/string.h
>> +++ b/include/linux/string.h
>> @@ -187,4 +187,204 @@ static inline const char *kbasename(const char *path)
>> return tail ? tail + 1 : path;
>> }
>>
FYI, we noticed the following commit:
commit: 74cc41d3b6a99fa2caa4e4edc82efea4d13b8d55 ("x86/asm/64: Remove all
remaining direct thread_struct::sp0 reads")
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git
x86/entry_consolidation
in testcase: trinity
with following parameters:
On 09/09/2017 02:47 PM, Ben Hutchings wrote:
This is the start of the stable review cycle for the 3.2.93 release.
There are 106 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4dfc2788033d30dfccfd4268e06dd73ce2c654ed
commit: 841c950d67c6facde32a8644ced20c04aebb7dd8 i40e/i40evf: use cmpxchg64
when updating private flags in ethtool
date: 2 weeks ago
config: parisc-allmodconfig
On Thu, 31 Aug 2017 01:17:15 +0700
s.abhi...@gmail.com wrote:
> From: Abhisit Sangjan
>
> TI LMP92001 Analog System Monitor and Controller
>
> 8-bit GPIOs.
> 12 DACs with 12-bit resolution.
>
> The GPIOs and DACs are shared port function with Cy function pin to
> take
On Thu, 31 Aug 2017 01:25:28 +0700
s.abhi...@gmail.com wrote:
> From: Abhisit Sangjan
>
> TI LMP92001 Analog System Monitor and Controller
>
> 8-bit GPIOs.
> 12 DACs with 12-bit resolution.
>
> The GPIOs and DACs are shared port function with Cy function pin to
> take
On Sat, Sep 09, 2017 at 09:54:42AM -0700, Guenter Roeck wrote:
> On 09/08/2017 12:13 PM, Greg Kroah-Hartman wrote:
> > On Fri, Sep 08, 2017 at 10:29:52AM -0700, Badhri Jagan Sridharan wrote:
> > > On Fri, Sep 8, 2017 at 2:45 AM, Greg Kroah-Hartman
> > > wrote:
> > > >
On Fri, Sep 08, 2017 at 11:18:08PM +0530, Harsha Sharma wrote:
> Hello,
> I have tried to follow above given instructions but please correct me if I am
> wrong somewhere.
What "above given instructions"?
And please fix your email client to not send html email, it is getting
rejected by the
On Tue, 5 Sep 2017 14:16:42 +0200
Lars-Peter Clausen wrote:
> On 09/05/2017 02:14 PM, Dragos Bogdan wrote:
> > Since most of the SD ADCs have the option of reseting the serial
> > interface by sending a number of SCLKs with CS = 0 and DIN = 1,
> > a dedicated function that can
On Tue, 5 Sep 2017 14:17:21 +0200
Lars-Peter Clausen wrote:
> On 09/05/2017 02:16 PM, Dragos Bogdan wrote:
> > The serial interface can be reset by writing 32 consecutive 1s to the
> > device.
> > 'ret' was initialized correctly but its value was overwritten when
> >
On Sun, 10 Sep 2017 16:00:35 +0200
Martin Kepplinger wrote:
> Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron
> :
> >On Mon, 4 Sep 2017 23:06:37 -0400
> >harinath Nampally wrote:
> >
> >> > I agree with your
On Sun, 10 Sep 2017 14:45:01 +0200
Martin Kepplinger wrote:
> struct data is defined and declared locally. Initiliazation has to be done
> manually, so let's add that.
>
> Signed-off-by: Martin Kepplinger
> ---
>
> This is more of a question actually! Did
-support/20170910-143930
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
for-next/core
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests
On Sun, 2017-09-10 at 01:10 -0700, Christoph Hellwig wrote:
> On Fri, Sep 08, 2017 at 10:25:53AM -0700, Linus Torvalds wrote:
> > I don't think anybody actually tests linux-next kernels in any big
> > way, and the automated tests that do get run probably don't run with
> > any integrity checking
Hi Sam,
2017-09-09 15:39 GMT+09:00 Sam Ravnborg :
> On Fri, Sep 08, 2017 at 02:38:23PM -0700, Linus Torvalds wrote:
>> On Fri, Sep 8, 2017 at 11:39 AM, Linus Torvalds
>> wrote:
>> >
>> > Strange. Does anybody see what the pattern to the failure
On Sun, 2017-09-10 at 09:52 +0200, Heinrich Schuchardt wrote:
> void foo(int a)
> switch (a) {
> case 'h':
> fun1();
> exit(1);
> default:
> }
>
> creates a warning
> Possible switch case/default not preceded by break
> or fallthrough comment
>
>
On Thu, 31 Aug 2017 01:14:09 +0700
s.abhi...@gmail.com wrote:
> From: Abhisit Sangjan
>
> TI LMP92001 Analog System Monitor and Controller
>
> 8-bit GPIOs.
> 12 DACs with 12-bit resolution.
>
> The GPIOs and DACs are shared port function with Cy function pin to
> take
FYI, we noticed the following commit:
commit: 266c175b9b3242f472f0ae5260a97cf62747a1d1 ("ACPI / CPPC: Make cppc acpi
driver aware of pcc subspace ids")
url:
https://github.com/0day-ci/linux/commits/George-Cherian/mailbox-PCC-Move-the-MAX_PCC_SUBSPACES-definition-to-header-file/20170908-060133
1 - 100 of 526 matches
Mail list logo