From: John Crispin
Add a binding for the USB phy on Mediatek/Ralink SoCs.
Signed-off-by: John Crispin
Signed-off-by: Harvey Hunt
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
---
Changes in V6:
* Add MT7628 binding
* Add optional reg pro
From: John Crispin
Add a driver to setup the USB phy on Mediatek/Ralink SoCs.
The driver sets up power and host mode, but also needs to
configure PHY registers for the MT7628 and MT7688.
Signed-off-by: John Crispin
Signed-off-by: Harvey Hunt
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@
Ingo Molnar writes:
> * Willy Tarreau wrote:
>
>> Nowadays we could use similar methods using RDTSC providing more accurate
>> counting. This doesn't provide a lot of entropy of course, given that a
>> 2 GHz machine will at most count 31 bits there. But I tend to think that
>> what matters durin
On Thu, 10 Aug 2017, Prarit Bhargava wrote:
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index cedafa008de5..1ddf04201047 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -25,6 +25,7 @@
> #include
> #include
> #include
> +#include
Tha
On 2017-08-15 14:02, Felipe Balbi wrote:
Hi,
Danilo Krummrich writes:
thanks for reviewing.
np :-)
On 2017-08-15 12:03, Felipe Balbi wrote:
Hi,
Danilo Krummrich writes:
udc_stop needs to be called before gadget driver unbind. Otherwise
it
might happen that udc drivers still call into t
Hi,
Ard and I have worked together to implement vmap stack support for
arm64. This supersedes our earlier vmap stack RFCs [0,1]. The git author
stats are a little misleading, as I've teased parts out into smaller
patches for review.
The series is based on our stack dump rework [2,3], which can be
Before we add yet another stack to the kernel, it would be nice to
ensure that we consistently organise stack definitions and related
helper functions.
This patch moves the basic IRQ stack defintions to to
live with their task stack counterparts. Helpers used for unwinding are
moved into , where
We allocate our IRQ stacks using a percpu array. This allows us to generate our
IRQ stack pointers with adr_this_cpu, but bloats the kernel Image with the boot
CPU's IRQ stack. Additionally, these are packed with other percpu variables,
and aren't guaranteed to have guard pages.
When we enable VMA
In some cases, an architecture might wish its stacks to be aligned to a
boundary larger than THREAD_SIZE. For example, using an alignment of
double THREAD_SIZE can allow for stack overflows smaller than
THREAD_SIZE to be detected by checking a single bit of the stack
pointer.
This patch allows arc
This patch adds stack overflow detection to arm64, usable when vmap'd stacks
are in use.
Overflow is detected in a small preamble executed for each exception entry,
which checks whether there is enough space on the current stack for the general
purpose registers to be saved. If there is not enough
This patch enables arm64 to be built with vmap'd task and IRQ stacks.
As vmap'd stacks are mapped at page granularity, stacks must be a multiple of
PAGE_SIZE. This means that a 64K page kernel must use stacks of at least 64K in
size.
To minimize the increase in Image size, IRQ stacks are dynamica
Our __die() implementation tries to dump the stack memory, in addition
to a backtrace, which is problematic.
For contemporary 16K stacks, this can be a lot of data, which can take a
long time to dump, and can push other useful context out of the kernel's
printk ringbuffer (and/or a user's scrollba
From: Ard Biesheuvel
For historical reasons, we leave the top 16 bytes of our task and IRQ
stacks unused, a practice used to ensure that the SP can always be
masked to find the base of the current stack (historically, where
thread_info could be found).
However, this is not necessary, as:
* When
Both unwind_frame() and dump_backtrace() try to check whether a stack
address is sane to access, with very similar logic. Both will need
updating in order to handle overflow stacks.
Factor out this logic into a helper, so that we can avoid further
duplication when we add overflow stacks.
Signed-o
On 15/08/17 12:52, Daniel Borkmann wrote:
> On 08/14/2017 07:55 PM, Edward Cree wrote:
>> if (arg_type == ARG_ANYTHING) {
>> if (is_pointer_value(env, regno)) {
>> @@ -1639,10 +1675,13 @@ static int check_call(struct bpf_verifier_env *env,
>> int func_id, int insn_idx)
>> }
>
Currently we define SEGMENT_ALIGN directly in our vmlinux.lds.S.
This is unfortunate, as the EFI stub currently open-codes the same
number, and in future we'll want to fiddle with this.
This patch moves the definition to our , where it can be
used by both vmlinux.lds.S and the EFI stub code.
Sig
In subsequent patches, we will detect stack overflow in our exception
entry code, by verifying the SP after it has been decremented to make
space for the exception regs.
This verification code is small, and we can minimize its impact by
placing it directly in the vectors. To avoid redundant modifi
From: Ard Biesheuvel
Given that adr_this_cpu already requires a temp register in addition
to the destination register, tweak the instruction sequence so that sp
may be used as well.
This will simplify switching to per-cpu stacks in subsequent patches. While
this limits the range of adr_this_cpu,
The EFI stub is intimately coupled with the kernel, and takes advantage
of this by relocating the kernel at a weaker alignment than the
documented boot protocol mandates.
However, it does so by assuming it can align the kernel to the segment
alignment, and assumes that this is 64K. In subsequent p
Some headers rely on PAGE_* definitions from , but cannot
include this due to potential circular includes. For example, a number
of definitions in rely on PAGE_SHIFT, and
includes .
This requires users of these definitions to include both headers, which
is fragile and error-prone.
This patch am
Currently we define THREAD_SIZE and THREAD_SIZE_ORDER separately, with
the latter dependent on particular CONFIG_ARM64_*K_PAGES definitions.
This is somewhat opaque, and will get in the way of future modifications
to THREAD_SIZE.
This patch cleans this up, defining both in terms of a common
THREAD
On Tue, Aug 15, 2017 at 10:20:18PM +1000, Aleksa Sarai wrote:
> On 08/15/2017 10:15 PM, Roman Gushchin wrote:
> > Generally, oom_score_adj should have a meaning only on a cgroup level,
> > so extending it to the system level doesn't sound as a good idea.
>
> But wasn't the original purpose of oom_
Hello.
While searching for races in the Linux kernel I've come across
"drivers/usb/misc/adutux.ko" module. Here is a question that I came up
with while analyzing results. Lines are given using the info from Linux
v4.12.
Consider the following case:
Thread 1: Thread 2:
adu_
On Tue, Jul 25, 2017 at 08:10:41PM +0800, Shaokun Zhang wrote:
> This patch adds support for DDRC PMU driver in HiSilicon SoC chip, Each
> DDRC has own control, counter and interrupt registers and is an separate
> PMU. For each DDRC PMU, it has 8-fixed-purpose counters which have been
> mapped to 8
On Mon, Aug 14, 2017 at 08:29:46PM +0200, Mike Galbraith wrote:
> On Mon, 2017-08-14 at 13:34 -0400, Luiz Capitulino wrote:
> > On Mon, 14 Aug 2017 19:01:09 +0200
> >
> > > What is the source of the load balancing inducing such latency when a
> > > single
> > > task is affine to a CPU? If this is
This commit implements a new TCP congestion control algorithm, namely Agile-SD.
A detailed description of Agile-SD is published in the following 2 articles:
[1] "Agile-SD: a Linux-based TCP congestion control algorithm for supporting
high-speed and short-distance networks",
Alrshah, M.A., Othman
From: Jun Gao
Add MT7622 i2c binding to binding file and change the compatible
information formats of all SoCs to the same.
Signed-off-by: Jun Gao
---
Documentation/devicetree/bindings/i2c/i2c-mtk.txt | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation
From: Jun Gao
Add i2c compatible for MT7622. Compare to MT8173 i2c controller,
MT7622 limits message numbers to 255, and does not support 4GB
DMA mode.
Signed-off-by: Jun Gao
---
drivers/i2c/busses/i2c-mt65xx.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/i2c/bus
This patch series based on v4.13-rc1, include MT7622 i2c dt-binding
and compatible.
changes since v2:
- Remove all the length settings from mt7622_i2c_quirks
changes since v1:
- Modify commit message
- Revise dt-binding documentation
Jun Gao (2):
dt-bindings: i2c: Add MediaTek MT7622 i2c bindi
Hi,
On Mon, Aug 14, 2017 at 12:15:16PM +, Reizer, Eyal wrote:
> The following commits:
> commit c815fdebef44 ("wlcore: spi: Populate config firmware data")
> commit d776fc86b82f ("wlcore: sdio: Populate config firmware data")
>
> Populated the nvs entry for wilink6 and wilink7 only while it i
Hi Pavel,
On Mon, Aug 14, 2017 at 03:38:16PM +0200, Pavel Machek wrote:
> I'm (still) trying to debug "N950 not booting" situation. I'm stuck
> with black screen, so I thought it would be cool to use RGB led for
> debugging...
>
> Unfortunately, I don't see required dts bindings in the mainline.
Hello.
While searching for races in the Linux kernel I've come across
"drivers/isdn/hardware/avm/c4.ko" module. Here is a question that I came
up with while analyzing results. Lines are given using the info from
Linux v4.12.
Consider the following case:
Thread 1: Thread 2:
Am Dienstag, den 15.08.2017, 15:59 +0300 schrieb Anton Volkov:
> Hello.
>
> While searching for races in the Linux kernel I've come across
> "drivers/usb/misc/adutux.ko" module. Here is a question that I came up
> with while analyzing results. Lines are given using the info from Linux
> v4.12.
On Tue, Aug 15, 2017 at 08:09:50AM -0400, Theodore Ts'o wrote:
> On Tue, Aug 15, 2017 at 10:05:46AM +0200, Ingo Molnar wrote:
> > > > * Willy Tarreau wrote:
> > > > >
> > > > > Nowadays we could use similar methods using RDTSC providing more
> > > > > accurate
> > > > > counting. This doesn't pr
Hi Guodong,
On 2017/7/4 3:03, Guodong Xu wrote:
> On Mon, Jul 3, 2017 at 9:32 PM, Wei Xu wrote:
>> Hi Guodong,
>>
>> On 2017/7/3 14:04, Guodong Xu wrote:
>>> Hi, Xu Wei
>>>
>>>
>>>
>>> On Mon, Jul 3, 2017 at 6:47 PM, Will Deacon wrote:
On Sun, Jul 02, 2017 at 06:36:57PM -0500, Bjorn Helgaas
[ I'm back from vacation! ]
On Wed, 9 Aug 2017 17:51:33 +0200
Daniel Lezcano wrote:
> Well, may be the instruction pointer thing is not a good idea.
>
> I learnt from this experience, an overloaded kernel with a lot of
> interrupts can hang the console and issue RCU stall.
>
> However, someon
I like the idea of this patch, but it's really churny for some reason.
Any chance you could clean it up?
Some examples of what I mean inline.
On Fri, Aug 04, 2017 at 11:30:42AM -0700, Mark Salyzyn wrote:
> From: Kevin Brodsky
>
> AArch32 processes are currently installed a special [vectors] pag
Hi Guodong,
On 2017/8/10 3:37, Guodong Xu wrote:
> This patchset enables config items in arm64/defconfig for HiKey960. All
> of them correspond to real functions on HiKey960.
>
> Including:
> - Kirin PCIe
> - PMIC support, hi6421v530
> - syscon reboot mode
> - serdev bus
> - OP-TEE
> - K3 D
Hi Guodong,
On 2017/8/14 10:50, Guodong Xu wrote:
> This patchset adds more device nodes for hi3660 and hikey960, including:
> - cpu idle states
> - L2 cache
> - PMU
> - OP-TEE
> - reboot
> - pstore
> - DMA
> - watchdog
>
> Patch 7 fixes an issue in mmc nodes, by adding 'reset'
> Patch 8
On Sat, 2017-08-12 at 23:27 -0700, Nadav Amit wrote:
> Ben Hutchings wrote:
>
> > On Wed, 2017-08-09 at 12:41 -0700, Greg Kroah-Hartman wrote:
> >> 4.4-stable review patch. If anyone has any objections, please let me know.
> >>
> >> --
> >>
> >> From: Mel Gorman
> >>
> >> com
On 15.08.2017 16:20, Oliver Neukum wrote:
Am Dienstag, den 15.08.2017, 15:59 +0300 schrieb Anton Volkov:
Hello.
While searching for races in the Linux kernel I've come across
"drivers/usb/misc/adutux.ko" module. Here is a question that I came up
with while analyzing results. Lines are given usi
On Fri, Aug 04, 2017 at 11:31:40AM -0700, Mark Salyzyn wrote:
> From: Kevin Brodsky
>
> Make it possible to disable the kuser helpers by adding a KUSER_HELPERS
> config option (enabled by default). When disabled, all kuser
> helpers-related code is removed from the kernel and no mapping is done
>
On Fri, Aug 04, 2017 at 11:28:36PM +0800, Dou Liyang wrote:
> Hi will,
>
> At 08/04/2017 09:30 PM, Will Deacon wrote:
> > On Wed, Jul 26, 2017 at 09:34:26PM +0800, Dou Liyang wrote:
> > > Commit a7be6e5a7f8d ("mm: drop useless local parameters of
> > > __register_one_node()") removes the last user
On Tue, 2017-08-15 at 08:15 -0400, Jordan Glover wrote:
> Hello,
> I write to put different perspective into the topic. I'm glad that
> kernel developers care about performance optimizations and I see how
> 10% overhead can be a problem for some. On the other hand last ten
> years gave us 1000% fas
Hi,
On Mon, Aug 14, 2017 at 11:57:15AM -0700, Badhri Jagan Sridharan wrote:
> Hi Heikki,
>
> While testing with different type-c phones available in the market,
> With some phones, I noticed that supports_usb_power_delivery
> reports "no" eventhough an explicit pd contract has been
> established.
On Tue, Aug 15, 2017 at 12:47:36PM +0200, Thomas Gleixner wrote:
> 8<---
>
> --- a/arch/x86/kernel/tsc.c
> +++ b/arch/x86/kernel/tsc.c
> @@ -1360,3 +1360,19 @@ unsigned long calibrate_delay_is_known(v
> return 0;
> }
> #endif
> +
> +u64 __init tsc_early_random(void)
> +{
>
Hello.
While searching for races in the Linux kernel I've come across
"drivers/input/touchscreen/ucb1400_ts.ko" module. Here is a question
that I came up with while analyzing results. Lines are given using the
info from Linux v4.12.
Consider the following case:
Thread 1: T
On Tue, 15 Aug 2017, Borislav Petkov wrote:
> On Tue, Aug 15, 2017 at 12:47:36PM +0200, Thomas Gleixner wrote:
> > 8<---
> >
> > --- a/arch/x86/kernel/tsc.c
> > +++ b/arch/x86/kernel/tsc.c
> > @@ -1360,3 +1360,19 @@ unsigned long calibrate_delay_is_known(v
> > return 0;
> > }
Hi David,
On 09/08/17 23:51, David Daney wrote:
> For an already existing irqdomain hierarchy, as might be obtained via
> a call to pci_enable_msix_range(), a PCI driver wishing to add an
> additional irqdomain to the hierarchy needs to be able to insert the
> irqdomain to that already initialized
On Tue, 2017-08-15 at 12:53 +0100, Mark Brown wrote:
> On Tue, Aug 15, 2017 at 04:07:02PM +0800, Ryder Lee wrote:
>
> > This patch update interrupt property since we only use ASYS IRQ
> > in the driver, and this may confuse people.
>
> > - interrupts = ,
> > -;
>
From: Colin Ian King
An optional discovery status should be printed with a pr_cont
and needs a leading space to make it more readable. The final
new line should also be a pr_cont and the indentation is out
by one, so fix that too.
Signed-off-by: Colin Ian King
---
drivers/scsi/mpt3sas/mpt3sas_
On Tue, 15 Aug 2017, Colin King wrote:
> From: Colin Ian King
>
> The while loop never terminates because the loop counter i is never
> decremented. Fix this by decrementing i.
>
> Detected by CoverityScan, CID#751073 ("Infinite Loop")
>
> Signed-off-by: Colin Ian King
> ---
> drivers/usb/ga
On Tue, Aug 15, 2017 at 9:08 AM, mohamedalrshah
wrote:
> +
> +/* Agile-SD Parameters */
> +struct agilesdtcp {
> + u32 loss_cwnd; /* congestion window at last loss.*/
Please rebase your change on top of the latest net-next changes and
update this module to use the latest app
State of a register doesn't matter if it wasn't read in reaching an exit;
a write screens off all reads downstream of it from all explored_states
upstream of it.
This allows us to prune many more branches; here are some processed insn
counts for some Cilium programs:
Program bef
On Tue, Aug 15, 2017 at 09:51:40PM +0800, Ryder Lee wrote:
> On Tue, 2017-08-15 at 12:53 +0100, Mark Brown wrote:
> > What harm does having the extra information in the bindings do? If it's
> > possible there might be a use for the extra interrupt it seems better to
> > have people describe it.
On Mon, 2017-08-14 at 22:15 -0700, David Miller wrote:
> From: Ding Tianhong
> Date: Tue, 15 Aug 2017 11:23:22 +0800
>
> > Some devices have problems with Transaction Layer Packets with the Relaxed
> > Ordering Attribute set. This patch set adds a new PCIe Device Flag,
> > PCI_DEV_FLAGS_NO_RELAX
On Mon, Aug 14, 2017 at 04:02:43PM -0400, Joe Lawrence wrote:
> Add exported API for livepatch modules:
>
> klp_shadow_get()
> klp_shadow_attach()
> klp_shadow_get_or_attach()
> klp_shadow_update_or_attach()
> klp_shadow_detach()
> klp_shadow_detach_all()
>
> that implement "shadow" v
On Tue, Aug 15, 2017 at 01:50:35PM +0100, Mark Rutland wrote:
> Ard and I have worked together to implement vmap stack support for
> arm64. This supersedes our earlier vmap stack RFCs [0,1]. The git author
> stats are a little misleading, as I've teased parts out into smaller
> patches for review.
On Tue, Aug 15, 2017 at 9:08 AM, mohamedalrshah
wrote:
> This commit implements a new TCP congestion control algorithm, namely
> Agile-SD.
Also, please use a summary line for your patch that is more in keeping
with Linux style, using spaces rather than dashes, and leading with
tcp: or tcp_agile_
On Tue, 2017-08-15 at 06:58 -0700, Eric Dumazet wrote:
> On Mon, 2017-08-14 at 22:15 -0700, David Miller wrote:
> > From: Ding Tianhong
> > Date: Tue, 15 Aug 2017 11:23:22 +0800
> >
> > > Some devices have problems with Transaction Layer Packets with the Relaxed
> > > Ordering Attribute set. Thi
From: Colin Ian King
The for loop is statement is missing an indent, add it.
Signed-off-by: Colin Ian King
---
drivers/scsi/osst.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/osst.c b/drivers/scsi/osst.c
index 97ab5f160bc6..241908aca468 100644
--- a/drivers
On Tue, Aug 15, 2017 at 11:00:04AM +0800, Lan Tianyu wrote:
> On 2017年08月12日 03:35, Konrad Rzeszutek Wilk wrote:
> > On Fri, Aug 11, 2017 at 03:00:20PM +0200, Radim Krčmář wrote:
> >> 2017-08-11 10:11+0200, David Hildenbrand:
> >>> On 11.08.2017 09:49, Lan Tianyu wrote:
> Hi Konrad:
> Th
Hello.
While searching for races in the Linux kernel I've come across
"drivers/net/irda/via-ircc.ko" module. Here are questions that I came up
with while analyzing results. Lines are given using the info from Linux
v4.12.
Consider the following case:
Thread 1:Thread 2:
via_i
On Tue, Aug 15, 2017 at 6:36 AM, Heikki Krogerus
wrote:
> Hi,
>
> On Mon, Aug 14, 2017 at 11:57:15AM -0700, Badhri Jagan Sridharan wrote:
>> Hi Heikki,
>>
>> While testing with different type-c phones available in the market,
>> With some phones, I noticed that supports_usb_power_delivery
>> repor
On Mon, Aug 14, 2017 at 03:52:26PM -0700, David Rientjes wrote:
> On Mon, 14 Aug 2017, Roman Gushchin wrote:
>
> > diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
> > index dec5afdaa36d..22108f31e09d 100644
> > --- a/Documentation/cgroup-v2.txt
> > +++ b/Documentation/cgroup
Hi Joseph,
Am Mittwoch, 9. August 2017, 18:04:08 CEST schrieb Joseph Chen:
> change in v9:
> PATCH V9 1/12: (1) fix spelling issue: s/Chip/chip/
> (2) apply tag: Acked-for-MFD-by: Lee Jones
> PATCH V9 2/12: apply tag: Acked-for-MFD-by: Lee Jones
> PATCH V9 3/12: None
> PATCH V9 4/12
Loop more people to review the patch.
2017-08-15 19:15 GMT+08:00, Dongjiu Geng :
> The revision 0x300 generic error data entry is different
> from the old version, but currently iterating through the
> GHES estatus blocks does not take into account this difference.
> This will lead to failure to
This patch fixes the following soft lockup:
BUG: soft lockup - CPU#0 stuck for 23s! [weston:307]
On weston idle-timeout the IP is powered down and reset
asserted. On weston resume we get a massive vblank
IRQ storm due to the LDI registers having lost some state.
This state loss is caused by ade
On Tue, Aug 15, 2017 at 5:18 AM, Robin Murphy wrote:
> On 14/08/17 21:08, Rob Herring wrote:
>> +linuxppc-dev
>>
>> On Fri, Aug 11, 2017 at 11:29 AM, Robin Murphy wrote:
>>> Moving DMA configuration to happen later at driver probe time had the
>>> unnoticed side-effect that we now perform DMA con
2017-08-15 11:00+0800, Lan Tianyu:
> On 2017年08月12日 03:35, Konrad Rzeszutek Wilk wrote:
>> On Fri, Aug 11, 2017 at 03:00:20PM +0200, Radim Krčmář wrote:
>>> 2017-08-11 10:11+0200, David Hildenbrand:
On 11.08.2017 09:49, Lan Tianyu wrote:
> On 2017年08月11日 01:50, Konrad Rzeszutek Wilk wrote:
On Tue, Aug 15, 2017 at 02:00:06PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 15 Aug 2017 09:36:20 +0200
>
> Replace the specification of data structures by variable references
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a b
On Tue, Aug 15, 2017 at 03:48:18PM +0200, Thomas Gleixner wrote:
> > > +u64 __init tsc_early_random(void)
> > > +{
> > > + u64 uninitialized_var(res);
> > > + int i;
> > > +
> > > + if (!boot_cpu_has(X86_FEATURE_TSC))
> > > + return res;
> > > +
> > > + res ^= rdtsc();
> > > + for (i = 0; i
From: Colin Ian King
req->response_type is being assigned the sizeof TB_CFG_PKG_RESET
and should actually be assigned TB_CFG_PKG_RESET. Fix this.
Signed-off-by: Colin Ian King
---
drivers/thunderbolt/ctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thunderbolt/
On Tue, Aug 15, 2017 at 03:45:25AM -0700, Guenter Roeck wrote:
> On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.12.8 release.
> > There are 65 patches in this series, all will be posted as a response
> > to this one. If anyone has any i
On Tue, Aug 15, 2017 at 03:31:33PM +0100, Colin King wrote:
> From: Colin Ian King
>
> req->response_type is being assigned the sizeof TB_CFG_PKG_RESET
> and should actually be assigned TB_CFG_PKG_RESET. Fix this.
>
> Signed-off-by: Colin Ian King
IIRC I already acked this some time ago ;-)
A
On Tue, 15 Aug 2017, Theodore Ts'o wrote:
> On Tue, Aug 15, 2017 at 03:48:18PM +0200, Thomas Gleixner wrote:
> > > > +u64 __init tsc_early_random(void)
> > > > +{
> > > > + u64 uninitialized_var(res);
> > > > + int i;
> > > > +
> > > > + if (!boot_cpu_has(X86_FEATURE_TSC))
> > > >
On 8/13/17 1:21 AM, Julia Lawall wrote:
These uart_ops structures are only stored in the ops field of a
uart_port structure and this fields is const, so the uart_ops
structures can also be const.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
Acked-by: Timur Tabi
On 08/14/2017 11:02 PM, Michael Ellerman wrote:
Khalid Aziz writes:
On 08/10/2017 07:20 AM, Michael Ellerman wrote:
Khalid Aziz writes:
A protection flag may not be valid across entire address space and
hence arch_validate_prot() might need the address a protection bit is
being set on to e
Without the triggered buffer code, we get a link error:
drivers/iio/adc/at91-sama5d2_adc.o: In function `at91_adc_probe':
at91-sama5d2_adc.c:(.text+0x938): undefined reference to
`devm_iio_triggered_buffer_setup'
This adds a Kconfig 'select' statement like other ADC
drivers have it already.
Fix
From: Benjamin Herrenschmidt
> Sent: 15 August 2017 02:34
> On Tue, 2017-08-15 at 09:16 +0800, Jike Song wrote:
> > > Taking a step back, though, why does vfio-pci perform this check in the
> > > first place? If a malicious guest already has control of a device, any
> > > kind of interrupt spoofing
On 2017/8/15 22:03, Eric Dumazet wrote:
> On Tue, 2017-08-15 at 06:58 -0700, Eric Dumazet wrote:
>> On Mon, 2017-08-14 at 22:15 -0700, David Miller wrote:
>>> From: Ding Tianhong
>>> Date: Tue, 15 Aug 2017 11:23:22 +0800
>>>
Some devices have problems with Transaction Layer Packets with the
With CONFIG_THERMAL=m, a built-in aspeed pwm tacho driver causes
a link error:
drivers/hwmon/aspeed-pwm-tacho.o: In function `aspeed_pwm_tacho_probe':
aspeed-pwm-tacho.c:(.text+0x7f0): undefined reference to
`thermal_of_cooling_device_register'
This adds a dependency similar to what other hwmon
On Fri, Aug 04, 2017 at 05:29:06PM +0100, Robin Murphy wrote:
> Sudeep reports that the logic got slightly broken when a PCI iommu-map
> entry targets an IOMMU marked as disabled in DT, since of_pci_map_rid()
> succeeds in following a phandle, and of_iommu_xlate() doesn't return an
> error value, b
I noticed that in 4.13.0-rc4 there is a new error in dmesg on my sparc64
t5120 server: can't allocate MSI-X affinity masks.
[ 30.274284] qla2xxx [:00:00.0]-0005: : QLogic Fibre Channel HBA Driver:
10.00.00.00-k.
[ 30.274648] qla2xxx [:10:00.0]-001d: : Found an ISP2432 irq 21 iobase
On Tue, Aug 15, 2017 at 04:47:47PM +0200, Arnd Bergmann wrote:
> With CONFIG_THERMAL=m, a built-in aspeed pwm tacho driver causes
> a link error:
>
> drivers/hwmon/aspeed-pwm-tacho.o: In function `aspeed_pwm_tacho_probe':
> aspeed-pwm-tacho.c:(.text+0x7f0): undefined reference to
> `thermal_of_co
Lorenzo, Will,
On 25.07.17 10:32:37, Ganapatrao Kulkarni wrote:
> ARM IORT specification(rev. C) has added provision to define proximity
> domain in SMMUv3 IORT table. Adding required code to parse Proximity
> domain and set numa_node of smmv3 platform devices.
>
> Add code to parse proximity do
On Sat 2017-07-29 20:36:36, Nikitas Angelinas wrote:
> The error variable in do_syslog() is preemptively set to the error code
> before the error condition is checked, and then set to 0 if the error
> condition is not encountered. This is not necessary, as it is likely
> simpler to return immediate
On Mon, Aug 14, 2017 at 07:40:51PM -0700, David Miller wrote:
> From: Marcelo Ricardo Leitner
> Date: Mon, 14 Aug 2017 22:58:14 -0300
>
> > On Tue, Aug 15, 2017 at 10:43:59AM +0900, 吉藤英明 wrote:
> >> > diff --git a/net/sctp/ipv6.c b/net/sctp/ipv6.c
> >> > index 2a186b201ad2..a15d691829c6 100644
> >
On Tue, Aug 15, 2017 at 05:02:13PM +0200, Robert Richter wrote:
> Lorenzo, Will,
>
> On 25.07.17 10:32:37, Ganapatrao Kulkarni wrote:
> > ARM IORT specification(rev. C) has added provision to define proximity
> > domain in SMMUv3 IORT table. Adding required code to parse Proximity
> > domain and
On Tue, 2017-08-15 at 12:50 +0100, Mark Brown wrote:
> On Tue, Aug 15, 2017 at 05:09:14PM +0800, sean.w...@mediatek.com wrote:
> > From: Sean Wang
> >
> > add dt-binding document for MediaTek MT6380 PMIC
>
> Please use subject lines reflecting the style for the subsystem.
Hi , Mark
do you mean
The patch
regulator: mt6380: Add support for MT6380
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.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
On Tue, Aug 15, 2017 at 11:06:35PM +0800, Sean Wang wrote:
> On Tue, 2017-08-15 at 12:50 +0100, Mark Brown wrote:
> > Please use subject lines reflecting the style for the subsystem.
> do you mean should i use "dt-bindings: regulator: mediatek" similarly as
> the prefix instead of the one i curre
The patch
regulator: Add document for MediaTek MT6380 regulator
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hou
On Tue, Aug 15, 2017 at 10:45:17AM +0200, Stephan Mueller wrote:
> Am Dienstag, 15. August 2017, 00:21:05 CEST schrieb Theodore Ts'o:
>
> Hi Theodore,
>
> > Have you looked at section 3.1.1 of the above cited paper?
> >
> > http://eprint.iacr.org/2012/251.pdf
>
> Thanks for the hint, but th
If users give two options --show-total-period
and --show-nr-samples, show their proper usage because
the two options can not be used at the same time.
Cc: Namhyung Kim
Cc: Jiri Olsa
Signed-off-by: Taeung Song
---
tools/perf/builtin-annotate.c | 8 ++--
1 file changed, 6 insertions(+), 2 de
Cc: Namhyung Kim
Cc: Jiri Olsa
Signed-off-by: Taeung Song
---
tools/perf/ui/browsers/annotate.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/tools/perf/ui/browsers/annotate.c
b/tools/perf/ui/browsers/annotate.c
index 80f38da..faca1b9 100644
--- a/tools/pe
Hello,
Add --show-nr-samples option to perf-annotate
so that it corresponds with perf-report.
And support the three view based on percent,
total period and number of samples on the annotate TUI browser,
circulating them like below:
Percent -> Period -> Samples -> Percent ...
I'd appreciate so
Add --show-nr-samples option to perf-annotate
so that it corresponds with perf-report.
Cc: Namhyung Kim
Cc: Milian Wolff
Cc: Jiri Olsa
Signed-off-by: Taeung Song
---
tools/perf/builtin-annotate.c | 2 ++
tools/perf/util/annotate.c| 6 +-
2 files changed, 7 insertions(+), 1 deletion(-)
With a existing 't' hotkey, support the three view based on percent,
total period and number of samples on the annotate TUI browser,
circulating them like below:
Percent -> Period -> Samples -> Percent ...
Suggested-by: Namhyung Kim
Cc: Milian Wolff
Cc: Jiri Olsa
Signed-off-by: Taeung Song
The new lockdep support for completions causeed the stack usage
in dm-integrity to explode, in case of write_journal from 504 bytes
to 1120 (using arm gcc-7.1.1):
drivers/md/dm-integrity.c: In function 'write_journal':
drivers/md/dm-integrity.c:827:1: error: the frame size of 1120 bytes is larger
401 - 500 of 848 matches
Mail list logo
