On Thu, Jul 02, 2020 at 08:22:52PM +0530, Amit Singh Tomar wrote:
> This commit adds DMA controller present on Actions S700, it differs from
> S900 in terms of number of dma channels and requests.
>
> Signed-off-by: Amit Singh Tomar
Reviewed-by: Manivannan Sadhasivam
Thanks,
Mani
> ---
> Chan
On Thu, Jul 02, 2020 at 08:22:53PM +0530, Amit Singh Tomar wrote:
> This commit adds device tree binding reset constants for mmc controller
> present on Actions S700 Soc.
>
> Acked-by: Rob Herring
> Signed-off-by: Amit Singh Tomar
Reviewed-by: Manivannan Sadhasivam
Thanks,
Mani
> ---
> Chang
On Thu, Jul 02, 2020 at 08:22:54PM +0530, Amit Singh Tomar wrote:
> The commit adds a new SoC specific compatible string "actions,s700-mmc"
> in combination with more generic string "actions,owl-mmc".
>
> Placement order of these strings should abide by the principle of
> "from most specific to mo
On Thu, Jul 02, 2020 at 08:22:55PM +0530, Amit Singh Tomar wrote:
> This commits adds support for MMC controllers present on Actions S700 SoC,
> there are 3 MMC controllers in this SoC which can be used for accessing
> SD/EMMC/SDIO cards.
>
> Signed-off-by: Amit Singh Tomar
Reviewed-by: Manivann
Vladimir Oltean writes:
> On Sun, Jul 12, 2020 at 05:16:56PM +0300, Sergey Organov wrote:
>> Vladimir Oltean writes:
>>
>> > Hi Sergey,
>> >
>> > On Sat, Jul 11, 2020 at 03:08:42PM +0300, Sergey Organov wrote:
>> >> Fix support for external PTP-aware devices such as DSA or PTP PHY:
>> >>
>> >>
On Thu, Jul 02, 2020 at 08:22:56PM +0530, Amit Singh Tomar wrote:
> This commit adds uSD support for Cubieboard7 board based on Actions Semi
> S700 SoC. SD0 is connected to uSD slot. Since there is no PMIC support
> added yet, fixed regulator has been used as a regulator node.
>
> Signed-off-by: A
On Sat, Jul 11, 2020 at 11:12:58AM -0700, Linus Torvalds wrote:
> Yeah, that's just the commit that enables the code, not the commit
> that introduces the fundamental problem.
>
> That said, this is a prime example of why I absolutely detest patch
> series that do this kind of thing, and are sever
On Sat, Jul 11, 2020 at 02:21:27PM -0400, Waiman Long wrote:
> +static DEFINE_PER_CPU_READ_MOSTLY(u8, pcpu_lockval) = _Q_LOCKED_VAL;
>
> /*
> * We must be able to distinguish between no-tail and the tail at 0:0,
> @@ -138,6 +139,19 @@ struct mcs_spinlock *grab_mcs_node(struct mcs_spinlock
>
On Sat, Jul 11, 2020 at 02:21:28PM -0400, Waiman Long wrote:
> The previous patch enables native qspinlock to store lock holder cpu
> number into the lock word when the lock is acquired via the slowpath.
> Since PV qspinlock uses atomic unlock, allowing the fastpath and
> slowpath to put different
Re-write the end of 'nl80211_trigger_scan()' with a more standard, easy to
understand and future proof version.
Signed-off-by: Christophe JAILLET
---
net/wireless/nl80211.c | 19 +++
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/net/wireless/nl80211.c b/net/wirel
Since commit 5fe231e87372 ("cfg80211: vastly simplify locking"), the
'unlock' label at the end of 'nl80211_trigger_scan()' is useless and
misleading, because nothing is unlocked there.
Direct return can be used instead of 'err = -; goto unlock;'
construction.
Remove this label and simplify code a
The pull request you sent on Sat, 11 Jul 2020 13:24:01 -0700 (PDT):
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
> tags/riscv-for-linus-5.8-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9901a6bd157719f9f93186868c527c5ba5edf8e5
Thank you!
--
The pull request you sent on Sat, 11 Jul 2020 12:25:23 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9599e9e7e3ee3a5afcdf00b05d4e86d256a98ae3
Thank you!
--
Deet-doot-dot, I am a bot.
ht
On Thu, Jul 09, 2020 at 06:52:50PM -0500, Gustavo A. R. Silva wrote:
> Reorganize the code a bit in a more standard way[1] and remove
> unnecessary fall-through markings.
>
> [1] https://lore.kernel.org/lkml/20200708054703.GR207186@unreal/
>
> Signed-off-by: Gustavo A. R. Silva
> ---
> Changes in
Hello,
syzbot found the following crash on:
HEAD commit:0bddd227 Documentation: update for gcc 4.9 requirement
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13178abd10
kernel config: https://syzkaller.appspot.com/x/.config?x=66ad203c2bb6d8b
dashboard
On 7/12/20 7:38 AM, Ivan Safonov wrote:
Remove unused members of struct xmit_buf: alloc_sz, ff_hwaddr,
dma_transfer_addr, bpending and last.
Signed-off-by: Ivan Safonov
---
Have you tested this change? Previously with this driver, an unused quantity was
removed from one of the structs and th
On 11/07/2020 08:48, Yong Wu wrote:
Put all the macros about smi larb/port togethers, this is a preparing
patch for extending LARB_NR and adding new dom-id support.
Signed-off-by: Yong Wu
---
include/dt-bindings/memory/mt2712-larb-port.h | 2 +-
include/dt-bindings/memory/mt6779-larb-po
On 12/07/2020 18:55, Matthias Brugger wrote:
> On 10/07/2020 15:58, Matthias Brugger wrote:
>>
>>
>> On 07/07/2020 12:34, Enric Balletbo i Serra wrote:
>>> This reverts commit eb9aecd90d1a39601e91cd08b90d5fee51d321a6
>>>
>>> The above patch is supposed to fix a register index error on mt2701. It
>>
On Fri, 10 Jul 2020 at 21:28, Yafang Shao wrote:
>
> Recently we found an issue on our production environment that when memcg
> oom is triggered the oom killer doesn't chose the process with largest
> resident memory but chose the first scanned process. Note that all
> processes in this memcg have
On Sun, Jul 12, 2020 at 10:59:17AM +0200, Sedat Dilek wrote:
> On Sat, Jul 11, 2020 at 6:32 PM Paul Menzel wrote:
> >
> > Dear Sami,
> >
> >
> > Am 24.06.20 um 22:31 schrieb Sami Tolvanen:
> > > This patch series adds support for building x86_64 and arm64 kernels
> > > with Clang's Link Time Optim
Hi,
On Sun, Jul 12, 2020 at 11:00 PM Manivannan Sadhasivam
wrote:
>
> On Thu, Jul 02, 2020 at 08:22:56PM +0530, Amit Singh Tomar wrote:
> > This commit adds uSD support for Cubieboard7 board based on Actions Semi
> > S700 SoC. SD0 is connected to uSD slot. Since there is no PMIC support
> > added
On Sat, Jul 11, 2020 at 11:16:33AM -0700, Joe Perches wrote:
> On Sat, 2020-07-11 at 20:41 +0530, Suraj Upadhyay wrote:
> > On Fri, Jul 10, 2020 at 07:56:43PM +0200, Sam Ravnborg wrote:
> > > Hi Suraj.
> > >
> > > On Tue, Jul 07, 2020 at 10:04:14PM +0530, Suraj Upadhyay wrote:
> > > > This patchse
On Tue, Jul 07, 2020 at 05:53:12PM +0530, Kajol Jain wrote:
> Added the "PerChip" field in enum so that perf knows they are
> per chip events.
>
> Added the "PerCore" field in enum so that perf knows they are
> per core events and add these fields to pmu_event structure.
>
> Similar to the way w
On Tue, Jul 07, 2020 at 05:53:10PM +0530, Kajol Jain wrote:
SNIP
> }
>
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 93fe72a9dc0b..3cafbb320d68 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -306,7 +306,7 @@ static bool perf_
On Tue, Jul 07, 2020 at 05:53:14PM +0530, Kajol Jain wrote:
> This patch adds hv_24x7 core level events in nest_metric.json file
> and also add PerChip/PerCore field in metric events.
>
> Result:
>
> power9 platform:
>
> command:# ./perf stat --metric-only -M PowerBUS_Frequency -C 0 -I 1000
>
On Tue, Jul 07, 2020 at 05:53:09PM +0530, Kajol Jain wrote:
> Patchset enhance current runtime parameter support. It introduces new
> fields like "PerChip" and "PerCore" similar to the field "PerPkg" which is
> used to specify perpkg events.
>
> The "PerCore" and "PerChip" specifies whether its c
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0aea6d5c5be33ce94c16f9ab2f64de1f481f424b
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 3 weeks ago
config: x86_64-randconfig-s021-20200713 (attache
On Mon, 2020-07-13 at 00:24 +0530, Suraj Upadhyay wrote:
> On Sat, Jul 11, 2020 at 11:16:33AM -0700, Joe Perches wrote:
[]
> > Perhaps change the __drm_printk macro to not
> > dereference the drm argument when NULL.
> >
> > A trivial but perhaps inefficient way might be
> > used like:
> >
> >
Hi!
> > > > > Some LED controllers may come with an internal HW triggering mechanism
> > > > > for the LED and an ability to switch between user control of the LED,
> > > > > or the internal control. One such example is AXP20X PMIC, that allows
> > > > > wither for user control of the LED, or for
Hi Jingle,
On Fri, Jul 10, 2020 at 01:41:16AM -0400, Jingle Wu wrote:
> Due to the higer resolution touchpads would be produced,
> The mainly modifications were as below:
> 1. the former resolution bits were not enough. Extend the
> resolution bits from 12 to 16 bits.
> 2. Increase the report ID 0
From: Tom Rix
clang static analysis flags this error
88pm860x_battery.c:522:19: warning: Assigned value is
garbage or undefined [core.uninitialized.Assign]
info->start_soc = soc;
^ ~~~
soc is set by calling calc_soc.
But calc_soc can return witho
The pull request you sent on Sun, 12 Jul 2020 12:14:58 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.8-rc4-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/72c34e8d7099c329c2934c2ac9c886f638b6edaf
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 12 Jul 2020 10:30:40 -0600:
> git://git.kernel.dk/linux-block.git tags/io_uring-5.8-2020-07-12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4437dd6e8f71e8b4b5546924a6e48e7edaf4a8dc
Thank you!
--
Deet-doot-dot, I am a bot.
https://
On Sun, Jul 12, 2020 at 08:29:46PM +0300, Sergey Organov wrote:
> Vladimir Oltean writes:
>
> > As far as I understand. the reason why SKBTX_IN_PROGRESS exists is for
> > skb_tx_timestamp() to only provide a software timestamp if the hardware
> > timestamping isn't going to. So hardware timestamp
On Sun, Jul 12, 2020 at 03:31:51PM +0300, Adrian Bunk wrote:
> On Thu, Jul 09, 2020 at 11:41:47AM -0700, Nick Desaulniers wrote:
> >...
> > but also a larger question of "should we do
> > this?" or "how might we place limits on where this can be used?"
> >...
>
> I won't attend, but I do have a to
Inform dmsetup users to zero the first 4k of the metadata device at
cache creation in examples, just as mentioned in thin-provisioning
documentation. Instructions to use lvmcache for end users may be added
as well.
Link: https://www.redhat.com/archives/dm-devel/2013-April/msg00124.html
Signed-off-
On 2020-07-10 11:12, Alexander A. Klimov wrote:
> Am 10.07.20 um 16:22 schrieb Bart Van Assche:
>> On 2020-07-09 12:48, Alexander A. Klimov wrote:
>>> diff --git a/drivers/infiniband/ulp/srpt/Kconfig
>>> b/drivers/infiniband/ulp/srpt/Kconfig
>>> index 4b5d9b792cfa..f63b34d9ae32 100644
>>> --- a/dr
On Thu 2020-07-09 13:24:21, Rob Herring wrote:
> On Mon, 22 Jun 2020 13:59:04 -0500, Dan Murphy wrote:
> > Add DT bindings for the LEDs multicolor class framework.
> > Add multicolor ID to the color ID list for device tree bindings.
> >
> > CC: Rob Herring
> > Acked-by: Pavel Machek
> > Acked-by
On 2020-07-12 14:11, Jonathan Cameron wrote:
On Sun, 12 Jul 2020 13:07:13 +0100
Jonathan Cameron wrote:
On Thu, 9 Jul 2020 17:21:58 +0200
Artur Rojek wrote:
> From: Paul Cercueil
>
> Instead of having one array of struct iio_chan_spec for all SoCs, and
> have some SoCs remove the last item
--
I sent to you a message days ago waiting to hear from you urgently
-20200712
for you to fetch changes up to ee769ebbe9e5fc7219e979fb7c5ed5bb5722649e:
xtensa: simplify xtensa_pmu_irq_handler (2020-07-08 00:18:15 -0700)
Xtensa fixes for v5.8:
- fix __sync_fetch_and_{and,or}_4 declarations to avoid
Hi!
> > > This is the multi color LED framework. This framework presents clustered
> > > colored LEDs into an array and allows the user space to adjust the
> > > brightness
> > > of the cluster using a single file write. The individual colored LEDs
> > > intensities are controlled via a single
On Mon, Jul 13, 2020 at 03:40:39AM +0800, Austin Chang wrote:
> + # When using dmsetup directly instead of volume manager like lvm2,
> + # the first 4k of the metadata device should be zeroed to indicate
> + # empty metadata.
> + dd if=/dev/zero of=/dev/mapper/metadata bs=4k conv=notrunc
... d
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0aea6d5c5be33ce94c16f9ab2f64de1f481f424b
commit: c6bf20109a3fae92402cb76ad709ec5256bcd169 mt76: mt7615: add WoW support
date: 9 weeks ago
config: arm-randconfig-r001-20200713 (attached as .config)
compiler:
Am 12.07.20 um 21:52 schrieb Bart Van Assche:
On 2020-07-10 11:12, Alexander A. Klimov wrote:
Am 10.07.20 um 16:22 schrieb Bart Van Assche:
On 2020-07-09 12:48, Alexander A. Klimov wrote:
diff --git a/drivers/infiniband/ulp/srpt/Kconfig
b/drivers/infiniband/ulp/srpt/Kconfig
index 4b5d9b792
Hi Jonathan,
Le dim. 12 juil. 2020 à 14:19, Jonathan Cameron a
écrit :
On Thu, 9 Jul 2020 17:22:00 +0200
Artur Rojek wrote:
The SADC component in JZ47xx SoCs provides support for touchscreen
operations (pen position and pen down pressure) in single-ended and
differential modes.
The to
On Sun, Jul 12, 2020 at 12:39 PM Josh Triplett wrote:
>
> Rust has hard stability guarantees when upgrading from one stable
> version to the next.
I think the worry is more about actual compiler bugs, not the set of
exposed features.
That's always been the biggest pain point. Compiler bugs are v
On Sun, Jul 12, 2020 at 10:31 AM Matthew Wilcox wrote:
>
> But I don't see any other way to do it. It's not like I can put THPs
> in the page cache before fixing the things that won't work.
I agree that sometimes there are bootstrapping issues. Incremental and
explanatory commits are still bette
On Sun, Jul 12, 2020 at 12:39:44PM -0700, Josh Triplett wrote:
> On Sun, Jul 12, 2020 at 03:31:51PM +0300, Adrian Bunk wrote:
> > On Thu, Jul 09, 2020 at 11:41:47AM -0700, Nick Desaulniers wrote:
> > >...
> > > but also a larger question of "should we do
> > > this?" or "how might we place limits o
Queue index is received from the user. Therefore, we must validate it
before using it to access the queue props array.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/command_submission.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/misc/haba
Hi!
> The board has a vibrator mottor. Hook it to the input subsystem.
motor, I believe.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/pic
On Thu 2020-07-02 11:41:34, Eric W. Biederman wrote:
> Now that the last callser has been removed remove this code from exec.
Typo "caller".
> For anyone thinking of resurrecing do_execve_file please note that
resurrecting?
> the code was buggy in several fundamental ways.
>
> - It did not ens
Hi!
> /* Summary */
> This contains an annotation patch for a data race in copy_process() reported
> by
> KCSAN when reading and writing nr_threads. The data race is intentional and
Would "KCSAN fixes" be better subject of the pull request? fixes is a bit
too generic...
qrtr_tun_write_iter() is dereferencing `ZERO_SIZE_PTR`s when `from->count`
equals to zero. Fix it by rejecting zero-length kzalloc() requests.
This patch fixes the following syzbot bug:
https://syzkaller.appspot.com/bug?id=f56bbe6668873ee245986bbd23312b895fa5a50a
Reported-by: syzbot+03e343d
On 7/12/20 8:55 PM, Larry Finger wrote:
On 7/12/20 7:38 AM, Ivan Safonov wrote:
Remove unused members of struct xmit_buf: alloc_sz, ff_hwaddr,
dma_transfer_addr, bpending and last.
Signed-off-by: Ivan Safonov
---
Have you tested this change? Previously with this driver, an unused
quantity w
On Sun, Jul 12, 2020 at 08:59:32PM +0100, Matthew Wilcox wrote:
> On Mon, Jul 13, 2020 at 03:40:39AM +0800, Austin Chang wrote:
> > + # When using dmsetup directly instead of volume manager like lvm2,
> > + # the first 4k of the metadata device should be zeroed to indicate
> > + # empty metadata
On Sun, 12 Jul 2020 21:11:11 +0200
Pavel Machek wrote:
> Hi!
>
> > > > > > Some LED controllers may come with an internal HW triggering
> > > > > > mechanism
> > > > > > for the LED and an ability to switch between user control of the
> > > > > > LED,
> > > > > > or the internal control. One s
On Wed, Jul 08, 2020 at 10:36:30AM +0300, Alexey Budankov wrote:
>
> Changes in v10:
> - reused struct priv, renamed props into flags and used unsigned int type as
> a storage
> - implemented and adopted usage of evlist__ctlfd_initialized() function
> - updated while condition with checking !(don
At the top this file, we have:
#define pr_fmt(fmt) "chcr:" fmt
So there is no need to repeat "chcr : " in some error message when the
pr_xxx macro is used.
This would lead to log "chcr:chcr : blabla"
Signed-off-by: Christophe JAILLET
---
drivers/crypto/chelsio/chcr_algo.c | 19 +-
The error handling path of 'chcr_authenc_setkey()' is the same as this
error handling code.
So just 'goto out' as done everywhere in the function to simplify the code.
Signed-off-by: Christophe JAILLET
---
drivers/crypto/chelsio/chcr_algo.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0aea6d5c5be33ce94c16f9ab2f64de1f481f424b
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 3 weeks ago
config: openrisc-randconfig-s031-20200712
On Sun, Jul 12, 2020 at 05:03:00PM -0400, Peilin Ye wrote:
> qrtr_tun_write_iter() is dereferencing `ZERO_SIZE_PTR`s when `from->count`
> equals to zero. Fix it by rejecting zero-length kzalloc() requests.
>
> This patch fixes the following syzbot bug:
>
>
> https://syzkaller.appspot.com/bug
On Sun, 2020-07-12 at 08:12 -0700, Tom Rix wrote:
> On 7/12/20 6:09 AM, H. Peter Anvin wrote:
> > On 2020-07-12 05:59, t...@redhat.com wrote:
> > > From: Tom Rix
[]
> > > So change the type in sizeof to 'unsigned int'
> > You must be kidding.
> >
> > If you want to change it, change it to sizeof(
On Thu, Jul 09, 2020 at 10:22:21PM -0700, Linus Torvalds wrote:
> On Thu, Jul 9, 2020 at 9:29 PM Naresh Kamboju
> wrote:
> >
> > Your patch applied and re-tested.
> > warning triggered 10 times.
> >
> > old: bfe0-c000 new: bfa0 (val: 7d530067)
>
> Hmm.. It's not even the overlapping
Inform dmsetup users to zero the first 4k of the metadata device at
cache creation in examples, just as mentioned in thin-provisioning
documentation. Instructions to use lvmcache for end users may be added
as well.
Link: https://www.redhat.com/archives/dm-devel/2013-April/msg00124.html
Signed-off-
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4437dd6e8f71e8b4b5546924a6e48e7edaf4a8dc
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 3 weeks ago
config: sh-randconfig-s032-20200713 (attached as
Hi Andy,
On Sun, 12 Jul 2020 18:56:04 +0300 Andy Shevchenko
wrote:
>
> On Fri, Jul 10, 2020 at 06:33:18PM +1000, Stephen Rothwell wrote:
> >
> > Changes since 20200709:
>
> I can't build it on Debian with Sparse enabled
>
> CC init/main.o
> init/main.c:760:20: warning: no previous protot
Tagged keys are keys that contain metadata indicating what
they are and how to handle them using the new added tag_object API.
A tag object represents the metadata (or simply a header/configuration)
and the actual data (e.g. black key) obtained from hardware.
Patch #2 adds support, for tagged keys,
A tag object represents the metadata (or simply a header/configuration)
and the actual data (e.g. black key) obtained from hardware.
Add functionality to tag an object with metadata:
- validate metadata: check tag object header;
- retrieve metadata: get tag object header configuration, black key
co
Tagged keys are keys that contain metadata indicating what
they are and how to handle them using tag_object API.
Add support, for tagged keys, to skcipher algorithms by
adding new transformations, with _tk_ prefix to distinguish
between plaintext and tagged keys.
For job descriptors a new option
Hi Melissa,
First of all, thanks a lot for your patch! This is a nice change since
it increases the code coverage.
Reviewed-by: Rodrigo Siqueira
On 07/10, Melissa Wen wrote:
> This change expands the coverage for the IGT kms_cursor_crc test, where
> the size varies between 64 and 512 for a squa
Applied to drm-misc-next.
Thanks
On 07/12, Rodrigo Siqueira wrote:
> Hi Melissa,
>
> First of all, thanks a lot for your patch! This is a nice change since
> it increases the code coverage.
>
> Reviewed-by: Rodrigo Siqueira
>
> On 07/10, Melissa Wen wrote:
> > This change expands the coverage
Hello Pavel,
On Sun, Jul 12, 2020 at 09:11:11PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > > > Some LED controllers may come with an internal HW triggering
> > > > > > mechanism
> > > > > > for the LED and an ability to switch between user control of the
> > > > > > LED,
> > > > > > or the inte
On July 12, 2020 8:12:43 AM PDT, Tom Rix wrote:
>
>On 7/12/20 6:09 AM, H. Peter Anvin wrote:
>> On 2020-07-12 05:59, t...@redhat.com wrote:
>>> From: Tom Rix
>>>
>>> clang static analysis flags this error
>>>
>>> lib/decompress_bunzip2.c:671:13: warning: Result of 'malloc' is
>converted
>>> to
Hello,
syzbot found the following crash on:
HEAD commit:89032636 Add linux-next specific files for 20200708
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11638f9d10
kernel config: https://syzkaller.appspot.com/x/.config?x=64a250ebabc6c320
dashboard
From: Christophe JAILLET
Date: Sat, 11 Jul 2020 22:49:44 +0200
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script below and has been
> hand modified to replace GPF_ with a correct flag.
> It has been compile tested.
>
> W
From: Christophe JAILLET
Date: Sat, 11 Jul 2020 22:35:18 +0200
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script below and has been
> hand modified to replace GPF_ with a correct flag.
> It has been compile tested.
>
> W
Hi folks.
While testing 5.8 RCs I founded that kernel log flooded by the message
"WARNING: CPU: 28 PID: 211236 at fs/fuse/file.c:1684 tree
insert+0xaf/0xc0 [fuse]" when I start podman container.
In kernel 5.7 not has such a problem.
[92414.864536] [ cut here ]
[92414.864648
Vladimir Oltean writes:
> On Sun, Jul 12, 2020 at 08:29:46PM +0300, Sergey Organov wrote:
>> Vladimir Oltean writes:
>>
>> > As far as I understand. the reason why SKBTX_IN_PROGRESS exists is for
>> > skb_tx_timestamp() to only provide a software timestamp if the hardware
>> > timestamping isn'
Hello,
On Sun, Jul 12, 2020 at 09:11:11PM +0200, Pavel Machek wrote:
> Hi!
>
[]
> }
> diff --git a/include/linux/leds.h b/include/linux/leds.h
> index 2451962d1ec5..cba52714558f 100644
> --- a/include/linux/leds.h
> +++ b/include/linux/leds.h
> @@ -57,6 +57,10 @@ struct led_in
On Sat, 2020-07-11 at 10:21 +, Jonas Karlman wrote:
> On 2020-07-10 23:49, Nicolas Dufresne wrote:
> > Le vendredi 10 juillet 2020 à 09:25 -0300, Ezequiel Garcia a écrit :
> > > +Nicolas
> > >
> > > On Fri, 2020-07-10 at 14:05 +0200, Boris Brezillon wrote:
> > > > On Fri, 10 Jul 2020 08:50:28
Hello,
syzbot found the following crash on:
HEAD commit:4437dd6e Merge tag 'io_uring-5.8-2020-07-12' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17183f0b10
kernel config: https://syzkaller.appspot.com/x/.config?x=66ad203c2bb6d8b
dash
On Sun, Jul 12, 2020 at 2:50 PM Joel Fernandes wrote:
>
> I reproduced Naresh's issue on a 32-bit x86 machine and the below patch fixes
> it.
> The issue is solely within execve() itself and the way it allocates/copies the
> temporary stack.
>
> It is actually indeed an overlapping case because t
On 7/12/20 1:34 PM, Peter Zijlstra wrote:
On Sat, Jul 11, 2020 at 02:21:28PM -0400, Waiman Long wrote:
The previous patch enables native qspinlock to store lock holder cpu
number into the lock word when the lock is acquired via the slowpath.
Since PV qspinlock uses atomic unlock, allowing the fa
Hi all,
Attempting to fetch the dmi tree gets this error:
http://jdelvare.nerim.net/devel/linux/jdelvare-dmi/series:
2020-07-13 08:58:05 ERROR 403: Forbidden.
I am still using the previously fetched quilt series.
Jean, I don't suppose you would like to produce a git tree for me to
fetch instead
When using Clang's Integrated Assembler (LLVM_IAS=1) we fell over
ClangBuiltLinux (CBL) issue #1043 where Jian Cai provided a fix.
With Jian's fix applied another issue raised up when CONFIG_HYPERV=m.
It turned out that the conversion of vectors to IDTENTRY_SYSVEC in
case of CONFIG_HYPERV was inc
On Mon, Jul 13, 2020 at 01:32:09AM +0300, Sergey Organov wrote:
> >
> > If you run "ethtool -T eth0" on a FEC network interface, it will always
> > report its own PHC, and never the PHC of a PHY. So, you cannot claim
> > that you are fixing PHY timestamping, since PHY timestamping is not
> > advert
On Mon, 13 Jul 2020 00:38:21 +0200
Ondřej Jirman wrote:
> Hello,
>
> On Sun, Jul 12, 2020 at 09:11:11PM +0200, Pavel Machek wrote:
> > Hi!
> >
>
> []
>
> > }
> > diff --git a/include/linux/leds.h b/include/linux/leds.h
> > index 2451962d1ec5..cba52714558f 100644
> > --- a/in
On Mon, 13 Jul 2020 01:15:44 +0200
Marek Behun wrote:
> On Mon, 13 Jul 2020 00:38:21 +0200
> Ondřej Jirman wrote:
>
> > So after trying to use this, this seems to disallow the use of multiple HW
> > triggers per LED. That's fine by me, because using one HW sysfs configured
> > trigger per LED t
On 12/07/2020 19:45, Amit Tomer wrote:
Hi,
> On Sun, Jul 12, 2020 at 11:00 PM Manivannan Sadhasivam
> wrote:
>>
>> On Thu, Jul 02, 2020 at 08:22:56PM +0530, Amit Singh Tomar wrote:
>>> This commit adds uSD support for Cubieboard7 board based on Actions Semi
>>> S700 SoC. SD0 is connected to uSD
On Mon, Jul 13, 2020 at 01:15:44AM +0200, Marek Behun wrote:
> On Mon, 13 Jul 2020 00:38:21 +0200
> Ondřej Jirman wrote:
>
> > Hello,
> >
> > On Sun, Jul 12, 2020 at 09:11:11PM +0200, Pavel Machek wrote:
> > > Hi!
> > >
> >
> > []
> >
> > > }
> > > diff --git a/include/linux/l
Hi Maxime,
On Wed, Jul 08, 2020 at 03:57:48PM +0200, Maxime Ripard wrote:
> On Wed, Jul 08, 2020 at 03:44:41PM +0200, Ondřej Jirman wrote:
> > >
[...]
> > > Yeah, but on the other hand, we regularly have people that come up and
> > > ask if a "legitimate" EPROBE_DEFER error message (as in: the d
On Sat, Jul 11, 2020 at 9:32 AM Paul Menzel wrote:
> Thank you very much for sending these changes.
>
> Do you have a branch, where your current work can be pulled from? Your
> branch on GitHub [1] seems 15 months old.
The clang-lto branch is rebased regularly on top of Linus' tree.
GitHub just l
On Sun, Jul 12, 2020 at 06:30:04AM -0500, Rob Landley wrote:
> On 7/12/20 6:11 AM, Alexander A. Klimov wrote:
> > Rationale:
> > Reduces attack surface on kernel devs opening the links for MITM
> > as HTTPS traffic is much harder to manipulate.
>
> Trimmed just to the one site without the self-sig
The pull request you sent on Sun, 12 Jul 2020 12:55:23 -0700:
> git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20200712
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5c38b7d3c48bbbec043913354b5974f998373efa
Thank you!
--
Deet-doot-dot, I am a bot.
ht
Ok, so rc4 was small, and now a week later, rc5 is large.
It's not _enormous_, but of all the 5.x kernels so far, this is the
rc5 with the most commits. So it's certainly not optimal. It was
actually very quiet the beginning of the week, but things picked up on
Friday. Like they do..
That said, a
Hi Bart,
> > Hello,
> > > >
> > > > Just a gentle reminder that I'd like some feedback.
> > > > Any suggestions here?
> > > If no-one objects, I think you can submit your patches for review as non-
> > RFC.
> > >
> > [PATCH v5 0/5] scsi: ufs: Add Host Performance Booster Support
> > ~~
> > It
Add information found in downstream kernels, to make the code less
magic. Fix comment spelling along the way.
Signed-off-by: Michał Mirosław
Reviewed-by: Dmitry Osipenko
Tested-by: Dmitry Osipenko
---
drivers/input/touchscreen/elants_i2c.c | 18 +-
1 file changed, 13 insertions
From: Dmitry Osipenko
eKTF3624 touchscreen firmware uses two variants of the reply opcodes for
reporting touch events: one is 0x63 (used by older firmware) and other is
0x66 (used by newer firmware). The 0x66 variant is equal to 0x63 of
eKTH3500, while 0x63 needs small adjustment of the touch pre
Board designers are now able to choose between all three supported
enet clocking methods, by changing the clocktree via the devicetree:
a) route enet_ref externally from pad to pad (the default):
no clock tree changes required
b) route internally on SoC from enet_ref
&fec {
assigned-clocks
201 - 300 of 572 matches
Mail list logo
