On 11/09, Yonghong Song wrote:
>
> + if (insn_class == UPROBE_PUSH_INSN) {
> + src_ptr = get_push_reg_ptr(auprobe, regs);
> + reg_width = sizeof_long();
> + sp = regs->sp;
> + if (copy_to_user((void __user *)(sp - reg_width), src_ptr,
> reg_width
Instead of directly assigning reset, fw and rproc ops, put them
in to of_match data and get from that. Currently same ops
are used for all compatibles, but that will change when we add
q6v5-wcss support.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 38 +
IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan
(Lithium) IP. An mdt type single image format is used for the
firmware. So the mdt_load function can be directly used to load
the firmware. Also add the relevant resets required for this core.
Signed-off-by: Sricharan R
---
.../d
Most of the q6v5-pil start function is same for the q6v5-wcss rproc
that will be added later. So split and move out the common pieces
so that the same code can be reused.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 166 -
1 file changed
qcom_mdt_load function loads the mdt type firmware and
initialises the secure memory as well. Make the initialisation only
when requested by the caller, so that the function can be used
by self-authenticating remoteproc as well.
Acked-by: Bjorn Andersson
Signed-off-by: Sricharan R
---
drivers/s
q6v5-wcss core's start function is mostly common
with the q6v5 of msm8996. So reuse that and add
the stop function.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 212 +
1 file changed, 212 insertions(+)
diff --git a/drivers/remoteproc/qc
IPQ8074 has an integrated Hexagon dsp core Q6v5 and a wireless lan
(Lithium) IP. This series adds the remoteproc driver to reset, load
and boot Q6 firmware.
The first patch is to make the mdt_loader authenticate
the firmware only if required, so that the code can be reused for
self-authenticating
Removed unnecessary else block, and removed redundant return and call to kfree
in if block.
Signed-off-by: Ola N. Kaldestad
---
kernel/sysctl.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index d9c31bc..87fbb3e 100644
--- a/kerne
We may have to pass a port's dedicated CPU port to port-wide functions
such as dsa_port_mdb_add, e.g. when offloading bridge device's MDB.
The DSA port-wide functions currently take a non-const struct dsa_port *
as first argument so we cannot make cpu_dp const yet, even though it'd
be more correct
On 11/9/2017 4:46 AM, Borislav Petkov wrote:
On Wed, Nov 08, 2017 at 12:13:12PM -0700, Tyler Baicar wrote:
Currently the GHES code only calls into the AER driver for
recoverable type errors. This is incorrect because errors of
other severities do not get logged by the AER driver and do not
get e
On Thu, Nov 9, 2017 at 1:42 AM, Linus Walleij wrote:
> On Thu, Nov 9, 2017 at 4:51 AM, Stephen Rothwell
> wrote:
>> On Fri, 3 Nov 2017 16:37:24 +1100 Stephen Rothwell
>> wrote:
>>>
>>> After merging the gpio tree, yesterday's linux-next build (arm
>>> multi_v7_defconfig) produced these warning
Reviewed-By: Clement Courbet
Thanks for the addition, Yury ! I've used a modified version of v1
for measuring improvements from find_next_and_bit() on x86 and arm
and found it very useful.
On 11/09/2017 06:45 AM, Mark Brown wrote:
> On Wed, Nov 08, 2017 at 06:27:27PM -0600, Andrew F. Davis wrote:
>> GPIO1 control register is number 51, fix this here.
>>
>> Fixes: bafcbfe429eb ("ASoC: tlv320aic31xx: Make the register values human
>> readable")
>> Signed-off-by: Andrew F. Davis
>> --
When TCP connetion in TCP_TIME_WAIT or TCP_NEW_SYN_RECV state, it can't
get the sport/dport/saddr/daddr from inet_sock.
trace_tcp_set_state may be called when the oldstate in these two states.
Signed-off-by: Yafang Shao
---
include/trace/events/tcp.h | 33 ++---
1 fi
The TCP/IP transition from TCP_LISTEN to TCP_SYN_RECV isn't traced in
the tcp_set_state tracepoint.
In order to trace the whole tcp lifespans, two helpers are introduced,
static inline void __tcp_set_state(struct sock *sk, int state)
static inline void __sk_state_store(struct sock *sk, int newstat
On Wed, 2017-11-08 at 15:25 -0600, Andrew F. Davis wrote:
> The correct DT property for specifying a GPIO used for reset
> is "reset-gpio", fix this here.
>
> Fixes: 4341881d0562 ("ARM: dts: Add devicetree for Gumstix Pepper board")
>
> Signed-off-by: Andrew F. Davis
> ---
> arch/arm/boot/dts/a
Hi Andrew,
On Wed, 2017-11-08 at 15:24 -0600, Andrew F. Davis wrote:
> The property used to specify a GPIO intended for reset is "reset-gpio",
> this binding uses "gpio-reset", as almost all other bindings use the
> former name this use of the latter is certainly not intended and
> was a typo. It
On 09/11/17 15:41, Ulf Hansson wrote:
> On 3 November 2017 at 14:20, Adrian Hunter wrote:
>> From: Venkat Gopalakrishnan
>>
>> This patch adds CMDQ support for command-queue compatible
>> hosts.
>>
>> Command queue is added in eMMC-5.1 specification. This
>> enables the controller to process upto
2017-11-09 00:55-0800, Eduardo Valentin:
> Hello,
>
> On Wed, Nov 08, 2017 at 06:36:52PM +0100, Radim Krčmář wrote:
> > 2017-11-06 12:26-0800, Eduardo Valentin:
> > > Currently, the existing qspinlock implementation will fallback to
> > > test-and-set if the hypervisor has not set the PV_UNHALT fl
From: Markus Elfring
Date: Thu, 9 Nov 2017 15:06:16 +0100
Use the data type "sig_atomic_t" for the variable "running"
so that it can be safely modified by a signal handler.
Fixes: 69e8cc134bcbf0ccfcf852c400b8e6788d1d0038 ("bpf: sockmap sample program")
Signed-off-by: Markus Elfring
---
samples
Due using virtualization it is common to see
many "too much work for irq*" messages.
There are fixes proposed erlier:
- e7328ae1848966181a7ac47e8ae6cddbd2cf55f3 (serial:
8250, increase PASS_LIMIT)
- f4f653e9875e573860e783fecbebde284a8626f5 (serial:
8250, disable "too much work" messages
On 11/09/2017 06:41 AM, Mark Brown wrote:
> On Wed, Nov 08, 2017 at 06:27:25PM -0600, Andrew F. Davis wrote:
>> Simple non-functional changes including:
>>
>> * Fix header copyright tags
>> * Fix spelling errors
>> * Reformat code for easier reading
>> * Move some code blocks to a more natural
Add mclk-fs support to audio graph card
as initially supported in simple card.
Signed-off-by: Olivier Moysan
---
Documentation/devicetree/bindings/sound/audio-graph-card.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/sound/audio-graph-card.txt
b/Docume
The aim of these patches is to port mclk-fs property to audio graph card,
as originally implemented in simple card.
Olivier Moysan (2):
ASoC: add mclk-fs to audio graph card binding
ASoC: add mclk-fs support to audio graph card
.../devicetree/bindings/sound/audio-graph-card.txt | 1 +
soun
Add mclk-fs support to audio graph card
as it was previously implemented in simple card.
Signed-off-by: Olivier Moysan
---
sound/soc/generic/audio-graph-card.c | 47 ++--
1 file changed, 39 insertions(+), 8 deletions(-)
diff --git a/sound/soc/generic/audio-graph-
On Thu, Nov 09, 2017 at 05:33:56PM +0800, Tina Zhang wrote:
> v16->v17:
> 1) modify VFIO_DEVICE_GET_GFX_DMABUF interface. (Alex)
> 2) add comments for x_hot/y_hot. (Gerd)
Hmm, doesn't apply cleanly here.
Tried 4.14-rc8 + gem proxy v2 + this series.
Seems the patches depend on unmerged gvt changes.
On 9 November 2017 at 02:11, Kees Cook wrote:
> On Wed, Nov 8, 2017 at 2:30 PM, Rasmus Villemoes
> wrote:
>>
>> Rasmus Villemoes (6):
>> plugins: implement format_template attribute
>> compiler.h: add __format_template
>
> Could you split these two off and send separately? This seems like a
>
find_bit functions are widely used in the kernel, including hot paths.
This module tests performance of that functions in 2 typical scenarios:
randomly filled bitmap with relatively equal distribution of set and
cleared bits, and sparse bitmap which has 1 set bit for 500 cleared bits.
On ThunderX
On Wed, Nov 08, 2017 at 04:00:38PM -0800, Dave Hansen wrote:
> I'd argue that those two end up looking pretty much the same to an app.
> The only difference is that the slice-local and slice-remote cache hits
> have slightly different access latencies. I don't think it's enough to
> notice.
So if
On Thu, Nov 9, 2017 at 7:29 PM, Colin King wrote:
> From: Colin Ian King
>
> upcall may be assigned a NULL pointer as genlmsg_put can potentially
> return a NULL. Add a null check to avoid a null pointer dereference
> on upcall.
>
> Detected by CoverityScan, CID#728404 ("Dereference null return
On 11/09, Oleg Nesterov wrote:
>
> And. Do you really need ->post_xol() method to emulate "push"? Why we can't
> simply execute it out-of-line if copy_to_user() fails?
>
> branch_post_xol_op() is needed because we can't execute "call" out-of-line,
> we need to restart and try again if copy_to_user(
This affects every kernel I tried, 4.9.[54|35|24], 3.18.27, RH 3.10.0-693*.
The test machine is a Dell R740 with 2X8168 and 384GB.
#include
#include
#include
inline long GetPerf()
{
int _hi, _lo;
__asm__ __volatile__ ("rdtsc":"=a" (_lo), "=d"(_hi));
return ((long) _hi << 32) | _lo;
On Friday, November 03, 2017 06:21:37 PM Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Add ability to the Goldfish FB driver to be recognized by OS via DT.
>
> Signed-off-by: Miodrag Dinic
> Signed-off-by: Goran Ferenc
> Signed-off-by: Aleksandar Markovic
Patch queued for 4.15,
On Friday, November 03, 2017 06:21:36 PM Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Add documentation for DT binding of Goldfish FB driver. The compatible
> string used by OS for binding the driver is "google,goldfish-fb".
>
> Signed-off-by: Miodrag Dinic
> Signed-off-by: Goran
On Thu, Nov 09, 2017 at 02:47:40PM +0100, Greg Kroah-Hartman wrote:
> Was not what? Discussed? Yes it was. I think the lwn.net article even
> says so.
There is absolutely no public track record of any discussion. And if
there was any it seems like a large number of the biggest contributors
and
From: Colin Ian King
upcall may be assigned a NULL pointer as genlmsg_put can potentially
return a NULL. Add a null check to avoid a null pointer dereference
on upcall.
Detected by CoverityScan, CID#728404 ("Dereference null return value")
Fixes: commit ccb1352e76cf ("net: Add Open vSwitch ker
On Thu, Nov 9, 2017 at 3:39 AM, Greentime Hu wrote:
> 2017-11-08 21:18 GMT+08:00 Rob Herring :
>> Please Cc the DT list on bindings.
>
> Sorry. I am not sure what you mean.
> Do you mean add devicet...@vger.kernel.org to cc list?
Yes. Use get_maintainers.pl as a guide.
>> On Tue, Nov 7, 2017 at
On Thu, 2017-11-09 at 10:12 +0100, Greg Kroah-Hartman wrote:
> On Wed, Nov 08, 2017 at 06:10:19PM -0800, Joe Perches wrote:
> > On Wed, 2017-11-08 at 19:10 -0600, Rob Herring wrote:
> > > Add a check warning if SPDX-License-Identifier tags are not used in
> > > newly added files.
> >
> > If this i
[Sorry for the late reply]
On Tue 31-10-17 11:12:38, Jan Kara wrote:
> On Tue 31-10-17 00:39:58, Yang Shi wrote:
[...]
> > I do agree it is not fair and not neat to account to producer rather than
> > misbehaving consumer, but current memcg design looks not support such use
> > case. And, the othe
Em Thu, Nov 09, 2017 at 02:27:19PM +0100, Markus Trippelsdorf escreveu:
> On 2017.11.09 at 10:22 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Nov 09, 2017 at 09:17:49AM +0100, Jiri Olsa escreveu:
> > > Reply-To:
> > > In-Reply-To: <20171109081319.GB236@x4>
> > >
> > > On Thu, Nov 09, 2017 a
The first patch above (https://patchwork.kernel.org/patch/9970181/)
makes the oops go away, but it just papers over the problem. The real
problem is that the watchdog core clears WDOG_HW_RUNNING in
watchdog_stop, and the gpio driver fails to set it in its stop
function when it doesn't actually stop
* Arnd Bergmann wrote:
> On Fri, Oct 27, 2017 at 10:25 PM, Ricardo Neri
> wrote:
>
> > diff --git a/arch/x86/include/asm/inat.h b/arch/x86/include/asm/inat.h
> > index 02aff08..1c78580 100644
> > --- a/arch/x86/include/asm/inat.h
> > +++ b/arch/x86/include/asm/inat.h
> > @@ -97,6 +97,16 @@
> >
Since commit 705bc96c2c15313c ("irqchip: renesas-intc-irqpin: Add
minimal runtime PM support"), when an IRQ is used for wakeup, the INTC
block's module clock (if exists) is manually kept running during system
suspend, to make sure the device stays active.
However, this explicit clock handling is m
Hi all,
If an interrupt controller in a Renesas ARM SoC is part of a Clock
Domain, and it is part of the wakeup path, it must be kept active during
system suspend.
Currently this is handled in all interrupt controller drivers by
explicitly increasing the use count of the module clock when
Since commit 6f46aedb9c85873b ("irqchip: renesas-irqc: Add wake-up
support"), when an IRQ is used for wakeup, the INTC
block's module clock is manually kept running during system suspend, to
make sure the device stays active.
However, this explicit clock handling is merely a workaround for a
failu
On Wed, Nov 8, 2017 at 8:10 PM, Joe Perches wrote:
> On Wed, 2017-11-08 at 19:10 -0600, Rob Herring wrote:
>> Add a check warning if SPDX-License-Identifier tags are not used in
>> newly added files.
>
> If this is to be done, and I think it's not a great idea,
Which part? SPDX tags or checking n
Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable
when wake-up is enabled"), when a GPIO is used for wakeup, the GPIO
block's module clock (if exists) is manually kept running during system
suspend, to make sure the device stays active.
However, this explicit clock handling
On Wed, Nov 08, 2017 at 07:26:30PM +0100, Luis R. Rodriguez wrote:
> On Tue, Nov 07, 2017 at 05:30:09PM +0100, Greg Kroah-Hartman wrote:
> > Now that the SPDX tag is in all driver core files, that identifies the
> > license in a specific and legally-defined manner.
>
> Takashi and Jiri mentioned t
On 11/09, Yonghong Song wrote:
>
> This patch extends the emulation to "push "
> insns. These insns are typical in the beginning
> of the function. For example, bcc
> in https://github.com/iovisor/bcc repo provides
> tools to measure funclantency, detect memleak, etc.
> The tools will place uprobes
On Thu 09-11-17 14:30:18, Vitaly Kuznetsov wrote:
> Michal Hocko writes:
[...]
> > How realistic is that the host gives only such a small amount of memory
> > btw?
>
> It happens all the time, Hyper-V host will gradually increase guest's
> memory when Dynamic Memory is enabled. Moreover, there's
On Tue, Nov 07, 2017 at 06:55:22PM +0100, Giulio Benetti wrote:
> Hi,
>
> Il 07/11/2017 12:05, Maxime Ripard ha scritto:
> > Hi,
> >
> > On Tue, Nov 07, 2017 at 11:03:30AM +0100, Giulio Benetti wrote:
> > > This patch adds device tree mali node compatible with r6p2 utgard kernel
> > > driver
> >
On 3 November 2017 at 14:20, Adrian Hunter wrote:
> From: Venkat Gopalakrishnan
>
> This patch adds CMDQ support for command-queue compatible
> hosts.
>
> Command queue is added in eMMC-5.1 specification. This
> enables the controller to process upto 32 requests at
> a time.
>
> Adrian Hunter con
On Wednesday, October 18, 2017 04:45:31 PM Ondrej Zary wrote:
> On Wednesday 18 October 2017, David Miller wrote:
> > From: John Paul Adrian Glaubitz
> > Date: Wed, 18 Oct 2017 15:14:27 +0200
> >
> > > Hi Bartlomiej!
> > >
> > > On 10/18/2017 02:56 PM, Bartlomiej Zolnierkiewicz wrote:
> > >> igafb
On Wed, Nov 08, 2017 at 05:07:46PM -0600, Rob Herring wrote:
> On Thu, Nov 2, 2017 at 10:16 AM, Greg KH wrote:
> > [resend without the full diffstat as lkml and some email systems didn't
> > like to see emails with 12k lines...]
> >
> > Hi,
> >
> > As discussed at the Maintainers Summit last week
On 3 November 2017 at 14:20, Adrian Hunter wrote:
> Add CQHCI initialization and implement CQHCI operations for Intel GLK.
>
> Signed-off-by: Adrian Hunter
This looks good to me!
Kind regards
Uffe
> ---
> drivers/mmc/host/Kconfig | 1 +
> drivers/mmc/host/sdhci-pci-core.c | 155
>
On 3 November 2017 at 14:20, Adrian Hunter wrote:
> card_busy_detect() doesn't set a correct timeout, and it doesn't take care
> of error status bits. Stop using it for blk-mq.
I think this changelog isn't very descriptive. Could you please work
on that for the next version.
>
> Signed-off-by: A
On Thu, Nov 9, 2017 at 1:48 PM, Greg KH wrote:
> On Thu, Nov 09, 2017 at 12:40:36PM +, Ben Hutchings wrote:
>> On Thu, 2017-11-09 at 13:21 +0100, Arnd Bergmann wrote:
>> > On Thu, Nov 9, 2017 at 1:08 PM, Greg KH wrote:
>> > > On Thu, Nov 09, 2017 at 12:55:30PM +0100, Arnd Bergmann wrote:
>> [
On Tuesday, October 17, 2017 06:01:58 PM Stefan Agner wrote:
> On 2017-10-17 15:56, Bartlomiej Zolnierkiewicz wrote:
> > Hi,
> >
> > Stefan/Shawn:
> >
> > Should I merge this patch? It seems to be still needed:
> >
> > https://www.spinics.net/lists/linux-fbdev/msg23112.html
>
> In my opinion ye
Michal Hocko writes:
> On Wed 08-11-17 17:16:19, Vitaly Kuznetsov wrote:
>> Michal Hocko writes:
>>
>> > On Wed 08-11-17 16:39:49, Vitaly Kuznetsov wrote:
>> >> Michal Hocko writes:
>> >>
>> >> > On Wed 08-11-17 14:01:55, Vitaly Kuznetsov wrote:
>> >> >> Hyper-V balloon driver needs to hotplu
Am Donnerstag, den 09.11.2017, 13:19 +0100 schrieb Andrey Konovalov:
>
> This isn't the "BOGUS urb xfer" warning, this is "BOGUS urb flags". So
> 2 means the URB_ISO_ASAP flag, which is passed in urb->transfer_flags
> but not allowed. And as far as I understand, it gets set because uurb
> (which i
Instead of x86_hyper being either NULL on bare metal or a pointer to a
struct hypervisor_x86 in case of the kernel running as a guest merge
the struct into x86_platform and x86_init.
This will remove the need for wrappers making it hard to find out what
is being called. With dummy functions added
Add a new guest_late_init hook to the hypervisor_x86 structure. It
will replace the current kvm_guest_init() call which is changed to
make use of the new hook.
Cc: pbonz...@redhat.com
Cc: rkrc...@redhat.com
Cc: k...@vger.kernel.org
Signed-off-by: Juergen Gross
Acked-by: Paolo Bonzini
---
arch/
Booting a Xen PVH guest requires a special boot entry as it is
mandatory to setup some Xen-specific interfaces rather early. When grub
or OVMF are used as boot loaders, however, those will fill the boot
parameters in zeropage and there is no longer a need to do something
PVH specific in the early b
The x86_hyper pointer is only used for checking whether a virtual
device is supporting the hypervisor the system is running on.
Use an enum for that purpose instead and drop the x86_hyper pointer.
Cc: k...@microsoft.com
Cc: haiya...@microsoft.com
Cc: sthem...@microsoft.com
Cc: akata...@vmware.com
Add a test for ACPI_FADT_NO_VGA when scanning the FADT and set the new
flag x86_platform.legacy.no_vga accordingly.
Cc: r...@rjwysocki.net
Cc: len.br...@intel.com
Cc: pa...@ucw.cz
Cc: linux...@vger.kernel.org
Signed-off-by: Juergen Gross
---
arch/x86/include/asm/x86_init.h | 1 +
arch/x86/kerne
In case we are booted via the default boot entry by a generic loader
like grub or OVMF it is necessary to distinguish between a HVM guest
with a device model supporting legacy devices and a PVH guest without
device model.
PVH guests will always have x86_platform.legacy.no_vga set and
x86_platform.
On 2017.11.09 at 10:22 -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Nov 09, 2017 at 09:17:49AM +0100, Jiri Olsa escreveu:
> > Reply-To:
> > In-Reply-To: <20171109081319.GB236@x4>
> >
> > On Thu, Nov 09, 2017 at 09:13:19AM +0100, Markus Trippelsdorf wrote:
> > > On 2017.11.05 at 15:40 +0100, I
>> Which information (or wording) would you find more appropriate
>> at these places?
>
> Hi! Basically dropping your patch and instead of the "Unknown error"
> return to user reason why BQ2415X_BOOST_MODE_STATUS or
> BQ2415X_FAULT_STATUS commands failed. Or at least instead of the
> "Unknown erro
On Wed, Nov 08, 2017 at 05:25:20PM -0600, Andrew F. Davis wrote:
> On 11/08/2017 04:18 PM, Mark Brown wrote:
> > There is code in the driver to use the GPIO, including in the probe
> > where the GPIO is requested and set to high (which will bring it out of
> > reset if the default state was low).
Em Thu, Nov 09, 2017 at 09:17:49AM +0100, Jiri Olsa escreveu:
> Reply-To:
> In-Reply-To: <20171109081319.GB236@x4>
>
> On Thu, Nov 09, 2017 at 09:13:19AM +0100, Markus Trippelsdorf wrote:
> > On 2017.11.05 at 15:40 +0100, Ingo Molnar wrote:
> > util/parse-events.l:343:26: note: in expansion of ma
On Wed, Nov 08, 2017 at 11:46:54AM -0800, Dave Hansen wrote:
> From: Dave Hansen
>
> This is largely code from Andy Lutomirski. I fixed a few bugs
> in it, and added a few SWITCH_TO_* spots.
...
> Signed-off-by: Dave Hansen
> Cc: Moritz Lipp
> Cc: Daniel Gruss
> Cc: Michael Schwarz
> Cc: R
On Wed 08-11-17 17:16:19, Vitaly Kuznetsov wrote:
> Michal Hocko writes:
>
> > On Wed 08-11-17 16:39:49, Vitaly Kuznetsov wrote:
> >> Michal Hocko writes:
> >>
> >> > On Wed 08-11-17 14:01:55, Vitaly Kuznetsov wrote:
> >> >> Hyper-V balloon driver needs to hotplug memory in smaller chunks and t
On 09/11/17 15:07, Ulf Hansson wrote:
> On 3 November 2017 at 14:20, Adrian Hunter wrote:
>> For blk-mq, add support for completing requests directly in the ->done
>> callback. That means that error handling and urgent background operations
>> must be handled by recovery_work in that case.
>
> As
On Thursday 09 November 2017 14:04:19 SF Markus Elfring wrote:
> > Better fix would be to display separate messages; user is probably
> > interested in what failed...
>
> Which information (or wording) would you find more appropriate
> at these places?
Hi! Basically dropping your patch and instea
Reviewed-by: Dan Carpenter
regards,
dan carpenter
On Thu, Nov 9, 2017 at 9:34 AM, Christoph Hellwig wrote:
> On Thu, Nov 09, 2017 at 07:16:52AM +0100, Luc Van Oostenryck wrote:
>> sparc is big-endian only but sparse assumes the same endianness
>> as the building machine.
>> This is problematic for code which expect __BYTE_ORDER__ being
>> correct
On Monday, October 16, 2017 09:04:46 PM Christophe JAILLET wrote:
> This patch serie tries to fix several issues found in the error handling
> code of 'au1200fb_drv_probe()'.
> The 5 first patches fixes various issues (double free, missing error code,
> un-released resources on error, incorrect IR
On Thu, Nov 09, 2017 at 08:46:58AM +0100, Jiri Olsa wrote:
SNIP
> > Jirka,
> >
> > I carefully looked at bp_cpuinfo[] and nr_slots[] data structures.
> > nr_slots[] is an array of length two (one slot of TYPE_INST and
> > another for TYPE_DATA).
> > The accounting "thinks" that there is one limi
On Thu, Nov 09, 2017 at 01:41:24PM +0200, Nikolay Borisov wrote:
> On 9.11.2017 05:22, NeilBrown wrote:
> > @@ -493,12 +496,18 @@ void __d_drop(struct dentry *dentry)
> > } else
> > hlist_bl_lock(b);
> > __hlist_bl_del(&dentry->d_hash);
> > - d
On Thu, Nov 9, 2017 at 6:49 AM, Arvind Yadav wrote:
> Here, em28xx_free_v4l2 is release "v4l2->dev->v4l2"
> Which is allready release by em28xx_v4l2_init.
>
> Signed-off-by: Arvind Yadav
Hi Arvind,
I still see the crash with your patch.
Thanks!
em28xx 1-1:0.0: Disconnecting
em28xx 1-1:0.0: Re
On 3 November 2017 at 14:20, Adrian Hunter wrote:
> For blk-mq, add support for completing requests directly in the ->done
> callback. That means that error handling and urgent background operations
> must be handled by recovery_work in that case.
As the mmc docs sucks, I think it's important tha
> Better fix would be to display separate messages; user is probably
> interested in what failed...
Which information (or wording) would you find more appropriate
at these places?
Regards,
Markus
On Thu, Nov 09, 2017 at 04:58:18PM +0530, Manjeet Pawar wrote:
> simple_strtoul() is obselete now, so using newer function kstrtoul()
>
> Signed-off-by: Manjeet Pawar
> Signed-off-by: Vinay Kumar Rijhwani
> Signed-off-by: Rohit Thapliyal
NAK NAK NAK.
You haven't tested this on a 64-bit big-en
On 09/11/17 14:52, Linus Walleij wrote:
> On Thu, Nov 9, 2017 at 8:56 AM, Adrian Hunter wrote:
>> On 08/11/17 11:30, Linus Walleij wrote:
>>> On Fri, Nov 3, 2017 at 2:20 PM, Adrian Hunter
>>> wrote:
>>>
Recovery is simpler to understand if it is only used for errors. Create a
separate
Add ldbar spr to sysfs. The spr holds thread level In-Memory Collection (IMC)
counter configuration data. Exposing this will help to understand the current
configuration of thread-level counters in the system.
Primarily, Bit 0 of ldbar says whether the counters are enabled o
On Fri, Mar 31, 2017 at 10:00:40AM +0100, Zubair Lutfullah Kakakhel wrote:
> Hi,
>
> Couple of patches that convert the MIPSfpga platform to using
> the generic kernels
>
> Based on v4.11-rc4.
Thanks, Applied for 4.15.
Tweaks to fix conflicts:
- Use separate board-xilfpga.its.S.
- Add 32r2 and
On Wed, Dec 14, 2016 at 03:09:42PM +, Matt Redfearn wrote:
> The generic MIPS system type allows building a board agnostic kernel and
> should be the default starting point for users, so set it as the default
> system type in Kconfig.
> Since ip22 is no longer the default, update ip22_defconfig
On 09/11/17 14:26, Linus Walleij wrote:
> On Wed, Nov 8, 2017 at 3:14 PM, Adrian Hunter wrote:
>> On 08/11/17 11:22, Linus Walleij wrote:
>>> On Fri, Nov 3, 2017 at 2:20 PM, Adrian Hunter
>>> wrote:
>
>>> (...)
>
+EXPORT_SYMBOL(cqhci_resume);
>>>
>>> Why would the CQE case require special
On Thu, Nov 09, 2017 at 08:27:28AM +0200, Gilad Ben-Yossef wrote:
> On Tue, Nov 7, 2017 at 12:43 PM, Dan Carpenter
> wrote:
> > On Tue, Nov 07, 2017 at 09:40:02AM +, Gilad Ben-Yossef wrote:
> >> --- a/drivers/staging/ccree/ssi_pm.c
> >> +++ b/drivers/staging/ccree/ssi_pm.c
> >> @@ -90,20 +90,
On Thu, Nov 9, 2017 at 1:55 AM, Kees Cook wrote:
> On Wed, Nov 8, 2017 at 8:00 AM, Arnd Bergmann wrote:
>> I noticed that __getnstimeofday() is a rather odd interface, with
>> a number of quirks:
>>
>> - The caller may come from NMI context, but the implementation is not NMI
>> safe
>> - The cal
On Wed, Nov 08, 2017 at 11:46:53AM -0800, Dave Hansen wrote:
>
> From: Dave Hansen
>
> Global pages stay in the TLB across context switches. Since all
> contexts share the same kernel mapping, we use global pages to
> allow kernel entries in the TLB to survive when we context
> switch.
>
> But
On Thu, Nov 9, 2017 at 8:56 AM, Adrian Hunter wrote:
> On 08/11/17 11:30, Linus Walleij wrote:
>> On Fri, Nov 3, 2017 at 2:20 PM, Adrian Hunter
>> wrote:
>>
>>> Recovery is simpler to understand if it is only used for errors. Create a
>>> separate function for card polling.
>>>
>>> Signed-off-by
Em Thu, Nov 09, 2017 at 08:36:22AM +0100, Jiri Olsa escreveu:
> On Wed, Nov 08, 2017 at 01:03:21PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Nov 08, 2017 at 11:27:38AM +0100, Jiri Olsa escreveu:
> > > From: Jiri Olsa
> > >
> > > On Fedora systems the perl and python CFLAGS/LDFLAGS includ
Em Thu, Nov 09, 2017 at 08:27:49AM +0100, Jiri Olsa escreveu:
> On Wed, Nov 08, 2017 at 01:06:40PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Nov 08, 2017 at 11:27:39AM +0100, Jiri Olsa escreveu:
> > > There's no user of those.
> >
> > [acme@jouet linux]$ find tools/ -type f | xargs grep F
On Thu, Nov 09, 2017 at 12:40:36PM +, Ben Hutchings wrote:
> On Thu, 2017-11-09 at 13:21 +0100, Arnd Bergmann wrote:
> > On Thu, Nov 9, 2017 at 1:08 PM, Greg KH wrote:
> > > On Thu, Nov 09, 2017 at 12:55:30PM +0100, Arnd Bergmann wrote:
> [...]
> > > > I think if you upload the branch to the s
Hi,
Kindly ignore this patch, I send a wrong version. Will send out the
right one.
Thanks,
Anju
On Thursday 09 November 2017 05:43 PM, Anju T Sudhakar wrote:
Add ldbar spr to sysfs. The spr holds thread level In-Memory Collection (IMC)
counter configuration data. Exposing this will help t
From: Markus Elfring
Date: Thu, 9 Nov 2017 13:37:28 +0100
Duplicate error messages were used so far in this function implementation.
Make them unique instead.
This issue was detected by using the Coccinelle software.
Fixes: 69e8cc134bcbf0ccfcf852c400b8e6788d1d0038 ("bpf: sockmap sample program"
On Wed, Nov 08, 2017 at 06:27:27PM -0600, Andrew F. Davis wrote:
> GPIO1 control register is number 51, fix this here.
>
> Fixes: bafcbfe429eb ("ASoC: tlv320aic31xx: Make the register values human
> readable")
> Signed-off-by: Andrew F. Davis
> ---
We should send this as a bug fix to stable but
On Thu, Nov 9, 2017 at 8:43 AM, Adrian Hunter wrote:
> On 08/11/17 11:38, Linus Walleij wrote:
>> On Fri, Nov 3, 2017 at 2:20 PM, Adrian Hunter
>> wrote:
>>
>>> There are only a few things the recovery needs to do. Primarily, it just
>>> needs to:
>>> Determine the number of bytes transf
2017-11-07 4:26 GMT+08:00 Eduardo Valentin :
> Currently, the existing qspinlock implementation will fallback to
> test-and-set if the hypervisor has not set the PV_UNHALT flag.
>
> This patch gives the opportunity to guest kernels to select
> between test-and-set and the regular queueu fair lock i
701 - 800 of 1015 matches
Mail list logo
