Crash kernel region size is available via sysfs on Linux running on
bare metal. However, this does not work when Linux runs as Xen dom0.
In this case Xen crash kernel region size should be established using
__HYPERVISOR_kexec_op hypercall (Linux kernel kexec functionality does
not make a lot of sen
Crash kernel region size is available via sysfs on Linux running on
bare metal. However, this does not work when Linux runs as Xen dom0.
In this case Xen crash kernel region size should be established using
__HYPERVISOR_kexec_op hypercall (Linux kernel kexec functionality does
not make a lot of sen
Signed-off-by: Daniel Kiper
---
purgatory/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/purgatory/Makefile b/purgatory/Makefile
index 2b5c061..caea7ea 100644
--- a/purgatory/Makefile
+++ b/purgatory/Makefile
@@ -33,7 +33,7 @@ PURGATORY_SRCS+=$($(ARCH)_PURGATORY_S
Provide just print_crashkernel_region_size() stub. This way
we can properly build kexec utility on cris arch even
if the functionality is not available on it.
Signed-off-by: Daniel Kiper
---
kexec/arch/cris/kexec-cris.c |5 +
1 file changed, 5 insertions(+)
diff --git a/kexec/arch/cris/
Signed-off-by: Daniel Kiper
---
kexec/kexec.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kexec/kexec.c b/kexec/kexec.c
index f0bd527..20dd93d 100644
--- a/kexec/kexec.c
+++ b/kexec/kexec.c
@@ -969,7 +969,7 @@ void usage(void)
" prese
Follow similar x86 patch.
Signed-off-by: Daniel Kiper
---
kexec/arch/arm/crashdump-arm.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/kexec/arch/arm/crashdump-arm.c b/kexec/arch/arm/crashdump-arm.c
index b523e5f..b3e93ad 100644
--- a/kexec/arch/arm/crashdump-arm.c
+++ b/kexe
Signed-off-by: Daniel Kiper
---
kexec/crashdump.h |1 -
1 file changed, 1 deletion(-)
diff --git a/kexec/crashdump.h b/kexec/crashdump.h
index 95f1f0c..320767b 100644
--- a/kexec/crashdump.h
+++ b/kexec/crashdump.h
@@ -1,7 +1,6 @@
#ifndef CRASHDUMP_H
#define CRASHDUMP_H
-int get_crashker
Hi Rob,
On 11/22/2015 02:47 PM, Rob Herring wrote:
> On Fri, Nov 20, 2015 at 05:17:19PM -0700, Joshua Henderson wrote:
>> From: Andrei Pistirica
>>
>> Document the devicetree bindings for PINCTRL and GPIO found on Microchip
>> PIC32 class devices. This also adds a header defining related port and
On Tue 08 Dec 13:29 PST 2015, John Stultz wrote:
> This patch adds a basic driver to allow for commands like
> "reboot bootloader" and "reboot recovery" to communicate this
> reboot-reason to the bootloader.
>
> This is commonly done on Android devices, in order to reboot
> the device into fastbo
Linus,
On 11/30/2015 06:41 AM, Linus Walleij wrote:
> On Sat, Nov 21, 2015 at 1:17 AM, Joshua Henderson
> wrote:
>
>> From: Andrei Pistirica
>>
>> Add a driver for the pin controller present on the Microchip PIC32
>> including the specific variant PIC32MZDA. This driver provides pinmux
>> and p
> Is that an "Acked-by"? I'd like to pull this plus Vishal's
> gendisk-badblocks patches into a unified libnvdimm-error-handling
> branch. We're looking to have v4.5 able to avoid or survive nvdimm
> media errors through the pmem driver and DAX paths.
I'm making a V2 that fixes some build errors
From: Kosuke Tatsukawa
BugLink: http://bugs.launchpad.net/bugs/1512815
commit e81107d4c6bd098878af9796b24edc8d4a9524fd upstream.
My colleague ran into a program stall on a x86_64 server, where
n_tty_read() was waiting for data even if there was data in the buffer
in the pty. kernel stack for t
Hello,
Please consider including upstream commit
e81107d4c6bd098878af9796b24edc8d4a9524fd
in the next v3.13.y-ckt release. This commit was included mainline as of
v4.3-rc5.
It has been tested and confirmed to resolve
http://bugs.launchpad.net/bugs/1512815 .
commit e81107d4c6bd098878af9796b24e
On Tue 08 Dec 13:52 PST 2015, Arnd Bergmann wrote:
> On Tuesday 08 December 2015 13:29:22 John Stultz wrote:
>
[..]
> > +static int reboot_reason(struct notifier_block *nb, unsigned long action,
> > + void *data)
> > +{
> > + char *cmd =
> Should we backport this all the way to v2.6.32 (currently the oldest
> stable tree)?
We need to be able to explain how the case being tested can occur, then
explain the situation in which it actually prevents a race condition.
If nobody can do that then it shouldn't be backported because its ch
On Tue, 8 Dec 2015 10:18:50 + Qais Yousef wrote:
> Recent changes to how GFP_ATOMIC is defined seems to have broken the condition
> to use mips_alloc_from_contiguous() in mips_dma_alloc_coherent().
>
> I couldn't bottom out the exact change but I think it's this one
>
> d0164adc89f6 (mm, pa
On 12/08/2015 04:25 PM, Rasmus Villemoes wrote:
> If char is signed and one of these bytes happen to have a value
> outside the ascii range, the corresponding output will consist of
> "ff" followed by the two hex chars that were actually
> intended. One way to fix it would be to change the cast
The following code pattern exists in some DRM drivers:
ddev = drm_dev_alloc(&driver, parent_dev);
drm_dev_set_unique(ddev, dev_name(parent_dev));
(Sometimes dev_name(ddev->dev) is used, which is the same.)
As suggested in
http://lists.freedesktop.org/archives/dri-devel/2015-December/0964
drm_dev_set_unique() uses a format string to define the unique name of a
device. This feature is not used as currently all the calls to this
function either use "%s" as a format string or directly use
dev_name().
Even though this second kind of call does not introduce security
problems, because t
On Tue, Dec 8, 2015 at 3:29 PM, John Stultz wrote:
> This patch adds a basic driver to allow for commands like
> "reboot bootloader" and "reboot recovery" to communicate this
> reboot-reason to the bootloader.
>
> This is commonly done on Android devices, in order to reboot
> the device into fastb
Em Tue, Dec 08, 2015 at 03:48:25PM -0600, Josh Poimboeuf escreveu:
> On Tue, Dec 08, 2015 at 04:40:26PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Dec 08, 2015 at 01:17:00PM -0600, Josh Poimboeuf escreveu:
> > > On Tue, Dec 08, 2015 at 04:09:31PM -0300, Arnaldo Carvalho de Melo wrote:
> > >
On 12/8/2015 1:34 PM, Arnd Bergmann wrote:
On Tuesday 08 December 2015 08:53:53 santosh shilimkar wrote:
On 12/8/2015 7:30 AM, Arnd Bergmann wrote:
The knav_qmss driver is currently broken when CONFIG_LPAE is
set, which is a bit surprising because I'd expect that any serious
users of this platf
On Tue, Dec 8, 2015 at 4:15 PM, Bjorn Andersson
wrote:
> On Tue 08 Dec 13:52 PST 2015, Arnd Bergmann wrote:
>
>> On Tuesday 08 December 2015 13:29:22 John Stultz wrote:
[...]
>> > +static int __init reboot_reason_init(void)
>> > +{
>> > + return platform_driver_register(&reboot_reason_driver);
On Tue, 2015-12-08 at 14:18 -0600, Andy Fleming wrote:
> On Thu, Dec 3, 2015 at 1:19 AM, wrote:
> > From: Igal Liberman
> >
> > This patch adds the Ethernet MAC driver supporting the three
> > different types of MACs: dTSEC, tGEC and mEMAC.
> >
> > Signed-off-by: Igal Liberman
>
> [...]
>
>
On Mon, Dec 7, 2015 at 6:33 PM, Al Viro wrote:
> On Mon, Dec 07, 2015 at 05:59:41PM -0800, Andy Lutomirski wrote:
>
>> If I dump all task states (see attached typescript), I see a bunch of
>> things blocked in 9p rpc. This makes me think it could be a QEMU bug,
>> not a kernel bug.
>
> Maybe, may
On Mon, Nov 30, 2015 at 05:08:57PM -0800, Stephen Boyd wrote:
> Enable some ssbi drivers present on msm8660, msm8960 and apq8064
> devices so that we fully exercise the devices present in the dts
> files.
>
> Signed-off-by: Stephen Boyd
Acked-by: Andy Gross
--
To unsubscribe from this list: se
From: Greg KH
Sent: Sunday, October 18, 2015 8:57 AM
> Please make it against my tty-testing branch of tty.git on
git.kernel.org, that is the issue here, you are working against a
"clean" tree, not one with all of the other tty/serial changes in it.
I havn't see any respond for my v8 of this pat
On Tue, Dec 08, 2015 at 04:54:29PM -0600, Andy Gross wrote:
> On Mon, Nov 30, 2015 at 05:08:57PM -0800, Stephen Boyd wrote:
> > Enable some ssbi drivers present on msm8660, msm8960 and apq8064
> > devices so that we fully exercise the devices present in the dts
> > files.
> >
> > Signed-off-by: St
Hi Andrew,
On Tue, 8 Dec 2015 21:51:40 +1100 Stephen Rothwell
wrote:
>
> After merging the akpm-current tree, today's linux-next build (arm64
> allnoconfig and others) failed like this:
>
> arch/arm64/mm/mmap.c:54:1: error: unknown type name 'ifdef'
> arch/arm64/mm/mmap.c:55:2: error: expected
On Tue, Dec 08, 2015 at 07:27:32PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Dec 08, 2015 at 03:48:25PM -0600, Josh Poimboeuf escreveu:
> > On Tue, Dec 08, 2015 at 04:40:26PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Tue, Dec 08, 2015 at 01:17:00PM -0600, Josh Poimboeuf escreveu:
> > >
The latest maintenance release Git v2.6.4 is now available at
the usual places, with a handful of fixes that are already in
the 'master' front.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.6.4'
tag and th
Hi Tilman,
On di, 2015-12-08 at 12:00 +0100, Tilman Schmidt wrote:
> When shutting down the device, the struct ser_cardstate must not be
> kfree()d immediately after the call to platform_device_unregister()
> since the embedded struct platform_device is still in use.
> Move the kfree() call to the
Hi Tilman,
On di, 2015-12-08 at 12:00 +0100, Tilman Schmidt wrote:
> device->platform_data and platform_device->resource are never used
> and remain NULL through their entire life. Drops the kfree() calls
> for them from the device release method.
>
> Signed-off-by: Tilman Schmidt
> Reported-by:
On Tue, Dec 08, 2015 at 11:20:40AM -0500, Tejun Heo wrote:
> Hello,
>
> On Mon, Dec 07, 2015 at 05:06:20PM -0600, serge.hal...@ubuntu.com wrote:
> > fs/kernfs/mount.c | 74
> >
> > include/linux/kernfs.h |2 ++
> > kernel/cgroup.c
Normally, when a user can modify a file that has setuid or setgid bits,
those bits are cleared when they are not the file owner or a member
of the group. This is enforced when using write and truncate but not
when writing to a shared mmap on the file. This could allow the file
writer to gain privil
On 8 December 2015 at 22:12, Nicolas Iooss wrote:
> drm_dev_set_unique() uses a format string to define the unique name of a
> device. This feature is not used as currently all the calls to this
> function either use "%s" as a format string or directly use
> dev_name().
>
> Even though this secon
On Tue, 8 Dec 2015 13:33:22 -0500
Prarit Bhargava wrote:
> Intel RAPL initialized on several systems where the BIOS lock bit (msr
> 0x610, bit 63) was set. This occured because the return value of
> rapl_read_data_raw() was being checked, rather than the value of the
> variable passed in, locke
God dag,
Dette er Lloyds TSB Bank Plc Lån tilby.
Lloyds TSB tilbyr fleksible og rimelige lån til ethvert formål å
hjelpe deg å nå dine mål. vi lån med lav rente på 1,5%. Her er noen
viktige funksjoner i personlige lån som tilbys av Lloyds TSB. Her er de
Låne Faktorer vi samarbeider med de
Make st_* statistics per ring and the VBD sysfs would iterate over all the
rings.
Note: xenvbd_sysfs_delif() is called in xen_blkbk_remove() before all rings
are torn down, so it's safe.
This patch was based on konrad/xen.git/for-jens-4.5.
Signed-off-by: Bob Liu
---
drivers/block/xen-blkback/b
From: Colin Ian King
minor change, indenting is one tab out.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/ath/ath9k/xmit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath9k/xmit.c
b/drivers/net/wireless/ath/ath9k/xmit.c
index 3e3dac3.
On 12/09/2015 12:28 AM, Emil Velikov wrote:
> On 8 December 2015 at 22:12, Nicolas Iooss
> wrote:
>> drm_dev_set_unique() uses a format string to define the unique name of a
>> device. This feature is not used as currently all the calls to this
>> function either use "%s" as a format string or d
Dear Tony,
> > Which do you think is beter ?
> >- change into kernelcore="mirrored"
> >- keep kernelcore="reliable" and minmal printk fix
>
> UEFI came up with the "reliable" wording (as a more generic term ...
> as Andrew said
> it could cover differences in ECC modes, or some alternat
On Tue, 2015-12-08 at 22:24 +0200, Jarkko Sakkinen wrote:
> On Tue, Dec 08, 2015 at 01:01:02PM +0200, Jarkko Sakkinen wrote:
> > On Tue, Dec 08, 2015 at 09:35:05AM +1100, James Morris wrote:
> > > On Mon, 7 Dec 2015, Jarkko Sakkinen wrote:
> > >
> > > > On Fri, Nov 20, 2015 at 01:34:35PM +1100, Ja
On Thu, 3 Dec 2015 18:50:07 +0300 Andrey Ryabinin
wrote:
> UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
> Compiler inserts code that perform certain kinds of checks before
> operations that could cause UB. If check fails (i.e. UB detected)
> __ubsan_handle_* function
On Tue, 2015-12-08 at 15:28 -0600, Rob Herring wrote:
> On Tue, Dec 8, 2015 at 11:03 AM, Joe Perches wrote:
> > On Tue, 2015-12-08 at 08:16 -0800, Joe Perches wrote:
> > > On Wed, 2015-12-09 at 01:07 +0900, Masahiro Yamada wrote:
> > > > Trivial changes suggested by checkpatch.pl.
> > > []
> > > >
On Tue, Dec 08, 2015 at 01:19:32PM -0800, Kees Cook wrote:
> On Mon, Nov 23, 2015 at 6:37 AM, Mihai Donțu wrote:
> > On Sun, 15 Nov 2015 08:00:22 +0100 Pavel Machek wrote:
> >> Kernel complains:
> >>
> >> [5.256044] [ cut here ]
> >> [5.259267] WARNING: CPU: 0
On Tue, Dec 8, 2015 at 1:52 PM, Arnd Bergmann wrote:
>
> On Tuesday 08 December 2015 13:29:22 John Stultz wrote:
>
> > diff --git a/arch/arm/boot/dts/qcom-apq8064-nexus7-flo.dts
> > b/arch/arm/boot/dts/qcom-apq8064-nexus7-flo.dts
> > index 5183d18..ee5dcb7 100644
> > --- a/arch/arm/boot/dts/qcom-
Hi Boris,
On Wed, Dec 02, 2015 at 09:50:01AM +0100, Boris Brezillon wrote:
> struct nand_chip now embeds an mtd device. Patch all drivers to make use
> of this mtd instance instead of using the instance embedded in their
> private struct or dynamically allocated.
>
> Signed-off-by: Boris Brezillo
On Tue, 2015-12-08 at 13:50 -0500, Steven Rostedt wrote:
> It has come to my attention that kprobe event stack tracing does not
> work on powerpc.
Yep looks like you're right. I didn't realise it was separate from the regular
stack trace stuff.
> diff --git a/arch/powerpc/kernel/stacktrace.c
>
On Tue, Dec 8, 2015 at 2:07 PM, Bjorn Andersson
wrote:
> On Tue 08 Dec 13:29 PST 2015, John Stultz wrote:
>
>> This patch adds a basic driver to allow for commands like
>> "reboot bootloader" and "reboot recovery" to communicate this
>> reboot-reason to the bootloader.
>>
>> This is commonly done
On 2015-12-09 03:33, Prarit Bhargava wrote:
> Intel RAPL initialized on several systems where the BIOS lock bit (msr
> 0x610, bit 63) was set. This occured because the return value of
> rapl_read_data_raw() was being checked, rather than the value of the variable
> passed in, locked.
>
> This pat
On Wed, 09 Dec 2015 11:20:22 +1100
Michael Ellerman wrote:
> On Tue, 2015-12-08 at 13:50 -0500, Steven Rostedt wrote:
>
> > It has come to my attention that kprobe event stack tracing does not
> > work on powerpc.
>
> Yep looks like you're right. I didn't realise it was separate from the regu
On Tue, Dec 08, 2015 at 04:52:42PM +0800, Aaron Lu wrote:
> On Tue, Dec 08, 2015 at 03:51:16PM +0900, Joonsoo Kim wrote:
> > On Tue, Dec 08, 2015 at 01:14:39PM +0800, Aaron Lu wrote:
> > > On Tue, Dec 08, 2015 at 09:41:18AM +0900, Joonsoo Kim wrote:
> > > > On Mon, Dec 07, 2015 at 04:59:56PM +0800,
On 08.12.2015 22:41, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 12/08/2015 05:13 AM, Krzysztof Kozlowski wrote:
>> On 08.12.2015 03:18, Bartlomiej Zolnierkiewicz wrote:
>>> From: Ben Gamari
>>>
>>> The Exynos 5422 is identical to the 5800 except for the fact that it
>>> boots from
On Tue, Dec 8, 2015 at 2:26 PM, Rob Herring wrote:
> On Tue, Dec 8, 2015 at 3:29 PM, John Stultz wrote:
>> This patch adds a basic driver to allow for commands like
>> "reboot bootloader" and "reboot recovery" to communicate this
>> reboot-reason to the bootloader.
>>
>> This is commonly done on
Hi,
On Tue, Dec 01, 2015 at 12:02:57PM +0100, Boris Brezillon wrote:
> Hello,
>
> This huge series aims at clarifying the relationship between the mtd and
> nand_chip structures and hiding NAND framework internals to NAND
> controller drivers.
>
> The first part of the series provide an mtd_to_n
Add a binding for the regulator which controls the OTG chargepath switch.
The OTG switch gets its power from pm8941_5vs1, and that should be
expressed as a usb-otg-in-supply property in the DT node for the
charger driver. The regulator name is "otg".
Signed-off-by: Tim Bird
---
Changes since v1
Add a regulator to control the OTG chargepath switch. This
is used by USB code to control VBUS direction - out for host mode
on the OTG port, and in for charging mode.
Signed-off-by: Tim Bird
---
Changes since v1:
- changed name of supply to remove underscores
---
drivers/power/qcom_smbb.c | 7
Add the otg regulator provided by the charger block.
Signed-off-by: Tim Bird
---
arch/arm/boot/dts/qcom-pm8941.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-pm8941.dtsi
b/arch/arm/boot/dts/qcom-pm8941.dtsi
index b0d4439..1b80100 100644
--- a/arch/arm/boot/d
The mm-of-the-moment snapshot 2015-12-08-16-42 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Tuesday, December 08, 2015 10:01:26 PM Viresh Kumar wrote:
> On 08-12-15, 17:50, Rafael J. Wysocki wrote:
> > I don't remember that code clearly and it would take some time for me to
> > recall it and then figure out the details about the changes. Not
> > impossible,
> > but quite honestly I h
On Mon, Dec 07, 2015 at 10:25:19AM -0500, Steven Rostedt wrote:
> Hi,
>
> The attached config doesn't build on 4.2.6, but changing it to the
> following:
>
> VIDEO_V4L2_SUBDEV_API n -> y
> +V4L2_FLASH_LED_CLASS n
>
> does build.
Did this work on older kernels (4.2.5? .4? older?)
thanks,
gr
On Tue, Dec 08, 2015 at 10:51:03AM +0100, Roman Pen wrote:
> Hello.
>
> Here is an attempt to solve annoying race, which exists between two operations
> on debugfs entries: write (setting a request) and read (reading a response).
>
> E.g. let's assume that we have some storage device, which can h
On Mon, Dec 07, 2015 at 05:06:16PM -0600, serge.hal...@ubuntu.com wrote:
> From: Aditya Kali
>
> The new function kernfs_path_from_node() generates and returns kernfs
> path of a given kernfs_node relative to a given parent kernfs_node.
>
> Changelog 20151125:
> - Fully-wing multilinecomments
On Tue, Dec 08, 2015 at 09:34:16PM +0100, Wim de With wrote:
> This fixes the following sparse warnings:
>
> drivers/staging/lustre/lustre/llite/file.c:1310:38:expected void const
> [noderef] *from
> drivers/staging/lustre/lustre/llite/file.c:1310:38:got struct
> ll_recreate_obj *
> driv
Currently the only one combination is tested for overflow, i.e. rowsize = 16,
groupsize = 1, len = 1. Do various test to go through all possible branches.
Signed-off-by: Andy Shevchenko
Cc: Rasmus Villemoes
---
lib/test_hexdump.c | 21 ++---
1 file changed, 18 insertions(+), 3 d
On Tuesday, December 08, 2015 03:50:06 PM Andy Shevchenko wrote:
> On Tue, Dec 8, 2015 at 4:05 PM, Rafael J. Wysocki wrote:
> > On Tuesday, December 08, 2015 02:32:00 PM Thomas Gleixner wrote:
> >> On Mon, 7 Dec 2015, Rafael J. Wysocki wrote:
> >> > On Monday, December 07, 2015 12:57:33 PM Andy Sh
When test for overflow do iterate the buffer length in a range
0 .. BUF_SIZE.
Signed-off-by: Andy Shevchenko
Cc: Rasmus Villemoes
---
lib/test_hexdump.c | 27 +--
1 file changed, 13 insertions(+), 14 deletions(-)
diff --git a/lib/test_hexdump.c b/lib/test_hexdump.c
inde
Better to use memcmp() against entire buffer to check that nothing is happened
to the data in the tail.
Signed-off-by: Andy Shevchenko
---
lib/test_hexdump.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/test_hexdump.c b/lib/test_hexdump.c
index 141d031..4b949aa 1
On Monday, December 07, 2015 10:06:49 AM Bjorn Helgaas wrote:
> On Mon, Dec 07, 2015 at 02:41:34AM +0100, Rafael J. Wysocki wrote:
> > On Sunday, December 06, 2015 05:33:45 PM Julia Lawall wrote:
> > > The pci_platform_pm_ops structure is never modified, so declare it as
> > > const.
> > >
> > > D
Just to follow the scheme that most of the test modules are using.
There is no fuctional change.
Signed-off-by: Andy Shevchenko
Acked-by: Rasmus Villemoes
---
lib/Makefile | 2 +-
lib/{test-hexdump.c => test_hexdump.c} | 0
2 files changed, 1 insertion(+), 1 deletion(
After processing by hex_dump_to_buffer() check all the parts to be expected.
Part 1. The actual expected hex dump with or without ASCII part.
Part 2. Check if the buffer is dirty beyond needed.
Part 3. Return code should be as expected.
This is done by using comparison of the return code and me
Define a character to fill the test buffers. Though the character should be
printable since it's used when errors are reported. It should neither be from
hex digit [a-fA-F0-9] dictionary nor space. It is recommended not to use one
which is present in ASCII part of the test data. Later on we might s
Like others test are doing print the gathered statistics after test module is
finished. Return from the module based on the result.
Signed-off-by: Andy Shevchenko
Acked-by: Rasmus Villemoes
---
lib/test_hexdump.c | 26 +++---
1 file changed, 23 insertions(+), 3 deletions(-)
The test suite currently doesn't cover many corner cases when
hex_dump_to_buffer() runs into overflow. Refactor and amend test suite to cover
most of the cases.
Andrew, please, update entire series in your pool.
Changelog v2:
- address Rasmus' comments
- add tags
Andy Shevchenko (9):
test_hexd
The function prepares the expected result in the provided buffer.
Signed-off-by: Andy Shevchenko
Acked-by: Rasmus Villemoes
---
lib/test_hexdump.c | 26 +++---
1 file changed, 19 insertions(+), 7 deletions(-)
diff --git a/lib/test_hexdump.c b/lib/test_hexdump.c
index 5241df
The magic numbers of the length are converted to their actual meaning,
such as end of the buffer with and without ASCII part.
We don't touch the rest of the magic constants that will be removed in the
following commits.
Signed-off-by: Andy Shevchenko
Cc: Rasmus Villemoes
---
lib/test_hexdump.c
Hi Rob,
Thanks
- Yakir
On 12/08/2015 11:01 PM, Rob Herring wrote:
On Mon, Dec 07, 2015 at 02:39:07PM +0800, Yakir Yang wrote:
Analogix dp driver is split from exynos dp driver, so we just
make an copy of exynos_dp.txt, and then simplify exynos_dp.txt
Beside update some exynos dtsi file with
On Tue, 2015-12-08 at 19:28 -0500, Steven Rostedt wrote:
> On Wed, 09 Dec 2015 11:20:22 +1100
> Michael Ellerman wrote:
> > On Tue, 2015-12-08 at 13:50 -0500, Steven Rostedt wrote:
> > > It has come to my attention that kprobe event stack tracing does not
> > > work on powerpc.
> > > diff --git
Hi Rob,
On 12/08/2015 11:03 PM, Rob Herring wrote:
On Mon, Dec 07, 2015 at 02:39:34PM +0800, Yakir Yang wrote:
Rockchip DP driver is a helper driver of analogix_dp coder driver,
so most of the DT property should be descriped in analogix_dp document.
Signed-off-by: Yakir Yang
Reviewed-by: Heik
On Tue, Dec 08 2015, Peter Zijlstra wrote:
>>
>
> *sigh*, so that patch was broken.. the below might fix it, but please
> someone look at it, I seem to have a less than stellar track record
> here...
This new change seems to be more intrusive than should be needed.
Can't we just do:
__sched
On Wed, Dec 9, 2015 at 3:20 AM, Rafael J. Wysocki wrote:
> I've put the entire series (including the three last patches with Vinod's
> ACKs)
> into my bleeding-edge branch, please check it in there and let me know if
> anything is not right.
I just have checked, everything looks good.
Thank you,
Fix multiple errors in the comments, improve the wording, fix
indentation and clean up some areas reported by checkpatch.
Signed-off-by: Clemens Gruber
---
include/asm-generic/vmlinux.lds.h | 57 ++-
1 file changed, 33 insertions(+), 24 deletions(-)
diff --gi
Hi Rob
On 12/08/2015 11:06 PM, Rob Herring wrote:
On Mon, Dec 07, 2015 at 02:39:50PM +0800, Yakir Yang wrote:
Add dt binding documentation for rockchip display port PHY.
Signed-off-by: Yakir Yang
Reviewed-by: Heiko Stuebner
One possible typo below, otherwise:
Acked-by: Rob Herring
Thank
On Tue, Dec 08, 2015 at 06:51:20AM -0500, Greg KH wrote:
> On Mon, Dec 07, 2015 at 05:06:16PM -0600, serge.hal...@ubuntu.com wrote:
> > From: Aditya Kali
> >
> > The new function kernfs_path_from_node() generates and returns kernfs
> > path of a given kernfs_node relative to a given parent kernfs
Hi Al,
After merging the vfs tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
In file included from fs/orangefs/acl.c:8:0:
fs/orangefs/acl.c: In function 'pvfs2_get_acl':
fs/orangefs/pvfs2-kernel.h:203:38: error: 'POSIX_ACL_XATTR_ACCESS' undeclared
(first use in this functi
On Wed, 09 Dec 2015 12:03:05 +1100
Michael Ellerman wrote:
> Looks like we actually have:
>
> #define kernel_stack_pointer(regs) ((regs)->gpr[1])
>
> So that would be the most self documenting way to do it I guess, though I've
> never actually seen that macro used anywhere before :)
Cool, t
Hi Rob,
Thanks for your respond.
On 12/08/2015 11:09 PM, Rob Herring wrote:
On Mon, Dec 07, 2015 at 02:40:42PM +0800, Yakir Yang wrote:
Some edp screen do not have hpd signal, so we can't just return
failed when hpd plug in detect failed.
This is an hardware property, so we need add a devicet
On Tue, 2015-12-08 at 14:14 +0100, Rafael J. Wysocki wrote:
> On Tuesday, December 08, 2015 09:37:56 AM Ken Xue wrote:
> > On Mon, 2015-12-07 at 23:48 +0100, Rafael J. Wysocki wrote:
> > > On Monday, December 07, 2015 12:44:33 PM Ken Xue wrote:
> > > > D3cold is only regarded as valid if the "_PR3"
> -Original Message-
> From: Long Li [mailto:lon...@microsoft.com]
> Sent: Friday, December 4, 2015 12:07 AM
> To: KY Srinivasan ; Haiyang Zhang
> ; James E.J. Bottomley
> Cc: de...@linuxdriverproject.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Long Li
> Subject: [
On Tue, Dec 8, 2015 at 1:39 PM, Richard Weinberger wrote:
>
> This pull request contains various bug fixes, most of them are
> fall out from the merge window.
>
> Richard Weinberger (2):
> um: Fix fpstate handling
Ugh. This is very ugly. It's apparently the result of commit
530e5c827182 ("x
This patch series has been forked from the following patch series since
it no longer depends on the rest of the patches.
[PATCH v4 00/10] ACPI GIC Self-probing, GICv2m and GICv3 support
https://lkml.org/lkml/2015/7/29/234
It has been ported to use the newly introduced device fwnode_handle
fo
This patch replaces the struct device_node with struct fwnode_handle
since this structure is common between DT and ACPI.
It also refactors gicv2m_init_one() to prepare for ACPI support.
There should be no functional changes.
Signed-off-by: Suravee Suthikulpanit
---
drivers/irqchip/irq-gic-v2m.c
This patch introduces pci_msi_register_fwnode_provider() for irqchip
to register a callback, to provide a way to determine appropriate MSI
domain for a pci device.
It also introduces pci_host_bridge_acpi_msi_domain(), which returns
the MSI domain of the specified PCI host bridge with DOMAIN_BUS_PC
This patch introduces gicv2m_acpi_init(), which uses information
in MADT GIC MSI frames structure to initialize GICv2m driver.
Signed-off-by: Suravee Suthikulpanit
Signed-off-by: Hanjun Guo
---
drivers/irqchip/irq-gic-v2m.c | 95 +
drivers/irqchip/irq-g
This patch adds an accessor function to retrieve struct irqchip_fwid.name.
Signed-off-by: Suravee Suthikulpanit
---
include/linux/irqdomain.h | 1 +
kernel/irq/irqdomain.c| 18 ++
2 files changed, 19 insertions(+)
diff --git a/include/linux/irqdomain.h b/include/linux/irqdo
Since there will be several places checking if fwnode.type
is equal FWNODE_IRQCHIP, this patch adds a convenient function
for this purpose.
Signed-off-by: Suravee Suthikulpanit
---
drivers/irqchip/irq-gic.c | 2 +-
include/linux/irqdomain.h | 5 +
kernel/irq/irqdomain.c| 2 +-
3 files ch
uot;)
I have used the pm tree from next-20151208 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://
>
> 68e115b19a01 ("cpufreq: governor: replace per-cpu delayed work with timers")
>
> I have used the pm tree from next-20151208 for today.
Yeah, it missed this stupid change. Sorry about that.
diff --git a/drivers/cpufreq/cpufreq_governor.c
b/drivers/cpufreq/cpufreq_gov
Analogix dp driver is split from exynos dp driver, so we just
make an copy of exynos_dp.txt, and then simplify exynos_dp.txt
Beside update some exynos dtsi file with the latest change
according to the devicetree binding documents.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
Tested-by: Javie
601 - 700 of 894 matches
Mail list logo