On Fri, Dec 07, 2018 at 02:50:42AM +, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/usb/serial/mos7840.c: In function 'mos7840_send_cmd_write_baud_rate':
> drivers/usb/serial/mos7840.c:1584:16: warning:
> variable 'number' set but not used
On Fri, Dec 07, 2018 at 03:11:01PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM831X_I2C
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM831x/2x PMICs with
> I2C"
>
> ...meaning that it currently is
On Fri, Dec 07, 2018 at 03:11:00PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM831X_SPI
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM831x/2x PMICs with
> SPI"
>
> ...meaning that it currently is
On Fri, Dec 07, 2018 at 03:11:02PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM831X
> drivers/mfd/Kconfig:bool
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove
Hi all,
Commit
24985cf0be81 ("ext4: use IS_ENCRYPTED() to check encryption status")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpknmQmHSDjF.pgp
Description: OpenPGP digital signature
From: Colin Ian King
There is a spelling mistake in a pr_err message, fix this.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/selftests/test-drm_damage_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/selftests/test-drm_damage_helper.c
On Fri, Dec 07, 2018 at 03:11:03PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM8350_I2C
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM8350 with I2C"
>
> ...meaning that it currently is not being
In case we are using simplefb or another conflicting framebuffer, make
the call to drm_fb_helper_remove_conflicting_framebuffers()
Signed-off-by: Maxime Jourdan
---
drivers/gpu/drm/meson/meson_drv.c | 20
1 file changed, 20 insertions(+)
diff --git
On Fri, Dec 07, 2018 at 03:11:05PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM8400
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM8400"
>
> ...meaning that it currently is not being built as a
From: Colin Ian King
There is a spelling mistake in a msg string, fix this.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_err.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_err.c
Hi,
I rebased on top of Jacek's patches and, as I could not find them on git kernel
tree, I included them here. Also with small fixup.
Changes since v1:
1. Rebase on Jacek's patches.
2. Add patch 3/5 for fixup of Jacek's solution.
3. Drop first two patches from the series (applied).
4. Patch
Allow initialization of pattern used in pattern trigger from Device Tree
property.
This is especially useful for embedded systems where the pattern trigger
would be used to indicate the process of boot status in a nice,
user-friendly blinking way. This initialization pattern will be used
till
Trigger driver can be initialized after the LED class device driver. In
such case led_trigger_set_default() won't be called and flag
LED_INIT_DEFAULT_TRIGGER should be set from led_trigger_register().
Signed-off-by: Krzysztof Kozlowski
---
drivers/leds/led-triggers.c | 4 +++-
1 file changed,
From: Jacek Anaszewski
It is of no avail to continue iterating through registered
triggers in the led_trigger_set_default() after the trigger to set
has been found. Add "break" statement to fix this omission.
Signed-off-by: Jacek Anaszewski
Acked-by: Pavel Machek
Signed-off-by: Krzysztof
From: Jacek Anaszewski
Add the flag LED_INIT_DEFAULT_TRIGGER for indicating that trigger
being set is a default trigger for the LED class device, and
thus it should be initialized with settings provided in the fwnode.
Set the flag in the led_trigger_set_default(). It is expected to be
cleared
Document new linux,trigger-pattern property for initialization of LED
pattern trigger.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/leds/common.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/common.txt
Ooops, $SUBJECT should be:
"drm/selftest: fix spelling mistake "dimention" -> "dimension"
On 10/12/2018 09:26, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in a pr_err message, fix this.
>
> Signed-off-by: Colin Ian King
> ---
>
Hi all,
Commit
42632988767e ("phy: ti: fix semicolon.cocci warnings")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpOdxl0PRnV7.pgp
Description: OpenPGP digital signature
Hi Sergey,
+ lkml.
On Fri, Dec 07, 2018 at 06:50:04PM +0900, Sergey Senozhatsky wrote:
> On (12/06/18 11:58), Feng Tang wrote:
> > > Same here, I tried on several platforms and hardly get the sysrq magic key
> > > working, though it works while system is running.
> > >
> > > And it make me
On 28/11/2018 13:50, Manivannan Sadhasivam wrote:
> Add interrupt driver for RDA Micro RDA8810PL SoC.
>
> Signed-off-by: Andreas Färber
> Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Marc Zyngier
Given the dependency on the platform Kconfig entry, how do you want this
to be merged?
Hi:
This series tries to fix various issues of vhost:
- Patch 1 adds a missing write barrier between used idx updating and
logging.
- Patch 2-3 brings back the protection of device IOTLB through vq
mutex, this fixes possible use after free in device IOTLB entries.
- Patch 4 fixes the diry
Vhost dirty page logging API is designed to sync through GPA. But we
try to log GIOVA when device IOTLB is enabled. This is wrong and may
lead to missing data after migration.
To solve this issue, when logging with device IOTLB enabled, we will:
1) reuse the device IOTLB translation result of
When we try to do rx busy polling in tx path in commit 441abde4cd84
("net: vhost: add rx busy polling in tx path"), we lock rx vq mutex
after tx vq mutex is held. This may lead deadlock so we try to lock vq
one by one in commit 78139c94dc8c ("net: vhost: lock the vqs one by
one"). With this
We miss a write barrier that guarantees used idx is updated and seen
before log. This will let userspace sync and copy used ring before
used idx is update. Fix this by adding a barrier before log_write().
Fixes: 8dd014adfea6f ("vhost-net: mergeable buffers support")
Signed-off-by: Jason Wang
---
Hi Frieder,
Thanks for the review. Please find my comments inline.
> -Original Message-
> From: Schrempf Frieder [mailto:frieder.schre...@kontron.de]
> Sent: Thursday, December 6, 2018 2:53 PM
> To: Yogesh Narayan Gaur ; linux-
> m...@lists.infradead.org; boris.brezil...@bootlin.com;
This reverts commit 78139c94dc8c96a478e67dab3bee84dc6eccb5fd. We don't
protect device IOTLB with vq mutex, which will lead e.g use after free
for device IOTLB entries. And since we've exact the same lock order
with the help of previous patch, it's safe to revert it without having
deadlock.
Fixes:
On Tue, Dec 04, 2018 at 08:46:41AM +, Dexuan Cui wrote:
> > From: Greg KH
> > Sent: Monday, December 3, 2018 11:43 PM
> > On Tue, Dec 04, 2018 at 03:35:13PM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Today's linux-next merge of the char-misc tree got a conflict in:
> > >
> > >
On Sat 08-12-18 00:49:44, Al Viro wrote:
> On Fri, Dec 07, 2018 at 08:49:16PM +0100, Alexander Lochmann wrote:
>
> > > _What_ SUID bit? We are talking about a write to block device, for fsck
> > > sake...
> > >
> > That's the way I understood Jan's explanation:
> > "
> > Thinking more about
On Sun, Dec 09, 2018 at 11:44:19AM -0500, Theodore Y. Ts'o wrote:
> On Sun, Dec 09, 2018 at 12:30:39PM +0100, Greg KH wrote:
> > > P.P.P.S. If I were king, I'd be asking for a huge number of kunit
> > > tests for block-mq to be developed, and then running them under a
> > > Thread Sanitizer.
> >
On Mon, Dec 10, 2018 at 11:33:49AM +0300, Alexey Brodkin wrote:
> Zebu boards were added in v4.9 and then renamed to "haps" in v4.10.
>
> Thus backporting
> commit 64234961c145 (ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from
> defconfigs)
> we missed "zebu" defconfigs in v4.9.
>
> Note this
HGz -> GHz
Signed-off-by: Michael Straube
---
drivers/staging/rtl8723bs/TODO | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/TODO b/drivers/staging/rtl8723bs/TODO
index 80dbdaca3a8f..58e02f944b6d 100644
--- a/drivers/staging/rtl8723bs/TODO
+++
The function rtw_port_switch_chk() returns always false.
Remove the function and related dead code.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 34 ---
.../staging/rtl8723bs/include/rtw_mlme_ext.h | 1 -
2 files changed, 35 deletions(-)
On Mon, Dec 10, 2018 at 1:49 AM Linus Torvalds
wrote:
> Most of it looks pretty small and normal. Would I have preferred for
> there to be less churn? Yes. But it's certainly smaller than rc5 was,
> so we're moving in the right direction, and we have at least one more
> rc to go.
>
> I say "at
Am Sonntag, 9. Dezember 2018, 23:14:05 CET schrieb Heiko Stuebner:
Forgot the
From: Rob Herring
here, but if you're ok with how it looks I can apply it to my tree.
Heiko
> Convert Rockchip SoC bindings to DT schema format using json-schema.
>
> Cc: Mark Rutland
> Cc: Heiko Stuebner
> Cc:
Hi Anson,
On Mon, Dec 10, 2018 at 5:17 AM Anson Huang wrote:
> + data->vdd_reg = devm_regulator_get_optional(>dev, "vdd");
> + if (!IS_ERR(data->vdd_reg)) {
> + ret = regulator_enable(data->vdd_reg);
> + if (ret) {
> + dev_err(>dev,
Hi Marc,
On Mon, Dec 10, 2018 at 09:39:13AM +, Marc Zyngier wrote:
> On 28/11/2018 13:50, Manivannan Sadhasivam wrote:
> > Add interrupt driver for RDA Micro RDA8810PL SoC.
> >
> > Signed-off-by: Andreas Färber
> > Signed-off-by: Manivannan Sadhasivam
>
> Reviewed-by: Marc Zyngier
>
>
On 2018/12/10 15:11, Sergey Senozhatsky wrote:
> On (12/10/18 05:58), Liu, Chuansheng wrote:
>>> On (12/10/18 05:40), Liu, Chuansheng wrote:
@@ -130,6 +130,13 @@ static void check_hung_task(struct task_struct *t,
>>> unsigned long timeout)
On Mon, Dec 10, 2018 at 12:32:21AM +0200, Igor Stoppa wrote:
>
>
> On 06/12/2018 11:44, Peter Zijlstra wrote:
> > On Wed, Dec 05, 2018 at 03:13:56PM -0800, Andy Lutomirski wrote:
> >
> > > > + if (op == WR_MEMCPY)
> > > > + memcpy((void *)wr_poking_addr, (void *)src, len);
>
On 08/12/2018 00:08, Lyude Paul wrote:
> uh
> didn't we fix this weeks ago? with "drm/nouveau: tegra: Call
> nouveau_drm_device_init()"
Yes here's the fix from Thierry:
https://patchwork.freedesktop.org/patch/263587/
and I can confirm that it does fix the Oops when applied on top
syzbot reported a kernel-infoleak, which is caused by an uninitialized
field(sin6_flowinfo) of addr->a.v6 in sctp_inet6addr_event().
The call trace is as below:
BUG: KMSAN: kernel-infoleak in _copy_to_user+0x19a/0x230 lib/usercopy.c:33
CPU: 1 PID: 8164 Comm: syz-executor2 Not tainted
On 2018-12-07 04:38 AM, Alexandre Belloni wrote:
On 06/12/2018 15:22:51+0800, yuank...@codeaurora.org wrote:
Hi,
Kindly, this format change formats the rtc dump from:
alrm_time : 00:00:00
alrm_date : 1970-01-01
alarm_IRQ : no
alrm_pending
Hello Mark,
On 12/7/2018 1:51 AM, Mark Brown wrote:
On Wed, Nov 28, 2018 at 05:00:34PM +0800, Cheng-Yi Chiang wrote:
Add a callback for init ops on dai_link to create and setup jack.
Signed-off-by: Rohit kumar
Signed-off-by: Cheng-Yi Chiang
This looks like you're forwarding a patch from
Am Mittwoch, 5. Dezember 2018, 14:52:30 CET schrieb Randy Li:
> From: ayaka
>
> The Windows 2/3 or a RGB UI layer is a high performance flexibly
> plane. It is too waste to use it as a cursor plane.
>
> I have verified this patch with weston git version, I am not
> sure whether X would meet
On Mon, Dec 10, 2018 at 09:46:53AM +0100, Daniel Vetter wrote:
> Drivers might want to remove some sysfs files, which needs the same
> locks and ends up angering lockdep. Relevant snippet of the stack
> trace:
>
> kernfs_remove_by_name_ns+0x3b/0x80
> bus_remove_driver+0x92/0xa0
>
On Mon, 10 Dec 2018, YueHaibing wrote:
> On 2018/12/10 14:15, Lee Jones wrote:
> > On Sun, 09 Dec 2018, YueHaibing wrote:
> >
> >> Remove duplicated include.
> >>
> >> Signed-off-by: YueHaibing
> >> ---
> >> drivers/input/keyboard/mtk-pmic-keys.c | 1 -
> >> 1 file changed, 1 deletion(-)
> >>
/commits/Long-Cheng/add-uart-DMA-function/20181210-125624
config: s390-allmodconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin
On 10/12/2018 09:56, Manivannan Sadhasivam wrote:
> Hi Marc,
>
> On Mon, Dec 10, 2018 at 09:39:13AM +, Marc Zyngier wrote:
>> On 28/11/2018 13:50, Manivannan Sadhasivam wrote:
>>> Add interrupt driver for RDA Micro RDA8810PL SoC.
>>>
>>> Signed-off-by: Andreas Färber
>>> Signed-off-by:
When introducing the video-codec node for the video engine, the
compatible for the H5 was used instead of the compatible for the
A64. Use the right compatible instead.
Fixes: d60ce24740d2 ("arm64: dts: allwinner: a64: Add Video Engine node")
Signed-off-by: Paul Kocialkowski
---
On Sat, Dec 08, 2018 at 12:38:05PM -0500, Steven Rostedt wrote:
> On Sat, 8 Dec 2018 11:44:23 +0100
> Peter Zijlstra wrote:
> > > Why do we care about lost events? Because strace records *all* events,
> > > as that's what it does and that's what it always has done. It would be
> > > a break in
On Mon, Dec 10, 2018 at 11:06:34AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Dec 10, 2018 at 09:46:53AM +0100, Daniel Vetter wrote:
> > Drivers might want to remove some sysfs files, which needs the same
> > locks and ends up angering lockdep. Relevant snippet of the stack
> > trace:
> >
> >
Hi Rafael,
On 12/10/18 11:04, Rafael J. Wysocki wrote:
> On Thu, Dec 6, 2018 at 3:55 PM Greg KH wrote:
>>
>> On Wed, Dec 05, 2018 at 12:41:35PM -0800, Evan Green wrote:
>>> On Tue, Nov 27, 2018 at 10:03 AM Georgi Djakov
>>> wrote:
Modern SoCs have multiple processors and various
On Mon, 10 Dec 2018 09:41:51 +
Yogesh Narayan Gaur wrote:
> > > +/* Instead of busy looping invoke readl_poll_timeout functionality.
> > > +*/ static int fspi_readl_poll_tout(struct nxp_fspi *f, void __iomem
> > > *base,
> > > + u32 mask, u32 delay_us,
> > > +
On Mon, Dec 10, 2018 at 11:18:32AM +0100, Daniel Vetter wrote:
> On Mon, Dec 10, 2018 at 11:06:34AM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Dec 10, 2018 at 09:46:53AM +0100, Daniel Vetter wrote:
> > > Drivers might want to remove some sysfs files, which needs the same
> > > locks and ends up
Since we found a problem with the 'copy-from' operation after objects have
been truncated, offloading object copies to OSDs should be discouraged
until the issue is fixed.
Thus, this patch adds the 'nocopyfrom' mount option to the default mount
options which effectily means that remote copies
Access to GICR_WAKER is restricted on msm8996 SoC in Hypervisor.
There are many devices out there with this restriction in place
and there has been no update to this firmware since last few years,
making those devices totally unusable for upstream development.
My previous attempts to add quirk
Access to GICR_WAKER is restricted on msm8996 SoC in Hypervisor.
Its been more than 2+ years of wait for this to be fixed, which has
no hopes to be fixed. This change was introduced for the "lead device"
on msm8996 platform. It looks like all publicly available msm8996 and
other Qualcomm SoCs have
Access to GICR_WAKER is restricted on msm8996 SoC in Hypervisor.
There are many devices out there with this restriction in place
and there has been no update to this firmware since last few years,
making those devices totally unusable for upstream development.
IIDR register value conflicts with
Add compatible to gicv3 node to enable quirk required to restrict writing
to GICR_WAKER register which is restricted on msm8996 SoC in Hypervisor.
With this quirk MSM8996 can at least boot out of mainline, which can help
community to work with boards based on MSM8996.
Without this patch Qualcomm
This patch adds support to device tree based quirks based on
device tree compatible string.
Signed-off-by: Srinivas Kandagatla
---
drivers/irqchip/irq-gic-common.c | 12
drivers/irqchip/irq-gic-common.h | 3 +++
drivers/irqchip/irq-gic-v3.c | 5 +
3 files changed, 20
Hi Greg,
This includes automatic enabling of IOMMU based DMA protection from
possibly malicious devices connected through Thunderbolt ports. In
addition we make sure PCIe ATS (Address Translation Service) is not
enabled for such devices to prevent them from passing IOMMU protection.
Please pull,
On Fri, 7 Dec 2018, Benjamin Tissoires wrote:
> OK, thanks Dmitry.
>
> Jiri, I have pushed this in for-4.20/upstream-fixes.
>
> I think the branch has enough now to justify a PR towards Linus.
Agreed. I will be sending it today. Thanks,
--
Jiri Kosina
SUSE Labs
On 10/12/2018 08:56, Christoffer Dall wrote:
On Mon, Dec 03, 2018 at 01:37:37PM +, Suzuki K Poulose wrote:
Hi Anshuman,
On 03/12/2018 12:11, Anshuman Khandual wrote:
On 10/31/2018 11:27 PM, Punit Agrawal wrote:
The code for operations such as marking the pfn as dirty, and
On Sat, Dec 08, 2018 at 08:36:25AM +, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/gpu/drm/ast/ast_fb.c: In function 'astfb_create':
> drivers/gpu/drm/ast/ast_fb.c:194:17: warning:
> variable 'bo' set but not used [-Wunused-but-set-variable]
>
> It never
On Fri, 07 Dec 2018 10:17:10 +0100,
Jian-Hong Pan wrote:
>
> Add Realtek ALC294 quirks for ASUS X542UN, UX533FD, UX433FN and UX333FA
> laptops.
>
> Chris Chiu (1):
> ALSA: hda/realtek: ALC294 mic and headset-mode fixups for ASUS X542UN
>
> Jian-Hong Pan (2):
> ALSA: hda/realtek: Enable
On Fri 07-12-18 21:24:46, Jerome Glisse wrote:
> Another crazy idea, why not treating GUP as another mapping of the page
> and caller of GUP would have to provide either a fake anon_vma struct or
> a fake vma struct (or both for PRIVATE mapping of a file where you can
> have a mix of both private
On (12/10/18 18:58), Tetsuo Handa wrote:
> +*/
> + if (sysctl_hung_task_panic && !ignore_loglevel)
> + ignore_loglevel = true;
> >>>
> >>> console_verbose()?
> >>
> >> Thanks Sergey, it is really my need. I will prepare
Hi Yogesh, Boris,
On 10.12.18 11:19, Boris Brezillon wrote:
> On Mon, 10 Dec 2018 09:41:51 +
> Yogesh Narayan Gaur wrote:
>
+/* Instead of busy looping invoke readl_poll_timeout functionality.
+*/ static int fspi_readl_poll_tout(struct nxp_fspi *f, void __iomem *base,
+
Hi Yogesh,
On 10.12.18 10:41, Yogesh Narayan Gaur wrote:
[...]>>> +
>>> +static void nxp_fspi_prepare_lut(struct nxp_fspi *f,
>>> +const struct spi_mem_op *op)
>>> +{
>>> + void __iomem *base = f->iobase;
>>> + u32 lutval[4] = {};
>>> + int lutidx = 1, i;
>>> +
Just a bit of paranoia, since if we start pushing this deep into
callchains it's hard to spot all places where an mmu notifier
implementation might fail when it's not allowed to.
Inspired by some confusion we had discussing i915 mmu notifiers and
whether we could use the newly-introduced return
This is a similar idea to the fs_reclaim fake lockdep lock. It's
fairly easy to provoke a specific notifier to be run on a specific
range: Just prep it, and then munmap() it.
A bit harder, but still doable, is to provoke the mmu notifiers for
all the various callchains that might lead to them.
We need to make sure implementations don't cheat and don't have a
possible schedule/blocking point deeply burried where review can't
catch it.
I'm not sure whether this is the best way to make sure all the
might_sleep() callsites trigger, and it's a bit ugly in the code flow.
But it gets the job
On Mon, 10 Dec 2018 10:31:57 +
Schrempf Frieder wrote:
> >> Yes, I need to validate op->addr.nbytes else LUT would going to be
> >> programmed for 0 addrlen.
> >> I have checked this on the target.
> >
> > Also agree there. Some operations have 0 address bytes. We could also
> > test
In some special cases we must not block, but there's not a
spinlock, preempt-off, irqs-off or similar critical section already
that arms the might_sleep() debug checks. Add a non_block_start/end()
pair to annotate these.
This will be used in the oom paths of mmu-notifiers, where blocking is
not
Hi all,
Here's v2 of my mmu notifier debug checks.
I think the last two patches could probably be extended to all callbacks,
but I'm not really clear on the exact rules. But happy to extend them if
there's interest.
This stuff helps us catch issues in the i915 mmu notifier implementation.
On Mon, 10 Dec 2018 10:35:35 +
Schrempf Frieder wrote:
> >>> +
> >>> +static int nxp_fspi_exec_op(struct spi_mem *mem, const struct
> >>> +spi_mem_op *op) {
> >>> + struct nxp_fspi *f = spi_controller_get_devdata(mem->spi->master);
> >>> + int err = 0;
> >>> +
> >>> + mutex_lock(>lock);
>
Hi Boris, Frieder,
> -Original Message-
> From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> Sent: Monday, December 10, 2018 3:49 PM
> To: Yogesh Narayan Gaur
> Cc: Schrempf Frieder ; linux-
> m...@lists.infradead.org; marek.va...@gmail.com; broo...@kernel.org; linux-
>
Patches #1 and #3 are Reviewed-by: Christian König
Patch #2 is Acked-by: Christian König because
I can't judge if adding the counter in the thread structure is actually
a good idea.
In patch #4 I honestly don't understand at all how this stuff works, so
no-comment from my side on this.
Hi, Yogesh,
On 12/03/2018 10:39 AM, Yogesh Narayan Gaur wrote:
> - Add opcodes for octal I/O commands
> * Read : 1-1-8 and 1-8-8 protocol
> * Write : 1-1-8 and 1-8-8 protocol
> * opcodes for 4-byte address mode command
>
> - Entry of macros in _convert_3to4_xxx function
>
> - Add flag
On 10/12/2018 08:56, Christoffer Dall wrote:
On Mon, Dec 03, 2018 at 01:37:37PM +, Suzuki K Poulose wrote:
Hi Anshuman,
On 03/12/2018 12:11, Anshuman Khandual wrote:
On 10/31/2018 11:27 PM, Punit Agrawal wrote:
The code for operations such as marking the pfn as dirty, and
On Wed, Nov 28, 2018 at 11:22:28AM -0800, Jarkko Sakkinen wrote:
Good morning, I hope everyone had a pleasant weekend.
> On Wed, Nov 28, 2018 at 04:49:41AM -0600, Dr. Greg wrote:
> > We've been carrying a patch, that drops in on top of the proposed
> > kernel driver, that implements the needed
On Mon, 10 Dec 2018 10:43:56 +
Yogesh Narayan Gaur wrote:
> > > Thus, in LUT preparation we have assigned only the base address.
> > > Now if I have assigned ahb_buf_size to FSPI_FLSHXXCR0 register then for
> > read/write data beyond limit of ahb_buf_size offset I get data corruption.
> >
Hi,
Can you please provide more details. I don't understand how this patch
can cause boot failure.
>From the log found at
https://storage.kernelci.org/mainline/master/v4.20-rc5-79-gabb8d6ecbd8f/arm/multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y/lab-baylibre/boot-tegra124-jetson-tk1.html
On 10/12/2018 10:23, Srinivas Kandagatla wrote:
> This patch adds support to device tree based quirks based on
> device tree compatible string.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> drivers/irqchip/irq-gic-common.c | 12
> drivers/irqchip/irq-gic-common.h | 3 +++
>
On Mon, 3 Dec 2018 08:39:18 +
Yogesh Narayan Gaur wrote:
> - Add opcodes for octal I/O commands
> * Read : 1-1-8 and 1-8-8 protocol
> * Write : 1-1-8 and 1-8-8 protocol
> * opcodes for 4-byte address mode command
>
> - Entry of macros in _convert_3to4_xxx function
>
> - Add flag
Hi Boris,
> -Original Message-
> From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> Sent: Monday, December 10, 2018 4:20 PM
> To: Yogesh Narayan Gaur
> Cc: Schrempf Frieder ; linux-
> m...@lists.infradead.org; marek.va...@gmail.com; broo...@kernel.org; linux-
>
On Mon, Dec 10, 2018 at 11:18 AM Georgi Djakov wrote:
>
> Hi Rafael,
>
> On 12/10/18 11:04, Rafael J. Wysocki wrote:
> > On Thu, Dec 6, 2018 at 3:55 PM Greg KH wrote:
> >>
> >> On Wed, Dec 05, 2018 at 12:41:35PM -0800, Evan Green wrote:
> >>> On Tue, Nov 27, 2018 at 10:03 AM Georgi Djakov
>
On Mon, Dec 10, 2018 at 10:47:42AM +, Suzuki K Poulose wrote:
>
>
> On 10/12/2018 08:56, Christoffer Dall wrote:
> >On Mon, Dec 03, 2018 at 01:37:37PM +, Suzuki K Poulose wrote:
> >>Hi Anshuman,
> >>
> >>On 03/12/2018 12:11, Anshuman Khandual wrote:
> >>>
> >>>
> >>>On 10/31/2018 11:27
Move ad7606 ADC driver out of staging and into the mainline.
Signed-off-by: Stefan Popa
---
Changes in v2:
- Simplified the Kconfig menu.
- Added SPDX-License-Identifier.
- Ordered the includes alphabetically.
- Used a threaded interrupt.
- Replaced
Document support for AD7606 Analog to Digital Converter.
Signed-off-by: Stefan Popa
---
Changes in v2:
- fixed indentation issues.
- used gpios instead of gpio.
- added vendor prefix for conversion-start-gpios, first-data-gpios,
and range-gpios.
Changes in v3:
On Mon, 10 Dec 2018 10:59:54 +
Yogesh Narayan Gaur wrote:
> Hi Boris,
>
> > -Original Message-
> > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> > Sent: Monday, December 10, 2018 4:20 PM
> > To: Yogesh Narayan Gaur
> > Cc: Schrempf Frieder ; linux-
> >
On Mon, 10 Dec 2018 10:59:54 +
Yogesh Narayan Gaur wrote:
> Hi Boris,
>
> > -Original Message-
> > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> > Sent: Monday, December 10, 2018 4:20 PM
> > To: Yogesh Narayan Gaur
> > Cc: Schrempf Frieder ; linux-
> >
On Thu, Dec 06, 2018 at 01:38:42PM -0600, Rob Herring wrote:
> On Wed, Dec 5, 2018 at 1:44 PM Simon Horman wrote:
> >
> > On Tue, Dec 04, 2018 at 09:08:57AM -0600, Rob Herring wrote:
> > > On Tue, Dec 4, 2018 at 8:57 AM Geert Uytterhoeven
> > > wrote:
> > > >
> > > > Hi Simon,
> > > >
> > > >
On Mon, Dec 10, 2018 at 11:23 AM Luis Henriques wrote:
>
> Since we found a problem with the 'copy-from' operation after objects have
> been truncated, offloading object copies to OSDs should be discouraged
> until the issue is fixed.
>
> Thus, this patch adds the 'nocopyfrom' mount option to the
On 6.12.2018 17:16, Uwe Kleine-König wrote:
> On Thu, Dec 06, 2018 at 03:37:55PM +, Vokáč Michal wrote:
>> On 6.12.2018 14:59, Uwe Kleine-König wrote:
>>> On Thu, Dec 06, 2018 at 01:41:31PM +, Vokáč Michal wrote:
>>>
>>> Can it happen, that pinctrl_pins_pwm is PTR_ERR(-EPROBE_DEFER)?
>>
>>
Hi Boris,
> -Original Message-
> From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> Sent: Monday, December 10, 2018 4:27 PM
> To: Yogesh Narayan Gaur
> Cc: linux-...@lists.infradead.org; broo...@kernel.org;
> marek.va...@gmail.com; vigne...@ti.com; linux-...@vger.kernel.org;
>
Thanks for the review,
On 07/12/18 18:23, Mark Rutland wrote:
On Fri, Dec 07, 2018 at 04:35:08PM +, Srinivas Kandagatla wrote:
The FastRPC driver implements an IPC (Inter-Processor Communication)
mechanism that allows for clients to transparently make remote method
invocations across DSP
On Mon, Dec 10, 2018 at 11:15:05AM +, Vokáč Michal wrote:
> On 6.12.2018 17:16, Uwe Kleine-König wrote:
> > On Thu, Dec 06, 2018 at 03:37:55PM +, Vokáč Michal wrote:
> >> On 6.12.2018 14:59, Uwe Kleine-König wrote:
> >>> On Thu, Dec 06, 2018 at 01:41:31PM +, Vokáč Michal wrote:
> >>>
>
On 10/12/18 2:15 PM, Boris Brezillon wrote:
> On Wed, 3 Oct 2018 22:26:03 +0530
> Vignesh R wrote:
>
>> Cadence OSPI controller IP supports Octal IO (x8 IO lines),
>> It also has an integrated PHY. IP register layout is very
>> similar to existing QSPI IP except for additional bits to support
Hi Linus,
On Sun, Dec 09, 2018 at 07:14:05AM +0100, Linus Lüssing wrote:
> So far any changes with ebtables will reset the state of limit rules,
> leading to spikes in traffic. This is especially noticeable if changes
> are done frequently, for instance via a daemon.
>
> This patch fixes this by
On 2018/12/7 17:24, Miquel Raynal wrote:
Hi Jianxin,
Looks good to me overall, a few comments inline.
Jianxin Pan wrote on Sat, 17 Nov 2018
00:40:38 +0800:
From: Liang Yang
Add initial support for the Amlogic NAND flash controller which found
in the Meson-GXBB/GXL/AXG SoCs.
1 - 100 of 1203 matches
Mail list logo
