On Sun, Aug 26, 2018 at 04:53:12PM -0400, Waiman Long wrote:
> v1->v2:
> - For patch 1, remove wake_q_empty() & add task_in_wake_q().
> - Rewrite patch 2 after comments from Dave Chinner and break it down
>to 2 separate patches. Now the original xfs logic was kept. The
>patches just try t
On Sun, Aug 26, 2018 at 11:13:55PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_err message.
This patch is duplicated. This issue is covered by your previous patch.
https://marc.info/?l=linux-fpga&m=153202583007071&w=2
Thanks
Hao
>
> Signed-off-b
On Fri, Aug 24, 2018 at 4:55 AM, Jens Wiklander
wrote:
> Hello arm-soc maintainers,
>
> Please pull these tee driver enhancements. There's one small fix for the
> OP-TEE driver to take DT status into account. There's also a patch
> providing a kernel only tee client interface that can be used by o
On Sat, Aug 25, 2018 at 07:21:14PM -0700, Matthew Wilcox wrote:
> On Fri, Aug 24, 2018 at 06:32:14PM +0900, Naoya Horiguchi wrote:
> > - int hwcache_align, object_size, objs_per_slab;
> > - int sanity_checks, slab_size, store_user, trace;
> > + int hwcache_align, objs_per_slab;
> > + int sa
On Sun, Aug 26, 2018 at 04:53:14PM -0400, Waiman Long wrote:
> The current log space reservation code allows multiple wakeups of the
> same sleeping waiter to happen. This is a just a waste of cpu time as
> well as increasing spin lock hold time. So a new XLOG_TIC_WAKING flag is
> added to track if
i have been trying to contact you
For Skylake Server, Linux has supported a number of free running
counters that collect counts of IO clocks/Bandwidth/Utilization.
For example, to collect the inbound bandwidth,
root@skx /sys/devices# ls | grep uncore_iio
uncore_iio_0
uncore_iio_1
uncore_iio_2
uncore_iio_3
uncore_iio_4
uncore_iio_
Hi all,
Changes since 20180824:
Dropped trees: xarray, ida (temporarily)
Non-merge commits (relative to Linus' tree): 427
585 files changed, 17988 insertions(+), 5276 deletions(-)
I have created today's linux-next tr
Hi all,
Changes since 20180824:
Dropped trees: xarray, ida (temporarily)
Non-merge commits (relative to Linus' tree): 427
585 files changed, 17988 insertions(+), 5276 deletions(-)
I have created today's linux-next tr
On Mon, Aug 20, 2018 at 04:37:09PM +0800, Ian Kent wrote:
> The autofs_sbi() inline function does not check the super block
> magic number to verify it has been given an autofs super block.
IMO it's the wrong way to fix it. The one and only caller where that
check might trigger is
We move __fstate_save and __fstate_restore to a new source
file, fpu.S.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
Reviewed-by: Christoph Hellwig
---
arch/riscv/kernel/Makefile | 1 +
arch/riscv/kernel/entry.S | 87 --
a
This patch cleanup the MARCH string passing to both compiler and
assembler. Note that the CFLAGS should not contain "fd" before we
have mechnisms like kernel_fpu_begin/end in other architectures.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
---
arch/risc
We expect that a kernel with CONFIG_FPU=y can still support no-FPU
machines. To do so, the kernel should first examine the existence of a
FPU, then do nothing if a FPU does exist; otherwise, it should
disable/bypass all FPU-related functions.
In this patch, a new global variable, has_fpu, is creat
FPU codes have been separated from common part in previous patches.
This patch add the CONFIG_FPU option and some stubs, so that a no-FPU
configuration is allowed.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
Reviewed-by: Christoph Hellwig
---
arch/riscv
This patchset adds an option, CONFIG_FPU, to enable/disable floating-
point procedures.
Kernel's new behavior will be as follows:
* with CONFIG_FPU=y
All FPU codes are reserved. If no FPU is found during booting, a
global flag will be set, and those functions will be bypassed with
conditio
FPU-related logic is separated from normal signal handling path in
this patch. Kernel can easily be configured to exclude those procedures
for no-FPU systems.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
Reviewed-by: Christoph Hellwig
---
arch/riscv/ker
On 2018/8/26 2:07, Andrew Lunn wrote:
This patch is a theoretical protect, and the problem does not really
happen.
I think you really get the point, do you think we need this patch?
I think it is not needed.
And if it was needed, it would indicate there is a bug somewhere else.
Hi, Andrew
On Fri, Aug 24, 2018 at 03:26:13PM +0200, Jan Tuerk wrote:
> This patch adds support for the emtrion GmbH emCON-MX6 modules.
> They are available with imx.6 Solo, Dual-Lite, Dual and Quad
> equipped with Memory from 512MB to 2GB (configured by U-Boot).
>
> Our default developer-Kit ships with the
On Tue, Jul 31, 2018 at 06:10:35AM +0800, Anson Huang wrote:
> The i.MX7ULP B0 chip has some pin changes for USB and VIU
> module, update pinfunc header file accordingly.
>
> Signed-off-by: Anson Huang
Applied, thanks.
If there are packets in hardware when changing the speed
or duplex, it may cause hardware hang up.
This patch adds netif_carrier_off before change speed and
duplex in ethtool_ops.set_link_ksettings, and adds
netif_carrier_on after complete the change.
Signed-off-by: Peng Li
---
drivers/net/ethe
If there are packets in hardware when changing the speed
or duplex, it may cause hardware hang up.
This patch adds the code for waiting chip to clean the all
pkts(TX & RX) in chip when the driver uses the function named
"adjust link".
This patch cleans the pkts as follows:
1) close rx of chip, cl
If there are packets in hardware when changing the spped
or duplex, it may cause hardware hang up.
This patchset adds the code for waiting chip to clean the all
pkts(TX & RX) in chip when the driver uses the function named
"adjust link".
This patchset cleans the pkts as follows:
1) close rx of ch
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20180813 was the first linux-next after
the merge window opened.)
Commits in v4.19-rc1 (relative to v4.18): 12317
Commits in next-20180813:
Tentatively merged into cifs-2.6.git for-next but would like a little
more experimentation with it if possible (or description of what
scenarios/servers have been tried)
On Mon, Jul 9, 2018 at 9:53 AM Jon Kuhn wrote:
>
> When a Mac client saves an item containing a backslash to a file server
> the
Hi Marc
Thanks for the comments
On 8/27/2018 3:01 AM, Marc Zyngier Wrote:
> [I'm travelling, so expect some major delays in responding to email]
>
> Hi Jia,
>
> On Sun, 26 Aug 2018 10:00:51 +0100,
> Jia He wrote:
>>
>> There is a WARN_ON when my QDF2400 server boots up (pagesize is 4k)
>
> [sn
simple_strtol and simple_strtoul are obsolete, both place
use kstrtouint instead.
V2: fix error tmp += tn
V3: fix compile error
Signed-off-by: Ding Xiang
---
drivers/bluetooth/bt3c_cs.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/bluetooth/bt3c_cs.c b/dr
On Thu, Aug 02, 2018 at 12:35:52PM +0100, Mark Brown wrote:
> On Thu, Aug 02, 2018 at 12:47:27PM +0200, Oleksij Rempel wrote:
> > On 02.08.2018 12:44, Mark Brown wrote:
>
> > > I thought we'd got an ack for this from Raphael on a previous version or
> > > am I mistaken?
>
> > No, we got an:
> > "
On Mon, Aug 06, 2018 at 01:40:05PM +0800, Anson Huang wrote:
> System poweroff is already supported by PSCI on i.MX7D,
> remove "snvs_poweroff" node to avoid below debug message
> from syscon-poweroff driver:
>
> [1.831414] syscon-poweroff 3037.snvs:snvs-poweroff: pm_power_off
> already c
On Sun, 26 Aug 2018, Joe Perches wrote:
> On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > On Sun, Aug 26, 2018 at 11:57:57AM -0700, Joe Perches wrote:
> >
> > > > That, BTW, is why I hate the use of sizeof(*p) in kmalloc, etc.
> > > > arguments. typeof is even worse in that respect.
> >
On Sun, 26 Aug 2018, Al Viro wrote:
> On Sun, Aug 26, 2018 at 03:26:54PM -0700, Joe Perches wrote:
> > On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > > On Sun, Aug 26, 2018 at 11:57:57AM -0700, Joe Perches wrote:
> > >
> > > > > That, BTW, is why I hate the use of sizeof(*p) in kmalloc,
In function tipc_dest_push, the 32bit variables 'node' and 'port'
are stored separately in uppper and lower part of 64bit 'value'.
Then this value is assigned to dst->value which is a union like:
union
{
struct {
u32 port;
u32 node;
};
u64 value;
}
This works on little-endian machines
Thanks, V2 will be send out.
-Original Message-
From: David Miller [mailto:da...@davemloft.net]
Sent: 2018年8月26日 8:37
To: Bai, Haiqing
Cc: net...@vger.kernel.org; jon.ma...@ericsson.com; Xue, Ying; Gao, Zhenbo;
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] tipc: fix the big/lit
In some usages, e.g. virtio-balloon, a kernel module needs to know if
page poisoning is in use. This patch exposes the page_poisoning_enabled
function to kernel modules.
Signed-off-by: Wei Wang
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Michael S. Tsirkin
Acked-by: Andrew Morton
---
mm/page_pois
Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates the
support of reporting hints of guest free pages to host via virtio-balloon.
Currenlty, only free page blocks of MAX_ORDER - 1 are reported. They are
obtained one by one from the mm free list via the regular allocation
function.
The new feature, VIRTIO_BALLOON_F_FREE_PAGE_HINT, implemented by this
series enables the virtio-balloon driver to report hints of guest free
pages to host. It can be used to accelerate virtual machine (VM) live
migration. Here is an introduction of this usage:
Live migration needs to transfer the
The VIRTIO_BALLOON_F_PAGE_POISON feature bit is used to indicate if the
guest is using page poisoning. Guest writes to the poison_val config
field to tell host about the page poisoning value that is in use.
Suggested-by: Michael S. Tsirkin
Signed-off-by: Wei Wang
Cc: Michael S. Tsirkin
Cc: Mich
On 08/07/18 at 02:49pm, Chao Fan wrote:
> If 'CONFIG_MEMORY_HOTREMOVE' specified, walk the acpi srat memory
> tables, store the immovable memory regions, so that kaslr can get
> the information abouth where can be selected or not.
> If 'CONFIG_MEMORY_HOTREMOVE' not specified, go on the old code.
Ju
Andrey,
Are you fine with these two patches?
Shawn
On Mon, Aug 06, 2018 at 02:39:48PM +0800, Anson Huang wrote:
> gpcv2 driver is NOT just used on i.MX7D which has Cortex-A7
> cores, but also on i.MX8MQ/i.MX8MM platforms which use Cortex-A53
> cores, so let's use A_CORE instread of A7 to avoid c
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
The GCC version checks in arch/powerpc/Makefile are obsolete now.
Signed-off-by: Masahiro Yamada
---
arch/powerpc/Makefile | 38 +--
On Tue, Aug 07, 2018 at 02:20:55AM +0800, Robin Gong wrote:
> To support loading sdma firmware automatically from rootfs, enable
> CONFIG_FW_LOADER_USER_HELPER/CONFIG_FW_LOADER_USER_HELPER_FALLBACK.
> Please get sdma firmware from below link and put it into
> rootfs entry -- /lib/firmware/imx/sdma/
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
The version check in arch/parisc/Makefile is obsolete now.
Signed-off-by: Masahiro Yamada
---
arch/parisc/Makefile | 9 -
1 file changed, 9 deletions(-)
d
When make perf with -O, it gets error when make clean with below log:
$ make -C tools/perf O= # OK
$ make -C tools/perf O=
find: cannot delete ‘/builtin-script.o’: No such file or
directory
find: cannot delete ‘/.subcmd-config.o.cmd’: No such file or
directory
...
Makefile:38:
On Sun, Aug 26, 2018 at 10:00:46PM -0400, Julia Lawall wrote:
>
>
> On Sun, 26 Aug 2018, Al Viro wrote:
>
> > On Sun, Aug 26, 2018 at 03:26:54PM -0700, Joe Perches wrote:
> > > On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > > > On Sun, Aug 26, 2018 at 11:57:57AM -0700, Joe Perches wrote:
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
The workaround code in fs/reiserfs/Makefile is obsolete now.
Signed-off-by: Masahiro Yamada
---
fs/reiserfs/Makefile | 9 -
1 file changed, 9 deletions(-)
On Mon, Aug 27, 2018 at 10:13:49AM +0800, Baoquan He wrote:
>On 08/07/18 at 02:49pm, Chao Fan wrote:
>> If 'CONFIG_MEMORY_HOTREMOVE' specified, walk the acpi srat memory
>> tables, store the immovable memory regions, so that kaslr can get
>> the information abouth where can be selected or not.
>> I
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> The interrupt controller hardware in this pin controller has two status
> enable bits. The first "normal" status enable bit enables or disables
> the summary interrupt line being raised when a gpio interrupt triggers
> and the "raw" status enable
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> We rely on devices to use pinmuxing configurations in DT to select the
> GPIO function (function 0) if they're going to use the gpio in GPIO
> mode. Let's simplify things for driver authors by implementing
> gpio_request_enable() for this pinctrl
Hi Tony,
On Monday 20 August 2018 08:01 PM, Tony Lindgren wrote:
> * Kishon Vijay Abraham I [180808 06:35]:
>> On Tuesday 05 June 2018 07:35 PM, Rob Herring wrote:
>>> Really need 64-bit addresses and sizes? Use ranges to limit the
>>> address space if possible.
>>
>> We now have address-cells as
On Sun, 26 Aug 2018 11:09:58 +0200
Peter Zijlstra wrote:
> On Sat, Aug 25, 2018 at 09:21:22PM -0700, Andy Lutomirski wrote:
> > I just re-read text_poke(). It's, um, horrible. Not only is the
> > implementation overcomplicated and probably buggy, but it's SLOW.
> > It's totally the wrong AP
On Thu 16 Aug 13:06 PDT 2018, Stephen Boyd wrote:
> When requesting a gpio as an interrupt, we should make sure to mux the
> pin as the GPIO function and configure it to be an input so that various
> functions or output signals don't affect the interrupt state of the pin.
> So far, we've relied on
On Fri, Aug 24, 2018 at 9:26 PM Vikash Garodia wrote:
>
> Hi Alex,
>
> On 2018-08-24 13:09, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
>
> [snip]
>
> >> +struct video_firmware {
> >> + struct device *dev;
> >> + struct iommu_domain *iommu_d
On 08/27/18 at 10:56am, Chao Fan wrote:
> >> +#ifdef CONFIG_MEMORY_HOTREMOVE
> >> +/*
> >> + * According to ACPI table, filter the immvoable memory regions
> >> + * and store them in immovable_mem[].
> >> + */
> >> +static void handle_immovable_mem(void)
> >
> >Can we change this function like bel
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
With GCC >= 4.6 assumed, 'upto_gcc44' is empty, 'atleast_gcc44' is y.
Signed-off-by: Masahiro Yamada
---
arch/arc/Makefile | 10 +-
1 file changed, 1 inser
On Fri, Aug 24, 2018 at 6:01 PM Stanimir Varbanov
wrote:
>
> Hi Alex,
>
> On 08/24/2018 10:39 AM, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
> >>
> >> Separate firmware loading part into a new function.
> >>
> >> Signed-off-by: Vikash Garodia
> >> --
On Fri, Aug 24, 2018 at 5:57 PM Stanimir Varbanov
wrote:
>
> Hi Alex,
>
> On 08/24/2018 10:38 AM, Alexandre Courbot wrote:
> > On Thu, Aug 23, 2018 at 11:29 PM Vikash Garodia
> > wrote:
> >>
> >> Add routine to reset the ARM9 and brings it out of reset. Also
> >> abstract the Venus CPU state han
i have been trying to contact you
at 8:03 PM, Masami Hiramatsu wrote:
> On Sun, 26 Aug 2018 11:09:58 +0200
> Peter Zijlstra wrote:
>
>> On Sat, Aug 25, 2018 at 09:21:22PM -0700, Andy Lutomirski wrote:
>>> I just re-read text_poke(). It's, um, horrible. Not only is the
>>> implementation overcomplicated and probably buggy, but
On Mon, 27 Aug 2018, Al Viro wrote:
> On Sun, Aug 26, 2018 at 10:00:46PM -0400, Julia Lawall wrote:
> >
> >
> > On Sun, 26 Aug 2018, Al Viro wrote:
> >
> > > On Sun, Aug 26, 2018 at 03:26:54PM -0700, Joe Perches wrote:
> > > > On Sun, 2018-08-26 at 22:24 +0100, Al Viro wrote:
> > > > > On Sun,
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
This effectively reverts commit da541b20021c ("objtool: Skip
unreachable warnings for GCC 4.4 and older"), which was a workaround
for GCC 4.4 or older.
Signed-off-by:
Hi Alexandre,
> -Original Message-
> From: Alexandre Bailon [mailto:abai...@baylibre.com]
> Sent: Wednesday, August 8, 2018 6:01 PM
> To: A.s. Dong ; linux-...@vger.kernel.org;
> sb...@kernel.org
> Cc: Jacky Bai ; Anson Huang ;
> mturque...@baylibre.com; linux-kernel@vger.kernel.org; dl-li
Kindly ping again... This is really pending too long...
Stephen & Shawn,
Any suggestion on how to proceed this patch set?
Regards
Dong Aisheng
> -Original Message-
> From: A.s. Dong
> Sent: Thursday, July 26, 2018 9:51 AM
> To: linux-...@vger.kernel.org; sb...@kernel.org
> Cc: linux-ker
Hi Jens
On 08/25/2018 11:41 PM, Jens Axboe wrote:
> do {
> - set_current_state(TASK_UNINTERRUPTIBLE);
> + if (test_bit(0, &data.flags))
> + break;
>
> - if (!has_sleeper && rq_wait_inc_below(rqw, get_limit(rwb, rw)))
> + W
---
kernel: 4.4.153-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git branch: 4.4.153-rc1-hikey-20180826-270
git commit: 1d9b202cd56188353c13a49bf48f3f97383984ee
git describe: 4.4.153-rc1-hikey-20180826-270
Test details:
https://qa-reports.linaro.org/lkft/linaro-hike
Hi Philipp,
On Tue, Aug 21, 2018 at 12:34 AM Philipp Zabel wrote:
>
> On Mon, 2018-08-20 at 23:27 +0900, Tomasz Figa wrote:
> [...]
> > +3. Start queuing buffers to ``OUTPUT`` queue containing stream data after
> > > > > > + the seek until a suitable resume point is found.
> > > > > > +
> > > >
On Sun, Aug 26, 2018 at 11:35:17PM -0400, Julia Lawall wrote:
> * x = \(kmalloc\|kzalloc\|devm_kmalloc\|devm_kzalloc\)(...)
I can name several you've missed right off the top of my head -
vmalloc, kvmalloc, kmem_cache_alloc, kmem_cache_zalloc, variants
with _trace slapped on, and that is not to m
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
'$(call cc-option,-fno-unit-at-a-time)' is now dead code since
'$(cc-version) -lt 0400' is always false.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile.um |
On Sun, Aug 26, 2018 at 08:23:48PM +0800, Jacek Tomaka wrote:
> I am trying to get microcode version from user space. Reading it
> from /proc/cpuinfo requires greping/awking to extract the bits of
> information that are readily available in microcode/version.
If the only reason is because you find
On Tue, Aug 21, 2018 at 8:29 PM Stanimir Varbanov
wrote:
>
> Hi Tomasz,
>
> On 08/08/2018 05:55 AM, Tomasz Figa wrote:
> > On Tue, Aug 7, 2018 at 4:37 PM Hans Verkuil wrote:
>
> >>> +7. If all the following conditions are met, the client may resume
> >>> the
> >>> +decoding inst
i have been trying to contact you
On Thu, Aug 16, 2018 at 03:28:40PM -0400, Michael Jin wrote:
> Add new device IDs for family 17h models 10h-2fh.
>
> This is required by amd64_edac_mod in order to properly detect PCI
> device functions 0 and 6.
>
> Link: https://lkml.kernel.org/r/20180815114107.29797-1-mikhail@gmail.com
> Cc
Commit 7634ccd2da (libata: maintainership update) added an invalid email
address. Fix that.
Signed-off-by: Baruch Siach
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a5b256b25905..9ae5cdef37a1 100644
--- a/MAINTAINERS
+++ b/MA
On Mon, 27 Aug 2018, Al Viro wrote:
> On Sun, Aug 26, 2018 at 11:35:17PM -0400, Julia Lawall wrote:
>
> > * x = \(kmalloc\|kzalloc\|devm_kmalloc\|devm_kzalloc\)(...)
>
> I can name several you've missed right off the top of my head -
> vmalloc, kvmalloc, kmem_cache_alloc, kmem_cache_zalloc, var
On Fri, 24 Aug 2018 16:52:43 +0100
Will Deacon wrote:
> From: Peter Zijlstra
>
> Some architectures require different TLB invalidation instructions
> depending on whether it is only the last-level of page table being
> changed, or whether there are also changes to the intermediate
> (directory)
On 24-08-18, 08:56, Fabrizio Castro wrote:
> From: Biju Das
>
> This patch adds binding for r8a774a1 (RZ/G2M).
Acked-by: Vinod Koul
--
~Vinod
On Fri, 24 Aug 2018 13:39:53 +0200
Peter Zijlstra wrote:
> On Fri, Aug 24, 2018 at 01:32:14PM +0200, Peter Zijlstra wrote:
> > On Fri, Aug 24, 2018 at 10:47:17AM +0200, Peter Zijlstra wrote:
> > > On Thu, Aug 23, 2018 at 02:39:59PM +0100, Will Deacon wrote:
> > > > The only problem with this
On 07-08-18, 13:42, Paul Cercueil wrote:
> From: Daniel Silsby
>
> The 'dtc' word in jz DMA descriptors contains two fields: The
> lowest 24 bits are the transfer count, and upper 8 bits are the DOA
> offset to next descriptor. The upper 8 bits are now correctly masked
> off when computing residu
Hi Pavel,
On Sunday, August 26, 2018 3:52 PM, Pavel Machek wrote:
>
> > +++ b/Documentation/devicetree/bindings/input/dlg,da7280.txt
> > @@ -0,0 +1,101 @@
> > +Dialog Semiconductor DA7280 Haptics bindings
> > +
> > +Required properties:
> > +- compatible: Should be "dlg,da7280".
> > +- reg: Specif
i have been trying to contact you
On 07-08-18, 13:42, Paul Cercueil wrote:
> Hi,
>
> This is the V4 of my Ingenic JZ47xx DMA patchset.
This does not apply for me. Please rebase on rc1, fix Rob's and my
comment and send
Also I noticed checkpatch gave warns on some style issues (--strict
option) please see if they make sense and f
On Mon, Aug 27, 2018 at 09:30:45AM +0530, Naresh Kamboju wrote:
> On 26 August 2018 at 12:12, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.4.153 release.
> > There are 5 patches in this series, all will be posted as a response
> > to this one. If anyone h
syzbot wrote on Sun, Aug 26, 2018:
> HEAD commit:e27bc174c9c6 Add linux-next specific files for 20180824
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15dc19a640
> kernel config: https://syzkaller.appspot.com/x/.config?x=28446088176757ea
> dashboa
On 02-08-18, 16:10, Andrea Merello wrote:
s/cylic/cyclic in patch title
> Whenever a single or cyclic transaction is prepared, the driver
> could eventually split it over several SG descriptors in order
> to deal with the HW maximum transfer length.
>
> This could end up in DMA operations starti
On 02-08-18, 16:10, Andrea Merello wrote:
> The width of the "length register" cannot be autodetected, and it is now
> specified with a DT property. Add DOC for it.
Add Documentation for it...
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Cc: Radhey Shyam Pandey
>
On 02-08-18, 16:10, Andrea Merello wrote:
> The AXIDMA and CDMA HW can be either direct-access or scatter-gather
> version. These are SW incompatible.
>
> The driver can handle both versions: a DT property was used to
> tell the driver whether to assume the HW is in scatter-gather mode.
>
> This
Thanks Axel,
On Fri, Aug 24, 2018 at 07:16:12PM +0800, Axel Lin wrote:
> Set it once is enough.
> Also move n_voltages close to volt_table for better readability.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/bd71837-regulator.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
On 08/07/18 at 02:50pm, Chao Fan wrote:
> If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
> memory regions is not zero. Calculate the intersection between memory
> regions from e820/efi memory table and immovable memory regions.
> Or go on the old code.
>
> Rename process_mem_r
On 22-08-18, 10:40, Huang Shijie wrote:
> The following patch introduced an issue.
> commit f6206f00d8c5 ("dmaengine: mic_x100_dma: use the new helper to
> simplify the code")
>
> This issue is :
>
> kfree(mic_dma_dev)
> .
> dma_async_device_unregister(mic_dma_dev->devi
Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
bumped the minimum GCC version to 4.6 for all architectures.
Remove the workaround code.
It was the only user of cc-if-fullversion. Remove the macro as well.
Signed-off-by: Masahiro Yamada
---
arch/x86/Makefile | 12 -
On 08/07/18 at 02:50pm, Chao Fan wrote:
> If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
If CONFIG_MEMORY_HOTREMOVE is enabled,
> memory regions is not zero. Calculate the intersection between memory
> regions from e820/efi memory table and immovable memory regions.
> Or go on
Hi Corey,
On 08/24/2018 06:38 PM, Corey Minyard wrote:
On 08/24/2018 06:10 AM, George Cherian wrote:
Dont set ssif_info->intf to NULL before ipmi_unresgiter_smi.
shutdown_ssif will anyways free ssif_info.
This is correct, but it goes a little deeper. I just sent out a
patch yesterday tha
On 08/27/18 at 01:35pm, Baoquan He wrote:
> Is it possible to take num_immovable_mem out from the #ifdef
> CONFIG_MEMORY_HOTREMOVE region so that you can check it earlier to see
> if the old way need be taken? This way, we can reduce one level of
> indentation in the for loop. Just personal thoug
i have been trying to contact you
On 2018-08-26 19:49, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Apparently, this driver (or the hardware) does not support character
> length settings. It's apparently running in 8-bit mode, but it makes
> userspace believe it's in 5-bit mode. That makes tcsetattr with CS8
> incorrectly fail, break
On Mon, Aug 27, 2018 at 01:56:07PM +0800, Baoquan He wrote:
>On 08/07/18 at 02:50pm, Chao Fan wrote:
>> If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
>If CONFIG_MEMORY_HOTREMOVE is enabled,
>> memory regions is not zero. Calculate the intersection between memory
>> regions fr
On Mon, Aug 27, 2018 at 02:28:54PM +0800, Chao Fan wrote:
>On Mon, Aug 27, 2018 at 01:56:07PM +0800, Baoquan He wrote:
>>On 08/07/18 at 02:50pm, Chao Fan wrote:
[...]
>>
>>Is it possible to take num_immovable_mem definition out from #ifdef
>>CONFIG_MEMORY_HOTREMOVE block and check it here like belo
On Tue, Aug 07, 2018 at 12:38:36PM +0530, Jagan Teki wrote:
> Adopt the SPDX license identifier headers to ease license compliance
> management.
>
> Also added Engicam Copyright on missing files.
>
> Signed-off-by: Jagan Teki
Applied all, thanks.
On Thu, Aug 09, 2018 at 02:32:07PM +0200, Esben Haabendal wrote:
> From: Esben Haabendal
>
> Gives substantial performance improvement for transfers larger than 16
> bytes (DMA_THRESHOLD). Smaller transfers are unaffected.
>
> Signed-off-by: Esben Haabendal
Applied, thanks.
Hi ,
Sorry for very late reminder, just wanted to know is below understanding
of code is wrong?
Regards
Gaurav
On 4/17/2018 11:59 AM, Kohli, Gaurav wrote:
On 4/17/2018 3:18 AM, Tejun Heo wrote:
On Fri, Apr 13, 2018 at 03:05:03PM +0530, Gaurav Kohli wrote:
During percpu_counter destroy, de
On Fri, 24 Aug 2018 21:42:04 -0400
Steven Rostedt wrote:
> On Sat, 25 Aug 2018 10:35:13 +0900
> Masami Hiramatsu wrote:
>
> > On Fri, 24 Aug 2018 16:37:37 -0400
> > Steven Rostedt wrote:
> >
> > > On Fri, 17 Aug 2018 01:30:36 +0900
> > > Masami Hiramatsu wrote:
> > >
> > > > Add --console
On Fri, 24 Aug 2018 18:53:42 -0400
Steven Rostedt wrote:
> On Fri, 17 Aug 2018 01:38:09 +0900
> Masami Hiramatsu wrote:
>
> > Add a testcase for nop tracer. This tracer has 2 test
> > options, so check it too.
> >
>
> I'd rather not include this. In fact, I'd love to get rid of the nop
> opti
1 - 100 of 191 matches
Mail list logo
