On 17-09-18, 11:17, Anson Huang wrote:
> On i.MX6UL/i.MX6ULL, accessing OCOTP directly is wrong because
> the ocotp clock needs to be enabled first. Add support for reading
> OCOTP through the nvmem API, and keep the old method there to
> support old dtb.
>
> Signed-off-by: Anson Huang
> ---
>
On 17-09-18, 11:17, Anson Huang wrote:
> On i.MX6UL/i.MX6ULL, accessing OCOTP directly is wrong because
> the ocotp clock needs to be enabled first. Add support for reading
> OCOTP through the nvmem API, and keep the old method there to
> support old dtb.
>
> Signed-off-by: Anson Huang
> ---
>
On 01.10.2018 03:04, Stephen Rothwell wrote:
> Commit
> f17bbdb5eea2 ("parisc: Remove PTE load and fault check from L2_ptep macro")
> is missing a Signed-off-by from its committer.
Fixed now.
Thanks!
Helge
signature.asc
Description: OpenPGP digital signature
On 01.10.2018 03:04, Stephen Rothwell wrote:
> Commit
> f17bbdb5eea2 ("parisc: Remove PTE load and fault check from L2_ptep macro")
> is missing a Signed-off-by from its committer.
Fixed now.
Thanks!
Helge
signature.asc
Description: OpenPGP digital signature
Hi Pavel,
On Sun, 30 Sep 2018 22:16:42 +0200
Pavel Machek wrote:
> On Mon 2018-09-17 07:20:35, Andreas Kemnade wrote:
> > the charging current uses unsigned int variables, if we step back
> > if the current is still low, we would run into negative which
> > means setting the target to a huge
Hi Pavel,
On Sun, 30 Sep 2018 22:16:42 +0200
Pavel Machek wrote:
> On Mon 2018-09-17 07:20:35, Andreas Kemnade wrote:
> > the charging current uses unsigned int variables, if we step back
> > if the current is still low, we would run into negative which
> > means setting the target to a huge
On 14-09-18, 10:59, Anson Huang wrote:
> On i.MX6UL/i.MX6ULL, accessing OCOTP directly is wrong because
> the ocotp clock needs to be enabled first. Add support for reading
> OCOTP through the nvmem API instead.
>
> Signed-off-by: Anson Huang
> ---
> drivers/cpufreq/imx6q-cpufreq.c | 39
On 14-09-18, 10:59, Anson Huang wrote:
> On i.MX6UL/i.MX6ULL, accessing OCOTP directly is wrong because
> the ocotp clock needs to be enabled first. Add support for reading
> OCOTP through the nvmem API instead.
>
> Signed-off-by: Anson Huang
> ---
> drivers/cpufreq/imx6q-cpufreq.c | 39
On (09/29/18 20:13), Sergey Senozhatsky wrote:
> We used to flush "incomplete" cont lines (fragments) from console_unlock().
>
> void console_unlock(void)
> {
> ...
> /* flush buffered message fragment immediately to console */
> console_cont_flush(text, sizeof(text));
> again:
>
On (09/29/18 20:13), Sergey Senozhatsky wrote:
> We used to flush "incomplete" cont lines (fragments) from console_unlock().
>
> void console_unlock(void)
> {
> ...
> /* flush buffered message fragment immediately to console */
> console_cont_flush(text, sizeof(text));
> again:
>
On 2018-10-01, Dave Chinner wrote:
> > I've added some selftests for this, but it's not clear to me whether
> > they should live here or in xfstests (as far as I can tell there are no
> > other VFS tests in selftests, while there are some tests that look like
> > generic VFS tests in xfstests).
On 2018-10-01, Dave Chinner wrote:
> > I've added some selftests for this, but it's not clear to me whether
> > they should live here or in xfstests (as far as I can tell there are no
> > other VFS tests in selftests, while there are some tests that look like
> > generic VFS tests in xfstests).
On 2018-09-29, Jann Horn wrote:
> The problem is what happens if a folder you are walking through is
> concurrently moved out of the chroot. Consider the following scenario:
>
> You attempt to open "C/../../etc/passwd" under the root "/A/B".
> Something else concurrently moves /A/B/C to /A/C.
On 2018-09-29, Jann Horn wrote:
> The problem is what happens if a folder you are walking through is
> concurrently moved out of the chroot. Consider the following scenario:
>
> You attempt to open "C/../../etc/passwd" under the root "/A/B".
> Something else concurrently moves /A/B/C to /A/C.
Hi Milian,
Seems this has a regression:
With acme/perf/urgent:
$ ./perf record -e cycles:u --call-graph=dwarf ls
$ ./perf script
ls 13585 602082.534478: 28032 cycles:u:
1f1f4 __GI___tunables_init+0xd3dc00a4
(/usr/lib64/ld-2.26.so)
Hi Milian,
Seems this has a regression:
With acme/perf/urgent:
$ ./perf record -e cycles:u --call-graph=dwarf ls
$ ./perf script
ls 13585 602082.534478: 28032 cycles:u:
1f1f4 __GI___tunables_init+0xd3dc00a4
(/usr/lib64/ld-2.26.so)
From: Jonathan Marek
This patch adds an of_match for the usb-otg-vbus regulator to
bq24190_charger.
Signed-off-by: Jonathan Marek
Signed-off-by: Brian Masney
---
drivers/power/supply/bq24190_charger.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/power/supply/bq24190_charger.c
Add support for the ti,bq24192 variant and a child node for the
usb-otg-vbus regulator.
Signed-off-by: Brian Masney
---
Documentation/devicetree/bindings/power/supply/bq24190.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
From: Jonathan Marek
This patch adds an of_match for the usb-otg-vbus regulator to
bq24190_charger.
Signed-off-by: Jonathan Marek
Signed-off-by: Brian Masney
---
drivers/power/supply/bq24190_charger.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/power/supply/bq24190_charger.c
Add support for the ti,bq24192 variant and a child node for the
usb-otg-vbus regulator.
Signed-off-by: Brian Masney
---
Documentation/devicetree/bindings/power/supply/bq24190.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
This patch set adds USB OTG support for the LG Nexus 5 (hammerhead)
phone. My only question is related to patch #4 where the GPIO support
is added to bq24190_charger. Based on the information in the device tree
binding Documentation/devicetree/bindings/power/supply/bq24190.txt, I
should be using a
This patch set adds USB OTG support for the LG Nexus 5 (hammerhead)
phone. My only question is related to patch #4 where the GPIO support
is added to bq24190_charger. Based on the information in the device tree
binding Documentation/devicetree/bindings/power/supply/bq24190.txt, I
should be using a
From: Jonathan Marek
Add the device tree bindings for USB OTG support. Driver was tested
using on a LG Nexus 5 (hammerhead) phone.
Signed-off-by: Jonathan Marek
Signed-off-by: Brian Masney
Tested-by: Brian Masney
---
See my cover letter for a question about how I can convert this patch
over
From: Jonathan Marek
This patch adds support for the bq24192 variant to bq24190_charger.
Signed-off-by: Jonathan Marek
Signed-off-by: Brian Masney
---
drivers/power/supply/bq24190_charger.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
From: Jonathan Marek
Add extcon support so that we can notify USB drivers of cable state
changes. This also adds support for an optional GPIO that is changed
depending on the cable state.
This patch makes the USB OTG work correctly on a LG Nexus 5
(hammerhead) phone.
Signed-off-by: Jonathan
From: Jonathan Marek
This patch adds support for the bq24192 variant to bq24190_charger.
Signed-off-by: Jonathan Marek
Signed-off-by: Brian Masney
---
drivers/power/supply/bq24190_charger.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
From: Jonathan Marek
Add extcon support so that we can notify USB drivers of cable state
changes. This also adds support for an optional GPIO that is changed
depending on the cable state.
This patch makes the USB OTG work correctly on a LG Nexus 5
(hammerhead) phone.
Signed-off-by: Jonathan
From: Jonathan Marek
Add the device tree bindings for USB OTG support. Driver was tested
using on a LG Nexus 5 (hammerhead) phone.
Signed-off-by: Jonathan Marek
Signed-off-by: Brian Masney
Tested-by: Brian Masney
---
See my cover letter for a question about how I can convert this patch
over
syzbot has found a reproducer for the following crash on:
HEAD commit:17b57b1883c1 Linux 4.19-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17920a7e40
kernel config: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb
dashboard link:
syzbot has found a reproducer for the following crash on:
HEAD commit:17b57b1883c1 Linux 4.19-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17920a7e40
kernel config: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb
dashboard link:
On 21-08-18, 22:10, Dave Gerlach wrote:
Please ping people back if you haven't received a response for too long. Sorry
that I missed getting to this at an earlier point of time.
> Currently the _of_add_opp_table_v2 call loops through the OPP nodes in
> the operating-points-v2 table in the device
On 21-08-18, 22:10, Dave Gerlach wrote:
Please ping people back if you haven't received a response for too long. Sorry
that I missed getting to this at an earlier point of time.
> Currently the _of_add_opp_table_v2 call loops through the OPP nodes in
> the operating-points-v2 table in the device
On Sun, Sep 30, 2018 at 01:30:11PM -0700, Joe Perches wrote:
> On Sun, 2018-09-30 at 21:52 +0200, Michael Straube wrote:
> > Cleanup all inconsistent indenting reported by smatch.
>
> There are also some others like:
>
> drivers/staging/rtl8188eu/core/rtw_mlme.c:1752:
On Sun, Sep 30, 2018 at 01:30:11PM -0700, Joe Perches wrote:
> On Sun, 2018-09-30 at 21:52 +0200, Michael Straube wrote:
> > Cleanup all inconsistent indenting reported by smatch.
>
> There are also some others like:
>
> drivers/staging/rtl8188eu/core/rtw_mlme.c:1752:
On Sun, Sep 30, 2018 at 4:47 PM Laurent Vivier wrote:
>
> This series introduces a new namespace for binfmt_misc.
>
This seems conceptually quite reasonable, but I'm wondering if the
number of namespace types is getting out of hand given the current
API. Should we be considering whether we need
On Sun, Sep 30, 2018 at 4:47 PM Laurent Vivier wrote:
>
> This series introduces a new namespace for binfmt_misc.
>
This seems conceptually quite reasonable, but I'm wondering if the
number of namespace types is getting out of hand given the current
API. Should we be considering whether we need
Joe Perches writes:
> On Sun, 2018-09-30 at 20:29 +0200, Rick Veens wrote:
>> The following:
>> bool efuse_re_pg_sec1flag;
>> u8 efuse_re_pg_data[8];
>> are not referenced anywhere in the rtlwifi code.
>>
>> Signed-off-by: Rick Veens
>> ---
>> drivers/staging/rtlwifi/wifi.h | 4
>
>
Joe Perches writes:
> On Sun, 2018-09-30 at 20:29 +0200, Rick Veens wrote:
>> The following:
>> bool efuse_re_pg_sec1flag;
>> u8 efuse_re_pg_data[8];
>> are not referenced anywhere in the rtlwifi code.
>>
>> Signed-off-by: Rick Veens
>> ---
>> drivers/staging/rtlwifi/wifi.h | 4
>
>
On Sat, Sep 29, 2018 at 08:34:50PM +1000, Aleksa Sarai wrote:
> I've added some selftests for this, but it's not clear to me whether
> they should live here or in xfstests (as far as I can tell there are no
> other VFS tests in selftests, while there are some tests that look like
> generic VFS
On Sat, Sep 29, 2018 at 08:34:50PM +1000, Aleksa Sarai wrote:
> I've added some selftests for this, but it's not clear to me whether
> they should live here or in xfstests (as far as I can tell there are no
> other VFS tests in selftests, while there are some tests that look like
> generic VFS
As has been stated in easily accessible terms elsewhere:
"Most courts hold that simple, non-exclusive licenses with unspecified
durations that are silent on revocability are revocable at will. This
means that the licensor may terminate the license at any time, with or
without cause." +
As has been stated in easily accessible terms elsewhere:
"Most courts hold that simple, non-exclusive licenses with unspecified
durations that are silent on revocability are revocable at will. This
means that the licensor may terminate the license at any time, with or
without cause." +
"You are easily replacable" Bruce Peren's message to past contributors.:
"Any actual kernel developers who leave will be replaced by one of the
other 4000 active this year. If they have been vociferous about their
rights to entirely unlimited conduct (and all of the side-issues that
seem to
"You are easily replacable" Bruce Peren's message to past contributors.:
"Any actual kernel developers who leave will be replaced by one of the
other 4000 active this year. If they have been vociferous about their
rights to entirely unlimited conduct (and all of the side-issues that
seem to
Gnu GPL version 2, section 0:
"Each licensee is addressed as "you". "
The "you" is not referring to the licensor (copyright owner). It is
referring to the licensees and then future
sub-licensees/additional-licensees receiving the work from said previous
licensee.
It is independently clear
Gnu GPL version 2, section 0:
"Each licensee is addressed as "you". "
The "you" is not referring to the licensor (copyright owner). It is
referring to the licensees and then future
sub-licensees/additional-licensees receiving the work from said previous
licensee.
It is independently clear
The paramount reason Eben Moglen has the FSF accepting contributions
only with copyright assignment is because the grantor of a license that
is a gratuity (no consideration (read: usually money) given) can remove
the permission regarding the use of his property at his pleasure.
(Regardless of
The paramount reason Eben Moglen has the FSF accepting contributions
only with copyright assignment is because the grantor of a license that
is a gratuity (no consideration (read: usually money) given) can remove
the permission regarding the use of his property at his pleasure.
(Regardless of
The paramount reason Eben Moglen has the FSF accepting contributions
only with copyright assignment is because the grantor of a license that
is a gratuity (no consideration (read: usually money) given) can remove
the permission regarding the use of his property at his pleasure.
(Regardless of
The paramount reason Eben Moglen has the FSF accepting contributions
only with copyright assignment is because the grantor of a license that
is a gratuity (no consideration (read: usually money) given) can remove
the permission regarding the use of his property at his pleasure.
(Regardless of
On Fri, Sep 28, 2018 at 06:52:13PM -0500, Rob Herring wrote:
> On Fri, Sep 28, 2018 at 4:36 AM Song Qiang wrote:
> >
> > On Wed, Sep 26, 2018 at 05:46:18PM -0500, Rob Herring wrote:
> > > On Sat, Sep 22, 2018 at 04:05:23PM +0100, Jonathan Cameron wrote:
> > > > On Tue, 18 Sep 2018 16:24:22 +0800
On Fri, Sep 28, 2018 at 06:52:13PM -0500, Rob Herring wrote:
> On Fri, Sep 28, 2018 at 4:36 AM Song Qiang wrote:
> >
> > On Wed, Sep 26, 2018 at 05:46:18PM -0500, Rob Herring wrote:
> > > On Sat, Sep 22, 2018 at 04:05:23PM +0100, Jonathan Cameron wrote:
> > > > On Tue, 18 Sep 2018 16:24:22 +0800
Raydium touchpanel (2386:4B33) sometimes does not workin desktop session
although it works in display manager.
During user logging, the display manager exits, close the HID device,
then the device gets runtime suspended and powered off. The desktop
session begins shortly after, opens the HID
Raydium touchpanel (2386:4B33) sometimes does not workin desktop session
although it works in display manager.
During user logging, the display manager exits, close the HID device,
then the device gets runtime suspended and powered off. The desktop
session begins shortly after, opens the HID
On Apple machines, plugging-in or unplugging the power triggers a GPE
for the EC. Since these machines expose an SBS device, this GPE ends
up triggering the acpi_sbs_callback(). This in turn tries to get the
status of the SBS charger. However, on MBP13,* and MBP14,* machines,
performing the
There was a small race when removing the sbshc module where
smbus_alarm() had queued acpi_smbus_callback() for deferred execution
but it hadn't been run yet, so that when it did run hc had been freed
and the module unloaded, resulting in an invalid paging request.
A similar race existed when
On Apple machines, plugging-in or unplugging the power triggers a GPE
for the EC. Since these machines expose an SBS device, this GPE ends
up triggering the acpi_sbs_callback(). This in turn tries to get the
status of the SBS charger. However, on MBP13,* and MBP14,* machines,
performing the
There was a small race when removing the sbshc module where
smbus_alarm() had queued acpi_smbus_callback() for deferred execution
but it hadn't been run yet, so that when it did run hc had been freed
and the module unloaded, resulting in an invalid paging request.
A similar race existed when
On (10/01/18 11:37), Sergey Senozhatsky wrote:
> If we are about to have a list of printk buffers then we probably can
> define a list of NR_CPUS cont buffers. And we probably can reuse the
> existing struct cont for buffered printk, having 2 different struct-s
> for the same thing - struct cont
On Sat, Sep 29, 2018 at 11:20 PM kernel test robot
wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 ("flow_dissector: implements
> flow dissector BPF hook")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git
On (10/01/18 11:37), Sergey Senozhatsky wrote:
> If we are about to have a list of printk buffers then we probably can
> define a list of NR_CPUS cont buffers. And we probably can reuse the
> existing struct cont for buffered printk, having 2 different struct-s
> for the same thing - struct cont
On Sat, Sep 29, 2018 at 11:20 PM kernel test robot
wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 ("flow_dissector: implements
> flow dissector BPF hook")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git
On (09/29/18 20:15), Tetsuo Handa wrote:
>
> Because there is no guarantee that memory information is dumped under the
> oom_lock mutex. The oom_lock is held when calling out_of_memory(), and it
> cannot be held when reporting GFP_ATOMIC memory allocation failures.
IOW, static pr_line buffer
On (09/29/18 20:15), Tetsuo Handa wrote:
>
> Because there is no guarantee that memory information is dumped under the
> oom_lock mutex. The oom_lock is held when calling out_of_memory(), and it
> cannot be held when reporting GFP_ATOMIC memory allocation failures.
IOW, static pr_line buffer
Hi,
On Sep 30 2018 12:03, Connor McAdams wrote:
This patch adds a control for 600 ohm gain on the Sound Blaster ZxR.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 44 ++--
1 file changed, 42 insertions(+), 2 deletions(-)
diff
Hi,
On Sep 30 2018 12:03, Connor McAdams wrote:
This patch adds a control for 600 ohm gain on the Sound Blaster ZxR.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c | 44 ++--
1 file changed, 42 insertions(+), 2 deletions(-)
diff
Hi,
On Sep 30 2018 12:03, Connor McAdams wrote:
This patch adds separate hda_codec_ops for the DBPro daughter board, as
it behaves more like a generic HDA codec than the other ca0132 cards,
despite having a ca0132 on board.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c |
Hi,
On Sep 30 2018 12:03, Connor McAdams wrote:
This patch adds separate hda_codec_ops for the DBPro daughter board, as
it behaves more like a generic HDA codec than the other ca0132 cards,
despite having a ca0132 on board.
Signed-off-by: Connor McAdams
---
sound/pci/hda/patch_ca0132.c |
This timer is used by SMP system and use mfcr/mtcr instruction
to access the regs.
Changelog:
- Remove #define CPUHP_AP_CSKY_TIMER_STARTING
- Add CPUHP_AP_CSKY_TIMER_STARTING in cpuhotplug.h
- Support csky mp timer alpha version.
- Just use low-counter with 32bit width as clocksource.
-
This timer is used by SMP system and use mfcr/mtcr instruction
to access the regs.
Changelog:
- Remove #define CPUHP_AP_CSKY_TIMER_STARTING
- Add CPUHP_AP_CSKY_TIMER_STARTING in cpuhotplug.h
- Support csky mp timer alpha version.
- Just use low-counter with 32bit width as clocksource.
-
>From "PATCH V5 00/30] C-SKY(csky) Linux Kernel Port" I seperated the
drivers from the patchset. I've sent driver patches with "V5 V6 V7 V8".
Now is V9. The changelog is in every patch.
Perhaps I should seperate driver patchset earlier and the csky port patchset
is too big now.
Any feedback is
On 2018-10-1 9:27, Jaegeuk Kim wrote:
> On 10/01, Chao Yu wrote:
>> On 2018-10-1 7:58, Jaegeuk Kim wrote:
>>> On 09/29, Chao Yu wrote:
On 2018/9/29 7:40, Jaegeuk Kim wrote:
> Testing other fix.
>
> ---
> fs/f2fs/checkpoint.c | 7 +++
> fs/f2fs/f2fs.h | 1 +
>From "PATCH V5 00/30] C-SKY(csky) Linux Kernel Port" I seperated the
drivers from the patchset. I've sent driver patches with "V5 V6 V7 V8".
Now is V9. The changelog is in every patch.
Perhaps I should seperate driver patchset earlier and the csky port patchset
is too big now.
Any feedback is
On 2018-10-1 9:27, Jaegeuk Kim wrote:
> On 10/01, Chao Yu wrote:
>> On 2018-10-1 7:58, Jaegeuk Kim wrote:
>>> On 09/29, Chao Yu wrote:
On 2018/9/29 7:40, Jaegeuk Kim wrote:
> Testing other fix.
>
> ---
> fs/f2fs/checkpoint.c | 7 +++
> fs/f2fs/f2fs.h | 1 +
Changelog:
- Add COMIPLE_TEST in Kconfig
- no cast is needed for "struct clock_event_device *ce = dev"
- remove: extra space after (u64)
- Add License and Copyright
- Use timer-of framework
- Change name with upstream feedback
- Use clksource_mmio framework
Signed-off-by: Guo Ren
---
Dt-bindings doc about C-SKY Multi-processors interrupt controller.
Changelog:
- Should be: '#interrupt-cells' not 'interrupt-cells'
Signed-off-by: Guo Ren
---
.../bindings/interrupt-controller/csky,mpintc.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
- Dt-bindings doc about C-SKY apb bus interrupt controller.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
.../interrupt-controller/csky,apb-intc.txt | 62 ++
1 file changed, 62 insertions(+)
create mode 100644
Dt-bindings doc about C-SKY Multi-processors interrupt controller.
Changelog:
- Should be: '#interrupt-cells' not 'interrupt-cells'
Signed-off-by: Guo Ren
---
.../bindings/interrupt-controller/csky,mpintc.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
- Dt-bindings doc about C-SKY apb bus interrupt controller.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
.../interrupt-controller/csky,apb-intc.txt | 62 ++
1 file changed, 62 insertions(+)
create mode 100644
Changelog:
- Add COMIPLE_TEST in Kconfig
- no cast is needed for "struct clock_event_device *ce = dev"
- remove: extra space after (u64)
- Add License and Copyright
- Use timer-of framework
- Change name with upstream feedback
- Use clksource_mmio framework
Signed-off-by: Guo Ren
---
- Dt-bindings doc for gx6605s SOC's system timer.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
- Dt-bindings doc for gx6605s SOC's system timer.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Dt-bingdings doc for C-SKY SMP system setting.
Changelog:
- Drop the interrupt-parent.
Signed-off-by: Guo Ren
---
.../devicetree/bindings/timer/csky,mptimer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
- irq-csky-apb-intc is a simple SOC interrupt controller which is
used in a lot of C-SKY CPU SOC products.
Changelog:
- use "bool ret" instead of "int ret"
- add support-pulse-signal in irq-csky-apb-intc.c
- change name with upstream feed-back
- add INTC_IFR to clear irq-pending
- remove
- Irq-csky-mpintc is C-SKY smp system interrupt controller and it
could support 16 soft irqs, 16 private irqs, and 992 max common
irqs.
Changelog:
- Move IPI_IRQ into the driver
- Remove irq_set_default_host() and use set_ipi_irq_mapping()
- Change name with upstream feed-back
- Change
Dt-bingdings doc for C-SKY SMP system setting.
Changelog:
- Drop the interrupt-parent.
Signed-off-by: Guo Ren
---
.../devicetree/bindings/timer/csky,mptimer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
- irq-csky-apb-intc is a simple SOC interrupt controller which is
used in a lot of C-SKY CPU SOC products.
Changelog:
- use "bool ret" instead of "int ret"
- add support-pulse-signal in irq-csky-apb-intc.c
- change name with upstream feed-back
- add INTC_IFR to clear irq-pending
- remove
- Irq-csky-mpintc is C-SKY smp system interrupt controller and it
could support 16 soft irqs, 16 private irqs, and 992 max common
irqs.
Changelog:
- Move IPI_IRQ into the driver
- Remove irq_set_default_host() and use set_ipi_irq_mapping()
- Change name with upstream feed-back
- Change
My Sincere Greetings,
I am Mrs Luiza Haydar, I decided to donate what I have to you for investment
towards the good work of charity organization, and also to help the motherless
and the less privileged ones and to carry out a charitable works in your
Country and around the World on my
My Sincere Greetings,
I am Mrs Luiza Haydar, I decided to donate what I have to you for investment
towards the good work of charity organization, and also to help the motherless
and the less privileged ones and to carry out a charitable works in your
Country and around the World on my
Hi Sasha,
On Mon, 1 Oct 2018 00:38:27 + Sasha Levin
wrote:
>
> From: Stephen Rothwell
>
> [ Upstream commit bcfb84a996f6fa90b5e6e2954b2accb7a4711097 ]
>
> A powerpc build of cifs with gcc v8.2.0 produces this warning:
>
> fs/cifs/cifssmb.c: In function ‘CIFSSMBNegotiate’:
>
Hi Sasha,
On Mon, 1 Oct 2018 00:38:27 + Sasha Levin
wrote:
>
> From: Stephen Rothwell
>
> [ Upstream commit bcfb84a996f6fa90b5e6e2954b2accb7a4711097 ]
>
> A powerpc build of cifs with gcc v8.2.0 produces this warning:
>
> fs/cifs/cifssmb.c: In function ‘CIFSSMBNegotiate’:
>
On Mon, Oct 01, 2018 at 01:46:27AM +0200, Laurent Vivier wrote:
> Signed-off-by: Laurent Vivier
> ---
I don't take patches without any changelog text, I don't know if other
maintainers are as nice. But for a new feature, you really should write
something...
thanks,
greg k-h
On Mon, Oct 01, 2018 at 01:46:27AM +0200, Laurent Vivier wrote:
> Signed-off-by: Laurent Vivier
> ---
I don't take patches without any changelog text, I don't know if other
maintainers are as nice. But for a new feature, you really should write
something...
thanks,
greg k-h
Agree. I will create new patch which will just allow stalling by default.
Vào Th 6, 28 thg 9, 2018 vào lúc 05:47 Mark Brown đã viết:
>
> On Wed, Sep 26, 2018 at 09:37:39PM +0700, Đặng Trần Hiếu wrote:
>
> > Default value of the register is to allow stalling (NOSTALL bit not
> > set) but the
Agree. I will create new patch which will just allow stalling by default.
Vào Th 6, 28 thg 9, 2018 vào lúc 05:47 Mark Brown đã viết:
>
> On Wed, Sep 26, 2018 at 09:37:39PM +0700, Đặng Trần Hiếu wrote:
>
> > Default value of the register is to allow stalling (NOSTALL bit not
> > set) but the
Hi all,
Commit
f17bbdb5eea2 ("parisc: Remove PTE load and fault check from L2_ptep macro")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgp61gh6EvjUt.pgp
Description: OpenPGP digital signature
Hi all,
Commit
f17bbdb5eea2 ("parisc: Remove PTE load and fault check from L2_ptep macro")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgp61gh6EvjUt.pgp
Description: OpenPGP digital signature
From: Florian Westphal
[ Upstream commit 10568f6c5761db24249c610c94d6e44d5505a0ba ]
Satish Patel reports a skb_warn_bad_offload() splat caused
by -j CHECKSUM rules:
-A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM
The CHECKSUM target has never worked with GSO skbs, and the above rule
makes
From: Stephen Boyd
[ Upstream commit b55326dc969ea2d704a008d9a97583b128f54f4f ]
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
1 - 100 of 724 matches
Mail list logo
