Support for this is being added to the driver but the original
patch forgot to add this documentation.
Signed-off-by: Benjamin Herrenschmidt
---
Documentation/devicetree/bindings/fsi/fsi-master-gpio.txt | 4
1 file changed, 4 insertions(+)
diff --git
Hi Geert
> > +_con {
> > + remote-endpoint = <_dw_hdmi0_out>;
> > +};
>
> I think the hdmi0 and hdmi0_con parts can be moved to salvator-common.dtsi.
> Can we do that now (with stubs?), or does this have to wait until r8a77965 has
> received HDMI sound support?
HDMI sound doesn't use
On Tue, 2018-05-29 at 11:30 +1000, Benjamin Herrenschmidt wrote:
> This adds support for an optional device-tree property that
> makes the driver skip all the delays around clocking the
> GPIOs and set it in the device-tree of common POWER9 based
> OpenPower platforms.
>
> This useful on chips
On Tue, 2018-05-29 at 11:30 +1000, Benjamin Herrenschmidt wrote:
> This adds support for an optional device-tree property that
> makes the driver skip all the delays around clocking the
> GPIOs and set it in the device-tree of common POWER9 based
> OpenPower platforms.
>
> This useful on chips
Abhishek Goel writes:
> @@ -215,7 +216,7 @@ static inline void add_powernv_state(int index, const
> char *name,
>u64 psscr_val, u64 psscr_mask)
> {
> strlcpy(powernv_states[index].name, name, CPUIDLE_NAME_LEN);
> -
Abhishek Goel writes:
> @@ -215,7 +216,7 @@ static inline void add_powernv_state(int index, const
> char *name,
>u64 psscr_val, u64 psscr_mask)
> {
> strlcpy(powernv_states[index].name, name, CPUIDLE_NAME_LEN);
> -
From: Jeremy Kerr
Reduce time spent with interrupts disabled by limiting the critical
sections to bitbanging FSI symbols. We only need to ensure exclusive use
of the bus for an entire transfer, not that the transfer be performed in
atomic context.
Signed-off-by: Jeremy Kerr
Signed-off-by:
From: Jeremy Kerr
Reduce time spent with interrupts disabled by limiting the critical
sections to bitbanging FSI symbols. We only need to ensure exclusive use
of the bus for an entire transfer, not that the transfer be performed in
atomic context.
Signed-off-by: Jeremy Kerr
Signed-off-by:
Remove calls to the empty and useless fsi_master_gpio_error()
function, and report CRC errors as "FSI_ERR_NO_SLAVE" when
reading an all 1's response.
Signed-off-by: Benjamin Herrenschmidt
---
drivers/fsi/fsi-master-gpio.c | 26 +-
1 file changed, 5 insertions(+), 21
Remove calls to the empty and useless fsi_master_gpio_error()
function, and report CRC errors as "FSI_ERR_NO_SLAVE" when
reading an all 1's response.
Signed-off-by: Benjamin Herrenschmidt
---
drivers/fsi/fsi-master-gpio.c | 26 +-
1 file changed, 5 insertions(+), 21
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 786b71f5b754273ccef6d9462e52062b3e1f9877
commit: 854e55ad289efe7991f0ada85d5846f5afb9 objtool, perf: Fix GCC 8
-Wrestrict error
date: 2 months ago
config: x86_64-randconfig-s4-05290856 (attached as
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 786b71f5b754273ccef6d9462e52062b3e1f9877
commit: 854e55ad289efe7991f0ada85d5846f5afb9 objtool, perf: Fix GCC 8
-Wrestrict error
date: 2 months ago
config: x86_64-randconfig-s4-05290856 (attached as
Colin,
> Trivial fix to spelling mistake in pm8001_printk message text; also I
> believe NOT_UNSUPPORTED should probably be NOT_SUPPORTED. Also fix the
> indent of the pm8001_printk statement.
Applied to 4.18/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Colin,
> Trivial fix to spelling mistake in pm8001_printk message text; also I
> believe NOT_UNSUPPORTED should probably be NOT_SUPPORTED. Also fix the
> indent of the pm8001_printk statement.
Applied to 4.18/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Colin,
> Trivial fix to spelling mistake in pr_err message text
Applied to 4.18/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
Colin,
> Trivial fix to spelling mistake in pr_err message text
Applied to 4.18/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
From: Jeremy Kerr
We currently use a spinlock (bit_lock) around operations that clock bits
out of the FSI bus, and a mutex to protect against simultaneous access
to the master.
This means that bit_lock isn't needed for mutual exlusion, only to
prevent timing issues when clocking bits out.
To
From: Jeremy Kerr
We currently use a spinlock (bit_lock) around operations that clock bits
out of the FSI bus, and a mutex to protect against simultaneous access
to the master.
This means that bit_lock isn't needed for mutual exlusion, only to
prevent timing issues when clocking bits out.
To
This adds support for an optional device-tree property that
makes the driver skip all the delays around clocking the
GPIOs and set it in the device-tree of common POWER9 based
OpenPower platforms.
This useful on chips like the AST2500 where the GPIO block is
running at a fairly low clock
This adds support for an optional device-tree property that
makes the driver skip all the delays around clocking the
GPIOs and set it in the device-tree of common POWER9 based
OpenPower platforms.
This useful on chips like the AST2500 where the GPIO block is
running at a fairly low clock
The FSI protocol defines two modes of recovery from CRC errors,
this implements both:
- If the device returns an ECRC (it detected a CRC error in the
command), then we simply issue the command again.
- If the master detects a CRC error in the response, we send
an E_POLL command which
The FSI protocol defines two modes of recovery from CRC errors,
this implements both:
- If the device returns an ECRC (it detected a CRC error in the
command), then we simply issue the command again.
- If the master detects a CRC error in the response, we send
an E_POLL command which
FSI_GPIO_PRIME_SLAVE_CLOCKS is the number of clocks if the
"idle" phase between the end of a response and the beginning
of the next one. It corresponds to tSendDelay in the FSI
specification.
The default value in the slave is 16 clocks. 100 is way overkill
and significantly reduces the driver
This series brings in a number of improvements to our FSI stack
(one of the service interfaces for communicating between a BMC chip and
our POWER processors).
The GPIO based "Soft FSI" performance is significantly improved, and
it's reliability as well.
The SBE fifo driver provides the interface
FSI_GPIO_PRIME_SLAVE_CLOCKS is the number of clocks if the
"idle" phase between the end of a response and the beginning
of the next one. It corresponds to tSendDelay in the FSI
specification.
The default value in the slave is 16 clocks. 100 is way overkill
and significantly reduces the driver
This series brings in a number of improvements to our FSI stack
(one of the service interfaces for communicating between a BMC chip and
our POWER processors).
The GPIO based "Soft FSI" performance is significantly improved, and
it's reliability as well.
The SBE fifo driver provides the interface
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
fs/read_write.c
between commit:
63ea46a359b2 ("vfs: dedupe: extract helper for a single dedup")
from the overlayfs tree and commit:
227627114799 ("fs: avoid fdput() after failed fdget() in
vfs_dedupe_file_range()")
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
fs/read_write.c
between commit:
63ea46a359b2 ("vfs: dedupe: extract helper for a single dedup")
from the overlayfs tree and commit:
227627114799 ("fs: avoid fdput() after failed fdget() in
vfs_dedupe_file_range()")
On 05/28/2018 09:12 PM, Waiman Long wrote:
> On 05/24/2018 06:28 AM, Juri Lelli wrote:
>> On 17/05/18 16:55, Waiman Long wrote:
>>
>> [...]
>>
>>> @@ -849,7 +860,12 @@ static void rebuild_sched_domains_locked(void)
>>> * passing doms with offlined cpu to partition_sched_domains().
>>> *
On 05/28/2018 09:12 PM, Waiman Long wrote:
> On 05/24/2018 06:28 AM, Juri Lelli wrote:
>> On 17/05/18 16:55, Waiman Long wrote:
>>
>> [...]
>>
>>> @@ -849,7 +860,12 @@ static void rebuild_sched_domains_locked(void)
>>> * passing doms with offlined cpu to partition_sched_domains().
>>> *
Mike,
I understand and appreciate your position but I still don't think the
arguments for enabling DM multipath are sufficiently compelling. The
whole point of ANA is for things to be plug and play without any admin
intervention whatsoever.
I also think we're getting ahead of ourselves a bit.
Mike,
I understand and appreciate your position but I still don't think the
arguments for enabling DM multipath are sufficiently compelling. The
whole point of ANA is for things to be plug and play without any admin
intervention whatsoever.
I also think we're getting ahead of ourselves a bit.
On Mon, 28 May 2018 01:32:58 +0900
Masami Hiramatsu wrote:
> Hi Steve,
>
> On Fri, 25 May 2018 17:13:53 -0400
> Steven Rostedt wrote:
>
> > On Fri, 25 May 2018 17:12:29 -0400
> > Steven Rostedt wrote:
> >
> >
> > > #!/bin/sh
> >
> > Hmm, I think I need to make this #!/bin/bash
> >
On Mon, 28 May 2018 01:32:58 +0900
Masami Hiramatsu wrote:
> Hi Steve,
>
> On Fri, 25 May 2018 17:13:53 -0400
> Steven Rostedt wrote:
>
> > On Fri, 25 May 2018 17:12:29 -0400
> > Steven Rostedt wrote:
> >
> >
> > > #!/bin/sh
> >
> > Hmm, I think I need to make this #!/bin/bash
> >
Hi Marcus,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on balbi-usb/next]
[also build test WARNING on v4.17-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Marcus,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on balbi-usb/next]
[also build test WARNING on v4.17-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Jungsub Shin:
> I suffered this problem below environments.
>
> OS : Ubuntu 18.04 LTS / 4.15.0-20-generic / 64bit
> AUFS module parameter : brs =3D 1 / allow_userns =3D N
> Mount command : mount -t aufs -o
Jungsub Shin:
> I suffered this problem below environments.
>
> OS : Ubuntu 18.04 LTS / 4.15.0-20-generic / 64bit
> AUFS module parameter : brs =3D 1 / allow_userns =3D N
> Mount command : mount -t aufs -o
On 05/24/2018 06:28 AM, Juri Lelli wrote:
> On 17/05/18 16:55, Waiman Long wrote:
>
> [...]
>
>> @@ -849,7 +860,12 @@ static void rebuild_sched_domains_locked(void)
>> * passing doms with offlined cpu to partition_sched_domains().
>> * Anyways, hotplug work item will rebuild sched
On 05/24/2018 06:28 AM, Juri Lelli wrote:
> On 17/05/18 16:55, Waiman Long wrote:
>
> [...]
>
>> @@ -849,7 +860,12 @@ static void rebuild_sched_domains_locked(void)
>> * passing doms with offlined cpu to partition_sched_domains().
>> * Anyways, hotplug work item will rebuild sched
Hi Himanshu
do you need any other information ?
Thanks
Jianchao
On 05/25/2018 02:48 PM, jianchao.wang wrote:
> Hi Himanshu
>
> I'm afraid I cannot provide you the vmcore file, it is from our customer.
> If any information needed in the vmcore, I could provide with you.
>
> In this scene,
Hi Himanshu
do you need any other information ?
Thanks
Jianchao
On 05/25/2018 02:48 PM, jianchao.wang wrote:
> Hi Himanshu
>
> I'm afraid I cannot provide you the vmcore file, it is from our customer.
> If any information needed in the vmcore, I could provide with you.
>
> In this scene,
This patch adds a frontend driver for the Socionext SC1501A series
and Socionext MN88443x ISDB-S/T demodulators.
Signed-off-by: Katsuhiro Suzuki
---
Changes since v1:
- Fix sparse warning about type of constant
- Use div_s64() instead of divide operator
---
This patch adds a frontend driver for the Socionext SC1501A series
and Socionext MN88443x ISDB-S/T demodulators.
Signed-off-by: Katsuhiro Suzuki
---
Changes since v1:
- Fix sparse warning about type of constant
- Use div_s64() instead of divide operator
---
From: Arnd Bergmann Sent: 2018年5月28日 23:50
> While compile-testing on arm64 with gcc-8.1, I ran into a build diagnostic:
>
> drivers/net/ethernet/freescale/fec_main.c: In function 'fec_probe':
> drivers/net/ethernet/freescale/fec_main.c:3517:25: error: '%d' directive
> writing between 1 and 10
From: Arnd Bergmann Sent: 2018年5月28日 23:50
> While compile-testing on arm64 with gcc-8.1, I ran into a build diagnostic:
>
> drivers/net/ethernet/freescale/fec_main.c: In function 'fec_probe':
> drivers/net/ethernet/freescale/fec_main.c:3517:25: error: '%d' directive
> writing between 1 and 10
This patch fixes crystal frequency setting when power on this device.
Signed-off-by: Katsuhiro Suzuki
Acked-by: Abylay Ospan
---
Changes from before:
- Add Abylay's Ack
---
drivers/media/dvb-frontends/helene.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
This patch fixes crystal frequency setting when power on this device.
Signed-off-by: Katsuhiro Suzuki
Acked-by: Abylay Ospan
---
Changes from before:
- Add Abylay's Ack
---
drivers/media/dvb-frontends/helene.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
This patch fixes tuning frequency of satellite to kHz. That as same
as terrestrial one.
Signed-off-by: Katsuhiro Suzuki
---
drivers/media/dvb-frontends/helene.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/dvb-frontends/helene.c
This patch fixes tuning frequency of satellite to kHz. That as same
as terrestrial one.
Signed-off-by: Katsuhiro Suzuki
---
drivers/media/dvb-frontends/helene.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/dvb-frontends/helene.c
On 05/22/2018 09:53 AM, Juri Lelli wrote:
> Hi,
>
> On 17/05/18 16:55, Waiman Long wrote:
>> This patch enables us to report sched domain generation information.
>>
>> If DYNAMIC_DEBUG is enabled, issuing the following command
>>
>> echo "file cpuset.c +p" >
On 05/22/2018 09:53 AM, Juri Lelli wrote:
> Hi,
>
> On 17/05/18 16:55, Waiman Long wrote:
>> This patch enables us to report sched domain generation information.
>>
>> If DYNAMIC_DEBUG is enabled, issuing the following command
>>
>> echo "file cpuset.c +p" >
On 05/22/2018 08:57 AM, Juri Lelli wrote:
> Hi,
>
> On 17/05/18 16:55, Waiman Long wrote:
>
> [...]
>
>> /**
>> + * update_isolated_cpumask - update the isolated_cpus mask of parent cpuset
>> + * @cpuset: The cpuset that requests CPU isolation
>> + * @oldmask: The old isolated cpumask to be
On 05/22/2018 08:57 AM, Juri Lelli wrote:
> Hi,
>
> On 17/05/18 16:55, Waiman Long wrote:
>
> [...]
>
>> /**
>> + * update_isolated_cpumask - update the isolated_cpus mask of parent cpuset
>> + * @cpuset: The cpuset that requests CPU isolation
>> + * @oldmask: The old isolated cpumask to be
On 05/28/2018 03:00 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.16.13 release.
There are 272 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.
Responses should be
On 05/28/2018 03:00 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.16.13 release.
There are 272 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.
Responses should be
On 05/28/2018 02:56 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.45 release.
There are 496 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.
Responses should be
On 05/28/2018 02:56 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.45 release.
There are 496 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.
Responses should be
On 05/28/2018 02:58 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.104 release.
There are 329 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.
Responses should be
On 05/28/2018 02:58 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.104 release.
There are 329 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.
Responses should be
On 05/28/2018 02:59 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.134 release.
There are 268 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.
Responses should be
On 05/28/2018 02:59 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.134 release.
There are 268 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.
Responses should be
On Tue, May 29, 2018 at 12:36 AM, Eric Dumazet wrote:
> On Mon, May 28, 2018 at 8:36 AM Yafang Shao wrote:
>
>> This is additional to the commit ea1627c20c34 ("tcp: minor optimizations
> around tcp_hdr() usage").
>> At this point, skb->data is same with tcp_hdr() as tcp header has not
>> been
On 05/28/2018 03:00 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.111 release.
There are 185 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.
Responses should
On Tue, May 29, 2018 at 12:36 AM, Eric Dumazet wrote:
> On Mon, May 28, 2018 at 8:36 AM Yafang Shao wrote:
>
>> This is additional to the commit ea1627c20c34 ("tcp: minor optimizations
> around tcp_hdr() usage").
>> At this point, skb->data is same with tcp_hdr() as tcp header has not
>> been
On 05/28/2018 03:00 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.111 release.
There are 185 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.
Responses should
On Fri, May 25, 2018 at 07:42:10PM +0900, J. R. Okajima wrote:
> Jungsub Shin:
> > I know that almost mount option short and page size is enough to
> > contain almost mount options. but because of options for
> > unionfs(overlay, aufs), lenght of mount option could be exceed it
> > and cut.
> >
>
On Fri, May 25, 2018 at 07:42:10PM +0900, J. R. Okajima wrote:
> Jungsub Shin:
> > I know that almost mount option short and page size is enough to
> > contain almost mount options. but because of options for
> > unionfs(overlay, aufs), lenght of mount option could be exceed it
> > and cut.
> >
>
Hi Mathieu,
On Mon, May 28, 2018 at 04:13:47PM -0600, Mathieu Poirier wrote:
> Leo and/or Robert,
>
> On Mon, May 28, 2018 at 04:45:00PM +0800, Leo Yan wrote:
> > Commit e573e978fb12 ("perf cs-etm: Inject capabilitity for CoreSight
> > traces") reworks the samples generation flow from CoreSight
Hi Mathieu,
On Mon, May 28, 2018 at 04:13:47PM -0600, Mathieu Poirier wrote:
> Leo and/or Robert,
>
> On Mon, May 28, 2018 at 04:45:00PM +0800, Leo Yan wrote:
> > Commit e573e978fb12 ("perf cs-etm: Inject capabilitity for CoreSight
> > traces") reworks the samples generation flow from CoreSight
>
> Before the guest finishes the device initialization, the device can be
> removed anytime by the host, and after that the host won't respond to
> the guest's request, so the guest should be prepared to handle this
> case.
>
> Signed-off-by: Dexuan Cui
> Cc: Stephen Hemminger
> Cc: K. Y.
>
> Before the guest finishes the device initialization, the device can be
> removed anytime by the host, and after that the host won't respond to
> the guest's request, so the guest should be prepared to handle this
> case.
>
> Signed-off-by: Dexuan Cui
> Cc: Stephen Hemminger
> Cc: K. Y.
On 29.05.2018 02:48, Dmitry Osipenko wrote:
> inversion=true" if mask has form of 0x11000111, though this could be not
For clarity: I meant s/0x11000111/0xFF000FFF/.
On 29.05.2018 02:48, Dmitry Osipenko wrote:
> inversion=true" if mask has form of 0x11000111, though this could be not
For clarity: I meant s/0x11000111/0xFF000FFF/.
On Tue, 2018-05-29 at 09:48 +1000, Benjamin Herrenschmidt wrote:
> > Well it's not supposed to be much slower for the static case.
> >
> > vhost has a cache so should be fine.
> >
> > A while ago Paolo implemented a translation cache which should be
> > perfect for this case - most of the code
On Tue, 2018-05-29 at 09:48 +1000, Benjamin Herrenschmidt wrote:
> > Well it's not supposed to be much slower for the static case.
> >
> > vhost has a cache so should be fine.
> >
> > A while ago Paolo implemented a translation cache which should be
> > perfect for this case - most of the code
On 28.05.2018 16:15, Ville Syrjälä wrote:
> On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote:
>> Color keying is the action of replacing pixels matching a given color
>> (or range of colors) with transparent pixels in an overlay when
>> performing blitting. Depending on the hardware
On 28.05.2018 16:15, Ville Syrjälä wrote:
> On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote:
>> Color keying is the action of replacing pixels matching a given color
>> (or range of colors) with transparent pixels in an overlay when
>> performing blitting. Depending on the hardware
From: Hoeun Ryu
Make printk_safe_flush() safe in NMI context. And printk_safe_flush_on_panic()
is
folded into this function. The prototype of printk_safe_flush() is changed to
"void printk_safe_flush(bool panic)".
nmi_trigger_cpumask_backtrace() can be called in NMI context. For example the
From: Hoeun Ryu
Make printk_safe_flush() safe in NMI context. And printk_safe_flush_on_panic()
is
folded into this function. The prototype of printk_safe_flush() is changed to
"void printk_safe_flush(bool panic)".
nmi_trigger_cpumask_backtrace() can be called in NMI context. For example the
Hi Miklos,
Today's linux-next merge of the overlayfs tree got a conflict in:
fs/btrfs/ioctl.c
between commit:
0b4dc087e29a ("Btrfs: dedupe_file_range ioctl: remove 16MiB restriction")
from the btrfs-kdave tree and commits:
83d499febfac ("vfs: dedpue: return loff_t")
7765f19ed5f9
Hi Miklos,
Today's linux-next merge of the overlayfs tree got a conflict in:
fs/btrfs/ioctl.c
between commit:
0b4dc087e29a ("Btrfs: dedupe_file_range ioctl: remove 16MiB restriction")
from the btrfs-kdave tree and commits:
83d499febfac ("vfs: dedpue: return loff_t")
7765f19ed5f9
On Fri, 2018-05-25 at 18:07 +0200, Arnd Bergmann wrote:
> Without that option, we run into a link failure:
>
> drivers/usb/gadget/udc/aspeed-vhub/hub.o: In function
> `ast_vhub_std_hub_request':
> hub.c:(.text+0x5b0): undefined reference to `usb_gadget_get_string'
Thanks ! I hadn't realized
On Fri, 2018-05-25 at 20:45 +0300, Michael S. Tsirkin wrote:
> On Thu, May 24, 2018 at 08:27:04AM +1000, Benjamin Herrenschmidt wrote:
> > On Wed, 2018-05-23 at 21:50 +0300, Michael S. Tsirkin wrote:
> >
> > > I re-read that discussion and I'm still unclear on the
> > > original question, since I
On Fri, 2018-05-25 at 18:07 +0200, Arnd Bergmann wrote:
> Without that option, we run into a link failure:
>
> drivers/usb/gadget/udc/aspeed-vhub/hub.o: In function
> `ast_vhub_std_hub_request':
> hub.c:(.text+0x5b0): undefined reference to `usb_gadget_get_string'
Thanks ! I hadn't realized
On Fri, 2018-05-25 at 20:45 +0300, Michael S. Tsirkin wrote:
> On Thu, May 24, 2018 at 08:27:04AM +1000, Benjamin Herrenschmidt wrote:
> > On Wed, 2018-05-23 at 21:50 +0300, Michael S. Tsirkin wrote:
> >
> > > I re-read that discussion and I'm still unclear on the
> > > original question, since I
Hello,
syzbot found the following crash on:
HEAD commit:861d9dd37526 Merge tag 'kbuild-fixes-v4.17-2' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10bffd0f80
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02
Hello,
syzbot found the following crash on:
HEAD commit:861d9dd37526 Merge tag 'kbuild-fixes-v4.17-2' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10bffd0f80
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02
It is up to a driver to implement shutdown() callback. If shutdown()
callback is not implemented, PCI device can have pending interrupt and
even do DMA transactions while the system is going down.
If kexec is in use, this can damage the newly booting kexec kernel
or even prevent it from booting
It is up to a driver to implement shutdown() callback. If shutdown()
callback is not implemented, PCI device can have pending interrupt and
even do DMA transactions while the system is going down.
If kexec is in use, this can damage the newly booting kexec kernel
or even prevent it from booting
Hello,
syzbot found the following crash on:
HEAD commit:7a1a98c171ea Merge branch 'bpf-sendmsg-hook'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=131f406780
kernel config: https://syzkaller.appspot.com/x/.config?x=e4078980b886800c
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:7a1a98c171ea Merge branch 'bpf-sendmsg-hook'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=131f406780
kernel config: https://syzkaller.appspot.com/x/.config?x=e4078980b886800c
dashboard link:
On Sat, May 26, 2018 at 6:43 AM, David Miller wrote:
> From: Jon Maxwell
> Date: Fri, 25 May 2018 07:38:29 +1000
>
>> Fixup the checksum for CHECKSUM_COMPLETE when pulling skbs on RX path.
>> Otherwise we get splats when tc mirred is used to redirect packets to ifb.
>>
>> Before fix:
>>
>> nic:
On Sat, May 26, 2018 at 6:43 AM, David Miller wrote:
> From: Jon Maxwell
> Date: Fri, 25 May 2018 07:38:29 +1000
>
>> Fixup the checksum for CHECKSUM_COMPLETE when pulling skbs on RX path.
>> Otherwise we get splats when tc mirred is used to redirect packets to ifb.
>>
>> Before fix:
>>
>> nic:
The return value of flush_sigqueue_mask() is never checked anywhere.
Signed-off-by: Christian Brauner
---
v0->v1:
* patch introduced
---
kernel/signal.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index c382ac346a81..0959965b523d
legacy_queue() already behaves like a boolean function. Let's actually
declare it as such too.
Signed-off-by: Christian Brauner
---
v0->v1:
* patch introduced
---
kernel/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index
The goto is not needed and does not add any clarity. Simply return -EINVAL
on unexpected sigset_t struct size directly.
Signed-off-by: Christian Brauner
---
v0->v1:
* patch unchanged
---
kernel/signal.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git
sig_task_ignored() already behaves like a boolean function. Let's actually
declare it as such too.
Signed-off-by: Christian Brauner
---
v0->v1:
* patch introduced
---
kernel/signal.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index
wants_signal() already behaves like a boolean function. Let's actually
declare it as such too.
Signed-off-by: Christian Brauner
---
v0->v1:
* patch introduced
---
kernel/signal.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
The return value of flush_sigqueue_mask() is never checked anywhere.
Signed-off-by: Christian Brauner
---
v0->v1:
* patch introduced
---
kernel/signal.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index c382ac346a81..0959965b523d
201 - 300 of 4398 matches
Mail list logo
