On Wed, 06 May 2015, Javier Martinez Canillas wrote:
> The defined struct max77686_opmode_data isn't used neither by
> the max77686 mfd driver nor the drivers for its sub-devices.
>
> Signed-off-by: Javier Martinez Canillas
> ---
> include/linux/mfd/max77686.h | 5 -
> 1 file changed, 5 del
On Thu, 2015-05-07 at 05:58 +, Oza (Pawandeep) Oza wrote:
> Yes.
> But dying kernel doesn’t mean it CAN NOT INCREMENT jiffies.
> do_timer should do the job until kernel takes its last breathe and more
> precisely CPU0 take its last breathe by halting itself as its last
> instruction.
Feel fr
On Fri, Mar 13, 2015 at 07:54:45AM -0400, Nicholas Mc Guire wrote:
> wait_for_completion_timeout does not return negative values so
> result handling here does not need to check for negative return.
>
> Signed-off-by: Nicholas Mc Guire
> ---
>
> Patch was compile tested with nhk8815_defconfig
>
Hi all,
Changes since 20150506:
The ext4 tree gained a build failure so I used the version from
next-20150506.
The vfs tree gained a conflict against the f2fs tree.
The rcu tree gained conflicts against the tip tree.
Non-merge commits (relative to Linus' tree): 2460
2454 files ch
On Wed, Mar 25, 2015 at 02:33:09PM +0100, Richard Weinberger wrote:
> As all four bytes are written in any case the memset() is in vain.
>
> Signed-off-by: Richard Weinberger
Applied to l2-mtd.git.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messag
On Mon, Mar 16, 2015 at 08:20:28PM +0100, Fabian Frederick wrote:
> of_device_id is always used as const.
> (See driver.of_match_table and open firmware functions)
>
> Signed-off-by: Fabian Frederick
Applied to l2-mtd.git.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
From: Kyungmin Park
Some platform uses freezer cgroup for speicial purpose to schedule out some
applications. but after suspend & resume, these processes are thawed and
running.
but it's inteneded and don't need to thaw it.
To avoid it, does it possible to modify resume code and don't thaw i
On 04/30, Boris Brezillon wrote:
> Clock rates are stored in an unsigned long field, but ->round_rate()
> (which returns a rounded rate from a requested one) returns a long
> value (errors are reported using negative error codes), which can lead
> to long overflow if the clock rate exceed 2Ghz.
>
From: Kent Overstreet
The bcache driver has always accepted arbitrarily large bios and split
them internally. Now that every driver must accept arbitrarily large
bios this code isn't nessecary anymore.
Cc: linux-bca...@vger.kernel.org
Signed-off-by: Kent Overstreet
[dpark: add more description
From: Kent Overstreet
As generic_make_request() is now able to handle arbitrarily sized bios,
it's no longer necessary for each individual block driver to define its
own ->merge_bvec_fn() callback. Remove every invocation completely.
Cc: Jens Axboe
Cc: Lars Ellenberg
Cc: drbd-u...@lists.linbit
From: Kent Overstreet
Allow __blk_queue_bounce() to handle bios with more than BIO_MAX_PAGES
segments. Doing that, it becomes possible to simplify the block layer
in the kernel.
The issue is that any code that clones the bio and must clone the biovec
(i.e. it can't use bio_clone_fast()) won't be
From: Kent Overstreet
Since generic_make_request() can now handle arbitrary size bios, all we
have to do is make sure the bvec array doesn't overflow.
__bio_add_page() doesn't need to call ->merge_bvec_fn(), where
we can get rid of unnecessary code paths.
Removing the call to ->merge_bvec_fn() i
It's been five years now that KM_* kmap flags have been removed and
that we can call clear_highpage from any context. So we remove
prep_zero_pages accordingly.
Signed-off-by: Anisse Astier
---
mm/page_alloc.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/
From: Kent Overstreet
The way the block layer is currently written, it goes to great lengths
to avoid having to split bios; upper layer code (such as bio_add_page())
checks what the underlying device can handle and tries to always create
bios that don't need to be split.
But this approach become
Hi,
I'm trying revive an old debate here[1], though with a simpler approach than
was previously tried. This patch series implements a new option to sanitize
freed pages, a (very) small subset of what is done in PaX/grsecurity[3],
inspired by a previous submission [4].
The first patch is fairly in
SANITIZE_FREED_PAGES feature relies on having all pages going through
the free_pages_prepare path in order to be cleared before being used. In
the hibernate use case, pages will automagically appear in the system
without being cleared.
This patch will make sure free pages are cleared on resume; wh
Add debug code for sanitize freed pages to print status and verify pages
at alloc to make sure they're clean. It can be useful if you have
crashes when using SANITIZE_FREED_PAGES.
Signed-off-by: Anisse Astier
---
kernel/power/snapshot.c | 8 ++--
mm/Kconfig | 10 ++
mm/
This new config option will sanitize all freed pages. This is a pretty
low-level change useful to track some cases of use-after-free, help
kernel same-page merging in VM environments, and counter a few info
leaks.
Signed-off-by: Anisse Astier
---
mm/Kconfig | 12
mm/page_alloc.
From: Kent Overstreet
Refactor sync_request_write() of md/raid10 to use bio_copy_data()
instead of open coding bio_vec iterations.
Cc: Christoph Hellwig
Cc: Neil Brown
Cc: linux-r...@vger.kernel.org
Reviewed-by: Christoph Hellwig
Acked-by: NeilBrown
Signed-off-by: Kent Overstreet
[dpark: ad
From: Dongsu Park
Update block/biovecs.txt so that it includes a note on what kind of
effects arbitrarily sized bios would bring to the block layer.
Also fix a trivial typo, bio_iter_iovec.
Cc: Christoph Hellwig
Cc: Kent Overstreet
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Signed-off-
From: Kent Overstreet
Btrfs has been doing bio splitting from btrfs_map_bio(), by checking
device limits as well as calling ->merge_bvec_fn() etc. That is not
necessary any more, because generic_make_request() is now able to
handle arbitrarily sized bios. So clean up unnecessary code paths.
Cc:
If a read request fits entirely in a chunk, it will be passed directly to the
underlying device (providing it hasn't failed of course). If it doesn't fit,
the slightly less efficient path that uses the stripe_cache is used.
Requests that get to the stripe cache are always completely split up as
ne
From: Kent Overstreet
Remove bio_fits_rdev() completely, because ->merge_bvec_fn() has now
gone. There's no point in calling bio_fits_rdev() only for ensuring
aligned read from rdev.
Cc: Neil Brown
Cc: linux-r...@vger.kernel.org
Signed-off-by: Kent Overstreet
[dpark: add more description in co
From: Kent Overstreet
Call pre-defined helper bio_add_page() instead of open coding for
iterating through bi_io_vec[]. Doing that, it's possible to make some
parts in filesystems and mm/page_io.c simpler than before.
Acked-by: Dave Kleikamp
Cc: Christoph Hellwig
Cc: Al Viro
Cc: linux-fsde...@
v3:
- rebase on top of 4.1-rc2
- support for QUEUE_FLAG_SG_GAPS
- update commit logs of patch 2&4
- split bio for chunk_aligned_read
v2: https://lkml.org/lkml/2015/4/28/28
v1: https://lkml.org/lkml/2014/12/22/128
This is the 3rd attempt of simplifying block layer based on immutable
biovec
Hi Dave,
Can you help me to review this patch? Thanks.
Jianwei
> -Original Message-
> From: Jianwei Wang [mailto:jianwei.w...@freescale.com]
> Sent: Friday, April 17, 2015 2:36 PM
> To: airl...@linux.ie; daniel.vet...@intel.com; ste...@agner.ch; Wood
> Scott-B07421; dri-de...@lists.freed
On Wed, May 06, 2015 at 09:17:25PM -0700, Michael Turquette wrote:
> Are you thinking of placing the hook somewhere such as
> update_entity_load_avg?
Nah, I was more thinking of Morten's series where we already compute the
utilization for the energy aware scheduling reasons.
--
To unsubscribe from
> > This series therefore does 2 things:
> >
> >
> > 1. Decouple pagefault_disable() from preempt_enable()
> >
> > ...
> >
> > 2. Reenable might_sleep() checks for might_fault()
>
> All seems sensible to me. pagefault_disabled has to go into the
> task_struct (rather than being per-cpu) becau
TUSB1210 ULPI PHY has vendor specific register for eye
diagram tuning. On some platforms the system firmware has
set optimized value to it. In order to not loose the
optimized value, the driver stores it during probe and
restores it every time the PHY is powered back on.
Signed-off-by: Heikki Krog
ULPI PHYs need to be bound to their controllers with a
lookup. This adds helpers that the ULPI drivers can use to
do both, the registration of the PHY and the lookup, at the
same time.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
Cc: Kishon Vijay Abraham I
---
drivers/phy/ulpi_phy.h |
This allows dwc3_phy_setup() to be more useful later. There
is nothing preventing the PHY configuration registers from
being programmed early. They do not loose their context in
soft reset.
There are however other PHY related operations that should
be executed before the driver request handles to
On some BYT platforms the USB2 PHY needs to be put into
operational mode by the controller driver with GPIOs
controlling the PHYs reset and cs signals.
Signed-off-by: Heikki Krogerus
---
drivers/usb/dwc3/dwc3-pci.c | 36
1 file changed, 36 insertions(+)
diff
So it can be called from other places later.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
---
drivers/usb/dwc3/core.c | 46 ++
1 file changed, 30 insertions(+), 16 deletions(-)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
in
Platforms that have configured DWC_USB3_HSPHY_INTERFACE with
value 3, i.e. UTMI+ and ULPI, need to inform the driver of
the actual HSPHY interface type with the property. "utmi" if
the interface is UTMI+ or "ulpi" if the interface is ULPI.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
---
Registers DWC3's ULPI interface with the ULPI bus when it's
available.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
---
drivers/usb/dwc3/Kconfig | 7
drivers/usb/dwc3/Makefile | 4 +++
drivers/usb/dwc3/core.c | 34 --
drivers/usb/dwc3/core.h | 14
dr
Make selection between ULPI and UTMI+ interfaces possible by
providing definition for the bit in Global USB2 PHY
Configuration Register that controls it.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
---
drivers/usb/dwc3/core.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/
We need to store it before phys are handled, so we can later
use it in ULPI interface support code.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
---
drivers/usb/dwc3/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/c
So they are available when ULPI interface support is added.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
---
drivers/usb/dwc3/core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index c7734ed..104b236 100644
---
Changes since v3:
- struct ulpi_bus is now static
- added a delay to sync the PHY clock after soft reset
Changes since v2:
- remove module handling from the bus driver as suggested by Paul Bolle.
- reordered the gpio requests in BYT quirk as suggested by David Cohen.
Major changes since v1:
- ca
Definitions for Global USB2 PHY Vendor Control Register
bits. We will need them to access ULPI PHY registers later.
Signed-off-by: Heikki Krogerus
Acked-by: David Cohen
---
drivers/usb/dwc3/core.h | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/
UTMI+ Low Pin Interface (ULPI) is a commonly used PHY
interface for USB 2.0. The ULPI specification describes a
standard set of registers which the vendors can extend for
their specific needs. ULPI PHYs provide often functions
such as charger detection and ADP sensing and probing.
There are two ma
On 2015/5/7 10:25, Steven Rostedt wrote:
> On Mon, 20 Apr 2015 16:44:40 +0800
> Xie XiuQi wrote:
>
...
>> + *
>> + * unsigned long pfn - Page Frame Number of the corrupted page
>> + * int type - Page types of the corrupted page
>> + * int result - Result of recovery actio
AFAICT gas will produce relocations for jumps to global labels in the
same file. This doesn't seem directly harmful to me, except that, on
x86, it forces five-byte jumps instead of two-byte jumps.
This seems especially unfortunate, since even hidden and protected
symbols have this problem.
Given
Hi Greg,
Upstream commit e4140819dadc3624accac8294881bca8a3cba4ed, "ARC: signal handling
robustify" was marked for stable inclusion. It made it into 3.18 but not earlier
likely due to interim changes preventing a clean merge.
Could you please queue up the fixed up patch below for 3.14 and earlier
On 2015/5/7 9:12, Naoya Horiguchi wrote:
> On Wed, Apr 29, 2015 at 07:14:27PM +0800, Xie XiuQi wrote:
>> Hi Naoya,
>>
>> Could you help to review and applied this series if possible.
>
> Sorry for late response, I was offline for several days due to national
> holidays.
It doesn't matter, wish yo
Yes.
But dying kernel doesn’t mean it CAN NOT INCREMENT jiffies.
do_timer should do the job until kernel takes its last breathe and more
precisely CPU0 take its last breathe by halting itself as its last instruction.
Regards,
-Oza
-Original Message-
From: Mike Galbraith [mailto:umgwanak
On Thu, 2015-05-07 at 05:12 +, Oza (Pawandeep) Oza wrote:
> But after Crash, jiffies do not increment.
Your kernel said "I'M DEAD", that's a good reason to believe it.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord
EP-E68D5E24548545C9BBB607A98ADD61E6
Hi Paul,
>On Monday, March 30, 2015 11:09:00 AM Maninder Singh wrote:
>> Dear All,
>> we found One Kernel Crash issue in cipso_v4_sock_delattr :-
>> As Cipso supports only inet sockets so cipso_v4_sock_delattr will crash when
>> try to access any other socket t
Hi Hn,
On Tue, Apr 28, 2015 at 06:35:58PM +0800, HungNien Chen wrote:
> Signed-off-by: HungNien Chen
Thank you for your submission, please find my comments below.
> ---
> drivers/input/touchscreen/Kconfig | 12 +
> drivers/input/touchscreen/Makefile |1 +
> drivers/input/touch
On Wed, May 06, 2015 at 05:13:41PM -0500, Jaime Arrocha wrote:
> Errors found by checkpatch.pl.
> ERROR: code indent should use tabs where possible
> /drivers/staging/comedi/drivers/das16m1.c:49
> /drivers/staging/comedi/drivers/das16m1.c:50
>
> Signed-off-by: Jaime Arrocha
> ---
you are sending
On Wed, May 06, 2015 at 10:17:24PM -0700, Stephen Boyd wrote:
> On 05/07, Simon Horman wrote:
> > On Wed, May 06, 2015 at 12:39:46AM -0700, Stephen Boyd wrote:
> > > drivers/clk/shmobile/clk-emev2.c:37:14: warning: symbol 'smu_base' was
> > > not declared. Should it be static?
> > >
> > > Cc: Tak
Hi all,
After merging the drm-intel tree, today's linux-next build (i386 defconfig)
produced this warning:
drivers/gpu/drm/i915/i915_gem_gtt.c: In function 'gen8_ppgtt_init':
drivers/gpu/drm/i915/i915_gem_gtt.c:954:22: warning: large integer implicitly
truncated to unsigned type [-Woverflow]
p
When a CPU has to enter an idle state where tick stops, it makes a call
to tick_broadcast_enter(). The call will fail if this CPU is the
broadcast CPU. Today, under such a circumstance, the arch cpuidle code
handles this CPU. This is not convincing because not only are we not
aware what the arch c
Hi Greg,
On 5 May 2015 at 15:10, Greg Kroah-Hartman wrote:
> On Sat, May 02, 2015 at 09:00:22PM +0200, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 3.19.7 release.
>> There are 177 patches in this series, all will be posted as a response
>> to this one. If an
On 05/07, Simon Horman wrote:
> On Wed, May 06, 2015 at 12:39:46AM -0700, Stephen Boyd wrote:
> > drivers/clk/shmobile/clk-emev2.c:37:14: warning: symbol 'smu_base' was not
> > declared. Should it be static?
> >
> > Cc: Takashi Yoshii
> > Cc: Magnus Damm
> > Cc: Simon Horman
> > Signed-off-by:
Update FALLOC_FL_INSERT_RANGE flag in fallocate.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
---
man2/fallocate.2 | 89
1 file changed, 84 insertions(+), 5 deletions(-)
diff --git a/man2/fallocate.2 b/man2/fallocate.2
index
Solution Statement: Fix the UTTERLY DEADLY bug.
Oza:
that BUG() is LEGAL. Kernel is not a problem there.
Somebody else outside of kernel/ARM (some other HW raises the bug), and send
indication to kernel that I am not alive.
So kernel choose to CRASH ITSELF.
So that is legal crash and wanted Cra
On Thu, 2015-05-07 at 04:37 +, Oza (Pawandeep) Oza wrote:
> Problem Statement: the timkeeping is stopped, do_timer is no more a
> job of cpu0.
>
> The reason: the variable "tick_do_timer_cpu" is not set to correct CPU
> (cpu0)
> And when BUG() happens, the tick_do_timer_cpu variable stay set t
On Thu, May 07, 2015 at 04:47:55AM +, Horiguchi Naoya(堀口 直也) wrote:
> libapikfs.a was renamed to libapi.a on commit 285a8f247b08 ("tools lib api:
> Rename libapikfs.a to libapi.a"), but tools/vm/Makefile still refers to the
> old file name, which breaks the build on tools/vm. This patch fixes i
At Mon, 4 May 2015 13:00:46 +0100,
Mark Brown wrote:
>
> On Mon, May 04, 2015 at 12:16:36AM +0900, Yoshinori Sato wrote:
> > I got following error on CONFIG_GPIOLIB=n.
>
> Applied, thanks, but please use subject lines reflecting the style for
> the subsystem.
Oh. I'm sorry.
Thanks applied.
--
libapikfs.a was renamed to libapi.a on commit 285a8f247b08 ("tools lib api:
Rename libapikfs.a to libapi.a"), but tools/vm/Makefile still refers to the
old file name, which breaks the build on tools/vm. This patch fixes it.
Signed-off-by: Naoya Horiguchi
---
tools/vm/Makefile | 2 +-
1 file chan
At Mon, 04 May 2015 17:09:21 +0200,
Arnd Bergmann wrote:
>
> On Monday 04 May 2015 19:42:02 Yoshinori Sato wrote:
> > +
> > + h8intc: intc@0 {
> > + compatible = "renesas,h8s-intc", "renesas,h8300-intc";
> > + #interrupt-cells = <1>;
> > + interrupt-controller;
> >
Hi Mike,
Let me explain the problem again.
Problem Statement: the timkeeping is stopped, do_timer is no more a job of cpu0.
The reason: the variable "tick_do_timer_cpu" is not set to correct CPU (cpu0)
And when BUG() happens, the tick_do_timer_cpu variable stay set to 1, 2 or 3
(we have 4 cores
On Wed, May 06, 2015 at 12:39:46AM -0700, Stephen Boyd wrote:
> drivers/clk/shmobile/clk-emev2.c:37:14: warning: symbol 'smu_base' was not
> declared. Should it be static?
>
> Cc: Takashi Yoshii
> Cc: Magnus Damm
> Cc: Simon Horman
> Signed-off-by: Stephen Boyd
Acked-by: Simon Horman
Steph
Signed-off-by: Masahiro Yamada
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b399b34..3f4060f4 100644
--- a/MAINTAINERS
+++ b/MAINTAIN
Initial device trees for UniPhier SoCs: PH1-sLD3, PH1-LD4, PH1-Pro4,
and PH1-sLD8.
Signed-off-by: Masahiro Yamada
---
Changes in v6:
- Remove redundant interrupt-parent property from timer nodes.
Changes in v5: None
Changes in v4:
- Add system-bus-controller-misc node instead of uniphier-sm
Hello Sascha,
Am 07.05.2015 06:25, schrieb Sascha Hauer:
On Wed, May 06, 2015 at 10:06:21AM +0200, Heiko Schocher wrote:
This patch add support for the imx6dl based aristainetos2 board
with following configuration:
CPU: Freescale i.MX6DL rev1.1 at 792 MHz
MReset cause: POR
MBoard: aristaiten
Add UniPhier, a new citizen in the ARM multi platform.
Signed-off-by: Masahiro Yamada
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs
Initial commit for a new SoC family, UniPhier, developed by
Socionext Inc. (formerly, System LSI Business Division of
Panasonic Corporation).
This commit includes a minimal set of components for booting the
kernel, including SMP support.
Signed-off-by: Masahiro Yamada
---
Changes in v6: None
Ch
This is an initial series for supporting Socionext UniPhier SoCs,
based on ARM Cortex-A9, mainly used for digital TVs, video recorders, etc.
Masahiro Yamada (4):
ARM: UniPhier: add basic support for UniPhier architecture
ARM: multi_v7_defconfig: enable UniPhier SoC family
ARM: dts: UniPhie
On Fri, Apr 10, 2015 at 11:58 AM, Jonathan Richardson
wrote:
> The polarity procedure no longer applies the settings to change the
> output signal because it can't be called when the pwm is enabled anyway.
> The polarity is only updated in the control register. The correct
> polarity will be appl
On Wed, May 06, 2015 at 10:06:21AM +0200, Heiko Schocher wrote:
> This patch add support for the imx6dl based aristainetos2 board
> with following configuration:
>
> CPU: Freescale i.MX6DL rev1.1 at 792 MHz
> MReset cause: POR
> MBoard: aristaitenos2
> DRAM: 1 GiB
> NAND: 1024 MiB
> MMC: FSL
At Mon, 04 May 2015 16:46:54 +0200,
Arnd Bergmann wrote:
>
> On Monday 04 May 2015 19:41:48 Yoshinori Sato wrote:
> > Signed-off-by: Yoshinori Sato
> > ---
> > include/asm-generic/asm-offsets.h | 1 +
> > 1 file changed, 1 insertion(+)
> > create mode 100644 include/asm-generic/asm-offsets.h
>
At Mon, 4 May 2015 19:27:00 -0700,
Guenter Roeck wrote:
>
> On Mon, May 04, 2015 at 07:41:43PM +0900, Yoshinori Sato wrote:
> > Hello.
> > I will re-introducing h8300.
> >
>
> Hi,
>
> With "make ARCH=h8300 edosk2674_defconfig; make ARCH=h8300",
> I see the following build error:
>
> scripts/Ma
Quoting Abel Vesa (2015-05-06 09:50:40)
> If CONFIG_SMP is not defined the build will fail due to
> function 'gov_cfs_update_cpu' definition missing.
> Added empty static inline definition for NON-SMP systems.
>
> This patch applies to:
> https://git.linaro.org/people/mike.turquette/linux.git sche
Hi all,
After merging the tegra tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/clk/tegra/clk-emc.c: In function 'tegra_clk_register_emc':
drivers/clk/tegra/clk-emc.c:519:20: warning: assignment discards 'const'
qualifier from pointer target type
init.par
Hi Paul,
Today's linux-next merge of the rcu tree got conflicts in
include/linux/rcupdate.h, include/linux/rcutree.h and
kernel/rcu/tree_plugin.h between commit c1ad348b452a ("tick: Nohz:
Rework next timer evaluation") from the tip tree and commit
f49f794683d6 ("rcu: Eliminate a few CONFIG_RCU_NOC
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Luis R. Rodriguez
> Sent: Thursday, April 30, 2015 3:25 PM
> Subject: [PATCH v5 1/6] x86/mm/pat: use pr_info() and friends
>
...
> - printk(KERN_ERR "%s:%d map pfn expected ma
On 2015/05/06, 6:02 AM, "Mike Shuey" wrote:
>Clean up spacing in some variable declarations, to be more consistent.
>
>It's small, but I need to start somewhere. Please let me know if I'm not
>adhering to proper procedure for trivial cleanups.
It's actually Lustre coding style to align the vari
Add 1588 timer node in files:
arch/powerpc/boot/dts/bsc9131rdb.dtsi
arch/powerpc/boot/dts/bsc9132qds.dtsi
arch/powerpc/boot/dts/p1010rdb.dtsi
arch/powerpc/boot/dts/p1020rdb-pd.dts
arch/powerpc/boot/dts/p1021rdb-pc.dtsi
arch/powerpc/boot/dts/p1022ds.dtsi
arch/powerpc/boot/dts/p1025twr.dtsi
Fix 1588
On Fri, May 01, 2015 at 01:57:13PM +0200, Jonas Gorski wrote:
> On Thu, Apr 30, 2015 at 7:36 PM, Ben Shelton wrote:
> > The reason for doing this as a Kconfig option rather than with an additional
> > partition is that we use the same .itb boot image (and kernel arguments) for
> > a series of embe
On Wed, 2015-05-06 at 22:57 +0530, pawandeep oza wrote:
> but when say core0 has raised BUG..
...
> what is the right way to approach this problem
Look at the spot BUG() printed? BUG() means "Way to go slick, the code
you fed me (file:line) is toxic. Have a nice day, your ex-buddy core0".
This patch converts the elog code to use the opal irq domain instead
of notifier events.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal-elog.c | 32 +++---
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/arch/powerpc/platforms/power
All users of the old opal events notifier have been converted over to
the irq domain so remove the event notifier functions.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal-irqchip.c | 16 ++---
arch/powerpc/platforms/powernv/opal.c | 84 +--
Whenever an interrupt is received for opal the linux kernel gets a
bitfield indicating certain events that have occurred and need handling
by the various device drivers. Currently this is handled using a
notifier interface where we call every device driver that has
registered to receive opal events
Convert the opal ipmi driver to use the new irq interface for events.
Signed-off-by: Alistair Popple
Cc: Corey Minyard
Cc: openipmi-develo...@lists.sourceforge.net
---
Corey,
If this looks ok can you please ack it? Michael Ellerman will then take
the whole series via the powerpc tree. Thanks.
Convert the opal dump driver to the new opal irq domain.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal-dump.c | 56 +-
1 file changed, 17 insertions(+), 39 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal-dump.c
b/arch/powerpc/p
The eeh code currently uses the old notifier method to get eeh events
from OPAL. It also contains some logic to filter opal events which has
been moved into the virtual irqchip. This patch converts the eeh code
to the new event interface which simplifies event handling.
Signed-off-by: Alistair Pop
This patch converts the opal message event to use the new opal irq
domain.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal.c | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal.c
b/arch/po
Convert the opal hvc driver to use the new irqchip to register for
opal events. As older firmware versions may not have device tree
bindings for the interrupt parent we just use a hardcoded hwirq based
on the event number.
Signed-off-by: Alistair Popple
---
drivers/tty/hvc/hvc_opal.c | 33 ++
On Wed, May 06, 2015 at 12:51:06PM -0400, Dan Streetman wrote:
> Add crypto compression alg for 842 hardware compression and decompression.
>
> This crypto compression alg is named "nx842" to indicate it uses hardware
> to perform the compression and decompression, while the software 842
> compres
Introduce three helpers to manage pci_dev->irq and pci_dev->irq_managed,
which helps to improve maintenance.
Signed-off-by: Jiang Liu
---
arch/x86/pci/intel_mid_pci.c |4 ++--
arch/x86/pci/irq.c | 10 --
drivers/acpi/pci_irq.c | 10 --
include/linux/pci.h
Add two hook points pcibios_{alloc|free}_irq() into PCI core, which will
be called when binding/unbinding PCI device drivers. Then PCI arch code
may hook into these two points to allocate IRQ resources on demand and
free them when not used anymore.
Signed-off-by: Jiang Liu
---
drivers/pci/pci-dr
To support IOAPIC hotplug, we need to correctly manage IOAPIC pin usage,
which is to allocate IRQs on demand and free them when not used anymore.
So use pcibios_alloc_irq() and pcibios_free_irq() to dynamically allocate
and free PCI IRQs.
Also remove obseleted code mp_should_keep_irq().
Signed-of
Once PCI MSI/MSI-X is enabled by the device driver, PCI device won't
make use of legacy PCI IRQ until PCI MSI/MSI-X is disabled again.
So optionally free legacy PCI IRQ when enabling MSI/MSI-X and reallocate
when disabling MSI/MSI-X.
Signed-off-by: Jiang Liu
---
drivers/pci/msi.c |6 +-
This patch set introduces a mechanism to allocate PCI IRQ on demand and
free it when not used anymore by hooking pci_device_probe() and
pci_device_remove().
It will be used to track IOAPIC pin usage on x86 so we could support
IOAPIC hot-removal.
The patch set passes Fengguang's 0day test suite an
On 27/04/15 07:12, Dan Carpenter wrote:
> Can't we just export the tkip.c function?
>
> regards,
> dan carpenter
>
Hi Dan,
(sorry for the delayed response)
The inputs of the two implementations of tkip_mixing_phase2() differ in
one parameter:
- ieee80211_crypt_tkip.c expects 'const u16 *TTAK'
On 5 May 2015 at 21:52, Gerd Hoffmann wrote:
> Completely different approach: Instead of encoding each and every
> framebuffer update as spice operation simply update the shadow
> framebuffer and maintain a dirty rectangle. Also schedule a worker
> to push an update for the dirty rectangle as sp
On Wed, May 06, 2015 at 12:51:00PM -0400, Dan Streetman wrote:
> Change the crypto 842 compression alg to use the software 842 compression
> and decompression library. Change the name of this crypto alg to "sw842".
> Remove the fallback to LZO compression.
That's not how the name works. All impl
On Mon, May 04, 2015 at 02:27:01PM +0200, Boris Brezillon wrote:
> The existing mv_cesa driver supports some features of the CESA IP but is
> quite limited, and reworking it to support new features (like involving the
> TDMA engine to offload the CPU) is almost impossible.
> This driver has been re
1 - 100 of 987 matches
Mail list logo
