On Thu, Oct 11, 2018 at 02:50:51AM +0530, Raju P.L.S.S.S.N wrote:
> RPMH based targets require that the sleep and wake state request votes
> be sent during system low power mode entry. The votes help reduce the
> power consumption when the AP is not using them. The votes sent by the
> clients are
On Fri, Oct 12, 2018 at 03:52:43PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Oct 12, 2018 at 05:20:40AM -0700, Guenter Roeck wrote:
> > On 10/11/2018 08:35 AM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.9.133 release.
> > > There are 35 patches in this
On Thu, Oct 11, 2018 at 09:59:19PM +0300, Alexey Budankov wrote:
SNIP
> @@ -1490,6 +1514,13 @@ static int perf_record_config(const char *var, const
> char *value, void *cb)
> var = "call-graph.record-mode";
> return perf_default_config(var, value, cb);
> }
>
On Thu, Oct 11, 2018 at 02:50:54AM +0530, Raju P.L.S.S.S.N wrote:
> Use cpu hotplug callback mechanism to attach/dettach the cpu in
> the cpu power domain. During cpu hotplug callback registration,
> the starting callback is invoked on all online cpus. So there is
> no need to attach from device
Hi Linus,
+ Laurent, as he reviewed most of that driver code
Sorry, I'm going slightly OT with this, but please read below.
On Fri, Oct 12, 2018 at 02:54:12PM +0200, Linus Walleij wrote:
> This allows nonexclusive (simultaneous) access to a single
> GPIO line for the fixed regulator enable
Arnd Bergmann wrote:
> + depends on IPV6 || !IPV6
That looks weird. It looks like it always ought to be true.
David
On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
> Hi Lee,
>
> On 10/12/2018 02:34 PM, Lee Jones wrote:
> > On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
> >> On 10/12/2018 12:20 PM, Kieran Bingham wrote:
> >>> Hi Vladimir,
> >>> On 12/10/18 09:39, Lee Jones wrote:
> On Fri, 12 Oct 2018,
On 01/08/2018 16:24, David Howells wrote:
From: Al Viro
Allow a detached tree created by open_tree(..., OPEN_TREE_CLONE) to be
attached by move_mount(2).
If by the time of final fput() of OPEN_TREE_CLONE-opened file its tree is
not detached anymore, it won't be dissolved. move_mount(2) is
On Fri, Oct 12, 2018 at 11:50:01AM +0200, Peter Zijlstra wrote:
>
> Can we please not top-post?
>
> On Thu, Oct 11, 2018 at 10:37:14PM +, Song Liu wrote:
> > Thanks Peter! These are really really helpful.
> >
> > I am trying to think through the case of a group of two events on two
> >
Boris,
On 10/11/2018 05:02 PM, Borislav Petkov wrote:
> On Thu, Oct 11, 2018 at 08:33:35PM +, Moger, Babu wrote:
>> Introduces the new config parameter AMD_QOS. This parameter will be
>> used to enable cache and memory bandwidth allocation and monitoring
>> features on AMD processors. This
On Fri, Aug 31, 2018 at 12:17:21AM +0800, Peng Hao wrote:
> Signed-off-by: Peng Hao
> ---
> Documentation/virtual/kvm/00-INDEX | 2 ++
> Documentation/virtual/kvm/coalesced-pio.txt | 15 +++
> 2 files changed, 17 insertions(+)
> create mode 100644
On Thu, Oct 11, 2018 at 05:39:27PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.76 release.
> There are 45 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
On 12 October 2018 at 20:16, Ulf Hansson wrote:
> On 12 October 2018 at 13:11, Viresh Kumar wrote:
>> Multiple generic power domains for a consumer device are supported with
>> the help of virtual devices, which are created for each consumer device
>> - genpd pair. These are the device
On Fri, Oct 12, 2018 at 05:31:17PM +0200, Arnd Bergmann wrote:
> The following changes since commit 17b57b1883c1285f3d0dc2266e8f79286a7bef38:
>
> Linux 4.19-rc6 (2018-09-30 07:15:35 -0700)
>
> are available in the Git repository at:
>
>
On Thu, Oct 11, 2018 at 05:34:47PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.161 release.
> There are 27 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
Anyone have any issues with this patch?
-- Steve
On Thu, 11 Oct 2018 23:00:21 -0400
Steven Rostedt wrote:
> [
> A while ago I posted an RFC patchset for dynamic function based
> events. But Masami pointed out that this could be done with kprobes
> with minimal changes. He posted a
On Thu, Oct 11, 2018 at 11:51:18AM -0500, Dan Murphy wrote:
> Add the device tree bindings for the lm3697
> LED driver for backlighting and display.
Bindings are for h/w, not drivers...
>
> Signed-off-by: Dan Murphy
> ---
> .../devicetree/bindings/leds/leds-lm3697.txt | 98
Hi,
On 12.10.2018 17:17, Jiri Olsa wrote:
> On Thu, Oct 11, 2018 at 09:59:19PM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> @@ -1490,6 +1514,13 @@ static int perf_record_config(const char *var, const
>> char *value, void *cb)
>> var = "call-graph.record-mode";
>>
On Fri, Oct 12, 2018 at 04:26:12PM +0200, jacopo mondi wrote:
> Sorry, I'm going slightly OT with this, but please read below.
> On Fri, Oct 12, 2018 at 02:54:12PM +0200, Linus Walleij wrote:
> > This allows nonexclusive (simultaneous) access to a single
> > GPIO line for the fixed regulator
This series presents base frequency to cpufreq sysfs when intel_pstate
is in use in HWP mode.
Changes:
v3:
- Update documentation
v2
- Removed guaranteed attribute addition to acpi_cppc sysfs
- Using the cppc_acpi interface to get base frequency and present
Srinivas Pandruvada (3):
ACPI /
Present base_frequency to user space via cpufreq sysfs when HWP is in
use.
This HWP base frequency is read from HWP Capabilities MSR, if platform
doesn't have ACPI _CPC object. On most of the HWP platforms the _CPC
object will point to the HWP Capabilities MSR using address space id as
On Fri 12-10-18 12:09:53, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> Inside set_pmd_migration_entry() we are holding page table locks and
> thus we can not sleep so we can not call invalidate_range_start/end()
>
> So remove call to mmu_notifier_invalidate_range_start/end() and add
>
Hi,
On Thu, Oct 11, 2018 at 6:12 PM Can Guo wrote:
> + if (err != -EPROBE_DEFER)
> + dev_err(dev, "failed to get %s err %d",
> + name, err);
I wouldn't spin just for this, but if you spin for some other reason
you could move the above "dev_err"
The patch
spi: Make GPIO CSs honour the SPI_NO_CS flag
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
On Fri, Oct 12, 2018 at 09:55:55AM -0700, Nick Desaulniers wrote:
> On Thu, Oct 11, 2018 at 6:50 PM Nathan Chancellor
> wrote:
> >
> > On Thu, Oct 11, 2018 at 01:31:26PM -0700, ndesaulni...@google.com wrote:
> > > by swapping h2 and h3.
> > >
> > > security/keys/trusted.c:146:17: warning: passing
Hi Nick,
Refer to
https://trustedcomputinggroup.org/wp-content/uploads/TPM-Main-Part-3-Commands_v1.2_rev116_01032011.pdf
for details.
Can you cite the relevant section?
Just pick any section that describes a TPM command. I randomly used
Section 10.3 for TPM Unbind. See the 'Incoming
Hi,
On Thu, Oct 11, 2018 at 10:57 PM wrote:
> Fused value is supposed to always override. If value is not fused for
> some
> parts (which I believe is case with some early samples), then driver
> will
> read it is '0' from nvmem and should use hstx-trim value passed from DT.
OK cool. Just
Hi Nick,
So maybe I'm misunderstanding something, but the issue seems to be that
unsigned char is promoted to 'unsigned char *' by Clang and probably
unsigned int or int by gcc.
No. This is extremely well defined behavior in C. In C, integral
types are NEVER promoted to pointer to integer
On 12 October 2018 at 13:11, Viresh Kumar wrote:
> The current implementation works only for the case where a single
> phandle is present in the "required-opps" property, while DT allows
> multiple phandles to be present there.
>
> This patch adds new infrastructure to parse all the phandles
On 12 October 2018 at 13:11, Viresh Kumar wrote:
> An earlier commit populated the OPP tables from the "required-opps"
> property, this commit populates the individual OPPs. This is repeated
> for each OPP in the OPP table and these populated OPPs will be used by
> later commits.
>
>
On 12 October 2018 at 13:11, Viresh Kumar wrote:
> We need to handle genpd OPP tables differently, this is already the case
> at one location and will be extended going forward. Add another field to
> the OPP table to check if the table belongs to a genpd or not.
>
> Signed-off-by: Viresh Kumar
On 12 October 2018 at 13:11, Viresh Kumar wrote:
> Create a separate routine to take care of custom set_opp() handler
> specific stuff.
>
> Signed-off-by: Viresh Kumar
Reviewed-by: Ulf Hansson
> ---
> drivers/opp/core.c | 67 +++---
> 1 file changed,
On Mon, Oct 08, 2018 at 04:29:39PM +, Pascal PAILLET-LME wrote:
> From: pascal paillet
>
> stpmic1 is a pmic from STMicroelectronics. The STPMIC1 integrates 10
> regulators ,3 switches, a watchdog and an input for a power on key.
regulators, 3 switches, ...
>
> Signed-off-by: pascal
Whenever kernel or user decides to call rx mode update, it clears
every multicast entry from forwarding table and in some time adds
it again. This time can be enough to drop incoming multicast packets.
That's why clear only staled multicast entries and update or add new
one afterwards.
The patchset omits redundant refresh of mcast address table and
prevents mcast packet lost.
Based on net-next/master
tested on am572x evm
Ivan Khoronzhuk (2):
net: ethernet: ti: cpsw_ale: use const for API having pointer on mac
address
net: ethernet: ti: cpsw: fix lost of mcast packets
It allows to use function under callbacks with same const qualifier of
mac address for farther changes.
Signed-off-by: Ivan Khoronzhuk
---
drivers/net/ethernet/ti/cpsw_ale.c | 12 ++--
drivers/net/ethernet/ti/cpsw_ale.h | 8
2 files changed, 10 insertions(+), 10 deletions(-)
On 10/04/2018 07:05 AM, Sebastian Andrzej Siewior wrote:
> Most users of __raw_xsave_addr() use a feature number, shift it to a
> mask and then __raw_xsave_addr() shifts it back to the feature number.
>
> Make __raw_xsave_addr() use the feature number as argument.
This generally looks like a
On Fri, Oct 12 2018 at 09:46 -0600, Ulf Hansson wrote:
On 12 October 2018 at 17:04, Sudeep Holla wrote:
On Thu, Oct 11, 2018 at 03:06:09PM -0600, Lina Iyer wrote:
On Thu, Oct 11 2018 at 11:37 -0600, Sudeep Holla wrote:
[...]
>
> Is DDR managed by Linux ? I assumed it was handled by higher
On Fri, Oct 12, 2018 at 04:58:38PM +0300, Andy Shevchenko wrote:
> On Fri, Oct 12, 2018 at 1:45 PM Russell King - ARM Linux
> > Given that DT describes the hardware, not the software implementation,
> > it must not change just because we move from GPIO numbers to GPIO
> > descriptors.
> > The
On 12 Oct 2018, at 12:09, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> Inside set_pmd_migration_entry() we are holding page table locks and
> thus we can not sleep so we can not call invalidate_range_start/end()
>
> So remove call to mmu_notifier_invalidate_range_start/end() and add
>
From: Thor Thayer
Vince has moved to a different role. Replace him as Altera
TSE maintainer.
Signed-off-by: Thor Thayer
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 72429b928626..f02cf78f5394 100644
--- a/MAINTAINERS
+++
On Fri, Oct 12, 2018 at 11:43:13AM +, Marcel Ziswiler wrote:
> On Fri, 2018-10-12 at 11:43 +0100, Russell King - ARM Linux wrote:
> > The existing DT description is reasonable, and introducing ficticious
> > regulators in DT to work around the implementation is not reasonable.
> I don't
On Fri, Oct 12, 2018 at 11:50:52AM -0500, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Vince has moved to a different role. Replace him as Altera
> TSE maintainer.
>
> Signed-off-by: Thor Thayer
Would be nice if Vince can ack this...
Hi Mark,
On Fri, Oct 12, 2018 at 06:44:24PM +0200, Mark Brown wrote:
> On Fri, Oct 12, 2018 at 04:26:12PM +0200, jacopo mondi wrote:
>
> > Sorry, I'm going slightly OT with this, but please read below.
>
> > On Fri, Oct 12, 2018 at 02:54:12PM +0200, Linus Walleij wrote:
> > > This allows
On Fri, Oct 12, 2018 at 9:01 AM James Bottomley wrote:
>
> On Fri, 2018-10-12 at 10:53 -0500, Denis Kenzior wrote:
> > Hi James,
> >
> > > > From the links provided in the patch it seems that one cannot
> > > > pass char/float/short to va_start(). Fair enough. So if we make
> > > > h3 an
On Fri, Oct 05, 2018 at 03:47:43PM -0500, Rob Herring wrote:
> On Wed, Oct 03, 2018 at 05:14:31PM -0700, Matthias Kaehlcke wrote:
> > The node has a reg property, therefore its name should include a unit
> > address.
> >
> > Also change the name from 'usb_id_nopull' to 'usb-id-nopull' to follow
>
On Fri, 2018-10-12 at 07:29 -0500, Denis Kenzior wrote:
> Hi Nick,
>
> > @@ -123,7 +123,7 @@ static int TSS_rawhmac(unsigned char *digest,
> > const unsigned char *key,
> >*/
> > static int TSS_authhmac(unsigned char *digest, const unsigned
> > char *key,
> > unsigned
From: Jérôme Glisse
Inside set_pmd_migration_entry() we are holding page table locks and
thus we can not sleep so we can not call invalidate_range_start/end()
So remove call to mmu_notifier_invalidate_range_start/end() and add
call to mmu_notifier_invalidate_range(). Note that we are already
Hello,
On Fri, Oct 12, 2018 at 03:04:48PM +, Vokáč Michal wrote:
> On 12.10.2018 10:57, Uwe Kleine-König wrote:
> > On Wed, Oct 10, 2018 at 09:33:26AM +, Vokáč Michal wrote:
> >> Normally the PWM output is held LOW when PWM is disabled. This can cause
> >> problems when inverted PWM
On Fri, Oct 12, 2018 at 09:03:29AM -0700, Stephen Boyd wrote:
> Quoting Manivannan Sadhasivam (2018-10-11 20:38:58)
> > On Thu, Sep 20, 2018 at 11:00:59PM -0700, Manivannan Sadhasivam wrote:
> > > This patchset adds clock support for Hi3670 SoC from HiSilicon utilizing
> > > the HiSi common clock
On Fri, 2018-10-12 at 09:28 -0700, David E. Box wrote:
> Remove Souvik who has left this role. Add Rajneesh and David who work
> jointly on telemetry updates for new platforms.
>
> Signed-off-by: David E. Box
> Signed-off-by: Rajneesh Bhardwaj
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@
On Fri, 2018-10-12 at 02:35 +0200, Jann Horn wrote:
> On Fri, Oct 12, 2018 at 1:40 AM Rick Edgecombe
> wrote:
> > This introduces a new rlimit, RLIMIT_MODSPACE, which limits the amount of
> > module space a user can use. The intention is to be able to limit module
> > space
> > allocations that
Hi,
On 12.10.2018 19:30, Andi Kleen wrote:
>> 4. Results
>> - Without this optimization, the guest pmi handling time is
>> ~450 ns, and the max sampling rate is reduced to 250.
>> - With this optimization, the guest pmi handling time is ~9000 ns
>> (i.e. 1 / 500 of the
See the previous patch for a long explanation.
TL;DR: the P52 and the t480s from Lenovo can't rely on I2C to fetch
the information, so we need it from PS/2.
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1628715
Signed-off-by: Benjamin Tissoires
---
drivers/input/mouse/elan_i2c_core.c | 49
Some new touchpads IC are connected through PS/2 and I2C. On some of these
new IC, the I2C part doesn't have all of the information available.
We need to be able to forward the touchpad parameters from PS/2 and
thus, we need those new optional properties.
Link:
We check for this bit all over the code, better have it defined once
for all.
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1628715
Signed-off-by: Benjamin Tissoires
---
drivers/input/mouse/elantech.c | 89 ++
1 file changed, 47 insertions(+), 42
The recent touchpads might not have all the information regarding the
characteristics through the I2C port.
On some Lenovo t480s, this results in the touchpad not being detected
as a clickpad, and on the Lenovo P52, this results in a failure while
fetching the resolution through I2C.
We need to
For the latest generation of Elantech touchpads, we need to forward
the min/max information from PS/2 to SMBus. Prepare this work
by fetching the information before creating the SMBus companion
device.
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1628715
Signed-off-by: Benjamin Tissoires
Since v4.18, we unconditionally switch the I2C capable touchpads over I2C.
In the model I had (a pre-prod t480s I guess), the touchpad was behaving
fine.
However, it occurs that later production models don't expose the clickpad
information from I2C. The Windows driver gets all the information from
On Thu, Sep 27, 2018 at 03:26:55PM +0800, Baolin Wang wrote:
> Some battery driver will use the open circuit voltage (OCV) value to look
> up the corresponding battery capacity percent in one certain degree Celsius.
> Thus this patch provides some battery properties to present the OCV table
>
> On Oct 12, 2018, at 7:40 AM, Pali Rohár wrote:
>
>> On Friday 12 October 2018 11:19:41 Andreas Henriksson wrote:
>> Hello everyone,
>>
>>> On Tue, Oct 02, 2018 at 04:44:10AM -0400, Jaroslav Skarvada wrote:
>>> I am downstream maintainer of dosfstools in Fedora/RHEL. My personal opinion
>>>
On 12 October 2018 at 13:11, Viresh Kumar wrote:
> Multiple generic power domains for a consumer device are supported with
> the help of virtual devices, which are created for each consumer device
> - genpd pair. These are the device structures which are attached to the
> power domain and are
On Fri, Sep 28, 2018 at 03:01:50PM +0200, Pierre-Yves MORDRET wrote:
> From: M'boumba Cedric Madianga
>
> Add one cell to support DMA/MDMA chaining.
You aren't adding a cell. Is the change compatible with existing users
(if you mask bits)?
>
> Signed-off-by: Pierre-Yves MORDRET
Author
In further testing in uniphier-sd.c,
I found my stupid mistakes.
Ulf,
Can you squash this series into
3fd784f745dd
"mmc: uniphier-sd: add UniPhier SD/eMMC controller driver"
if you have a chance to do rebase?
Of course, it is OK to apply this series
on top of your next branch if it is too late.
Once DMA is enabled, it is not possible to disable it because
uniphier_sd_dma_endisable() always sets the DMA_ENABLE_DMASDRW bit
regardless of the argument 'enable'. It should disable DMA when
'enable' is false.
Signed-off-by: Masahiro Yamada
---
drivers/mmc/host/uniphier-sd.c | 2 +-
1 file
host->chan_rx is NULL when UNIPHIER_SD_CAP_BROKEN_DMA_RX quirk flag
is set. In this case, it should not set up DMA.
Signed-off-by: Masahiro Yamada
---
drivers/mmc/host/uniphier-sd.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mmc/host/uniphier-sd.c
From: Colin Ian King
Trivial fix to spelling mistake in ODM_RT_TRACE trace message
Signed-off-by: Colin Ian King
---
drivers/staging/rtl8188eu/hal/odm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/hal/odm.c
On Fri, 2018-10-12 at 10:13 -0500, Denis Kenzior wrote:
> Hi James,
>
> > > So can't we simply use 'bool' or uint32 as the type for h3
> > > instead of re-ordering everything
> >
> > The problem is the standard is ambiguious. The only thing that's
> > guaranteed to work for all time is a char
On 12 October 2018 at 20:37, Ulf Hansson wrote:
> On 12 October 2018 at 13:11, Viresh Kumar wrote:
>> The OPP core currently stores the performance state in the consumer
>> device's OPP table, but that is going to change going forward and
>> performance state will rather be set directly in the
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 741234 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
drivers/firewire/core-topology.c | 1 +
1 file changed, 1 insertion(+)
diff --git
On Fri, Oct 12, 2018 at 11:22:30AM +0100, Lorenzo Pieralisi wrote:
> On Fri, Oct 12, 2018 at 04:01:29PM +0800, Honghui Zhang wrote:
>> On Thu, 2018-10-11 at 12:38 +0100, Lorenzo Pieralisi wrote:
>>> On Tue, Oct 09, 2018 at 11:08:15AM +0800, Honghui Zhang wrote:
On Mon, 2018-10-08 at 18:23
+++ Dave Hansen [11/10/18 16:47 -0700]:
On 10/11/2018 04:31 PM, Rick Edgecombe wrote:
+ if (check_inc_mod_rlimit(size))
+ return NULL;
+
p = __vmalloc_node_range(size, MODULE_ALIGN, module_alloc_base,
module_alloc_base + MODULES_VSIZE,
On Fri, Sep 28, 2018 at 03:01:49PM +0200, Pierre-Yves MORDRET wrote:
> From: M'boumba Cedric Madianga
>
> This patch adds dma bindings to support DMA/MDMA chaining transfer.
> 1 bit is to manage both DMA FIFO Threshold
> 1 bit is to manage DMA/MDMA Chaining features.
> 2 bits are used to specify
On Oct 12, 2018, at 7:25 AM, Alan Cox wrote:
>> But this really needs to be clarified. Alan said that a bunch of the
>> "yet another Spectre variant" attacks would have been mitigated by
>> this patch. An explanation of *how* would be in order.
>
> Today you have the situation where
On Fri, Oct 12, 2018 at 02:40:50PM +, Moger, Babu wrote:
> That is correct. CPU_SUP_AMD implicitly means x86.
> To be more specific, I will change it to
> "depends on X86_64 && CPU_SUP_AMD" as this feature is for X86_64 only.
No, what I'm saying is, make it dependent *only* on CPU_SUP_AMD.
On 12/10/2018 15:54, David Howells wrote:
Alan Jenkins wrote:
+ open_tree_clone \
+ move_mount \
I'll rename them to test-XXX if you're okay with that.
David
Yes, that's fine.
Feel free to make adaptations you like. I don't have anything planned
for them myself, outside of
On Thu, Oct 11, 2018 at 03:06:09PM -0600, Lina Iyer wrote:
> On Thu, Oct 11 2018 at 11:37 -0600, Sudeep Holla wrote:
[...]
> >
> > Is DDR managed by Linux ? I assumed it was handled by higher exception
> > levels. Can you give examples of resources used by CPU in this context.
> > When CPU can be
> My understanding is that the standard “breadcrumb” is that a cache line is
> fetched into L1D, and that the cacheline in question will go into L1D even if
> it was previously not cached at all. So flushing L1D will cause the timing
> from a probe to be different, but the breadcrumb is still
On 12.10.2018 10:57, Uwe Kleine-König wrote:
> Hello,
>
> On Wed, Oct 10, 2018 at 09:33:26AM +, Vokáč Michal wrote:
>> Normally the PWM output is held LOW when PWM is disabled. This can cause
>> problems when inverted PWM signal polarity is needed. With this behavior
>> the connected circuit
From: Colin Ian King
Trivial fix to spelling mistake in message text
Signed-off-by: Colin Ian King
---
drivers/staging/rtl8723bs/hal/odm_DIG.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/hal/odm_DIG.c
host->chan_{rx,tx} represents the DMA capability of the platform.
Even if DMA is supported, there are cases where we want to use PIO,
for example, data length is short enough as commit 5f52c3552946
("mmc: tmio: use PIO for short transfers") mentioned.
Regarding the hardware control flow, we are
On Fri, 2018-10-12 at 10:13 -0500, Denis Kenzior wrote:
> Hi James,
>
> > > So can't we simply use 'bool' or uint32 as the type for h3
> > > instead
> > > of re-ordering everything
> >
> > The problem is the standard is ambiguious. The only thing that's
> > guaranteed to work for all time is a
On Fri, Oct 12, 2018 at 05:55:28AM -0700, Sodagudi Prasad wrote:
> On 2018-10-10 09:49, Will Deacon wrote:
> >On Tue, Oct 09, 2018 at 01:56:14PM -0700, Sodagudi Prasad wrote:
> >>This is regarding - thread "try to fix contention between expire_timers
> >>and
> >>try_to_del_timer_sync".
>
Hi Greg,
Please pull these two arm64 fixes for 4.19. One of them fixes a nasty
WARN() that has started triggering because we assumed that memory
reservations from firmware would always correspond to regions of the
physical address space that we have mapped as memory. Unfortunately,
some existing
Hi James,
From the links provided in the patch it seems that one cannot pass
char/float/short to va_start(). Fair enough. So if we make h3 an
unsigned int, the issue goes away, no?
For the current version of clang, yes. However, if we're fixing this
for good a char * pointer is the only
On Fri, Oct 12, 2018 at 8:02 AM Alan Cox wrote:
>
> > My understanding is that the standard “breadcrumb” is that a cache line is
> > fetched into L1D, and that the cacheline in question will go into L1D even
> > if it was previously not cached at all. So flushing L1D will cause the
> > timing
On Thu, Sep 20, 2018 at 03:00:42PM +0530, Manish Narani wrote:
> Add documentation for MIO bank required property and Tap Delays optional
> properties in devicetree bindings.
>
> Signed-off-by: Manish Narani
> ---
> .../devicetree/bindings/mmc/arasan,sdhci.txt | 19
>
> 4. Results
> - Without this optimization, the guest pmi handling time is
> ~450 ns, and the max sampling rate is reduced to 250.
> - With this optimization, the guest pmi handling time is ~9000 ns
> (i.e. 1 / 500 of the non-optimization case), and the max sampling
>
On Thu, Oct 11, 2018 at 6:50 PM Nathan Chancellor
wrote:
>
> On Thu, Oct 11, 2018 at 01:31:26PM -0700, ndesaulni...@google.com wrote:
> > by swapping h2 and h3.
> >
> > security/keys/trusted.c:146:17: warning: passing an object that
> > undergoes default
> > argument promotion to 'va_start'
On Thu, Oct 11, 2018 at 05:33:01PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.124 release.
> There are 120 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
On Thu, Oct 11, 2018 at 05:34:47PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.161 release.
> There are 27 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
On Fri, Oct 12, 2018 at 10:05 AM Nick Desaulniers
wrote:
>
> On Fri, Oct 12, 2018 at 8:14 AM Denis Kenzior wrote:
> >
> > Hi James,
> >
> > >> So can't we simply use 'bool' or uint32 as the type for h3 instead
> > >> of re-ordering everything
> > >
> > > The problem is the standard is
On 10/10/2018 13:36, David Howells wrote:
Alan Jenkins wrote:
+ * Copyright (C) 2017 Red Hat, Inc. All Rights Reserved.
+ * Written by David Howells (dhowe...@redhat.com)
Do you want to update that and I can take them into my patchset?
David
Sure :). I've attached a slightly updated
On 10/12/2018 02:43 PM, Lee Jones wrote:
> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
>
>> On 10/12/2018 11:39 AM, Lee Jones wrote:
>>> On Fri, 12 Oct 2018, Vladimir Zapolskiy wrote:
On 10/12/2018 09:03 AM, Lee Jones wrote:
> On Tue, 09 Oct 2018, Vladimir Zapolskiy wrote:
>
On Fri, Oct 12, 2018 at 2:26 PM Jann Horn wrote:
>
> On Fri, Oct 12, 2018 at 11:41 AM Samuel Neves wrote:
> >
> > On Thu, Oct 11, 2018 at 8:25 PM Andy Lutomirski wrote:
> > > What exactly is this trying to protect against? And how many cycles
> > > should we expect L1D_FLUSH to take?
> >
> >
On Thu, Oct 11, 2018 at 03:54:21PM -0700, Kees Cook wrote:
> Right now rand_initialize() is run as an early_initcall(), but it only
> depends on timekeeping_init() (for mixing ktime_get_real() into the
> pools). However, the call to boot_init_stack_canary() for stack canary
> initialization runs
On Thu, 27 Sep 2018 13:39:58 +0200, Amelie Delaunay wrote:
> This patch adds documentation of device tree bindings for the
> STMicroelectronics Multi-Function eXpander (STMFX) MFD core.
>
> Signed-off-by: Amelie Delaunay
> Reviewed-by: Linus Walleij
> ---
>
On 21/09/2018 17:34, David Howells wrote:
Provide an fspick() system call that can be used to pick an existing
mountpoint into an fs_context which can thereafter be used to reconfigure a
superblock (equivalent of the superblock side of -o remount).
This looks like:
int fd =
On Thu, Aug 23, 2018 at 10:24:58AM +0800, piaojun wrote:
> If some error happened before find_vqs, error branch will goto
> virtscsi_remove_vqs to free vqs. Actually the vqs have not been allocated
> successfully, so this will cause wild-pointer-free problem. So
> virtscsi_remove_vqs could be
Hi Guilherme,
Just to let you know - I've done with more urgent issues now,
so I'll be back on this patch on Monday, installing qemu-system-hppa
and debugging the root case.
Thanks,
Dmitry
On Wed, 2018-10-03 at 07:46 -0300, Guilherme Piccoli wrote:
> On Tue, Oct 2, 2018 at 6:33 PM Dmitry
1 - 100 of 1114 matches
Mail list logo
