3.18-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
[ Upstream commit 7286a35e893176169b09715096a4aca557e2ccd2 ]
Fix afs_kill_pages() in two ways:
(1) If a writeback has been partially flushed, then if we try and kill the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
[ Upstream commit 6d06b0d25209c80e99c1e89700f1e09694a3766b ]
afs_write_begin() leaks a ref and a lock on a page if afs_fill_page()
fails. Fix the leak by unlocking and releasin
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Zygo Blaxell
[ Upstream commit e1699d2d7bf6e6cce3e1baff19f9dd4595a58664 ]
This is a story about 4 distinct (and very old) btrfs bugs.
Commit c8b978188c ("Btrfs: Add zlib compression support"
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Olga Kornievskaia
[ Upstream commit 033853325fe3bdc70819a8b97915bd3bca41d3af ]
Currently client doesn't respect max sizes server returns in CREATE_SESSION.
nfs4_session_set_rwsize() gets call
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit e7ede72a6d40cb3a30c087142d79381ca8a31dab ]
The current symbols__fixup_end() heuristic for the last entry in the rb
tree is suboptimal as it leads to not bein
Hi,
On 12/16/2017 05:50 AM, SF Markus Elfring wrote:
> Markus Elfring (2):
> Delete an error message for a failed memory allocation in two functions
> Improve a size determination in five functions
As I mentioned before, please keep your commit message subjects to
50 chars or less.
-Geoff
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Dionne
[ Upstream commit ab94f5d0dd6fd82e7eeca5e7c8096eaea0a0261f ]
The inode timestamps should be set from the client time
in the status received from the server, rather than the
server
This patch adds a new PCI vendor ID for Cadence.
Signed-off-by: Cyrille Pitchen
---
include/linux/pci_ids.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index ab20dc5db423..eb13e84e1fef 100644
--- a/include/linux/pci_ids.h
+++ b/include/
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: David Jeffery
commit d0709f1e66e8066c4ac6a54620ec116aa41937c0 upstream.
If a request_key() call to allocate and fill out a key attempts to insert the
key structure into a revoked keyring, the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Vlad Yasevich
[ Upstream commit 37c343b4f4e70e9dc328ab04903c0ec8d154c1a4 ]
When we notify peers of potential changes, it's also good to update
IGMP memberships. For example, during VM migra
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Chandan Rajendra
commit 9d5afec6b8bd46d6ed821aa1579634437f58ef1f upstream.
On a ppc64 machine, when mounting a fuzzed ext2 image (generated by
fsfuzzer) the following call trace is seen,
VFS:
This patch cleans drivers/Makefile up by moving the pci/endpoint and
pci/dwc entries from drivers/Makefile into drivers/pci/Makefile.
Since we don't want to introduce any dependency between CONFIG_PCI and
CONFIG_PCI_ENDPOINT, we now always execute drivers/pci/Makefile.
Hence all Makefiles in driv
Hi Ard
2017-12-18 10:40 GMT+01:00 Ard Biesheuvel :
> On 18 December 2017 at 10:17, Marcin Wojtas wrote:
>> Hi,
>>
>> This patchset introduces ACPI support in mvpp2 and mvmdio drivers.
>> First three patches introduce fwnode helpers for obtaining PHY
>> information from nodes and also MDIO fwnode
Hi Linus,
please pull a few important fixes for the parisc architecture from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-4.15-2
There are two important fixes:
- Add PCI quirks to disable built-in a serial AUX and a graphics cards from
specific GSP (manageme
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 5d9b70f7d52eb14bb37861c663bae44de9521c35 upstream.
Avoid null pointer dereference if some function is walking through the
devs array accessing members of a new virt_dev th
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: David Kozub
commit 62354454625741f0569c2cbe45b2d192f8fd258e upstream.
There is another JMS567-based USB3 UAS enclosure (152d:0578) that fails
with the following error:
[sda] tag#0 FAILED Resu
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Shuah Khan
commit be6123df1ea8f01ee2f896a16c2b7be3e4557a5a upstream.
stub_send_ret_submit() handles urb with a potential null transfer_buffer,
when it replays a packet with potential malicious
On Mon, 2017-12-18 at 12:27 -0500, J. Bruce Fields wrote:
> I'd forgotten about throughput/latency tradeoffs--but
> couldn't those in theory be managed by runtime configuration of the
> sceduler, or at least some smaller hammer than turning off preemption
> entirely?
A kernel that has all of the g
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 302ec300ef8a545a7fc7f667e5fd743b091c2eeb upstream.
Commit ecc0c469f277 ("autofs: don't fail mount for transient error") was
meant to replace an 'if' with a 'switch', but inste
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
[ Upstream commit 6e526fdff7be4f13b24f929a04c0e9ae6761291e ]
Make sure to check the number of endpoints to avoid dereferencing a
NULL-pointer or accessing memory beyond the endpo
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Torokhov
[ Upstream commit a4c2a13129f7c5bcf81704c06851601593303fd5 ]
TUXEDO BU1406 does not implement active multiplexing mode properly,
and takes around 550 ms in i8042_set_mux_mode(
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
[ Upstream commit 800a938f0bf9130c8256116649c0cc5806bfb2fd ]
If you write "-2 -3 -4" to the "versions" file, it will
notice that no versions are enabled, and nfsd_reset_versions()
i
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
[ Upstream commit 6be371b053dc86f11465cc1abce2e99bda0a0574 ]
When using the internal PHY it must be powered up when the MII is probed
or the PHY will not be detected. Since the P
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
[ Upstream commit 71328a3c321f7c14cc1edd33577717037744 ]
The location of the RBUF overflow and error counters has moved between
different version of the GENET MAC. This commi
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
[ Upstream commit 1ad3d225e5a40ca6c586989b4baaca710544c15a ]
The gap between the Tx status counters and the Rx RUNT counters is now
being added to allow correct reporting of the r
This patch documents the DT bindings for the Cadence PCIe controller
when configured in endpoint mode.
Signed-off-by: Cyrille Pitchen
---
.../devicetree/bindings/pci/cdns,cdns-pcie-ep.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit 911b79cde95c7da0ec02f48105358a36636b7a71 upstream.
If request_key() is used to find a keyring, only do the search part - don't
do the construction part if the keyring was
On Mon, 2017-12-18 at 17:56 +, Bart Van Assche wrote:
> On Mon, 2017-12-18 at 10:46 -0700, Jason Gunthorpe wrote:
> > On Sun, Dec 17, 2017 at 10:00:17PM -0800, Joe Perches wrote:
> >
> > > > Today when we run checkers we get so many warnings it is too hard to
> > > > make any sense of it.
> >
On Mon, Dec 18, 2017 at 3:54 AM, Peter Zijlstra wrote:
> On Fri, Dec 15, 2017 at 08:38:02AM -0800, Dan Williams wrote:
>
>> The motivation was that I noticed that get_user_pages_fast() was doing
>> a full pud_access_permitted() check, but the get_user_pages() slow
>> path was only doing a pud_writ
Johan Hovold writes:
>> +static const struct option_blacklist_info yuga_clm920_nc5_blacklist = {
>> +.reserved = BIT(0) | BIT(1) | BIT(4),
>> +};
>
> Do you really need to blacklist the first interface?
Good question. Interface #0 does look a lot like a Qualcomm DM/DIAG
function, based on tw
On Mon, 2017-12-18 at 10:10 -0800, Randy Dunlap wrote:
> On 12/18/2017 06:19 AM, Colin King wrote:
> > Here are some of the more spelling mistakes and typos that I've found
> > while fixing up spelling mistakes in kernel error message text since
> > October 2017
[]
> > diff --git a/scripts/spelling
Cc: Michal Hocko
Fixes: ("fs, elf: drop MAP_FIXED usage from elf_map")
Signed-off-by: Andrei Vagin
---
include/uapi/asm-generic/mman-common.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/uapi/asm-generic/mman-common.h
b/include/uapi/asm-generic/mman-common.h
in
On 11/06/2017 12:57 AM, Ram Pai wrote:
> Expose useful information for programs using memory protection keys.
> Provide implementation for powerpc and x86.
>
> On a powerpc system with pkeys support, here is what is shown:
>
> $ head /sys/kernel/mm/protection_keys/*
> ==> /sys/kernel/mm/protectio
On Mon, Dec 18, 2017 at 03:33:34PM +1000, Nicholas Piggin wrote:
> On Sun, 17 Dec 2017 20:58:54 -0600
> Josh Poimboeuf wrote:
>
> > On Fri, Dec 15, 2017 at 07:40:09PM +1000, Nicholas Piggin wrote:
> > > On Tue, 12 Dec 2017 08:05:01 -0600
> > > Josh Poimboeuf wrote:
> > >
> > > > On Tue, Dec 1
On Mon, Dec 18, 2017 at 09:48:37AM +0100, Zoltan Boszormenyi wrote:
> From: Böszörményi Zoltán
>
> Add a new IORESOURCE_ALLOCATED flag that is automatically used
> when alloc_resource() is used internally in kernel/resource.c
> and free_resource() now takes this flag into account.
>
> The core o
On 12/18/17 7:06 PM, Mike Galbraith wrote:
Greetings,
Kernel bound workloads seem to trigger the below for whatever reason.
I only see this when beating up NFS. There was a kworker wakeup
latency issue, but with a bandaid applied to fix that up, I can still
trigger this.
Hi,
i have seen
On 12/18, Jerome Brunet wrote:
> Nothing really prevents a provider from (trying to) register a clock
> without providing the clock ops structure.
>
> We do check the individual fields before using them, but not the
> structure pointer itself. This may have the usual nasty consequences when
> the
On Mon, 2017-12-18 at 13:36 +0100, Knut Omang wrote:
> On Mon, 2017-12-18 at 10:02 +0200, Leon Romanovsky wrote:
[]
> > Also, I agree with other reviewers, there is no excuse for adding
> > checkpatch specifics per-subsystem/folder, the differences are better
> > to be treated in checkpatch.pl itse
> > -union perf_event *perf_mmap__read_backward(struct perf_mmap *map)
> > +union perf_event *perf_mmap__read_backward(struct perf_mmap *map,
> > + u64 *start, u64 end)
> > {
> > - u64 head, end;
> > - u64 start = map->prev;
> > -
> > - /*
> > -* Ch
On Mon, Dec 18, 2017 at 09:48:38AM +0100, Zoltan Boszormenyi wrote:
> From: Böszörményi Zoltán
>
> In order to make request_*muxed_region() behave more like
> mutex_lock(), a possible failure case needs to be eliminated.
> When drivers do not properly share the same I/O region, e.g.
> one is usin
Do not check for NOT NULL before calling kfree because if the
pointer is NULL, no action occurs.
Done using the following semantic patch by coccinelle.
@@
expression ptr;
@@
- if (ptr != NULL) {
kfree(ptr);
ptr = NULL;
- }
The semantic patch has the effect of adding an assignment
of ptr to N
On 12/18/2017 09:28 AM, Scott Bauer wrote:
> This device mapper module remaps and unstripes IO so it lands
> solely on a single drive in a RAID 0/dm-stripe target.
> In a 4 drive RAID 0 the mapper exposes 1/4th of the LBA range
> as a virtual drive. Each IO to that virtual drive will land on
> only
Hello Kees,
I'm late to the party, and only just caught up with the fuss :-).
On 12/14/2017 12:19 AM, Kees Cook wrote:
> On Wed, Dec 13, 2017 at 6:40 AM, Cyril Hrubis wrote:
>> Hi!
>>> You selected stupid name for a flag. Everyone and their dog agrees
>>> with that. There's even consensus on bet
On Mon, 2017-12-18 at 20:01 +0100, Tobias Klausmann wrote:
> On 12/18/17 7:06 PM, Mike Galbraith wrote:
> > Greetings,
> >
> > Kernel bound workloads seem to trigger the below for whatever reason.
> > I only see this when beating up NFS. There was a kworker wakeup
> > latency issue, but with a b
>
> On 2017/12/7 7:33, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > Switch to non-overwrite mode if kernel doesnot support overwrite
> > ringbuffer.
> >
> > It's only effect when overwrite mode is supported.
> > No change to current behavior.
> >
> > Signed-off-by: Kan Liang
> > ---
>
> > +config DM_UN_STRIPE
> > + tristate "Transpose IO to individual drives on a raid device"
> > + depends on BLK_DEV_DM
> > + ---help---
> > + Enable this feature if you with to unstripe I/O on a RAID 0
> > + device to the respective drive. If your hardware has physical
On 12/12/2017 01:23 AM, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> -- Expand the documentation to discuss the hazards in
>enough detail to allow avoiding them.
>
> -- Mention the upcoming MAP_FIXED_SAFE flag.
>
> -- Enhance the alignment requirement slightly.
>
On Mon, Dec 18, 2017 at 11:03:51AM -0800, Joe Perches wrote:
> On Mon, 2017-12-18 at 13:36 +0100, Knut Omang wrote:
> > On Mon, 2017-12-18 at 10:02 +0200, Leon Romanovsky wrote:
> []
> > > Also, I agree with other reviewers, there is no excuse for adding
> > > checkpatch specifics per-subsystem/fol
Hi Richard,
On 11/21/2017 05:06 PM, Richard Cochran wrote:
> On Tue, Nov 21, 2017 at 09:06:37AM +0100, Arnd Bergmann wrote:
>>
>> I copied that line from clock_gettime() man page. I suppose we want to
>> fix change this in both pages, right? Any suggestions for a good way to
>> express your explan
On Tue, 19 Dec 2017 00:41:30 +0530
Shreeya Patel wrote:
> Do not check for NOT NULL before calling kfree because if the
> pointer is NULL, no action occurs.
> Done using the following semantic patch by coccinelle.
>
> @@
> expression ptr;
> @@
>
> - if (ptr != NULL) {
> kfree(ptr);
> ptr =
On 12/18/2017 12:01 AM, Andrew Lunn wrote:
> Hi Sean
>
>> It probably can't. Because before the GPIO line is manipulated to reset,
>> certain power control should be handled such as power sources from
>> external PMIC to let devices actually enter the proper state.
>>
>> So, I thought the kind of
On Mon, Dec 18, 2017 at 07:39:50PM +0100, Knut Omang wrote:
> On Mon, 2017-12-18 at 17:56 +, Bart Van Assche wrote:
> > On Mon, 2017-12-18 at 10:46 -0700, Jason Gunthorpe wrote:
> > > On Sun, Dec 17, 2017 at 10:00:17PM -0800, Joe Perches wrote:
> > >
> > > > > Today when we run checkers we get
On Mon, 2017-12-18 at 11:20 -0800, Stephen Hemminger wrote:
> On Tue, 19 Dec 2017 00:41:30 +0530
> Shreeya Patel wrote:
>
> >
> > Do not check for NOT NULL before calling kfree because if the
> > pointer is NULL, no action occurs.
> > Done using the following semantic patch by coccinelle.
> >
>
Hello Jason,
Thanks a lot for your feedback.
On 12/18/2017 06:55 PM, Jason Gunthorpe wrote:
> On Mon, Dec 18, 2017 at 01:29:01PM +0100, Javier Martinez Canillas wrote:
>> On 12/18/2017 01:22 PM, Javier Martinez Canillas wrote:
>>
>> [snip]
>>
>>>
>>> James,
>>>
>>> Can you please test the followi
Thanks; I've slightly changed it, find below. I'll queue it for the next
merge window.
---
Subject: sched: Rework / clarify prepare_lock_switch()
From: rodrigosiqueira
Date: Fri, 15 Dec 2017 12:06:03 -0200
The function prepare_lock_switch has an unused parameter, and also the
function name was
On Mon, Dec 18, 2017 at 02:23:40PM +0100, Miroslav Benes wrote:
> On Fri, 15 Dec 2017, Jason Baron wrote:
>
> > On 11/22/2017 05:29 AM, Miroslav Benes wrote:
> > > If a task sleeps in a set of patched functions uninterruptedly, it could
> > > block the whole transition indefinitely. Thus it may b
On Mon, Dec 18 2017 at 1:52pm -0500,
Scott Bauer wrote:
>
> > > +config DM_UN_STRIPE
> > > + tristate "Transpose IO to individual drives on a raid device"
> > > + depends on BLK_DEV_DM
> > > + ---help---
> > > + Enable this feature if you with to unstripe I/O on a RAID 0
> >
Hello James,
On 12/18/2017 07:26 PM, James Ettle wrote:
> The keyboard and touchpad work OK with the patch quoted below and the earlier
> two applied, i.e. the three patches with signatures:
>
> 667dcc75be864ff4c17cf58891853b7393bba3e2
> db3248e8a036c39141c8f7e9f1cf5c5ae6815f76
> 370d45a34dc8914
>-Original Message-
>From: Javier Martinez Canillas [mailto:javi...@redhat.com]
>Sent: Monday, December 18, 2017 11:30 AM
>To: Jason Gunthorpe
>Cc: Jarkko Sakkinen ; James Ettle
>; linux-integr...@vger.kernel.org; Shaikh, Azhar
>; linux-kernel@vger.kernel.org;
>james.l.mor...@oracle.com
On Mon, 2017-12-18 at 12:36 -0500, J. Bruce Fields wrote:
> On Mon, Dec 18, 2017 at 12:22:20PM -0500, Jeff Layton wrote:
> > On Mon, 2017-12-18 at 17:34 +0100, Jan Kara wrote:
> > > On Mon 18-12-17 10:11:56, Jeff Layton wrote:
> > > > static inline bool
> > > > inode_maybe_inc_iversion(struct ino
On Mon, Dec 18 2017 at 2:32pm -0500,
Mike Snitzer wrote:
> On Mon, Dec 18 2017 at 1:52pm -0500,
> Scott Bauer wrote:
>
> >
> > > > +config DM_UN_STRIPE
> > > > + tristate "Transpose IO to individual drives on a raid device"
> > > > + depends on BLK_DEV_DM
> > > > + ---help-
From: "John W. Linville"
Date: Thu, 14 Dec 2017 16:07:56 -0500
> Even without considering the ioctl problesms, the current ethtool
> API seems a bit crufty. It has been a catch-all, "where else would it
> go?" dumping ground for a long time, and it has accrued a number of
> not-entirely-related b
On 12/16/2017 6:02 PM, Knut Omang wrote:
On Sat, 2017-12-16 at 12:00 -0800, santosh.shilim...@oracle.com wrote:
On 12/16/17 10:24 AM, Joe Perches wrote:
[...]
Most of these existing messages from checkpatch should
probably be inspected and corrected where possible to
minimize the style differ
/ From: Casey Leedom
| Date: Friday, December 15, 2017 11:17 PST
|
| | From: Dmitry Torokhov
| | Sent: Friday, December 15, 2017 10:53 AM
| |
| | Hmm, can she collect output of 'udevadm monitor -p' at the time you
| | assign the adapter to the VM?
|
| Sure. I'll have Komali report on that.
On Fri, 15 Dec 2017 11:32:42 +
Mark Rutland wrote:
> Hi,
>
> On Wed, Dec 13, 2017 at 07:53:11PM +0100, Alexandre Belloni wrote:
> > The clocksource and clockevent timer are probed early in the boot process.
> > At that time it is difficult for linux to know whether a particular timer
> > can
From: Kan Liang
There is bug when mmap read event->count with large PEBS enabled.
Here is an example.
#./read_count
0x71f0
0x122c0
0x11c54
0x10001257d
0x2bdc5
The bug is caused by two issues.
- In x86_perf_event_update, the calculation of event->count does not
take th
From: Kan Liang
There is bug when mmap read event->count with large PEBS enabled.
Here is an example.
#./read_count
0x71f0
0x122c0
0x11c54
0x10001257d
0x2bdc5
There is auto-reload mechanism enabled for PEBS events in fixed period
mode. But the calculation of event->coun
From: Kan Liang
When the PEBS interrupt threshold is larger than one, there is no way to
get exact auto-reload times and value needed for event update unless
flush the PEBS buffer.
Drain the PEBS buffer in event read when large PEBS is enabled.
For the threshold is one, even auto-reload is enab
On Thu, Dec 7, 2017 at 5:38 AM, Jose Abreu wrote:
> Hi Sean,
>
> On 07-12-2017 00:00, Sean Paul wrote:
>> Welcome to version 4 of the patchset. I think we're nearing the finish line
>> (hopefully) now. This set addresses the review feedback from v3. I applied
>> some
>> R-b's from v3 review, and
From: Kan Liang
Large PEBS need to be specially handled in event count read.
Signed-off-by: Kan Liang
---
arch/x86/events/core.c | 3 +++
arch/x86/events/perf_event.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index f74e21d..c781
From: Kan Liang
There is auto-reload mechanism enabled for PEBS events in fixed period
mode. When calculating the event->count, the reload value also need to
be taken into account.
Pass the auto-reload value and times to event update.
They will be used later.
No functional change.
Signed-off-b
From: Samuel Mendoza-Jonas
Date: Fri, 15 Dec 2017 16:16:40 +1100
> The current HNCDSC handler takes the status flag from the AEN packet and
> will update or change the current channel based on this flag and the
> current channel status.
>
> However the flag from the HNCDSC packet merely represen
From: Alexander Kochetkov
Date: Fri, 15 Dec 2017 14:12:51 +0300
> Under certain conditions EMAC stop reception of incoming packets and
> continuously increment R_MISS register instead of saving data into
> provided buffer. The commit implement workaround for such situation.
> Then the stall detec
On Tue, Nov 28, 2017 at 12:33 PM, Wolfgang Rohdewald
wrote:
> @@ -913,6 +913,14 @@ static int pctv452e_frontend_attach(struct
> dvb_usb_adapter *a)
> &a->dev->i2c_adap);
> if (!a->fe_adap[0].fe)
> return -ENODEV;
> +
> +
On 17/12/2017 23:24, vcap...@pengaru.com wrote:
On Sun, Dec 17, 2017 at 05:49:44PM +, Bronek Kozicki wrote:
I just upgraded to 4.14.7 and tried to reproduce this error, this time under
strace. As you can see this happens when systemctl tries to read a specific
entry under /sys/fs . In case
Don't know how you generated the patch series, but this one should be
4/4 and not 3/4.
On Thu, 14 Dec 2017 07:03:52 +0100
Christophe JAILLET wrote:
> This include is not needed, so remove it.
>
> Signed-off-by: Christophe JAILLET
> ---
> Cross-compiled tested-only
>
> v3: new patch in the ser
On Thu, 14 Dec 2017 07:03:48 +0100
Christophe JAILLET wrote:
> The first patch converts 's3c_onenand_probe()' to devm_ functions.
> This fixes a leak in one path (line 872).
> This also free_irq which was not handled at all. ( I hope I'm correct :) )
>
> The 2nd patch is about an un-handled erro
On Thu, 14 Dec 2017 07:03:49 +0100
Christophe JAILLET wrote:
> Convert all error handling code in 's3c_onenand_probe()' to
> resource-managed alternatives in order to simplify code.
>
> This fixes a resource leak if 'platform_get_resource()' fails at line 872.
>
> The 'request_irq()' at line 97
>-Original Message-
>From: linux-integrity-ow...@vger.kernel.org [mailto:linux-integrity-
>ow...@vger.kernel.org] On Behalf Of Shaikh, Azhar
>Sent: Monday, December 18, 2017 11:34 AM
>To: Javier Martinez Canillas ; Jason Gunthorpe
>
>Cc: Jarkko Sakkinen ; James Ettle
>; linux-integr...@vg
By the way, Komali just reported another bug internally where
instantiating an SR-IOV Virtual Function causes cxgb4vf to be automatically
loaded, which is normal behavior. But then when she attempts to unload
cxgb4vf, it simply gets reloaded again. This is with:
[root@t5nic linux]# git sh
On Mon, 2017-12-18 at 11:03 -0800, Stephen Boyd wrote:
> On 12/18, Jerome Brunet wrote:
> > Nothing really prevents a provider from (trying to) register a clock
> > without providing the clock ops structure.
> >
> > We do check the individual fields before using them, but not the
> > structure poi
From: Romain Perier
Date: Fri, 15 Dec 2017 20:31:21 +0100
> From: Romain Perier
>
> The PCI pool API is deprecated. This commit replaces the PCI pool old
> API by the appropriate function with the DMA pool API.
>
> Signed-off-by: Romain Perier
> Acked-by: Peter Senna Tschudin
> Acked-by: Jef
From: Romain Perier
Date: Fri, 15 Dec 2017 20:31:22 +0100
> From: Romain Perier
>
> The PCI pool API is deprecated. This commit replaces the PCI pool old
> API by the appropriate function with the DMA pool API.
>
> Signed-off-by: Romain Perier
Acked-by: David S. Miller
On Mon, Dec 18, 2017 at 09:50:48AM +, Charles Keepax wrote:
> Is this unused?
I apologize I missed this. These were going to be mux controls for two
differential inputs. There are two inputs, but only one can be used at
a time. We have never seen anybody use the second input, so I will
remove
From: Alexey Khoroshilov
Date: Sat, 16 Dec 2017 00:52:39 +0300
> There are several error paths in xgene_mdio_probe(),
> where clk is left undisabled. The patch fixes them.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov
Applied, thank y
Hi Jerome & Stephen,
On Mon, Dec 18, 2017 at 12:06 PM, Jerome Brunet wrote:
> On Mon, 2017-12-18 at 11:03 -0800, Stephen Boyd wrote:
>> On 12/18, Jerome Brunet wrote:
>> > Nothing really prevents a provider from (trying to) register a clock
>> > without providing the clock ops structure.
>> >
>>
On Mon, Dec 18, 2017 at 08:29:30PM +0100, Javier Martinez Canillas wrote:
> My knowledge of LPC is near to non-existent so I please forgive me if I'm
> wrong,
> but my understanding is that it's the opposite of what you said.
>
> When CLKRUN_EN is SET, power management is ENABLED on the LPC bus
On Mon, Dec 18, 2017 at 07:34:29PM +, Shaikh, Azhar wrote:
> >IIUC, if CLKRUN_EN is enabled, then all the devices attached to the
> >LPC bus have to support the CLKRUN protocol. My guess is that on
> >some Braswell systems LPC power management is enabled but the TPM
> >device doesn't have CLKR
On 12/12/2017 at 17:21:19 +0100, Romain Izard wrote:
> The controller used by a flexcom module is configured at boot, and left
> alone after this. In the suspend mode called "backup with self-refresh"
> available on SAMA5D2, the chip will resume with most of its registers
> reset. In this case, we
On Mon, Dec 18, 2017 at 11:12 AM, Michael Kerrisk (man-pages)
wrote:
> Hello Kees,
>
> I'm late to the party, and only just caught up with the fuss :-).
No worries!
> On 12/14/2017 12:19 AM, Kees Cook wrote:
>> On Wed, Dec 13, 2017 at 6:40 AM, Cyril Hrubis wrote:
>>> Hi!
You selected stupi
On Mon, 18 Dec 2017 15:46:36 +0800
Ming Lei wrote:
> On Sat, Dec 9, 2017 at 7:27 AM, Michele Ballabio
> wrote:
> > On Fri, 8 Dec 2017 13:08:37 -0700
> > Jens Axboe wrote:
> >
> >> On 12/08/2017 08:38 AM, Michele Ballabio wrote:
> >> > Hi,
> >> > kernels 4.13.*, 4.14.* 4.15-rc2 crash on
On Mon, Dec 18, 2017 at 4:17 PM, Ludovic Barre wrote:
=
> +
> +/ {
> + model = "STMicroelectronics STM32MP157C eval daughter";
> + compatible = "st,stm32mp157c-ed1", "st,stm32mp157";
> +
> + chosen {
> + bootargs = "earlyprintk console=ttySTM3,115200 root=/dev/ram";
On Mon, Dec 18, 2017 at 08:46:09AM -0800, Doug Anderson wrote:
> Hi,
>
> On Mon, Dec 18, 2017 at 5:31 AM, Daniel Thompson
> wrote:
> > I think two different values on the userspace side should always map to
> > different values on the kernel side.
>
> This is what I thought originally, but I bel
Yikes! This breaks migration to/from older versions of kvm. Will you
be submitting another change to handle dynamic conversion between
formats?
On Mon, Dec 18, 2017 at 9:17 AM, Vitaly Kuznetsov wrote:
> From: Ladi Prosek
>
> Reorders existing fields and adds fields specific to Hyper-V. The layou
Update the DT parsing for the label node so that
the label is retrieved from the device child as
opposed to being part of the parent.
This will align this driver with the LED
binding documentation
Documentation/devicetree/bindings/leds/common.txt
Signed-off-by: Dan Murphy
---
v5 - no changes
Update the lp8860 label binding to the LED
standard as documented in
Documentation/devicetree/bindings/leds/common.txt
Signed-off-by: Dan Murphy
---
v5 - Renamed label to just white:backlight -
https://patchwork.kernel.org/patch/10108361
Comment was made on patch 4 https://patchwork.kernel.org
Add a default trigger optional node to the child node.
This will allow the driver to set the trigger for a backlight.
Signed-off-by: Dan Murphy
---
v5 - No changes
v4 - No changes
v3 - Removed optional and rebased - https://patchwork.kernel.org/patch/10093755/
v2 - Moved binding changes to firs
Add the ability to parse the DT and set the default
trigger mode for the LED.
Signed-off-by: Dan Murphy
---
v5 - No changes
v4 - No changes
v3 - no changes - https://patchwork.kernel.org/patch/10093751/
v2 - no changes
drivers/leds/leds-lp8860.c | 4
1 file changed, 4 insertions(+)
diff
Update the driver to conform with the LED framework.
Use devm_led_classdev_register
Destroy mutex on exit
Remove dependency on CONFIG_OF in the driver and move
to the Kconfig
Update the MODULE_LICENSE to GPL v2
Remove setting of MAX brightness as the LED framework
does this.
Signed-off-by: Dan Mur
Same thing as the other one, ll_statahead_thread should not contribute to
load.
IMO, mgc_process_log should not contribute to load in the case where it¹s
waiting for an import to recover, that¹s likely to be a pretty long wait
and doesn¹t really represent load. It¹s waiting for network recovery,
901 - 1000 of 1686 matches
Mail list logo
