There is no point in having a special case for the revision when probing
a switch model. The code gets cluttered with unnecessary defines, and
leads to errors when code such as mv88e6131_setup compares
PORT_SWITCH_ID_6131_B2 to ps->id which masks the revision.
Drop every revision definition, and l
Add the number of databases to the info structure.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6123.c | 3 +++
drivers/net/dsa/mv88e6131.c | 4
drivers/net/dsa/mv88e6171.c | 4
drivers/net/dsa/mv88e6352.c | 6 ++
drivers/net/dsa/mv88e6xxx.c
Read the switch ID only once, at probe time, to avoid multiple read
accesses and MII bus checking.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6xxx.c | 57 -
1 file changed, 30 insertions(+), 27 deletions(-)
diff -
Add a test for use of ACCESS_ONCE that could be written using
READ_ONCE or WRITE_ONCE.
--fix it too if desired.
The WRITE_ONCE fixes are less correct than the coccinelle script below
as checkpatch cannot have a completely correct "expression" mechanism
because checkpatch works on patches and not
On Sun, Apr 17, 2016 at 12:58:21PM -0400, Sasha Levin wrote:
> Hi all,
>
> I've hit the following while fuzzing with syzkaller inside a KVM tools guest
> running the latest -next kernel:
thanks for the report. Adding Tejun...
if I read the report correctly it's not about bpf, but rather points to
Now that the supported number of PCI IRQs are no longer capped
with 256, renaming the static array to support ISA IRQs only
and removing the MAX_IRQS constant.
Signed-off-by: Sinan Kaya
---
drivers/acpi/pci_link.c | 40
1 file changed, 20 insertions(+), 2
Removing the SCI penalize function as the penalty is now calculated on the
fly.
Signed-off-by: Sinan Kaya
---
arch/x86/kernel/acpi/boot.c | 1 -
drivers/acpi/pci_link.c | 4
include/linux/acpi.h| 1 -
3 files changed, 6 deletions(-)
diff --git a/arch/x86/kernel/acpi/boot.c b/ar
acpi_irq_get_penalty is now calculating the penalty on the fly now.
No need to maintain global list of penalties or calculate them
at the init time. Removing duplicate code in acpi_irq_penalty_init.
Signed-off-by: Sinan Kaya
---
arch/x86/pci/acpi.c | 1 -
drivers/acpi/pci_link.c | 3
Code has been redesigned to calculate penalty requirements on the fly. This
significantly simplifies the implementation and removes some of the init
calls from x86 architecture.
Signed-off-by: Sinan Kaya
---
drivers/acpi/pci_link.c | 97 ++---
1 file c
On Sun, Apr 17, 2016 at 01:23:55PM -0400, Vivien Didelot wrote:
> Change the dsa_switch_driver.probe function to return a const char *.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
Thanks
Andrew
> ---
> drivers/net/dsa/bcm_sf2.c | 6 +++---
> drivers/net/dsa/mv88e606
On Sun, Apr 17, 2016 at 01:23:59PM -0400, Vivien Didelot wrote:
> Add a new switch info structure which is meant to store switch models
> static information, such as product number, name, number of ports,
> number of databases, etc.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
Th
Hi!
> > > > > Ok, it works now. I was doing tests in daylight so it was poorly
> > > > > visible. The right part of keyboard stays lit (but that's expected
> > > > > AFAICT), but the left part blinks.
> > > >
> > > > During idle, both should go off and are doing so for me. Both LEDs off
> > > > i
On 04/16/2016 02:22 PM, Jonathan Cameron wrote:
> On 10/04/16 20:07, Alison Schofield wrote:
>> Driver includes struct regmap and struct device in its global data.
>> Remove the struct device and use regmap API to retrieve device info.
>>
Why? This adds nothing but more code to get dev through som
On Sun, 17 Apr 2016 19:11:42 +0200
Rafał Miłecki wrote:
> Now we have all drivers properly setting this new field we can start
> using it. For a very short period of time we should support both values:
> NAND_ECC_SOFT and NAND_ECC_SOFT_BCH treating them the same. It's because
> of_get_nand_ecc_mo
On Sun, 17 Apr 2016 19:10:11 +0200
Rafał Miłecki wrote:
> On 17 April 2016 at 19:05, Boris Brezillon
> wrote:
> > On Fri, 15 Apr 2016 21:54:12 +0200
> > Rafał Miłecki wrote:
> >
> >> This value should not be part of nand_ecc_modes_t as it specifies
> >> algorithm not a mode. We successfully man
From: 0xAX
The memblock_add_region() and memblock_reserve_region do not nothing specific
before the call of the memblock_add_range(), only print debug output.
We can do the same in the memblock_add() and memblock_reserve() since both
memblock_add_region() and memblock_reserve_region are not used
On Sat 16-04-16 14:18:19, Florian Margaine wrote:
> On Fri, 2016-04-15 at 12:17 +1000, Dave Chinner wrote:
> > On Thu, Apr 14, 2016 at 09:57:07AM +0200, Florian Margaine wrote:
> > > This lets userland get the filesystem freezing status, aka whether
> > > the
> > > filesystem is frozen or not. This
With the current cgroup namespace patches, the root dentry path of a
mount as shown in /proc/self/mountinfo is the full global cgroup
path. It is common for userspace to use /proc/self/mountinfo to
search for cgroup mountpoints, and expect the root dentry path to
relate to the cgroup paths in /pro
From: Serge Hallyn
We've calculated @len to be the bytes we need for '/..' entries from
@kn_from to the common ancestor, and calculated @nlen to be the extra
bytes we need to get from the common ancestor to @kn_to. We use them
as such at the end. But in the loop copying the actual entries, we
o
From: Serge Hallyn
When showing a cgroupfs entry in mountinfo, show the
path of the mount root dentry relative to the reader's
cgroup namespace root.
Signed-off-by: Serge Hallyn
---
fs/kernfs/mount.c | 14 ++
include/linux/kernfs.h | 2 ++
kernel/cgroup.c| 35
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/davinci_nand.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/mtd/nand/davinci_nand.c b/drivers/mtd/
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
drivers/staging/mt29f_spinand/mt29f_spinand.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/mt29f_spinand/mt29f_spinand.c
b/drivers/staging/mt29f_s
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/bf5xx_nand.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/nand/bf5xx_nand.c b/drivers/mtd/nand/bf5xx_nand.c
index b38f414..37da423 100
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/atmel_nand.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/mtd/nand/atmel_nand.c b/drivers/mtd/nand/atmel_nand.c
index eec8c
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
This patch may be skipped if we apply
[PATCH 00/12] mtd: get rid of of_mtd.{c,h} and of_get_nand_xx()
patchset first.
---
drivers/mtd/nand/hisi504_nand.c | 1 +
1 file ch
NAND core sets ECC algorithm in algo field now and it should be
preferred over the mode field. This also prepares driver for dropping
NAND_ECC_SOFT_BCH.
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/fsmc_nand.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/driver
This value should not be part of nand_ecc_modes_t as it specifies
algorithm not a mode. We successfully managed to introduce new "algo"
field which is respected now.
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/fsmc_nand.c | 3 +--
drivers/mtd/nand/jz4780_nand.c | 1 -
drivers/mtd/nand/
Now we have all drivers properly setting this new field we can start
using it. For a very short period of time we should support both values:
NAND_ECC_SOFT and NAND_ECC_SOFT_BCH treating them the same. It's because
of_get_nand_ecc_mode may still be setting NAND_ECC_SOFT_BCH.
Signed-off-by: Rafał M
There isn't any difference between handling NAND_ECC_SOFT and
NAND_ECC_SOFT_BCH now. What matters is the new field called "algo".
Please note we're keeping backward DT compatibility. We are still
treating "soft_bch" value as the one setting Hamming algorithm, it's
just handled in of_get_nand_ecc_al
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
arch/cris/arch-v32/drivers/mach-a3/nandflash.c | 1 +
arch/cris/arch-v32/drivers/mach-fs/nandflash.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/cris/arch-
This is part of process deprecating NAND_ECC_SOFT_BCH (and switching to
enum nand_ecc_algo).
Signed-off-by: Rafał Miłecki
---
drivers/mtd/nand/nand_base.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
index dd02c09..e1f3cf8 100644
On Fri, 15 Apr, at 08:38:37AM, Julia Lawall wrote:
>
> I looked at it a bit with Vaishali. I wonder if it would be possible at
> least to have only one flag? Then one wouldn't have to maintain the
> subtle relationship between atomic and duplicates. I'm not sure that it
> would help Coccinell
Apologies in advance for the "poor" quality of this bug report. No idea
how to proceed, because the issue historically has been intermittent to
non-existant for reasons unknown.
Within 24 hours of booting my Alpha (PWS 433au), I'm pretty much
guaranteed to see a "machine check" Oops which typical
No one need this macro now, so remove it. The motivation is
for supporting multipage bvecs, in which we only know
what the max count of bvecs is supported in the bio,
instead of max bio size.
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
include/linux/bio.h | 1 -
1 file changed, 1
Hi,
Interests[1] have been shown in multipage bvecs, so this patchset
try to prepare for the support and do two things:
1) the 1st 4 patches use bvec iterator to implement iterate_bvec(),
then we can drop the non-standard way for iterating bvec, which
can be thought as a good cleanup for lib/iov_
bvec iterator helpers should be used to implement by
iterate_bvec():lib/iov_iter.c too, and move them into
one header, so that we can keep bvec iterator header
out of CONFIG_BLOCK. Then we can remove the reinventing
of wheel in iterate_bvec().
Signed-off-by: Ming Lei
---
include/linux/bio.h | 5
bvec_iter_advance() only writes the parameter of iterator,
so the base address of bvec can be marked as const safely.
Without the change, we can see compiling warning in the
following patch for implementing iterate_bvec(): lib/iov_iter.c
with bvec iterator.
Reviewed-by: Christoph Hellwig
Signed-
No one need this macro, so remove it. The motivation is
for supporting multipage bvecs, in which we only know
what the max count of bvecs is supported in the bio,
instead of max size or max sectors.
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
include/linux/bio.h | 1 -
1 file cha
drbd is the only user of BIO_MAX_SIZE, so use BIO_MAX_PAGES
instead.
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
drivers/block/drbd/drbd_int.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/drbd/drbd_int.h b/drivers/block/drbd/drbd_int.h
ind
BIO_MAX_PAGES is used as maximum count of bvecs, so
replace BIO_MAX_SECTORS with BIO_MAX_PAGES since
BIO_MAX_SECTORS is to be removed.
Signed-off-by: Ming Lei
---
fs/xfs/xfs_buf.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
index 9a2
bvec has one native/mature iterator for long time, so not
necessary to use the reinvented wheel for iterating bvecs
in lib/iov_iter.c.
Two ITER_BVEC test cases are run:
- xfstest(-g auto) on loop dio/aio, no regression found
- swap file works well under extreme stress(stress-ng --a
This patch moves 'struct bio_vec' and 'struct bvec_iter'
into 'include/linux/bvec.h', then always include this header
into 'include/linux/blk_types.h'.
With this change, both 'struct bvec_iter' and bvec iterator
helpers don't depend on CONFIG_BLOCK any more, then we can
use bvec iterator to implem
On Apr 17, 2016, at 10:11 AM, Panos Vlachos wrote:
> Fixed one coding style issue in the
> file router_proc.c (Lustre staging driver)
Perhaps it's best to reference what the issue is.
I.e. "Fix too long line in …"
and then in the actual message add that you just split it?
>
> Signed-off-by: Pan
On Wednesday 02 March 2016 11:22:04 Geert Uytterhoeven wrote:
> On Wed, Mar 2, 2016 at 10:48 AM, Arnd Bergmann wrote:
> > Every new architecture has to add itself to the growing list of those
> > that do not support the legacy PC RTC driver.
> >
> > This replaces the long list of architectures tha
Hi Ivaylo,
On Sat, Apr 16, 2016 at 11:12:20AM +0300, Ivaylo Dimitrov wrote:
> Some sensors (like the one in Nokia N900) provide metadata in the first
> couple of lines. Make that information information available to the
> pipeline.
>
> Signed-off-by: Ivaylo Dimitrov
> ---
> drivers/media/i2c/sm
Skylake processor supports a new set of RAPL registers for controlling
entire SoC instead of just CPU package called PSys. This change adds
support in two sub systems:
x86/perf: Adds basic support for Skylake RAPL and PSys support
powercap/rapl: A new platform domain to the current power capping
Added Skylake client support for RAPL domains. In addition to RAPL domains
in Broadwell clients, it has support for platform domain (aka PSys). The
PSys domain controls entire SoC instead of just CPU package. Unlike
package domain, PSys support requires more than just processor level
implementation
Skylake processor supports a new set of RAPL registers for controlling
entire SoC instead of just CPU package. This is useful for thermal
and power control when source of power/thermal is not just CPU/GPU.
This change adds a new platform domain (AKA PSys) to the current
power capping Intel RAPL dri
On Sunday 17 April 2016 14:42:33 Johannes Berg wrote:
>
> I was thinking more restrictively of just the stuff that can't even be
> built without modifying the sources - like the "#if VERBOSE" thing.
All the DEBUG() statements are inside of this kind of check, so if we
remove the #ifdefs, it would
On Sunday 10 April 2016 07:37:23 Reizer, Eyal wrote:
> Add support for using with both wl12xx and wl18xx.
>
> - all wilink family needs special init command for entering wspi mode.
> extra clock cycles should be sent after the spi init command while the
> cs pin is high.
> - switch to controli
Add a BPF_F_CURRENT_CPU flag to optimize the use-case where user space has
per-CPU ring buffers and the eBPF program pushes the data into the current
CPU's ring buffer which saves us an extra helper function call in eBPF.
Also, make sure to properly reserve the remaining flags which are not used.
This minor set adds a new helper bpf_skb_event_output() for eBPF cls/act
program types which allows to pass events to user space applications. For
details, please see individual patches.
Thanks!
Daniel Borkmann (2):
bpf, trace: add BPF_F_CURRENT_CPU flag for bpf_perf_event_output
bpf: add eve
This patch adds a new helper for cls/act programs that can push events
to user space applications. For networking, this can be f.e. for sampling,
debugging, logging purposes or pushing of arbitrary wake-up events. The
idea is similar to a43eec304259 ("bpf: introduce bpf_perf_event_output()
helper")
drivers/staging/android/ion/ion.c produces 2 warnings and 29 checks.
This patch set fixes both warnings and all but 4 of the checks. All
except the last patch are trivial.
Signed-off-by: tcharding
---
Patch 1/4 is whitespace only.
This is my first Linux kernel patch.
thanks
tcharding (4):
drivers/staging/android/ion/ion.c checkpatch produces line over 80
character warnings.
This patch is whitespace only and fixes these warnings.
Signed-off-by: tcharding
---
drivers/staging/android/ion/ion.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging
drivers/staging/android/ion/ion.c checkpatch produces alignment checks.
This patch is whitespace only and fixes these checks.
Signed-off-by: tcharding
---
drivers/staging/android/ion/ion.c | 64 +++
1 file changed, 32 insertions(+), 32 deletions(-)
diff --gi
drivers/staging/android/ion/ion.c checkpatch produces
'Comparison to NULL could be written ...' checks.
This patch replaces comparison to NULL with !var as suggested by checkpatch.
Signed-off-by: tcharding
---
drivers/staging/android/ion/ion.c | 6 +++---
1 file changed, 3 insertions(+), 3 del
drivers/staging/android/ion/ion.c calls BUG_ON in places where WARN_ON will
suffice.
This patch replaces two such occurences. Two other occurences remain.
Signed-off-by: tcharding
---
Changing the remaining two BUG_ON's causes changes to the programm logic.
This is my first patch set to the ke
On 04/17/2016 01:29 PM, Alexei Starovoitov wrote:
> On Sun, Apr 17, 2016 at 12:58:21PM -0400, Sasha Levin wrote:
>> > Hi all,
>> >
>> > I've hit the following while fuzzing with syzkaller inside a KVM tools
>> > guest
>> > running the latest -next kernel:
> thanks for the report. Adding Tejun...
From: Arnd Bergmann
Date: Sun, 17 Apr 2016 11:19:55 +0200
> The new MACsec driver uses the AES crypto algorithm, but can be configured
> even if CONFIG_CRYPTO is disabled, leading to a build error:
>
> warning: (MAC80211 && MACSEC) selects CRYPTO_GCM which has unmet direct
> dependencies (CRYPT
From: Vivien Didelot
Date: Sun, 17 Apr 2016 13:23:54 -0400
> This patchset factorizes the mv88e6xxx code by sharing a new extendable
> info structure to store static data such as switch family, product
> number, number of ports, number of databases and the name.
...
Series applied, thanks Vivie
Hi Daniel,
[auto build test ERROR on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Daniel-Borkmann/bpf-trace-add-BPF_F_CURRENT_CPU-flag-for-bpf_perf_event_output/20160418-063147
config: m68k-allyesconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cg
On Thu, Apr 7, 2016 at 2:03 PM, Shannon Zhao wrote:
> From: Shannon Zhao
>
> ACPI 6.0 introduces a new table STAO to list the devices which are used
> by Xen and can't be used by Dom0. On Xen virtual platforms, the physical
> UART is used by Xen. So here it hides UART from Dom0.
>
> CC: "Rafael J
On Fri, Apr 15, 2016 at 8:43 AM, Shannon Zhao wrote:
> Hi Rafael，
>
> Could you please give your comments on this patch? Thanks in advanced!
I was traveling last week, sorry for the slow response.
On Mon, Apr 18, 2016 at 08:28:58AM +1000, tcharding wrote:
> drivers/staging/android/ion/ion.c checkpatch produces alignment checks.
>
> This patch is whitespace only and fixes these checks.
>
> Signed-off-by: tcharding
We need a "real" name here please, read Documentation/SubmittingPatches
for
On Sun, Apr 17, 2016 at 05:41:07PM +0200, Clemens Gruber wrote:
> Hi,
>
> I have an i.MX6Q board with the current mainline tree from Linus and
> systemd 229, which also acts as watchdog daemon.
> (RuntimeWatchdogSec=60)
>
> Since commit 11d7aba9ceb7 ("watchdog: imx2: Convert to use
> infrastructu
Hello,
On (03/30/16 16:12), Minchan Kim wrote:
> @@ -1421,7 +1434,6 @@ static unsigned long obj_malloc(struct size_class
> *class,
> unsigned long m_offset;
> void *vaddr;
>
> - handle |= OBJ_ALLOCATED_TAG;
a nitpick, why did you replace this ALLOCATED_TAG assignment
with 2 'ha
drivers/staging/android/ion/ion.c produces 2 warnings and 29 checks.
This patch set fixes both warnings and all but 4 of the checks. All
except the last patch are trivial.
Signed-off-by: Tobin C Harding
---
Patch 1/4 is whitespace only.
This is my first Linux kernel patch.
thanks
Tobin C Ha
drivers/staging/android/ion/ion.c checkpatch produces alignment checks.
This patch is whitespace only and fixes these checks.
Signed-off-by: Tobin C Harding
---
drivers/staging/android/ion/ion.c | 64 +++
1 file changed, 32 insertions(+), 32 deletions(-)
dif
drivers/staging/android/ion/ion.c calls BUG_ON in places where WARN_ON will
suffice.
This patch replaces two such occurences. Two other occurences remain.
Signed-off-by: Tobin C Harding
---
Changing the remaining two BUG_ON's causes changes to the programm logic.
This is my first patch set to
drivers/staging/android/ion/ion.c checkpatch produces
'Comparison to NULL could be written ...' checks.
This patch replaces comparison to NULL with !var as suggested by checkpatch.
Signed-off-by: Tobin C Harding
---
drivers/staging/android/ion/ion.c | 6 +++---
1 file changed, 3 insertions(+),
drivers/staging/android/ion/ion.c checkpatch produces line over 80
character warnings.
This patch is whitespace only and fixes these warnings.
Signed-off-by: Tobin C Harding
---
drivers/staging/android/ion/ion.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/s
On 04/13/16 19:13, Theodore Ts'o wrote:
>
> One other reason to suggest using a /proc file is that you're not at
> the mercy of the glibc folks to wire up a new system call. (Glibc has
> been refusing to wire up getrandom(2), for example. G.)
>
This brings right back up the libinux id
On Thu, 2016-04-14 at 10:48 -0700, Andy Lutomirski wrote:
> On Thu, Apr 14, 2016 at 10:22 AM, Ben Hutchings wrote:
> >
> > I'm updating my x32-as-boot-time-option patch for 4.6, and I noticed a
> > subtle change in system call number masking on x86_64 as a result of
> > moving the slow path into
We've always masked off the top 32 bits when x32 is enabled, but
hopefully no-one relies on that. Now that the slow path is in C, we
check all the bits there, regardless of whether x32 is enabled. Let's
make the fast path consistent with it.
Signed-off-by: Ben Hutchings
Cc: Andy Lutomirski
---
Hello Minchan,
On (03/30/16 16:12), Minchan Kim wrote:
[..]
> @@ -1835,23 +1827,31 @@ static void __zs_compact(struct zs_pool *pool, struct
> size_class *class)
> if (!migrate_zspage(pool, class, &cc))
> break;
>
> - putbac
On Sun, Apr 17, 2016 at 05:38:24PM -0700, H. Peter Anvin wrote:
> On 04/13/16 19:13, Theodore Ts'o wrote:
> >
> > One other reason to suggest using a /proc file is that you're not at
> > the mercy of the glibc folks to wire up a new system call. (Glibc has
> > been refusing to wire up getrandom(2
On Sun, Apr 17, 2016 at 10:47:54AM -0700, K. Y. Srinivasan wrote:
>
> Greg,
>
> Some time back I had sent a buch of patches for
> Hyper-V drivers. Are they still in the queue or should I resend
> them.
They are still in the queue, give me this week to get through all of
them...
thanks,
greg k-
Hi Greg,
On 23.03.2016 04:52, Vladimir Zapolskiy wrote:
> Both devm_ioremap() and devm_ioremap_wc() functions return either
> a pointer to valid iomem region or NULL, check for IS_ERR() is improper
> and may result in oops on error path. Now on error -ENOMEM is returned.
>
> Fixes: 0ab163ad1ea0 (
> > Commit 'b09d6d991' removes include/linux/clk-private.h and
> > re-arranges the clock related structures contained in it in
> > different files. The documentation has not been updated
> > accordingly, thus it wasn't anymore consistent.
> >
> > Place the structures referenced by Documentation/cl
On Wed, Apr 13, 2016 at 12:56:59AM -0500, Bjorn Helgaas wrote:
> pcibios_free_irq()"
>
> Please apply these reverts to the v4.4 stable kernel.
>
> We reverted the following changes from v4.5 to fix a regression:
>
> 8affb487d4a4 ("x86/PCI: Don't alloc pcibios-irq when MSI is enabled")
> 811a
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/dsa/mv88e6xxx.c
between commit:
207afda1b503 ("net: dsa: mv88e6xxx: share the same default FDB")
from the net tree and commit:
009a2b9843bf ("net: dsa: mv88e6xxx: add number of ports to info")
from the
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/ipv4/udp.c
between commit:
d894ba18d4e4 ("soreuseport: fix ordering for mixed v4/v6 sockets")
from the net tree and commit:
ca065d0cf80f ("udp: no longer use SLAB_DESTROY_BY_RCU")
from the net-next tree.
I tr
On Sun, 17 Apr 2016, Bob Tracy wrote:
> While a "machine check" is normally indicative of an underlying hardware
> issue, the fact this is a one-time-per-boot issue has me thinking
> otherwise. I suspect a code path being traversed prior to the Oops that
> gets bypassed afterward. As previously
On Mon, 2016-04-18 at 11:31 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> net/ipv4/udp.c
>
> between commit:
>
> d894ba18d4e4 ("soreuseport: fix ordering for mixed v4/v6 sockets")
>
> from the net tree and commit:
>
> c
On 04/13/16 08:41, Colin Walters wrote:
> On Wed, Apr 13, 2016, at 08:57 AM, Richard W.M. Jones wrote:
>
>> It's not possible to read the process umask without also modifying it,
>> which is what umask(2) does. A library cannot read umask safely,
>> especially if the main program might be multith
On Sat, Apr 16, 2016 at 10:26:06PM +0200, Arnd Bergmann wrote:
> Building the imx pinctrl driver without regmap fails with multiple
> build errors like:
>
> drivers/pinctrl/freescale/pinctrl-imx.c: In function 'imx_pinctrl_probe':
> drivers/pinctrl/freescale/pinctrl-imx.c:723:9: error: variable 'c
On Mon, Apr 18, 2016 at 09:06:35AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git testing.lookups
> commit 96352435afd792d713ec91e2d5693bdcf40a6b03 ("parallel lookups machinery,
> part 2")
Very odd. All sto
Hi Yingjoe,
On Fri, 2016-04-15 at 22:42 +0800, Yingjoe Chen wrote:
> On Fri, 2016-04-15 at 10:02 +0800, James Liao wrote:
> > On Thu, 2016-04-14 at 18:56 +0800, Yingjoe Chen wrote:
> > > On Thu, 2016-04-14 at 16:16 +0800, James Liao wrote:
> > > > From: Shunli Wang
> > > >
> > > > Add power dt-b
On Sun, Apr 17, 2016 at 06:42:12PM -0700, H. Peter Anvin wrote:
> On 04/13/16 08:41, Colin Walters wrote:
> > On Wed, Apr 13, 2016, at 08:57 AM, Richard W.M. Jones wrote:
> >
> >> It's not possible to read the process umask without also modifying it,
> >> which is what umask(2) does. A library ca
On Fri, Apr 15, 2016 at 06:00:53PM -0700, Stephen Boyd wrote:
> On 01/29, Stefan Agner wrote:
> > If a clock gets enabled early during boot time, it can lead to a PLL
> > startup. The wait_lock function makes sure that the PLL is really
> > stareted up before it gets used. However, the function sle
Hi Peterz,
2016-04-05 3:23 GMT+08:00 Peter Zijlstra :
>
>
> On 4 April 2016 21:12:23 CEST, Rik van Riel wrote:
>
>>What is the difference between cfs_rq->h_nr_running,
>>and rq->cfs.nr_running?
>>
>>Why do we have two?
>
>
> H is for hierarchy. That counts the total of runnable tasks in the entire
On Wed, Apr 13, 2016 at 08:39:32PM +, Stuart Yoder wrote:
> > > @@ -265,6 +265,93 @@
> > > compatible = "fsl,qoriq-mc";
> > > reg = <0x0008 0x0c00 0 0x40>,/* MC portal
> > > base */
> > > <0x 0x0834 0 0x4>;
On 04/17/16 18:09, Greg KH wrote:
>>
>> There aren't a *lot* of such system calls, but even in that thread the
>> "oh, only two applications need this, let them use syscall(3)" seems to
>> remain.
>
> And only 2 applications will continue to use it because no one wants to
> write syscall() wrapper
Al Viro writes:
> On Mon, Apr 18, 2016 at 09:06:35AM +0800, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git testing.lookups
>> commit 96352435afd792d713ec91e2d5693bdcf40a6b03 ("parallel lookups
>> machinery, par
On Mon, Apr 18, 2016 at 10:09:25AM +0900, Greg KH wrote:
> On Sun, Apr 17, 2016 at 05:38:24PM -0700, H. Peter Anvin wrote:
> > On 04/13/16 19:13, Theodore Ts'o wrote:
> > >
> > > One other reason to suggest using a /proc file is that you're not at
> > > the mercy of the glibc folks to wire up a ne
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Sunday, April 17, 2016 6:10 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com
> Subject
On Mon, Apr 18, 2016 at 10:08:37AM +0800, Huang, Ying wrote:
> Could you provide a debug branch in your tree for that?
Done - vfs.git#T1 and vfs.git#T2 resp.
How reproducible it is and how certain you are that it's not there on
the parent commit?
On 04/17/16 19:12, Josh Triplett wrote:
>>
>> I really like the 'libinux' idea, did anyone every hack up a first-pass
>> at this? And I'm guessing we have more syscalls now that would need to
>> be added (like getrandom(), but that shouldn't be too difficult.
>
> Personally, I'd suggest that libi
On Thu, Apr 14, 2016 at 11:12:06AM -0500, Rob Herring wrote:
> On Wed, Apr 13, 2016 at 06:08:26PM +0800, Yuan Yao wrote:
> > From: Yuan Yao
> >
> > new compatible string: "fsl,ls1043a-qspi".
> >
> > Signed-off-by: Yuan Yao
> > ---
> > Documentation/devicetree/bindings/mtd/fsl-quadspi.txt | 3 +
101 - 200 of 619 matches
Mail list logo
