Hi Mark,
OK, I will do it now
On Tue, Sep 05, 2017 at 10:28:38AM +0800, chengjian c00427203 wrote:
Convert pr_warning to standard pr_warn in arch/arm64/kernel/smp.c
Signed-off-by: Cheng Jian
---
arch/arm64/kernel/smp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Is this a
The newly added SMB2+ attribute support causes unused function
warnings when CONFIG_CIFS_XATTR is disabled:
fs/cifs/smb2ops.c:563:1: error: 'smb2_set_ea' defined but not used
[-Werror=unused-function]
smb2_set_ea(const unsigned int xid, struct cifs_tcon *tcon,
fs/cifs/smb2ops.c:513:1: error: 'sm
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive HID subsystem updates queued for 4.14 merge window.
=
- Wacom driver fixes/updates (device name generation improvements,
touch ring status support) from Jason Gerecke
- T100 touchpad
Hi Greg,
On 5 September 2017 at 12:41, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.9.48 release.
> There are 18 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
From: Changbin Du
If it is a MMIO request, it should be handled by slow path. This patch
actually fixed below warning when mmu debug is enabled.
WARNING: CPU: 5 PID: 2282 at arch/x86/kvm/mmu.c:226 fast_page_fault+0x41b/0x520
CPU: 5 PID: 2282 Comm: qemu-system-x86 Not tainted 4.13.0-rc6+ #34
task
On Tue, Sep 05, 2017 at 05:57:27PM +0900, Byungchul Park wrote:
> On Tue, Sep 05, 2017 at 09:19:30AM +0200, Peter Zijlstra wrote:
> > On Tue, Sep 05, 2017 at 09:08:25AM +0200, Peter Zijlstra wrote:
> > > So you worry about max_active==1 ? Or you worry about pool->lock or
> > > about the thread setu
On Mon, 04 Sep 2017 08:48:36 -0700, Joe Perches wrote:
> On Mon, 2017-09-04 at 10:08 +0200, Jean Delvare wrote:
> > Drop the header and numbering of types. This format was confusing as
> > it suggested one could pass the number instead of the type name,
> > however it did not actually work, and num
On Tue, 05 Sep 2017 10:53:41 +0200,
Lee Jones wrote:
>
> On Tue, 05 Sep 2017, Takashi Iwai wrote:
>
> > On Tue, 05 Sep 2017 10:10:49 +0200,
> > Lee Jones wrote:
> > >
> > > On Tue, 05 Sep 2017, Takashi Iwai wrote:
> > >
> > > > On Tue, 05 Sep 2017 09:24:51 +0200,
> > > > Lee Jones wrote:
> > >
On Tue, Sep 05, 2017 at 12:51:35AM -0700, Stephane Eranian wrote:
> >> Esp the cgroup stuff is entirely untested since I simply don't know how
> >> to operate that. I did run Vince's tests on it, and I think it doesn't
> >> regress, but I'm near a migraine so I can't really see straight atm.
> >>
>
On Wed 2017-08-30 11:47:03, Sergey Senozhatsky wrote:
> On (08/29/17 19:31), Joe Perches wrote:
> [..]
> > > the idea is not to do printk() on that seq buffer at all, but to
> > > log_store(), atomically, seq buffer messages
> > >
> > > spin_lock(&logbuf_lock)
> > > while (offset < seq_buffer-
Hi Mauro,
On Mon, Sep 04, 2017 at 05:41:27PM -0300, Mauro Carvalho Chehab wrote:
> From: Sakari Ailus
>
> There appears to be an issue in using \small in certain cases on Sphinx
> 1.4 and 1.5. Other format documents don't use \small either, remove it
> from here as well.
>
> [mche...@s-opensour
From: Naresh Kamboju
The test script works when kernel source and build module test_bpf.ko
present on the machine. This patch will check if module is present in
the path.
Signed-off-by: Naresh Kamboju
---
tools/testing/selftests/bpf/test_kmod.sh | 8 +---
1 file changed, 5 insertions(+), 3
From: Naresh Kamboju
on ARM and ARM64 devices kernel source tree is not available so
insmod "$SRC_TREE/lib/test_bpf.ko" is not working.
on these target devices the test_bpf.ko is installed under
/lib/modules/`uname -r`/kernel/lib/
so use modprobe dry run to check for missing test_bpf.ko module a
On 2017.09.05 at 10:53 +0200, Peter Zijlstra wrote:
> On Tue, Sep 05, 2017 at 09:27:38AM +0200, Markus Trippelsdorf wrote:
> > Current mainline git (24e700e291d52bd2) hangs when building software
> > concurrently (for example perf).
> > The issue is not 100% reproducible (sometimes building perf su
On (09/05/17 11:44), Petr Mladek wrote:
[..]
> > Tetsuo wants this, for instance,
> > for OOM reports and backtraces. SCIS/ATA people want it as well.
>
> The mixing of related lines might cause problems. But I am not sure
> if it can be fixed a safe way on the printk side. Especially I am
> afrai
Hi Sudeep,
I am not sure what the patch does is correct when having a big endian
kernel dealing with scmi_shared_mem. Unless there is a reason not to
have SCMI with big endian kernel, please see remarks below.
On 04/08/17 15:31, Sudeep Holla wrote:
The SCMI is intended to allow OSPM to manag
Hi,
On 04-09-17 09:31, Heikki Krogerus wrote:
Hi,
On Fri, Sep 01, 2017 at 11:48:38PM +0200, Hans de Goede wrote:
The Intel cherrytrail xhci controller has an extended cap mmio-range
which contains registers to control the muxing to the xhci (host mode)
or the dwc3 (device mode) and vbus-detect
This patch solves the following warning shown by checkpatch script
Warning: msleep < 20ms can sleep for up to 20ms
Signed-off-by: Janani Sankara Babu
---
drivers/staging/rtl8188eu/core/rtw_pwrctrl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/co
On 04.09.2017 18:41, Peter Zijlstra wrote:
> On Mon, Sep 04, 2017 at 05:56:06PM +0300, Alexey Budankov wrote:
>> On 04.09.2017 15:08, Peter Zijlstra wrote:
>>> On Mon, Sep 04, 2017 at 01:46:45PM +0300, Alexey Budankov wrote:
> So the below completely rewrites timekeeping (and probably breaks
>>
On Tue 05-09-17 10:19:13, Thomas Gleixner wrote:
> On Mon, 4 Sep 2017, Michal Hocko wrote:
>
> > Thomas, Johannes,
> > could you double check my thinking here? I will repost the patch to
> > Andrew if you are OK with this.
> > > + /*
> > > + * The only protection from memory hotplug vs. drain_sto
From: Tvrtko Ursulin
Exercise the new __sg_alloc_table_from_pages API (and through
it also the old sg_alloc_table_from_pages), checking that the
created table has the expected number of segments depending on
the sequence of input pages and other conditions.
v2: Move to data driven for readabilit
Hi Julien,
Thanks for reviewing this.
On 05/09/17 11:03, Julien Thierry wrote:
> Hi Sudeep,
>
> I am not sure what the patch does is correct when having a big endian
> kernel dealing with scmi_shared_mem. Unless there is a reason not to
> have SCMI with big endian kernel, please see remarks belo
This patch fixes the WARNING: Prefer using '"%s...", __func__' to using
this function's name, in a string
Signed-off-by: Janani Sankara Babu
---
drivers/staging/rtl8188eu/core/rtw_pwrctrl.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8188eu
On Tue, Sep 5, 2017 at 11:38 AM, Takashi Iwai wrote:
> On Tue, 05 Sep 2017 10:53:41 +0200,
> Lee Jones wrote:
>>
>> On Tue, 05 Sep 2017, Takashi Iwai wrote:
>>
>> > On Tue, 05 Sep 2017 10:10:49 +0200,
>> > Lee Jones wrote:
>> > >
>> > > On Tue, 05 Sep 2017, Takashi Iwai wrote:
>> > >
>> > > > On T
On Tue, Sep 05, 2017 at 11:36:24AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 05, 2017 at 05:57:27PM +0900, Byungchul Park wrote:
> > On Tue, Sep 05, 2017 at 09:19:30AM +0200, Peter Zijlstra wrote:
> > > On Tue, Sep 05, 2017 at 09:08:25AM +0200, Peter Zijlstra wrote:
> > > > So you worry about max_
On Mon, Sep 4, 2017 at 7:01 PM, Randy Dunlap wrote:
> On 09/02/17 23:28, kbuild test robot wrote:
>
> Summary:
>
> GENERIC_CLOCKEVENTS is not enabled. (ia64)
> COMPILE_TEST=y
>
> #
> # Clock Source drivers
> #
> CONFIG_TIMER_OF=y
> CONFIG_CLKSRC_MMIO=y
> # CONFIG_CLKSRC_PISTACHIO is not set
> CON
This patch aims to solve coding style issues by placing constants on the
right side of the test
Signed-off-by: Janani Sankara Babu
---
drivers/staging/rtl8188eu/core/rtw_pwrctrl.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_p
Sorry, messed up. This is not the correct one, will resend. thx.
On Tue, Sep 05, 2017 at 05:29:41PM +0800, changbin...@intel.com wrote:
> From: Changbin Du
>
> If it is a MMIO request, it should be handled by slow path. This patch
> actually fixed below warning when mmu debug is enabled.
>
> WA
From: Changbin Du
If it is a MMIO request, it should be handled by slow path. This patch
actually fixed below warning when mmu debug is enabled.
WARNING: CPU: 5 PID: 2282 at arch/x86/kvm/mmu.c:226 fast_page_fault+0x41b/0x520
CPU: 5 PID: 2282 Comm: qemu-system-x86 Not tainted 4.13.0-rc6+ #34
task
On Tue, 2017-08-29 at 12:54 -0700, Kees Cook wrote:
> On Tue, Aug 29, 2017 at 7:32 AM, Thomas Garnier wrote:
> > On Tue, Aug 22, 2017 at 9:42 AM, Thomas Garnier wrote:
> > > On Mon, Aug 14, 2017 at 2:37 PM, Thomas Garnier
> > > wrote:
> > > >
> > > > Disable the generic address limit check in
When cursor is at beginning of an empty or whitespace-only line and
speakup-r typed, kernel locks up. This happens because deadlock of in
input_event function over dev->event_lock, as demonstrated by lockdep
logs. The reason for that is speakup simulates a down arrow - because
cursor is at an empty
Hi,
This patch fixes kernel lockup shown by lockdep log below. Further
details are in patch header.
Samuel, please note that I removed initialisation of the static int
in_keyboard_notifier to zero as that is not required and reported as
error by checkpatch.
Thanks,
Okash
[ 1293.803242] ===
On 04/09/17 12:41, Masahiro Yamada wrote:
Masahiro Yamada (3):
nvmem: add missing of_node_put() in of_nvmem_cell_get()
nvmem: remove inline in drivers/nvmem/core.c
nvmem: remove unneeded IS_ENABLED(CONFIG_NVMEM) conditional
drivers/nvmem/core.c | 12 ++--
1 file changed, 6
On Tue, Sep 05, 2017 at 07:31:44PM +0900, Byungchul Park wrote:
> Let me show you a possible scenario with a leaf lock:
>
> lock(A)
>lock(A) wait_for_completion(B)
>unlock(A)...
>... unlock(A)
>process_one_work()
>
Hi Peter,
On 04-09-17 13:18, Peter Rosin wrote:
On 2017-09-01 23:48, Hans de Goede wrote:
Hi All,
This series consists of 4 parts:
1) Core mux changes to add support for getting mux-controllers on
non DT platforms and to add some standardised state values for USB
2) Add Intel CHT USB mux
Hi,
On 04-09-17 13:19, Peter Rosin wrote:
Hi!
Some comments inline...
On 2017-09-01 23:48, Hans de Goede wrote:
On non DT platforms we cannot get the mux_chip by pnode. Other subsystems
(regulator, clock, pwm) have the same problem and solve this by allowing
platform / board-setup code to add
On Tue, Sep 05, 2017 at 07:31:44PM +0900, Byungchul Park wrote:
> Recursive-read and the hint I proposed(a.k.a. might) should be used for
> their different specific applications. Both meaning and constraints of
> them are totally different.
>
> Using a right function semantically is more important
Greetings To You,
My Name is Mavis wanczyk , the winner of the Power ball jackpot of $ $758.7
million in the AUGUST 24, 2017, My jackpot was a gift from God to me hence my
Entire family/foundation has AGREED to do this. My foundation is donating
$500,000.00USD to you. please contac maviswanczy
Thomas Gleixner writes:
> On Tue, 5 Sep 2017, Huang, Ying wrote:
>
>> From: Huang Ying
>>
>> When developing code to bootup some APs (Application CPUs)
>> asynchronously, the following kernel panic is encountered. After
>> checking the code, it is found that the irq_to_desc() may return NULL
>
This patch convert pr_warning to standard pr_warn for arm64.
Signed-off-by: Cheng Jian
---
arch/arm64/include/asm/syscall.h | 4 ++--
arch/arm64/kernel/hw_breakpoint.c | 8
arch/arm64/kernel/smp.c | 4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/a
From: Colin Ian King
Don't populate the array syds on the stack, instead make it static const.
Makes the object code smaller by over 280 bytes:
Before:
textdata bss dec hex filename
81451 12784 704 94939 172db cx25840-core.o
textdata bss dec hex
On Tue, 5 Sep 2017, Michal Hocko wrote:
> On Tue 05-09-17 10:19:13, Thomas Gleixner wrote:
> > On Mon, 4 Sep 2017, Michal Hocko wrote:
> >
> > > Thomas, Johannes,
> > > could you double check my thinking here? I will repost the patch to
> > > Andrew if you are OK with this.
> > > > + /*
> >
There's a chapter for the legacy APIs. Move the frontend DVBv3
API to it, and update the chapter's introduction accordingly.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/dvb/frontend.rst| 1 -
Documentation/media/uapi/dvb/legacy_dvb_apis.rst | 21 ++-
Adjust dvb ca.h, dmx.h and frontend.h in order to make
checkpatch happier. Now, it only complains about the typedefs,
and those are there just to provide backward userspace
compatibility.
Signed-off-by: Mauro Carvalho Chehab
---
include/uapi/linux/dvb/ca.h | 2 +-
include/uapi/linux/dvb/dm
Hi Antony,
On Mon, Sep 04, 2017 at 04:26:19PM +0200, Antony Antony wrote:
> On Mon, Sep 04, 2017 at 10:27:32AM +0200, Maxime Ripard wrote:
> > On Fri, Sep 01, 2017 at 12:53:13PM +0200, Antony Antony wrote:
> > > > > +&emac {
> > > > > + pinctrl-names = "default";
> > > > > + pinctrl-0 = <&
On 04/09/17 16:35, Enric Balletbo i Serra wrote:
Dear all,
This patch series is a first RFC to know your opinion about implement
support to create brightness levels tables dinamically. I tried to argue
in every patch the specific reasons we think this can be interesting, to
sumup, the idea behin
With ARM v8.2 RAS Extension, SEA are usually triggered when memory errors
are consumed. In some cases, if the error address is in a clean page or a
read-only page, there is a chance to recover. Such as error occurs in a
instruction page, we can reread this page from disk instead of killing process.
Add a notify chain for process memory section, with
which other modules might do error recovery.
Signed-off-by: Xie XiuQi
Tested-by: Wang Xiongfeng
---
drivers/acpi/apei/ghes.c | 10 ++
include/acpi/ghes.h | 8
2 files changed, 18 insertions(+)
diff --git a/drivers/acpi/
In some platform, when SEA triggerred, physical address might be
reported by memory section, so we save it for error recovery later.
Signed-off-by: Xie XiuQi
Tested-by: Wang Xiongfeng
---
arch/arm64/kernel/ras.c | 31 +++
1 file changed, 31 insertions(+)
diff --git
With ARM v8.2 RAS Extension, SEA are usually triggered when memory errors
are consumed. In some cases, if the error address is in a clean page or a
read-only page, there is a chance to recover. Such as error occurs in a
instruction page, we can reread this page from disk instead of killing process.
On 04/09/17 16:35, Enric Balletbo i Serra wrote:
Brightness is not perceived linearly; rather, it typically follows some
kind of parabolic curve. We can support this by skipping values in the
brightness-levels array in a pseudo-quadratic curve. Typically we used
less than 256 levels, which yields
Avoid this warning:
/devel/v4l/docs/Documentation/media/v4l-drivers/qcom_camss.rst::
WARNING: document isn't included in any toctree
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/v4l-drivers/index.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/media
On Tue, Sep 05, 2017 at 03:12:32PM +0800, Hean-Loong, Ong wrote:
> From: Ong Hean Loong
>
> Driver for Intel FPGA Video and Image Processing Suite Frame Buffer II.
> The driver only supports the Intel Arria10 devkit and its variants.
> This driver can be either loaded staticlly or in modules.
> T
On Tue, Sep 05, 2017 at 09:47:26AM +0200, Arnd Bergmann wrote:
> gcc-8 points out a condition that almost certainly doesn't
> do what the author had in mind:
>
> drivers/gpu/drm/gma500/mdfld_intel_display.c: In function
> 'mdfldWaitForPipeEnable':
> drivers/gpu/drm/gma500/mdfld_intel_display.c:10
Hi Antony,
Almost good, I'm sorry I missed a few things before.
On Mon, Sep 04, 2017 at 04:30:14PM +0200, Antony Antony wrote:
> +&mmc1 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&mmc1_pins_a>;
> + vmmc-supply = <®_vcc3v3>;
> + vqmmc-supply = <®_vcc3v3>;
> + mmc-pwrseq
On 05/09/17 12:05, Daniel Thompson wrote:
On 04/09/17 16:35, Enric Balletbo i Serra wrote:
Dear all,
This patch series is a first RFC to know your opinion about implement
support to create brightness levels tables dinamically. I tried to argue
in every patch the specific reasons we think this c
Hi,
On 04-09-17 13:19, Peter Rosin wrote:
Hi!
Some comments inline...
On 2017-09-01 23:48, Hans de Goede wrote:
Intel Cherrytrail SoCs have an internal USB mux for muxing the otg-port
USB data lines between the xHCI host controller and the dwc3 gadget
controller. On some Cherrytrail systems t
On Tue, Sep 05, 2017 at 11:43:00AM +0300, Mikko Perttunen wrote:
> Hi,
>
> not many changes in v2:
>
> Changed address-cells and size-cells for the Host1x device tree node
> to have value 1, since all subdevices fit in the lower 4G. Also dropped
> the incorrect change about this from the dt-bindi
On 24.08.2017 05:53, Thang Q. Nguyen wrote:
On Sat, Aug 19, 2017 at 10:43 AM, Thang Q. Nguyen wrote:
From: "Thang Q. Nguyen"
For commit 4c39d4b949d3 ("usb: xhci: use bus->sysdev for DMA
configuration"), sysdev points to devices known to the system firmware
or hardware for DMA parameters.
Howe
The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
tags/locks-v4.14-1
for you to fetch changes up to 3953704fde7ec47
On Tue, Sep 05, 2017 at 01:17:39PM +0300, Alexey Budankov wrote:
> However we can't completely get rid of whole tree iterations because of
> inheritance code on forks in perf_event_init_context() here:
Right, fork() / inherit needs to iterate the full thing, nothing to be
done about that.
I'll g
Thanks, this looks good:
Reviewed-by: Christoph Hellwig
Thanks Arnd,
applied.
On Sun, Sep 3, 2017 at 11:47 AM, Gilad Ben-Yossef wrote:
> On Thu, Aug 31, 2017 at 3:31 PM, Harsh Jain wrote:
>> HI Gilad,
>>
>> I think we need an update in ESP also. Now EBUSY return means driver
>> has accepted, Packet should not be dropped in
>>
>> esp_output_tail() function.
>
> Good catch.
On Tue, Sep 05, 2017 at 12:52:36PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 05, 2017 at 07:31:44PM +0900, Byungchul Park wrote:
> > Let me show you a possible scenario with a leaf lock:
> >
> > lock(A)
> >lock(A) wait_for_completion(B)
> >unlock(A)
Hello,
On Tue 05-09-17 11:51:44, Nikolay Borisov wrote:
> I've hit the following problems under memory-heavy workload conditions:
>
> First is a BUG_ON : J_ASSERT(journal_current_handle() == handle);
>
>
> [ 64.261793] kernel BUG at fs/jbd2/transaction.c:1644!
> [
From: Colin Ian King
Don't populate the arrays vcore_val, vpll_val and vaux_val on the
stack, instead make them static const. Makes the object code smaller
by over 370 bytes:
Before:
textdata bss dec hex filename
69713248 64 10283282b drivers/mfd/stw481x.o
On 05.09.2017 14:10, Daniel Vetter wrote:
Since this is new hw support, is there also open source userspace using
all this?
The VIC HW in Tegra186 is backwards compatible with the one in Tegra210,
which has open userspace (https://github.com/cyndis/vaapi-tegra-driver),
so that userspace shou
Including linux/vmalloc.h in asm-generic/io.h isn't necessary since none
of the definitions are used in the header itself. Remove the include in
order to avoid potential header dependency problems if other headers
rely on implict inclusion of linux/vmalloc.h which means that changes
there could bre
The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
tags/wberr-v4.14-1
for you to fetch changes up to 6d4b51241394664
> Applied to powerpc next, thanks.
>
> https://git.kernel.org/powerpc/c/6ab41161b44a3b4d504ac29c9dd997
Thanks that you picked another update suggestion up.
* It might matter to mention that only one patch hunk was accepted in this case.
* Can it be that the adjusted commit subject does contain
Hi Vinod,
> On Tue, Aug 29, 2017 at 04:47:17PM +0800, Baolin Wang wrote:
>
> > +config SPRD_DMA
> > + bool "Spreadtrum DMA support"
> > + depends on ARCH_SPRD
>
> can you also add compile test to this, it helps in getting good coverage and
> easy to compile changes
Sure.
>
> > +/* DMA glo
Ping for comments if possible. Thanks.
On Monday, August 28, 2017 6:09 PM, Wang, Wei W wrote:
> [PATCH v15 5/5] virtio-balloon: VIRTIO_BALLOON_F_CTRL_VQ
>
> Add a new vq, ctrl_vq, to handle commands between the host and guest.
> With this feature, we will be able to have the control plane and dat
Dear RT folks!
I'm pleased to announce the v4.11.12-rt12 patch set.
Changes since v4.11.12-rt11:
- In the hrtimer/hotplug fix in the last release, there was one
call path missed. Mike Galbraith reported it and sent a patch to
handle it.
Known issues
- There was a report regar
Hi,
On 05.09.2017 13:17, Alexey Budankov wrote:
> On 04.09.2017 18:41, Peter Zijlstra wrote:
>> On Mon, Sep 04, 2017 at 05:56:06PM +0300, Alexey Budankov wrote:
>>> On 04.09.2017 15:08, Peter Zijlstra wrote:
On Mon, Sep 04, 2017 at 01:46:45PM +0300, Alexey Budankov wrote:
>> So the below c
From: Thomas Gleixner
The configurable printk timestamping wants access to clock realtime. Right
now there is no ktime_get_real_fast_ns() accessor because reading the
monotonic base and the realtime offset cannot be done atomically. Contrary
to boot time this offset can change during runtime and
printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
timestamp to printk messages. The local hardware clock loses time each
day making it difficult to determine exactly when an issue has occurred in
the kernel log, and making it difficult to determine how kernel and
hardware i
printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
timestamp to printk messages. The local hardware clock loses time each
day making it difficult to determine exactly when an issue has occurred in
the kernel log, and making it difficult to determine how kernel and
hardware i
printk timestamps will be extended to include mono and boot time by using
the fast timekeeping functions ktime_get_mono|boot_fast_ns() functions.
The functions can return garbage before timekeeping is initialized
resulting in garbage timestamps.
The fast time functions must return 0 before timekee
From: Colin Ian King
Don't populate the const arrays vfd_packet6 and fp_packet on the
stack, instead make them static. Makes the object code smaller
by over 600 bytes:
Before:
textdata bss dec hex filename
43794 179201024 62738f512 drivers/media/rc/imon.o
After
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 do this is usefull.
Signed-off-by: Dragos Bogdan
---
drivers/iio/adc/ad_sigma_delta.c | 28
include/li
On Tue, 5 Sep 2017, Prarit Bhargava wrote:
> +static struct tk_fast tk_fast_mono cacheline_aligned = {
> + .base = {
> + (struct tk_read_base){
> + .clock = &dummy_clock,
> + },
> + (struct tk_read_base){
> + .clock
The serial interface can be reset by writing 32 consecutive 1s to the device.
'ret' was initialized correctly but its value was overwritten when
ad7793_check_platform_data() was called. Since a dedicated reset function
is present now, it should be used instead.
Fixes: 2edb769d246e ("iio:ad7793: Ad
On Tue, Sep 5, 2017 at 2:23 PM, Harsh Jain wrote:
> On Sun, Sep 3, 2017 at 11:47 AM, Gilad Ben-Yossef wrote:
>> On Thu, Aug 31, 2017 at 3:31 PM, Harsh Jain wrote:
>>> HI Gilad,
>>>
>>> I think we need an update in ESP also. Now EBUSY return means driver
>>> has accepted, Packet should not be dro
On Tue 2017-09-05 18:59:00, Sergey Senozhatsky wrote:
> On (09/05/17 11:44), Petr Mladek wrote:
> [..]
> > > Tetsuo wants this, for instance,
> > > for OOM reports and backtraces. SCIS/ATA people want it as well.
> >
> > The mixing of related lines might cause problems. But I am not sure
> > if it
Arnd,
> Without CONFIG_BLK_DEV_BSGLIB, we get a link error here:
>
> drivers/scsi/scsi_transport_sas.o: In function `sas_bsg_initialize':
> scsi_transport_sas.c:(.text+0xcc0): undefined reference to `bsg_setup_queue'
> scsi_transport_sas.c:(.text+0xd10): undefined reference to `bsg_setup_queue'
>
On Tuesday, September 5, 2017 5:40:58 AM CEST Andi Kleen wrote:
> > The cycle value gets associated with a sample via it's period value, which
> > is used by `perf report` in the analysis. If I get a single "broken"
> > sample with
>
> I always thought it just used the number of samples?
No, that
It modifies mlx-platform driver hotplug interface. Instead driver
mlxcpld-hotplug, which is to be removed, mlx-platform will use more
generic architecture independent and regmap based mlxreg-hotplug
driver.
Signed-off-by: Vadim Pasternak
Acked-by: Andy Shevchenko
---
drivers/platform/x86/Kconfi
The patchset modifies x86/mlxcpld-hotplug.c for making it architecture
independent, renames to mlxreg-hotplug and moves it from
drivers/platform/x86 folder to new drivers/platform/mellanox folder.
This modification also introduces regmap interface for mlxreg-hotplug
driver to allow hotplug event fu
It removes mlxcpld-hotplug.
Signed-off-by: Vadim Pasternak
Acked-by: Andy Shevchenko
---
MAINTAINERS | 7 -
drivers/platform/x86/mlxcpld-hotplug.c| 515 --
include/linux/platform_data/mlxcpld-hotplug.h | 99 -
3 files chan
It introduces mlxreg-hotplug driver with the generic regmap interface for
hardware access to the programmable device with interrupt controlling
logic. Where the programmable devices can be attached to different
interfaces types, like I2C, LPC, SPI.
Driver has been tested on systems based on x86 and
Petr Mladek wrote:
> Some of these problems would be solved by a custom buffer.
> But you are right. There are less guarantees that it would
> get flushed or that it can be found in case of troubles.
> Now, I am not sure that it is a good idea to use it even
> for a single continuous line.
>
> I w
The crypto API was using the -EBUSY return value to indicate
both a hard failure to submit a crypto operation into a
transformation provider when the latter was busy and the backlog
mechanism was not enabled as well as a notification that the
operation was queued into the backlog when the backlog m
Replace -EBUSY with -EAGAIN when reporting transient busy
indication in the absence of backlog.
Signed-off-by: Gilad Ben-Yossef
Reviewed-by: Gary R Hook
---
Please squash this patch with the previous one when merging upstream.
---
drivers/crypto/ccp/ccp-crypto-main.c | 8 +++-
drivers/cry
all of the corner cases.
The patch set is based upon linux-next release tagged
next-20170905.
Changes from v7:
- Turn -EBUSY to -EAGAIN also in crypto using net
code which I missed before, as has been pointed
out by Harsh Jain.
Changes from v6:
- Fix brown paper bag compile error on marvell
Replace -EBUSY with -EAGAIN when handling transient busy
indication in the absence of backlog.
Signed-off-by: Gilad Ben-Yossef
---
Please squash this patch with the previous one when merging upstream.
---
net/ipv4/ah4.c | 2 +-
net/ipv4/esp4.c | 2 +-
net/ipv6/ah6.c | 2 +-
net/ipv6/esp6.c |
Now that -EBUSY return code only indicates backlog queueing
we can safely remove the now redundant check for the
CRYPTO_TFM_REQ_MAY_BACKLOG flag when -EBUSY is returned.
Signed-off-by: Gilad Ben-Yossef
---
crypto/ahash.c| 12 +++-
crypto/cts.c | 6 ++
crypto/lrw.c
This patch is creates in order to correct the coding style issues. It
removes the unwanted parenthesis from the code.
Signed-off-by: Janani Sankara Babu
---
drivers/staging/rtl8188eu/core/rtw_xmit.c | 52 +++
1 file changed, 26 insertions(+), 26 deletions(-)
diff --
Now that -EBUSY return code only indicates backlog queueing
we can safely remove the now redundant check for the
CRYPTO_TFM_REQ_MAY_BACKLOG flag when -EBUSY is returned.
Signed-off-by: Gilad Ben-Yossef
Acked-by: Boris Brezillon
---
drivers/crypto/marvell/cesa.c | 3 +--
drivers/crypto/marvell/c
public_key_verify_signature() is starting an async crypto op and
waiting for it to complete. Move it over to generic code doing
the same.
Signed-off-by: Gilad Ben-Yossef
---
crypto/asymmetric_keys/public_key.c | 28
1 file changed, 4 insertions(+), 24 deletions(-)
d
201 - 300 of 819 matches
Mail list logo
