Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Signed-off-by: Himanshu Jha
---
drivers/virtio/virtio_mmio.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c
index
Hi Mike,
On Sat, Aug 26, 2017 at 11:08 PM, Mike Galbraith wrote:
> On Sun, 2017-08-27 at 07:44 +0200, Mike Galbraith wrote:
>> On Sat, 2017-08-26 at 18:02 -0700, Joel Fernandes wrote:
>> > Binder (Android's IPC mechanism) which uses sync wake ups during
>> > synchronous
>> >
The port type callback call enquires the tcpc_dev if
the requested port type is supported. If supported, then
performs a tcpm reset if required after setting the tcpm
internal port_type variable.
Check against the tcpm port_type instead of checking
against caps.type as port_type reflects the
Check memory allocation failures and return -ENOMEM in such cases, as
already done for other memory allocations in this function.
This avoids NULL pointers dereference.
Signed-off-by: Christophe JAILLET
---
drivers/net/ethernet/intel/igb/igb_main.c | 2 ++
1 file
Enable Try.SRC or Try.SNK only when port_type is
DRP. Try.SRC or Try.SNK state machines are not
valid for SRC only or SNK only ports.
Signed-off-by: Badhri Jagan Sridharan
---
Changelog since v1:
- Corrected tag
drivers/staging/typec/tcpm.c | 6 --
1 file changed, 4
Hi everyone
Sorry for long delay
25.07.2017, 16:48, "Sebastian Reichel" :
> Here is a signed immutable branch for Andrew's patch, which moves
> bq27000 w1 driver to the power-supply subsystem. I guess git will
> figure everything out without this, but better
Hi everyone
25.07.2017, 14:27, "Johannes Poehlmann" :
> To make the ds1wm driver work on a powerpc architecture (big endian, 32bit)
> with a register offset multiplier of 4 I had to make some changes to
> Version 4 of the patchset
> work on Greg Kroah-Hartmanns
On Sun, Aug 27, 2017 at 08:52:50AM +0300, Tomas Winkler wrote:
> Device ids that are missing in 4.4 stable
>
> Tomas Winkler (2):
> mei: me: add broxton pci device ids
> mei: me: add lewisburg device ids
Thanks for the update, both now applied.
greg k-h
Hi.
Here is disk setup for QEMU VM:
===
[root@archmq ~]# smartctl -i /dev/sda
…
Device Model: QEMU HARDDISK
Serial Number:QM1
Firmware Version: 2.5+
User Capacity:4,294,967,296 bytes [4.29 GB]
Sector Size: 512 bytes logical/physical
Device is:Not in smartctl database
On Fri, Aug 25, 2017 at 09:41:02PM +0530, Himanshu Jha wrote:
> call to memset to assign 0 value immediately after allocating
> memory with kzalloc is unnecesaary as kzalloc allocates the memory
> filled with 0 value.
>
> Signed-off-by: Himanshu Jha
> ---
>
Am 27.08.2017 um 10:27 schrieb Alexandre Belloni:
> On 27/08/2017 at 04:30:08 +0200, Andreas Färber wrote:
>> Am 27.08.2017 um 04:05 schrieb Andrew Lunn:
>> By that same argument we could ask why so many drivers (and mine, too)
>> are calling rtc_valid_tm() when __rtc_read_time() calls it again...
Hi,
just to inform you that i have in mind to add spi(soon, at least seems
just a matter con Kconfig changes) and usdhc(later)
drivers/support for stmark2 mcf5441x based board.
But no problem, in case i'll re-add the this code as needed.
On 24/08/2017 16:34, Alexandre Belloni wrote:
As
On Mon, Aug 21, 2017 at 06:29:03PM +0300, Kirill A. Shutemov wrote:
> This patch prepare decompression code to boot-time switching between 4-
> and 5-level paging.
>
> Signed-off-by: Kirill A. Shutemov
> ---
> arch/x86/boot/compressed/head_64.S | 24
Hi!
So I fought with the driver a bit more, and now I have something that
kind-of-works.
"great great hack" belows worries me.
Yeah, disabled code needs to be removed before merge.
No, tag_ksz part probably is not acceptable. Do you see solution
better than just copying it into tag_ksz1 file?
PING messages are used to monitor the connect/disconnect.
However, when PD is carried over CC, so this is not required.
Also, the spec does not clearly say if PD is possible when
Type-c is connected to Type-A/B. So, removing sending
PING messages altogether.
Signed-off-by: Badhri Jagan Sridharan
When VBUS is not discovered within PD_T_PS_SOURCE_ON although Rp
is detected on CC, TCPM switches the port to SNK_UNATTACHED
state. SNK_UNATTACHED, however does not force TYPEC_CC_OPEN which
makes the partner(source) to think that it is connected.
To overcome this issue, force the port into
The following changes since commit ef954844c7ace62f773f4f23e28d2d915adc419f:
Linux 4.13-rc5 (2017-08-13 16:01:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.13-rc7
for you to fetch changes up to
Hello,
(Cc Andrew, Grant)
On (08/25/17 17:37), Rob Herring wrote:
> On Sat, Aug 26, 2017 at 02:36:47AM +0900, Sergey Senozhatsky wrote:
> > If add_preferred_console() returns error then we must free a
> > copy of `of_stdout_options' that we create right before the
> > console registration.
> >
The following changes since commit ef954844c7ace62f773f4f23e28d2d915adc419f:
Linux 4.13-rc5 (2017-08-13 16:01:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
tags/char-misc-4.13-rc7
for you to fetch changes up to
When compiling with LLVM, errors like this are shown:
builtin-lock.c:46:10: error: implicit conversion turns string literal into
bool: 'const char [39]' to 'bool'
Due to error message implicit conversion into bool. Fix it by defining a
BUG macro without a boolean argument and use it instead.
Allow user to define flex and bison binary names by passing
FLEX and BISON variables.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/Makefile.perf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/Makefile.perf
When building with an external FEATURES_DUMP, bpf complains
that features dump file is not found. Fix it by passing full file path.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/Makefile.perf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Prior to this patch, make scripts tested for CLANG with
ifeq ($(CC), clang), failing to detect CLANG binaries with
different names. Fix it by testing for the existence of
__clang__ macro in the list of compiler defined macros.
Signed-off-by: David Carrillo-Cisneros
---
Use already defined values for CC, AR and LD when available.
Signed-off-by: David Carrillo-Cisneros
---
tools/lib/api/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/lib/api/Makefile b/tools/lib/api/Makefile
index
Collection of minor fixes to compile with LLVM and
non-standard tool names.
David Carrillo-Cisneros (6):
tools build tests: Don't hardcode gcc name
perf tools: Allow external definition of flex and bison binary names
tools lib: Allow external definition of CC, AR and LD
perf tools:
Use $(CC) instead of harcoded gcc binary name.
Signed-off-by: David Carrillo-Cisneros
---
tools/build/tests/ex/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/build/tests/ex/Makefile b/tools/build/tests/ex/Makefile
index
Hello,
Do you find it relevant to clarify the following details?
Some data type definitions are provided by Linux source files.
How would you like to see them represented in the documentation formats
which are generated by the Sphinx software?
Regards,
Markus
Hi Alexandre,
Am 27.08.2017 um 11:13 schrieb Alexandre Belloni:
> Not much to add, apart from the spinlock issue already spotted by Andrew.
>
> On 27/08/2017 at 02:33:27 +0200, Andreas Färber wrote:
>> +struct rtd119x_rtc {
>> +void __iomem *base;
>> +struct clk *clk;
>> +struct
All registers are located within 0x400 size from the base address.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Add UniPhier AIDET (ARM Interrupt Detector) nodes to support
active low interrupts.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 7 +++
arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 7 +++
2 files changed, 14
Add UniPhier AIDET (ARM Interrupt Detector) nodes to support
active low interrupts.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4.dtsi | 7 +++
arch/arm/boot/dts/uniphier-pro4.dtsi | 7 +++
arch/arm/boot/dts/uniphier-pro5.dtsi | 7
All registers are located within 0x400 size from the base address.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-pro5.dtsi | 2 +-
arch/arm/boot/dts/uniphier-pxs2.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi Linus,
The following changes since commit a7990c647b35415e3dd07a077480a908678947ba:
iommu/arm-smmu: fix null-pointer dereference in arm_smmu_add_device
(2017-08-11 16:56:51 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
In be_tx_compl_process, frag_index declared as u32, so it's better to
declare last_index as u32 also.
CC: Ajit Khaparde
Fixes: b0fd2eb28bd4 ("be2net: Declare some u16 fields as u32 to improve
performance")
Signed-off-by: Haishuang Yan
Hi
18.07.2017, 02:09, "Jaghathiswari Rankappagounder Natarajan" :
> Hi Greg,
> Please pull in this patchset into the tree. Thanks!
Here is a patchset, is it visible in your mailbox?
If so, please pull it into your tree.
> Summary of what this patchset does:
>
> Our board has 4
Casting void pointers to other pointer types in unnecessary.
Signed-off-by: Himanshu Jha
---
drivers/nubus/nubus.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/nubus/nubus.c b/drivers/nubus/nubus.c
index df431e8..5450f1a 100644
---
On (08/27/17 16:19), Sergey Senozhatsky wrote:
[..]
> int uart_parse_earlycon(char *p, unsigned char *iotype, resource_size_t *addr,
> char **options)
> {
> if (strncmp(p, "mmio,", 5) == 0) {
> *iotype = UPIO_MEM;
> p += 5;
> } else if
On 27/08/2017 at 04:30:08 +0200, Andreas Färber wrote:
> Am 27.08.2017 um 04:05 schrieb Andrew Lunn:
> > n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote:
> >> +struct rtd119x_rtc {
> >> + void __iomem *base;
> >> + struct clk *clk;
> >> + struct rtc_device *rtcdev;
> >> +
Hi Andrew,
Am 27.08.2017 um 05:27 schrieb Andrew Lunn:
> On Sun, Aug 27, 2017 at 04:30:08AM +0200, Andreas Färber wrote:
>> Am 27.08.2017 um 04:05 schrieb Andrew Lunn:
>>> n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote:
+struct rtd119x_rtc {
+ void __iomem *base;
+
Hi Andrew,
On 08/25/2017 09:32 AM, Pavel Machek wrote:
> On Fri 2017-08-25 16:05:03, Andrew Jeffery wrote:
>> In some systems, such as BMCs, we want to retain the state of LEDs
>> across a reboot of the BMC whilst the host remains up.
>
> I'd spell out what BMC is...
I agree with Pavel. Please
Use PTR_ERROR_ZERO rather than if(IS_ERR(...)) + PTR_ERR.
Build successfully.
Signed-off-by: Himanshu Jha
---
drivers/crypto/marvell/tdma.c | 5 +
drivers/crypto/mv_cesa.c| 5 +
drivers/crypto/qce/ablkcipher.c | 5 +
3 files changed, 3
(Sorry my last reply was incorrectly formatted, resending..)
Hi Mike,
On Sat, Aug 26, 2017 at 10:44 PM, Mike Galbraith wrote:
> On Sat, 2017-08-26 at 18:02 -0700, Joel Fernandes wrote:
>> Binder (Android's IPC mechanism) which uses sync wake ups during
synchronous
>> transactions
On Sat, 2017-08-26 at 23:18 -0700, Joel Fernandes wrote:
>
> > Sync is not a contract, it's a hint. If you really want sync behavior,
> > you need to create a contract signed in blood to signal that you really
> > really are passing the baton.
>
> Yes that is the usecase of binder, we are
On Sat, Aug 26, 2017 at 3:12 AM, Maxime Ripard
wrote:
> Hi,
>
> The bindings of the stmmac glue for the new Allwinner EMAC controller
> are still controversial and being discussed, even though they've been
> merged in 4.13.
>
> In order not to introduce any
On Sun, 2017-08-27 at 07:44 +0200, Mike Galbraith wrote:
> On Sat, 2017-08-26 at 18:02 -0700, Joel Fernandes wrote:
> > Binder (Android's IPC mechanism) which uses sync wake ups during synchronous
> > transactions to the scheduler to indicate that the waker is about to sleep
> > soon. The current
cl_lock_operations are not supposed to change at runtime.
cl_lock_slice_add is working with const cl_lock_operations.
So mark the non-const cl_lock_operations structs as const.
Signed-off-by: Arvind Yadav
---
drivers/staging/lustre/lustre/obdecho/echo_client.c | 2 +-
According the spec, the following is the conditions for exiting Try.SNK
state:
"The port shall wait for tDRPTry and only then begin monitoring the CC1 and
CC2 pins for the SNK.Rp state. The port shall then transition to
Attached.SNK when the SNK.Rp state is detected on exactly one of the CC1
or
According to the spec the following is the condition
for exiting TryWait.SRC:
"The port shall transition to Attached.SRC when V BUS is at vSafe0V
and the SRC.Rd state is detected on exactly one of the CC pins for at
least tCCDebounce. The port shall transition to Unattached.SNK after
tDRPTry if
On Sat, 2017-08-26 at 23:39 -0700, Joel Fernandes wrote:
>
> > P.S. to get the most bang for your synchronous buck, you want a
> > preemptive wakeup.. but that butts heads with the fair engine.
> >
>
> By preemptive wake up I guess you mean the waker would give up its
> time slice and let the
Hi,
Not much to add, apart from the spinlock issue already spotted by Andrew.
On 27/08/2017 at 02:33:27 +0200, Andreas Färber wrote:
> +struct rtd119x_rtc {
> + void __iomem *base;
> + struct clk *clk;
> + struct rtc_device *rtcdev;
> + unsigned base_year;
checkpatch complains
Extend the one wire DS2482 master driver with a module option that allows
support
for PPM/SPU/1WS interface modes to be requested. This allows support of chips
that require one or more of these features such as the DS28E05.
Signed-off-by: Andrew Worsley
Acked-by: Evgeniy
Hi, this extends the one wire master DS2482 driver to support other interfacing
modes and adds a slave one wire DS28E05 EEPROM driver. This allows the one
wire master DS2482 driver to support the OverDrive interface mode which is
required for it to talk to the DS28E05 slave chip.
These patches
Add a one wire driver for the DS28E05 one wire slave chip. This chip
requires OverDrive support to talk to it.
Signed-off-by: Andrew Worsley
Acked-by: Evgeniy Polyakov
---
drivers/w1/slaves/Kconfig | 8 ++
drivers/w1/slaves/Makefile| 1 +
Check memory allocation failures and return -ENOMEM in such cases, as
already done above for another memory allocation.
This avoids NULL pointers dereference.
Signed-off-by: Christophe JAILLET
---
sound/soc/davinci/davinci-mcasp.c | 4
1 file changed, 4
According to the spec:
"4.5.2.2.10.2 Exiting from TryWait.SNK State
The port shall transition to Attached.SNK after tCCDebounce if or when VBUS
is detected. Note the Source may initiate USB PD communications which will
cause brief periods of the SNK.Open state on both the CC1 and CC2 pins,
but
Once, Rp or Rd is switched, wait for PD_T_CC_DEBOUNCE. If not the
PS_RDY message transmitted might result in failure.
Also, Only wait for PD_T_SRCSWAPSTDBY while in
PR_SWAP_SRC_SNK_TRANSITION_OFF. PD_T_PS_SOURCE_OFF is the overall
time after which the initial sink would issue hard reset.
In the case that the lower layer driver reports a cc change directly
from SINK state to SOURCE state, TCPM doesn't handle these cc change
in SRC_SEND_CAPABILITIES, SRC_READY states. And with SRC_ATTACHED
state, the change is not handled as the port is still considered
connected.
[49606.131672]
Hi
19.07.2017, 23:14, "Jan Kandziora" :
> The w1_ds28e17 driver from the next part of this patch needs to emit
> single-bit read timeslots to the DS28E17. The w1 subsystem already
> has this function but it is not exported outside drivers/w1/w1_io.c
>
> This subpatch exports the
Hi Chen
19.07.2017, 10:58, "Chen Lin" :
> The byteorder of para rn(W1_READ_ROM id) pass to w1_slave_found must
> be the same with the byterorder defined in struct w1_reg_num.
>
> The rn read from 'rv = w1_read_block(dev, (u8 *), 8)' is a byte
> serial and not cpu endian
On 17.08.2017 23:14, Gerhard Wiesinger wrote:
On 17.08.2017 22:58, Gerhard Wiesinger wrote:
>
> On 07.08.2017 19:50, Paolo Bonzini wrote:
>
> >Not much to say, unfortunately. It's pretty much the same capabilities
> >as a Prescott/Cedar Mill processor, except that it has MSR bitmaps. It
> >also
Em Thu, 17 Aug 2017 16:14:46 +0200
Wolfram Sang escreveu:
> Signed-off-by: Wolfram Sang
> ---
> Documentation/i2c/DMA-considerations | 50
>
> 1 file changed, 50 insertions(+)
> create
On Sat, Aug 26, 2017 at 11:09:49PM +0800, Donglin Peng wrote:
> It seems that the v3 patch should be applied other than v2.
Please send incremental fixes rather than new versions for things that
are are already applied.
signature.asc
Description: PGP signature
On Fri, Aug 25, 2017 at 03:40:50PM +0200, Paolo Bonzini wrote:
> On 25/08/2017 15:14, Adam Borowski wrote:
> >>> I would also try commit 1372324b328cd5dabaef5e345e37ad48c63df2a9 to
> >>> identify whether it was caused by a KVM change in 4.13 or something
> >>> else.
> > I've ran different guests
On Sat, Aug 26, 2017 at 12:48:01PM +0200, Oleksandr Natalenko wrote:
> Quick update: reproduced on both v4.12.7 and v4.13.0-rc6.
BTW, given it hangs during resume, it isn't easy to collect debug
info, and there should have been lots useful info there.
You mentioned that you can reproduce it on
While performing PORT_RESET, upon receiving the cc disconnect
signal from the underlaying tcpc device, TCPM transitions into
unattached state. Consider, the current type of port while determining
the unattached state.
In the below logs, although the port_type was set to sink, TCPM
transitioned
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Signed-off-by: Himanshu Jha
---
drivers/tty/serial/8250/8250_mtk.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_mtk.c
Check memory allocation failures and return -ENOMEM in such cases, as
already done few lines below for another memory allocation.
This avoids NULL pointers dereference.
Fixes: 14e494542636 ("libnvdimm, btt: BTT updates for UEFI 2.7 format")
Signed-off-by: Christophe JAILLET
According to spec:
" 4.5.2.2.9.2 Exiting from Try.SRC State:
The port shall transition to Attached.SRC when the SRC.Rd
state is detected on exactly one of the CC1 or CC2 pins for
at least tPDDebounce. The port shall transition to
TryWait.SNK after tDRPTry and the SRC.Rd state has not been
Hi Rob,
Am 23.08.2017 um 02:29 schrieb Rob Herring:
> On Sun, Aug 20, 2017 at 03:36:29AM +0200, Andreas Färber wrote:
>> Add a binding for the RTC on the Realtek RTD119x/RTD129x SoC families.
>>
>> Signed-off-by: Andreas Färber
>> ---
>>
On Mon, Aug 28, 2017 at 01:20:26AM +0800, Aviad Krawczyk wrote:
> Fix the hw MTU limitation by setting max_mtu
>
> Signed-off-by: Aviad Krawczyk
> Signed-off-by: Zhao Chen
Reviewed-by: Andrew Lunn
Andrew
On 27/08/2017 at 15:37:51 +0200, Andrew Lunn wrote:
> > >> +static inline int rtd119x_rtc_year_days(int year)
> > >> +{
> > >> +return rtc_year_days(1, 12, year);
> > >
> > > I'm not sure it is worth wrapping rtc_year_days
> > [snip]
> >
> > Well, I found your rtc_year_days rather
calling memcpy immediately after memset with the same region of memory
makes memset redundant.
Build successfully.
Signed-off-by: Himanshu Jha
---
drivers/staging/rtl8723bs/core/rtw_ioctl_set.c | 1 -
drivers/staging/rtl8723bs/core/rtw_mlme.c | 2 --
On Sun, Aug 27, 2017 at 08:52:58PM +, Mathieu Desnoyers wrote:
> - On Aug 27, 2017, at 1:35 PM, Paul E. McKenney
> paul...@linux.vnet.ibm.com wrote:
>
> > On Sun, Aug 27, 2017 at 12:54:04PM -0700, Mathieu Desnoyers wrote:
> >> Add a new MEMBARRIER_CMD_REGISTER_SYNC_CORE command to the
On 27/08/2017 at 12:36:31 -0700, Steven King wrote:
> On Sunday 27 August 2017 12:09:59 pm Alexandre Belloni wrote:
> > On 27/08/2017 at 13:22:09 +0200, Angelo Dureghello wrote:
> > > Hi,
> > >
> > > just to inform you that i have in mind to add spi(soon, at least seems
> > > just a matter con
- On Aug 27, 2017, at 2:00 PM, Paul E. McKenney paul...@linux.vnet.ibm.com
wrote:
> On Sun, Aug 27, 2017 at 08:52:58PM +, Mathieu Desnoyers wrote:
>> - On Aug 27, 2017, at 1:35 PM, Paul E. McKenney
>> paul...@linux.vnet.ibm.com
>> wrote:
>>
>> > On Sun, Aug 27, 2017 at 12:54:04PM
On Wed, Aug 23, 2017 at 2:01 PM, Andreas Dilger wrote:
>
> Doug,
> I noticed while checking for other implications of changing MAX_LFS_FILESIZE
> that fs/jfs/super.c is also working around this limit.
Note to people: I just committed the patch to update MAX_LFS_FILESIZE.
I
On Sunday 27 August 2017 12:09:59 pm Alexandre Belloni wrote:
> On 27/08/2017 at 13:22:09 +0200, Angelo Dureghello wrote:
> > Hi,
> >
> > just to inform you that i have in mind to add spi(soon, at least seems
> > just a matter con Kconfig changes) and usdhc(later)
> > drivers/support for stmark2
On Wed, Aug 23, 2017 at 04:06:24PM +1000, Paul Mackerras wrote:
> It seems to me that it would be better to do the anon_inode_getfd()
> call before the kvm_get_kvm() call, and go to the fail label if it
> fails.
And what happens if another thread does close() on the (guessed) fd?
Pavel,
Thanks for update and sorry about email format (due to web-access version)
I'll do review when getting back to office later this week.
- Woojung
From: Pavel Machek [pa...@denx.de]
Sent: Sunday, August 27, 2017 8:36 AM
To: Woojung Huh - C21699;
hi Mark,
On 08/27/2017 10:34 PM, Mark Brown wrote:
On Sun, Aug 27, 2017 at 10:31:52PM +0800, Jeffy Chen wrote:
This is a HTML only mail and I have a text only client...
sorry, i was replying with my phone, didn't notice it would use html by
default...
i think you've applied the right
On Sun, Aug 27, 2017 at 2:40 PM, Linus Torvalds
wrote:
>
> The race goes like this:
>
> thread1 thread2 thread3
>
>
> .. CPU1 ...
> __lock_page_killable
> wait_on_page_bit_common()
> get wq lock
>
On 2017-07-24 18:27, Matthias Kaehlcke wrote:
> MODULE_DEVICE_TABLE(type, name) creates an alias of type 'extern const
> typeof(name)'. If 'name' is already constant the 'const' attribute is
> specified twice, which is not allowed in C89 (see discussion at
> https://lkml.org/lkml/2017/5/23/1440).
On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote:
> On Fri 25-08-17 09:20:31, Joonsoo Kim wrote:
> > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote:
> > > On 08/24/2017 07:45 AM, js1...@gmail.com wrote:
> > > > From: Joonsoo Kim
> > > >
> > >
This driver supports multiple devices like mma8653,
mma8652, mma8452, mma8453 and fxls8471. Almost all
these devices have more than one event.
Current driver design hardcodes the event specific
information, so only one event can be supported by this
driver at any given
On Fri, Aug 25, 2017 at 09:56:10AM +0200, Vlastimil Babka wrote:
> On 08/25/2017 02:20 AM, Joonsoo Kim wrote:
> > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote:
> >
> > Hmm, this is already pointed by Minchan and I have answered that.
> >
> >
On Sun, 2017-08-27 at 22:00 +0300, Matthias Brugger wrote:
>
> On 08/19/2017 09:06 PM, sean.w...@mediatek.com wrote:
> > From: Sean Wang
> >
> > Document the devicetree bindings in 8250.txt for MediaTek BTIF
> > controller which could be found on MT7622 and MT7623 SoC.
>
- On Aug 27, 2017, at 1:35 PM, Paul E. McKenney paul...@linux.vnet.ibm.com
wrote:
> On Sun, Aug 27, 2017 at 12:54:04PM -0700, Mathieu Desnoyers wrote:
>> Add a new MEMBARRIER_CMD_REGISTER_SYNC_CORE command to the membarrier
>> system call. It allows processes to register their intent to have
On Sat, Aug 26, 2017 at 11:15 AM, Linus Torvalds
wrote:
>
> So how about just this fairly trivial patch?
So I just committed that trivial patch, because I think it's right,
but more importantly because I think I found a real and non-trivial
fundamental problem.
On Sun, Aug 27, 2017 at 2:40 PM, Linus Torvalds
wrote:
>
> End result: page is unlocked, CPU3 is waiting, nothing will wake CPU3 up.
Not CPU3. CPU3 was the waker. It's thread 2 that is waiting and never
got woken up, of course.
Other than that, the scenario still
On Fri, Aug 25, 2017 at 6:52 PM, Rick Altherr wrote:
>> Incidentally, people are sending patches to expose the FTDI
>> expanders as common GPIO chips under Linux, so we can
>> internally in the kernel or from the usersapce character device
>> access them as "some GPIOs".
>
>
Hi Jacek, Pavel
On Sun, 2017-08-27 at 13:01 +0200, Jacek Anaszewski wrote:
> Hi Andrew,
>
> On 08/25/2017 09:32 AM, Pavel Machek wrote:
> > On Fri 2017-08-25 16:05:03, Andrew Jeffery wrote:
> > > In some systems, such as BMCs, we want to retain the state of LEDs
> > > across a reboot of the BMC
In some systems, such as Baseboard Management Controllers (BMCs), we
want to retain the state of LEDs across a reboot of the BMC (whilst the
host remains up). Implement support for the retain-state-shutdown
devicetree property in leds-gpio.
Signed-off-by: Andrew Jeffery
Hello,
LEDs controlled by Baseboard Management Controllers (BMCs) are sometimes
required to retain their state across BMC resets. BMC resets may occur whilst
the host is alive, thus the chassis and host system remain powered up. In these
two patches I define an new devicetree property to describe
On Baseboard Management Controller (BMC) systems it's sometimes
necessary for a LED to retain its state across a BMC reset (which is
independent of the host system state). Add a devicetree property to
describe this behaviour. The property would typically be used in
conjunction with 'default-state
> When the devfreq_add_device fails to register deivce, the memory
> leak of devfreq instance happen. So, this patch fix the memory
> leak issue. Before freeing the devfreq instance checks whether
> devfreq instance is NULL or not because the device_unregister()
> frees the devfreq instance when
On 2017년 08월 28일 09:17, MyungJoo Ham wrote:
>> When the devfreq_add_device fails to register deivce, the memory
>> leak of devfreq instance happen. So, this patch fix the memory
>> leak issue. Before freeing the devfreq instance checks whether
>> devfreq instance is NULL or not because the
> Even if the freq_table is included in the struct devfreq,
> the commit 0ec09ac2cebe ("PM / devfreq: Set the freq_table
> of devfreq device") set the frequency table outside the mutex locking.
>
> So, this patch initializes the frequency table within the mutex locking.
>
> Cc:
On Fri, Aug 25, 2017 at 02:32:13PM -0700, Andrew Morton wrote:
> On Thu, 24 Aug 2017 15:36:30 +0900 js1...@gmail.com wrote:
>
> > From: Joonsoo Kim
> >
> > This patchset is the follow-up of the discussion about the
> > "Introduce ZONE_CMA (v7)" [1]. Please reference it
On 08/19/2017 09:06 PM, sean.w...@mediatek.com wrote:
From: Sean Wang
Document the devicetree bindings in 8250.txt for MediaTek BTIF
controller which could be found on MT7622 and MT7623 SoC.
Signed-off-by: Sean Wang
---
On 27/08/2017 at 13:22:09 +0200, Angelo Dureghello wrote:
> Hi,
>
> just to inform you that i have in mind to add spi(soon, at least seems
> just a matter con Kconfig changes) and usdhc(later)
> drivers/support for stmark2 mcf5441x based board.
> But no problem, in case i'll re-add the this code
1 - 100 of 612 matches
Mail list logo