On Thu, 2015-07-23 at 15:27 -0700, Spencer Baugh wrote:
> From: Brian Bunker
>
> AIX servers using VIOS servers that virtualize FC cards will have a
> problem booting without support for START_STOP_UNIT.
>
> v2: Cite sb3r36 exactly, clean up if conditions
>
> Signed-off-by: Brian Bunker
> Sign
Hi Jiri,
I will check this issue ASAP, thanks for report this!
Best Regards
Haibo Chen
> -Original Message-
> From: Jiri Slaby [mailto:jsl...@suse.cz]
> Sent: Thursday, July 30, 2015 5:32 PM
> To: Chen Haibo-B51421
> Cc: Ulf Hansson; linux-...@vger.kernel.org; Linux kernel mailing list
On Fri, 2015-07-31 at 09:55 +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> On Thu, 30 Jul 2015 11:32:05 -0400 Paul Gortmaker
> wrote:
> >
> > Well, it only shows up when we cross compile for mips. It does not
> > seem to be showing up for any other arch (and we cover ~10 of them).
> > Nor does i
When memory_failure() is called on a page which are just freed after page
migration from soft offlining, the counter num_poisoned_pages is raised twice.
So let's fix it with using TestSetPageHWPoison.
Signed-off-by: Naoya Horiguchi
---
mm/memory-failure.c | 4 ++--
1 file changed, 2 insertions(+
Now page freeing code doesn't consider PageHWPoison as a bad page, so by
setting it before completing the page containment, we can prevent the error
page from being reused just after successful page migration.
I added TTU_IGNORE_HWPOISON for try_to_unmap() to make sure that the page
table entry is
The race condition addressed in commit add05cecef80 ("mm: soft-offline: don't
free target page in successful page migration") was not closed completely,
because that can happen not only for soft-offline, but also for hard-offline.
Consider that a slab page is about to be freed into buddy pool, and
In "just unpoisoned" path, we do put_page and then unlock_page, which is a
wrong order and causes "freeing locked page" bug. So let's fix it.
Signed-off-by: Naoya Horiguchi
---
mm/memory-failure.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git v4.2-rc4.orig/mm/memory-failu
"non anonymous thp" case is still racy with freeing thp, which causes panic
due to put_page() for refcount-0 page. It seems that closing up this race
might be hard (and/or not worth doing,) so let's give up the error handling
for this case.
Signed-off-by: Naoya Horiguchi
---
v1 -> v2:
- keep pr_e
This is v2 of hwpoison fix series for v4.2.
I reflected the feedback for v1, and tried another solution for "reuse just
after soft-offline" problem (see patch 5/5.)
General description (mostly identical to v1)
===
Recently I addressed a few of hwpoison race problems and the patche
On Wed, 2015-07-22 at 15:01 -0700, Spencer Baugh wrote:
> From: Joern Engel
>
> Make the warning about unsupported SCSI opcode more useful:
>
> - Add in the initiator name so we know who's sending it.
> - Print the warning even for opcodes that spc_parse_cdb() knows about
>but that we don'
On Wed, 2015-07-22 at 15:08 -0700, Spencer Baugh wrote:
> From: Roland Dreier
>
> It's not necessarily a fatal error if a command with a data-out phase
> has a data length that differs from the transport data length (e.g.
> PERSISTENT RESERVE OUT might have a parameter list length in the CDB
> th
Hi Roger,
On 07/06/2015 11:46 PM, Roger Quadros wrote:
> Currently the extcon code notifiers the interested listeners
> before it updates the extcon state with the new state.
> This will cause the listeners that use extcon_cable_get_state()
> to get the stale state and loose the new state.
>
> Fi
On Tue, 2015-07-21 at 18:38 -0700, Roland Dreier wrote:
> On Tue, Jul 21, 2015 at 1:57 AM, Sagi Grimberg
> wrote:
> > How were you able to get a chained SG list in the target code?
>
> Local hack. So this bug can't be hit in current mainline code, but
> patch improves the code and removes a hid
On 30-07-15, 23:24, Stephen Boyd wrote:
> On 07/29, Viresh Kumar wrote:
> > With "operating-points-v2" bindings, its possible to specify the OPP to
>
> s/its/it's/ ?
>
> > which the device must be switched, before suspending.
> >
> > This patch adds support for getting that information.
> >
> >
On 07/30, Sudeep Holla wrote:
>
>
> On 29/07/15 18:37, Stephen Boyd wrote:
> >On 07/23/2015 04:10 AM, Sudeep Holla wrote:
> >>On some ARM based systems, a separate Cortex-M based System Control
> >>Processor(SCP) provides the overall power, clock, reset and system
> >>control. System Control and
On 07/29, Viresh Kumar wrote:
> With "operating-points-v2" bindings, its possible to specify the OPP to
s/its/it's/ ?
> which the device must be switched, before suspending.
>
> This patch adds support for getting that information.
>
> Reviewed-by: Bartlomiej Zolnierkiewicz
> Signed-off-by: Vi
> Fixes commit eae79b4f3e82 ("rsi: fix memory leak in
> rsi_load_ta_instructions()")
> which stopped the driver from functioning.
>
> Firmware data has been allocated using vmalloc(), resulting in memory
> that cannot be used for DMA. Hence the firmware was first copied to a
> buffer allocated w
On 07/31, Viresh Kumar wrote:
> On 30-07-15, 22:51, Stephen Boyd wrote:
> > > + opp->u_volt = microvolt[0];
> > > + opp->u_volt_min = microvolt[1];
> > > + opp->u_volt_max = microvolt[2];
> >
> > Should the default be 0 and ULONG_MAX for volt_min/volt_max when
> > there's on element?
>
> I am not
Hi Antoine,
On Thu, 30 Jul 2015 14:35:51 +0200
Antoine Tenart wrote:
> The BG2Q SoC uses cpufreq-dt for cpufreq. Register a platform device for
> this.
>
> Signed-off-by: Antoine Tenart
> ---
> arch/arm/mach-berlin/berlin.c | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --g
On 30-07-15, 23:10, Stephen Boyd wrote:
> On 07/29, Viresh Kumar wrote:
> > +bool dev_pm_opp_is_turbo(struct dev_pm_opp *opp)
> > +{
> > + struct dev_pm_opp *tmp_opp;
> > +
> > + opp_rcu_lockdep_assert();
> > +
> > + tmp_opp = rcu_dereference(opp);
> > + if (unlikely(IS_ERR_OR_NULL(tmp_opp)
On 07/29, Viresh Kumar wrote:
> With opp-v2 DT bindings, few OPPs can be used only for the boost mode.
> But using such OPPs require the boost mode to be supported by cpufreq
> driver.
>
> We will parse DT bindings only during ->init() and so can enable boost
> support only after registering cpufr
On 07/29, Viresh Kumar wrote:
> Support for parsing operating-points-v2 bindings is in place now, lets
> modify cpufreq-dt driver to use them.
>
> For backward compatibility we will continue to support earlier bindings.
> Special handling for that is required, to make sure OPPs are initialized
> f
On 30-07-15, 23:07, Stephen Boyd wrote:
> On 07/29, Viresh Kumar wrote:
> > With "operating-points-v2" its possible to tell which devices share
> > OPPs. We already have infrastructure to decode that information.
> >
> > This patch adds following APIs:
> > - of_get_cpus_sharing_opps: Returns cpuma
On 07/29, Viresh Kumar wrote:
> In some cases it wouldn't be known at time of driver registration, if
> the driver needs to support boost frequencies.
>
> For example, while getting boost information from DT with opp-v2
> bindings, we need to parse the bindings for all the CPUs to know if
> turbo/
On 07/29, Viresh Kumar wrote:
> From: Bartlomiej Zolnierkiewicz
>
> cpufreq table entries for OPPs with turbo modes enabled, should be
> marked with CPUFREQ_BOOST_FREQ flag. This ensures that these states are
> only used while operating in boost or turbo mode.
>
> Cc: Tomasz Figa
> Cc: Michael
Incoming packets in high speed are randomly corrupted by h/w
resulting in multiple errors. This workaround makes FS as
default mode in all affected socs by disabling HS chirp
signalling.This errata does not affect FS and LS mode.
Forces all HS devices to connect in FS mode for all socs
affected by
On 30-07-15, 20:53, Rafael J. Wysocki wrote:
> Well, on ACPI systems we actually do probe CPU devices. We have a processor
> driver there that binds to CPU devices and the cpufreq driver is just a
> frontend to that.
Hmm, maybe I need to look at that in detail..
> So question is what prevents DT
Hi Spencer & Alexei,
On Tue, 2015-07-21 at 15:07 -0700, Spencer Baugh wrote:
> From: Alexei Potashnik
>
> Make sure all non-READ SCSI commands get targ_xfer_tag initialized
> to 0x, not just WRITEs.
>
> Double-free of a TUR cmd object occurs under the following scenario:
>
> 1. TUR rec
On 07/29, Viresh Kumar wrote:
> +bool dev_pm_opp_is_turbo(struct dev_pm_opp *opp)
> +{
> + struct dev_pm_opp *tmp_opp;
> +
> + opp_rcu_lockdep_assert();
> +
> + tmp_opp = rcu_dereference(opp);
> + if (unlikely(IS_ERR_OR_NULL(tmp_opp)) || !tmp_opp->available) {
IS_ERR_OR_NULL alread
On Thu, 2015-07-30 at 18:51 -0700, Florian Fainelli wrote:
> On 30/07/15 15:51, David Miller wrote:
> > From: David Miller
> > Date: Thu, 30 Jul 2015 14:19:35 -0700 (PDT)
> >
> >> This looks fine, series applied, thanks.
> >
> > I think your control block is too large, you'll need to rework this
On Mon, Jul 20, 2015 at 09:00:09AM +0100, Mel Gorman wrote:
> From: Mel Gorman
>
> This series started with the idea to move LRU lists to pgdat but this
> part was more important to start with. It was written against 4.2-rc1 but
> applies to 4.2-rc3.
>
> The zonelist cache has been around for a
On 07/29, Viresh Kumar wrote:
> With "operating-points-v2" its possible to tell which devices share
> OPPs. We already have infrastructure to decode that information.
>
> This patch adds following APIs:
> - of_get_cpus_sharing_opps: Returns cpumask of CPUs sharing OPPs (only
> valid with v2 bind
On Thu, Jul 30, 2015 at 7:28 PM, Alban Bedel wrote:
> Currently CONFIG_ARCH_HAVE_CUSTOM_GPIO_H is defined for all MIPS
> machines, and each machine type provides its own gpio.h. However
> only a handful really implement the GPIO API, most just forward
> everythings to gpiolib.
>
> The Alchemy mach
On Mon, Jul 20, 2015 at 09:00:19AM +0100, Mel Gorman wrote:
> From: Mel Gorman
>
> The primary purpose of watermarks is to ensure that reclaim can always
> make forward progress in PF_MEMALLOC context (kswapd and direct reclaim).
> These assume that order-0 allocations are all that is necessary f
Kbuild descends into drivers/soc/tegra/ only when CONFIG_ARCH_TEGRA
is enabled. (see drivers/soc/Makefile)
$(CONFIG_ARCH_TEGRA) in drivers/soc/tegra/Makefile always evaluates
to 'y'.
Signed-off-by: Masahiro Yamada
---
drivers/soc/tegra/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 de
On Thu, Jul 30, 2015 at 04:35:58PM +0200, Maciej S. Szmigiero wrote:
> Adjust set DAI format function in fsl_ssi driver so it
> doesn't fail and clears RXDIR in AC'97 mode.
>
> Signed-off-by: Maciej Szmigiero
> ---
> sound/soc/fsl/fsl_ssi.c |8 +---
> 1 files changed, 5 insertions(+), 3
On 30-07-15, 22:51, Stephen Boyd wrote:
> > + opp->u_volt = microvolt[0];
> > + opp->u_volt_min = microvolt[1];
> > + opp->u_volt_max = microvolt[2];
>
> Should the default be 0 and ULONG_MAX for volt_min/volt_max when
> there's on element?
I am not still sure how the regulator API is going
On Fri, Jul 31, 2015 at 07:27:19AM +0200, Markus Pargmann wrote:
> Hi,
>
> On Thu, Jul 30, 2015 at 04:34:19PM +0200, Maciej S. Szmigiero wrote:
> > AC'97 bus can support asymmetric playback/capture rates
> > so enable them in this case in fsl_ssi driver.
> >
> > Signed-off-by: Maciej Szmigiero
>
On 07/29, Viresh Kumar wrote:
> This adds support in OPP library to parse and create list of OPPs from
> operating-points-v2 bindings. It takes care of most of the properties of
> new bindings (except shared-opp, which will be handled separately).
>
> For backward compatibility, we keep supporting
Hello, Mel.
On Mon, Jul 20, 2015 at 09:00:18AM +0100, Mel Gorman wrote:
> From: Mel Gorman
>
> High-order watermark checking exists for two reasons -- kswapd high-order
> awareness and protection for high-order atomic requests. Historically we
> depended on MIGRATE_RESERVE to preserve min_free_
Hi all,
Changes since 20150730:
The at91 tree gained a conflict against the arm-soc tree.
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 4897
4980 files changed, 244177 insertions(+), 113249 dele
On Fri, 2015-07-31 at 11:02 +0530, Shraddha Barke wrote:
> This patch fixes the following checkpatch.pl warning:
>
> WARNING: do not add new typedefs
> Signed-off-by: Shraddha Barke
> ---
> drivers/staging/wilc1000/coreconfigurator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> d
Hi.
2015-07-30 10:30 GMT+09:00 Masahiro Yamada :
> Hi,
>
>
> 2015-07-30 0:23 GMT+09:00 Rob Herring :
>> On Wed, Jul 29, 2015 at 8:22 AM, Ian Campbell
>> wrote:
>>> On Wed, 2015-07-29 at 20:07 +0900, Masahiro Yamada wrote:
Hi Ian,
2015-07-27 19:35 GMT+09:00 Ian Campbell :
On Thu, Jul 30, 2015 at 04:35:23PM +0200, Maciej S. Szmigiero wrote:
> Instantiate AC'97 CODEC in fsl_ssi driver AC'97 mode.
>
> Signed-off-by: Maciej Szmigiero
> ---
> sound/soc/fsl/fsl_ssi.c | 21 +
> 1 files changed, 21 insertions(+), 0 deletions(-)
>
> diff --git a/sou
On 07/29, Viresh Kumar wrote:
> Later commits would add support for new OPP bindings and this would be
> required then. So, lets do it in a separate patch to make it easily
> reviewable.
>
> Another change worth noticing is INIT_LIST_HEAD(&opp->node). We weren't
> doing it earlier as we never trie
This patch fixes the following checkpatch.pl warning:
WARNING: do not add new typedefs
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging
This patch fixes the following checkpatch.pl warning:
WARNING: do not add new typedefs
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging/
On 31 Jul 2015 10:49, "Shraddha Barke" wrote:
>
> This patch fixes the following checkpatch.pl warning:
>
> WARNING: braces {} are not necessary for single statement blocks
There should be one line space between your commit log
and Signed-off-by line.
> Signed-off-by: Shraddha Barke
> ---
> dr
Hi,
On Thu, Jul 30, 2015 at 04:34:19PM +0200, Maciej S. Szmigiero wrote:
> AC'97 bus can support asymmetric playback/capture rates
> so enable them in this case in fsl_ssi driver.
>
> Signed-off-by: Maciej Szmigiero
> ---
> sound/soc/fsl/fsl_ssi.c |4 +++-
> 1 files changed, 3 insertions(+)
This patch fixes the following checkpatch.pl warning:
WARNING: Missing a blank line after declarations
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging/
On 30-07-15, 15:04, Christoph Lameter wrote:
> You need to CC someone at SGI for this I guess. Robin? Nate? Dimitri?
>
> I am definitely not the right guy to be on the CC list.
Sorry about that. It happened because get_maintainers failed to
identify those people. Probably MAINTAINERS need some up
Alexander Shishkin writes:
> Alexander Shishkin writes:
>
>> Alexander Shishkin writes:
>>
>>> Hi Greg and everybody,
>>
>> Seems like a polite nudge might be in order. :)
>
> Greg.
Ping.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to maj
This patch fixes the following checkpatch.pl warning:
WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: Shraddha Barke
---
drivers/staging/wilc1000/coreconfigurator.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/staging/wilc1000/cor
On Thu, Jul 30, 2015 at 9:22 PM, Borislav Petkov wrote:
> On Thu, Jul 30, 2015 at 02:22:06PM -0700, Andy Lutomirski wrote:
>> Great. There's an opcode that invokes an interrupt gate that's not
>> marked as allowing unprivileged access, and that opcode doesn't appear
>> in the SDM. It appears in
Sure, I'll do that. Just wanted to know whether I should split the patches and
send them in this same mail thread (may be something like [PATCH 01/04 V2])
or should I start new threads and send them separately to the respective
maintainers.
Thanks and Regards,
Saurabh Karajgaonkar
On Thu, Jul 30
On Thu, Jul 30, 2015 at 06:25:06PM +0200, Jan Lübbe wrote:
> On Mi, 2015-07-29 at 17:03 +0800, Haibo Chen wrote:
> > tuning-step is the delay cell steps in tuning procedure. The default
> > value of tuning-step is 1. For imx6 series usdhc, tuning procedure can
> > be passed when the tuning-step val
Jan Kara writes:
>> > Yes, if userspace truncates the file, the situation we end up with is
>> > basically the same. However for truncate to happen some malicious process
>> > has to come and truncate the file - a failure scenario that is acceptable
>> > for most use cases since it doesn't happen
rcu: Don't disable preemption for Tiny and Tree RCU readers
Because preempt_disable() maps to barrier() for non-debug builds,
it forces the compiler to spill and reload registers. Because Tree
RCU and Tiny RCU now only appear in CONFIG_PREEMPT=n builds, these
barrier() instances generate needless
On Thu, 11 Jun 2015, Peter Zijlstra wrote:
> Right, I had a peek earlier at how fasync worked but came away confused.
>
> Today I seem to have had better luck. Installing fasync allocates memory
> and sets filp->f_flags |= FASYNC, which upon the demise of the file
> descriptor ensures the allocat
Hi Florian,
On 07/31/2015 01:51 PM, Florian Fainelli wrote:
> On 30/07/15 15:51, David Miller wrote:
>> From: David Miller
>> Date: Thu, 30 Jul 2015 14:19:35 -0700 (PDT)
>>
>>> This looks fine, series applied, thanks.
>>
>> I think your control block is too large, you'll need to rework this
>> so
On Thu, Jul 30, 2015 at 02:22:06PM -0700, Andy Lutomirski wrote:
> Great. There's an opcode that invokes an interrupt gate that's not
> marked as allowing unprivileged access, and that opcode doesn't appear
> in the SDM. It appears in the APM opcode map with no explanation at
> all.
>
> Thanks,
> On Jul 30, 2015, at 20:02, Neil Horman wrote:
>
> On Thu, Jul 30, 2015 at 11:48:17AM +0800, yalin wang wrote:
>>
>>> On Jul 29, 2015, at 18:34, Thomas Gleixner wrote:
>>>
>>> On Tue, 28 Jul 2015, Andrew Morton wrote:
>>>
On Tue, 28 Jul 2015 11:59:01 -0400 David Kershner
wrote:
On Fri, 2015-17-07 at 13:20:31 UTC, Luis Henriques wrote:
> After commit 0fd972a7d91d ("module: relocate module_init from init.h to
> module.h")
> ans-lcd module fails to build with:
>
> drivers/macintosh/ans-lcd.c:201:1: warning: data definition has no type or
> storage class [enabled by defaul
On Mon, 2015-20-07 at 10:45:51 UTC, Alexey Kardashevskiy wrote:
> The existing code stores the amount of memory allocated for a TCE table.
> At the moment it uses @offset which is a virtual offset in the TCE table
> which is only correct for a one level tables and it does not include
> memory alloc
On Thu, Jul 30, 2015 at 11:12:44AM -0700, Andy Lutomirski wrote:
> On Thu, Jul 30, 2015 at 6:09 AM, cee1 wrote:
> > Hi all,
> >
> > I'm interested in the idea of AF_BUS.
> >
> > There have already been varies discussions about it:
> > * Missing the AF_BUS - https://lwn.net/Articles/504970/
> > * K
Hi Roger,
I add minor comment about code clean.
After I modified it by myself, I applied it on extcon-fixes.
Best Regards,
Chanwoo Choi
On 07/07/2015 10:06 PM, Roger Quadros wrote:
> Users of find_cable_index_by_name() will cause a kernel hang
> as the while loop counter is never incremented and
On Thu, Jul 30, 2015 at 11:12 AM, Joe Stringer wrote:
> Signed-off-by: Joe Stringer
> ---
> net/openvswitch/vport.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/openvswitch/vport.c b/net/openvswitch/vport.c
> index d14f594..baa018f 100644
> --- a/net/openvswitch/vport.c
> +++
Range breakpoints will do the wrong thing if the address isn't
aligned. While we're there, add comments about why it's safe for
instruction breakpoints.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/hw_breakpoint.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/x86/ke
Hi, Peter-
Here are some baby steps toward eliminating nested NMIs. What do
you think?
Andy Lutomirski (3):
x86/perf/hw_breakpoint: Disallow kernel breakpoints unless kprobe-safe
x86/perf/hw_breakpoint: Improve range breakpoint validation
x86/perf/hw_breakpoint: Fix check for kernelspace b
Code on the kprobe blacklist doesn't want unexpected int3
exceptions. It probably doesn't want unexpected debug exceptions
either. Be safe: disallow breakpoints in nokprobes code.
On non-CONFIG_KPROBES kernels, there is no kprobe blacklist. In
that case, disallow kernel breakpoints entirely.
I
The check looked wrong, although I think it was actually safe. TASK_SIZE
is unnecessarily small for compat tasks, and it wasn't possible to make
a range breakpoint so large it started in user space and ended in kernel
space.
Nonetheless, let's fix up the check for the benefit of future
readers.
Hi Linus,
this is the fixes pull for -rc5,
it has a bunch of nouveau fixes, as Ben has been hibernating and has lots
of small fixes for lots of bugs across nouveau.
radeon has one major fix for hdmi/dp audio regression that is larger than
Alex would like, but seems to fix up a fair few bugs,
The common kernel.h has already supplied it.
Signed-off-by: Peter Chen
---
drivers/scsi/cxgbi/cxgb4i/cxgb4i.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/scsi/cxgbi/cxgb4i/cxgb4i.c
b/drivers/scsi/cxgbi/cxgb4i/cxgb4i.c
index de6feb8..908399a 100644
--- a/drivers/scsi/cxgbi/cxgb4i/
The UEFI driver would enable zero length, and the Linux driver doesn't
need it. Zero length let the hw complete the transfer with length 0,
when there is no received packet. It would add the load of USB host
controller and reduce the performance.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r81
Thanks.
I will try to add more layman terms here to map cooling state with
frequencies. So, the cooling state 0 maps to the highest frequency the
cpufreq table supports, and the highest cooling state n maps to the
lowest frequency. Right ?
On 30-07-15, 13:21, Radivoje Jovanovic wrote:
> In this c
On Wed, Jul 29, 2015 at 5:15 PM, Marc Zyngier wrote:
>
> On 29/07/15 09:52, Ley Foon Tan wrote:
> > On Wed, Jul 29, 2015 at 1:58 AM, Marc Zyngier wrote:
> >> Hi Ley,
> >>
> >> On 28/07/15 11:45, Ley Foon Tan wrote:
> >>> This patch adds Altera PCIe MSI driver. This soft IP supports configurable
>
Hi,
On Thu, 30 Jul 2015 11:23:17 +0200
Antoine Tenart wrote:
> Add a PWM controller driver for the Marvell Berlin SoCs. This PWM
> controller has 4 channels.
>
> Signed-off-by: Antoine Tenart
> ---
> drivers/pwm/Kconfig | 9 +++
> drivers/pwm/Makefile | 1 +
> drivers/pwm/pwm-ber
On Thu, Jul 30, 2015 at 3:50 PM, Andrew Cooper
wrote:
> On 30/07/2015 22:31, Andy Lutomirski wrote:
>> Note to -stable maintainers: by itself, this patch makes a
>> pre-existing Xen bug much easier to trigger; on a 32-bit Xen guest,
>> the new ldt_gdt selftest is likely to OOPS. Even without this
On Thu, Jul 30, 2015 at 12:42 PM, Christoph Hellwig wrote:
> On Thu, Jul 30, 2015 at 07:36:24AM -0400, Ming Lei wrote:
>> + /*
>> + * When working at direct I/O, under very unusual cases,
>> + * such as unaligned direct I/O from application and
>> + * access to loop block device
On Wed, 2015-07-22 at 16:14 +0800, Yingjoe Chen wrote:
> Spurious mtk timer interrupt is noticed at boot and cause kernel
> crash. It seems if GPT is enabled, it will latch irq status even
> when its IRQ is disabled. When irq is enabled afterward, we see
> spurious interrupt.
> Change init flow to
Hi Michal Nazarewicz,
Thanks for the review.
On Thu, 2015-07-30 at 15:59 +0200, Michal Nazarewicz wrote:
> On Thu, Jul 30 2015, Feng Tang wrote:
> > When system(one x86 soc) boot, we saw many normal dma allocation requests
> > goes to cma area. The call chain is
> > dma_generic_alloc_coherent
Hi, list
Ping..., any feedback for this series?
Best Regards,
Josh Wu
On 6/17/2015 6:39 PM, Josh Wu wrote:
In the function configure_geometry(), we will setup the ISI CFG2
according to the sensor output format.
It make no sense to just read back the CFG2 register and just set part
of it.
So
On 07/30/2015 10:16 PM, Waiman Long wrote:
On 07/29/2015 06:21 PM, Eric W. Biederman wrote:
Two quick questions.
- What motivates this work? Are you seeing lots of
parallel reads on proc?
The micro-benchmark that I used was artificial, but it was used to
reproduce an exit hanging problem
On Thu, Jul 30, 2015 at 11:26:28PM +, Zhang, Yang Z wrote:
> Paolo Bonzini wrote on 2015-07-29:
> > Do not compute TMR in advance. Instead, set the TMR just before the
> > interrupt is accepted into the IRR. This limits the coupling between
> > IOAPIC and LAPIC.
> >
>
> Uh.., it back to ori
On Thu, 2015-07-30 at 21:29 +0200, Jonas Gorski wrote:
> Hi,
>
> On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> > Change in v4:
> > 1. fix Mark Brown review comment.
>
> You should say what you actually fixed/changed, not just that you
> changed something. Also the individual patches should
Hi Jonas,
On Thu, 2015-07-30 at 21:27 +0200, Jonas Gorski wrote:
> Hi,
>
> On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> > Signed-off-by: Leilk Liu
> > ---
> > .../devicetree/bindings/spi/spi-mt65xx.txt | 38
> > ++
> > 1 file changed, 38 insertions(+)
> > c
Hello
I have good news for you.
Your long awaited package containing $10.5 Million is en-route your address.
It will be delivered via Diplomatic Armored Vehicle. The Diplomatic Armored
Company has delegated an official to effect the delivery of the package to you.
So, you need to confirm t
On 07/29/2015 06:21 PM, Eric W. Biederman wrote:
Two quick questions.
- What motivates this work? Are you seeing lots of
parallel reads on proc?
The micro-benchmark that I used was artificial, but it was used to
reproduce an exit hanging problem that I saw in real application. In
fact, o
From: Alexey Brodkin
This patch has been added to the 3.18 stable tree. If you have any
objections, please let us know.
===
[ Upstream commit f51e2f1911122879eefefa4c592dea8bf794b39c ]
Currently instruction_pointer() returns pt_regs->ret and so return value
is of type "long", which
The PCI subsystem always assumes that I/O is supported on PCIe bridges
and tries to assign an I/O window to each child bus even if that is not
the case.
This may result in messages such as:
pcieport :02:00.0: res[7]=[io 0x1000-0x0fff] get_res_add_size add_size
1000
pcieport :02:00.0
Hi Linus,
Can you please pull the XFS fixes from the tag below? There are a
couple of recently found, long standing remote attribute corruption
fixes caused by log recovery getting confused after a crash, and the
new DAX code in XFS (merged in 4.2-rc1) needs to actually use the
DAX fault path on r
On 07/30/2015 10:44 AM, Peter Zijlstra wrote:
On Fri, Jul 17, 2015 at 04:29:24PM -0700, Paul E. McKenney wrote:
/*
+* First try directly acquiring the root lock in order to reduce
+* latency in the common case where expedited grace periods are
+* rare. We check
On Thu, Jul 30, 2015 at 5:54 PM, Pablo Neira Ayuso wrote:
> On Sun, Jul 26, 2015 at 05:27:37PM +0530, Vaishali Thakkar wrote:
>> For simple modules that contain a single xt_match without any
>> additional setup code then ends up being a block of duplicated
>> boilerplate. This patch adds a new mac
On 30/07/15 15:51, David Miller wrote:
> From: David Miller
> Date: Thu, 30 Jul 2015 14:19:35 -0700 (PDT)
>
>> This looks fine, series applied, thanks.
>
> I think your control block is too large, you'll need to rework this
> somehow.
So napi_gro_cb really is 48 bytes on 64-bits architectures (
Dmitry,
Thank your very much.
Thanks,
Dudley
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 2015?7?31? 2:33
> To: Dudley Du
> Cc: mark.rutl...@arm.com; robh...@kernel.org; ble...@google.com;
> jmmah...@gmail.com; devicet...@vger.kernel.org; linux-
On Thu, 2015-07-30 at 22:53 +0800, Henry Chen wrote:
> Implement the suspend/resume function in order to control rtc's irq_wake flag
> and handle as wakeup source.
>
> Signed-off-by: Henry Chen
> ---
> drivers/rtc/rtc-mt6397.c | 26 ++
> 1 file changed, 26 insertions(+)
On 07/31/2015 12:59 AM, Greg KH wrote:
On Thu, Jul 30, 2015 at 05:45:44PM +0100, Matt Fleming wrote:
On Thu, 30 Jul, at 09:31:02AM, Greg KH wrote:
Why isn't this an issue in newer kernel releases? Did this already get
fixed by some other patch? If so, why can't we just take that patch?
If not
Signed-off-by: Moritz Fischer
---
arch/arm/boot/dts/zynq-7000.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/zynq-7000.dtsi b/arch/arm/boot/dts/zynq-7000.dtsi
index 0691508..6bebf02 100644
--- a/arch/arm/boot/dts/zynq-7000.dtsi
+++ b/arch/arm/boot/dts/zynq-7000
Signed-off-by: Moritz Fischer
---
arch/arm/mach-zynq/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-zynq/Kconfig b/arch/arm/mach-zynq/Kconfig
index 78e5e00..77d7df7 100644
--- a/arch/arm/mach-zynq/Kconfig
+++ b/arch/arm/mach-zynq/Kconfig
@@ -1,5 +1,6 @@
config ARCH_ZYN
This adds a reset controller driver to control the Xilinx Zynq
AP-SoC's various resets.
Signed-off-by: Moritz Fischer
---
drivers/reset/Makefile | 1 +
drivers/reset/reset-zynq.c | 155 +
2 files changed, 156 insertions(+)
create mode 100644 dri
1 - 100 of 908 matches
Mail list logo
