On 02/01/2018 07:41 PM, Farhan Ali wrote:
> The 'commit e25df1205f37 ("[S390] Kconfig: menus with depends on HAS_IOMEM.")'
> added the HAS_IOMEM dependecy for "Graphics support". This disabled the
> "Graphics support" menu for S390. But if we enable VT layer for S390,
> we would also need to enable
On 02/02/2018 08:33 AM, Sakari Ailus wrote:
+struct media_request_entity_data *
+media_request_get_entity_data(struct media_request *req,
+ struct media_entity *entity, void *fh)
>>>
>>> This makes the assumption that request data is bound to entities. Ho
Hi, Jens
Could you help to merge this patch to your tree? Thanks
On 2017年11月03日 10:29, kemi wrote:
>
>
> On 2017年10月24日 09:16, Kemi Wang wrote:
>> It's expensive to set buffer flags that are already set, because that
>> causes a costly cache line transition.
>>
>> A common case is setting the
Hi,
On 02-02-18 01:32, Chanwoo Choi wrote:
On 2018년 01월 26일 04:39, Hans de Goede wrote:
Some other drivers may be waiting for our extcon to show-up (exiting their
probe methods with -EPROBE_DEFER until we show up).
These drivers will typically get the cable state directly after getting
the ext
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4bf772b14675411a69b3c807f73006de0fe4b649
commit: 37cb11acf1f72a007a85894a6dd2ec93932bde46 RDMA/bnxt_re: Add SRQ support
for Broadcom adapters
date: 2 weeks ago
config: i386-randconfig-sb0-02021411 (attache
On Friday 02 February 2018 12:27 AM, David Lechner wrote:
> On 02/01/2018 02:01 AM, Sekhar Nori wrote:
>> On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
>>> This adds a new driver for mach-davinci PLL clocks. This is porting the
>>> code from arch/arm/mach-davinci/clock.c to the common
Hi Catalin, all
(Exclude Bamvor as his email became invalid)
This is 4.15-based kernel.
https://github.com/norov/linux/commits/ilp32-4.15
I tested it with LTP, no regressions found.
Kernel v4.15 incorporates SVE series from Dave Martin, so I updated ILP32
patches to agree with it. SVE-related c
On Fri, Feb 2, 2018 at 8:22 AM, Steffen Klassert
wrote:
> On Thu, Feb 01, 2018 at 11:30:00AM +0100, Dmitry Vyukov wrote:
>> On Thu, Feb 1, 2018 at 9:34 AM, Steffen Klassert
>>
>> Hi Steffen,
>>
>> Please see the email footer:
>>
>> > If you want to test a patch for this bug, please reply with:
>>
On Friday 02 February 2018 12:34 AM, David Lechner wrote:
> On 02/01/2018 02:58 AM, Sekhar Nori wrote:
>> On Saturday 20 January 2018 10:43 PM, David Lechner wrote:
>>> This adds platform-specific declarations for the PLL clocks on TI DA850/
>>> OMAP-L138/AM18XX SoCs.
>>>
>>> Signed-off-by: David L
On Thu, Feb 01, 2018 at 03:08:11PM -0700, Jason Gunthorpe wrote:
> On Thu, Feb 01, 2018 at 07:02:33PM +0530, Aishwarya Pant wrote:
> > Add documentation for core and hardware specific infiniband interfaces.
> > The descriptions have been collected from git commit logs, reading
> > through code and
On Thu, 01 Feb 2018, Lukas Bulwahn wrote:
> Hi Greg,
>
> On Thu, 1 Feb 2018, Greg KH wrote:
>
>> On Thu, Feb 01, 2018 at 06:33:30PM +0100, Ozan Alpay wrote:
>> > Dear Rodrigo Vivi, Ville Syrjälä,
>> >
>> > My name is Ozan Alpay, and I am a student mentored by Lukas Bulwahn. We
>> > intend to use
On Friday 02 February 2018 12:52 AM, David Lechner wrote:
>> +static const char * const da850_pll1_obsclk_parent_names[]
>> __initconst = {
>> + "oscin",
>
> Re: the issue of "ref_clk" vs. "oscin"...
>
> This is one of the places where having the otherwise unnecessary "oscin"
> clock
> really
The arbitrary 4MB minimum namespace size turns out to be too large for
some environments. Quoting Cheng-mean Liu:
In the case of emulated NVDIMM devices in the VM environment, there
are scenarios that NVDIMM device with much smaller sizes are
desired, for example, we might use a single
On Thu, Feb 01, 2018 at 07:57:42AM +0100, Ingo Molnar wrote:
>
> * Paul E. McKenney wrote:
>
> > > I believe these additional improvements (to the extent you agree with
> > > doing them!)
> > > could/should be done as add-on commits on top of this existing commit.
> >
> > Sounds good!
> >
>
On Thu, Feb 01, 2018 at 10:26:50AM -0500, Alan Stern wrote:
> On Thu, 1 Feb 2018, Andrea Parri wrote:
>
> > Ingo pointed out that:
> >
> > "The "memory model" name is overly generic, ambiguous and somewhat
> >misleading, as we usually mean the virtual memory layout/model
> >when we say
On Fri, Feb 02, 2018 at 12:46:03PM +0800, Boqun Feng wrote:
> On Wed, Jan 31, 2018 at 05:17:28PM -0800, Paul E. McKenney wrote:
> [...]
> > > - A long term question: have you considered and would it make sense to
> > > generate a
> > > memory-barriers.txt like file directly into Documentation/lo
Set rx mode before calling netif_wake_queue() when linking on to avoid
the device missing the receiving packets.
The transmission may start after calling netif_wake_queue(), and the
packets of resopnse may reach before calling rtl8152_set_rx_mode()
which let the device could receive packets. Then,
The device could only check the checksum of TCP and UDP packets. Therefore,
for the IPv4 packets excluding TCP and UDP, the check of checksum is necessary,
even though the IP checksum is correct.
Take ICMP for example, The IP checksum may be correct, but the ICMP checksum
may be wrong.
Signed-off
The two patched are used to fix rx issues.
Hayes Wang (2):
r8152: fix wrong checksum status for received IPv4 packets
r8152: set rx mode early when linking on
drivers/net/usb/r8152.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
--
2.13.6
Hey,
Since we've added support for IFLA_IF_NETNSID for RTM_{DEL,GET,SET,NEW}LINK
it is possible for userspace to send us requests with three different
properties to identify a target network namespace. This affects at least
RTM_{NEW,SET}LINK. Each of them could potentially refer to a different
net
Since we've added support for IFLA_IF_NETNSID for RTM_{DEL,GET,SET,NEW}LINK
it is possible for userspace to send us requests with three different
properties to identify a target network namespace. This affects at least
RTM_{NEW,SET}LINK. Each of them could potentially refer to a different
network n
On Wed, Jan 31, 2018 at 05:00:23PM +0200, Oleksandr Andrushchenko wrote:
> Hi, Eduardo!
>
> I am working on a frontend driver (PV DRM) and also seeing some strange
>
> things on driver unloading:
>
> xt# rmmod -f drm_xen_front.ko
> [ 3236.462497] [drm] Unregistering XEN PV vdispl
> [ 3236.485745
On Thu, Feb 01, 2018 at 03:09:41PM -0800, Paul E. McKenney wrote:
> On Thu, Feb 01, 2018 at 10:26:50AM -0500, Alan Stern wrote:
> > On Thu, 1 Feb 2018, Andrea Parri wrote:
> >
> > > Ingo pointed out that:
> > >
> > > "The "memory model" name is overly generic, ambiguous and somewhat
> > >mi
Hi,
On Thu, Feb 01, 2018 at 05:16:00PM +0200, Tuomas Tynkkynen wrote:
> Hi Maxime,
>
> On Thu, 2018-01-04 at 16:03 +0100, Maxime Ripard wrote:
> > On Fri, Dec 22, 2017 at 10:57:37PM +0200, Tuomas Tynkkynen wrote:
> > > Using the cd-inverted property is not useful when GPIOs are used as
> > > card
On Fri, Feb 2, 2018 at 7:20 AM, Al Viro wrote:
> On Fri, Feb 02, 2018 at 05:46:26AM +, Al Viro wrote:
>> On Thu, Feb 01, 2018 at 09:35:02PM -0800, Eric Biggers wrote:
>>
>> > Try starting up multiple instances of the program; that sometimes helps
>> > with
>> > these races that are hard to hi
Hi, Yury
As I left huawei few month ago. My account of linaro is invalid. You
could send to my personal email(bamv2...@gmail.com).
Sorry for inconvenience.
Regards
Bamvor
On Fri, Feb 2, 2018 at 4:16 PM, Yury Norov wrote:
> Hi Catalin, all
>
> (Exclude Bamvor as his email became invalid)
>
> T
Recent efforts led to the specification of a memory consistency model
for the Linux kernel [1], which "can (roughly speaking) be thought of
as an automated version of memory-barriers.txt" and which is (in turn)
"accompanied by extensive documentation on its use and its design".
Make sure that the
Now that a formal specification of the LKMM has become available to
the developer, some concern about how to track changes to the model
on the level of the "high-level documentation" was raised.
A first "mitigation" to this issue, suggested by Will, is to assign
maintainership (and responsibility!
alloc_contig_range() initiates compaction and eventual migration for
the purpose of either CMA or HugeTLB allocation. At present, reason
code remains the same MR_CMA for either of these cases. Lets make it
MR_CONTIG_RANGE which will appropriately reflect reason code in both
these cases.
Signed-off
On Thu, Feb 01, 2018 at 04:13:09PM +0100, Moritz Fischer wrote:
> On Thu, Feb 01, 2018 at 01:16:25PM +0800, Wu Hao wrote:
> > On Wed, Jan 31, 2018 at 08:52:36AM -0600, Alan Tull wrote:
> > > On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
> > >
> > > Hi Hao,
> > >
> > > I'm adding my "Acked-by'
Hi Morimoto-san,
Thank you for your patch.
On Thursday, 1 February 2018 09:45:36 EET Kuninori Morimoto wrote:
> From: Kuninori Morimoto
>
> panel-lvds.c is for LVDS Panel Driver,
> not R-Car Display Unit CRTCs
>
> Reported-by: Koji Matsuoka
> Signed-off-by: Kuninori Morimoto
A similar patch
On Mon, Jan 29, 2018 at 06:32:01PM -0600, Gustavo A. R. Silva wrote:
> Cast fi->interval.numerator to u64 in order to avoid a potential integer
> overflow. This variable is being used in a context that expects an
> expression of type u64.
>
> Addresses-Coverity-ID: 1324146 ("Unintentional integer
Hi Martin,
On Thu, 1 Feb 2018 09:08:05 +0100, Martin Hundebøll wrote:
> dmi_init() rightfully checks if dmi is available at all, and errors out
> if not. This leads to harmless errors being printed during boot on
> non-efi systems, even when these are booted quietly.
>
> Avoid this error-print by
Hi Gustavo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net/master]
[also build test ERROR on v4.15 next-20180202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On 02/02/18 01:36, Chris Patterson wrote:
> Works great, tested it and it fixes booting Linux v4.15 kernel for me :)
Can I add your "Tested-by:" to the patch when committing it?
Juergen
>
> Cheers!
>
> On Thu, Feb 1, 2018 at 3:17 PM, Boris Ostrovsky
> wrote:
>> On 02/01/2018 07:40 AM, Juerge
Many of the inlines in dcache.h were changed to accept
const struct pointers in commit f0d3b3ded999 ("constify dcache.c
inlined helpers where possible").
This patch allows 'const' in a couple that were added since then.
Signed-off-by: NeilBrown
---
Hi Al,
I still don't see this in your tree, d
On 01/31/2018 09:56 AM, Hugh Dickins wrote:
> On Wed, 31 Jan 2018, Anshuman Khandual wrote:
>> On 01/30/2018 08:06 PM, Michal Hocko wrote:
>>> On Tue 30-01-18 10:36:42, Anshuman Khandual wrote:
Allocation helper functions for migrate_pages() remmain scattered with
similar names making the
On Wed, 2018-01-31 at 10:02 -0600, Rob Herring wrote:
> On Wed, Jan 31, 2018 at 1:41 AM, Ryder Lee wrote:
> > A root complex usually consist of a host bridge and multiple P2P bridges,
> > and someone may express that in the form of a root node with many subnodes
> > and list all four interrupts fo
On Fri 02-02-18 14:45:18, Anshuman Khandual wrote:
> alloc_contig_range() initiates compaction and eventual migration for
> the purpose of either CMA or HugeTLB allocation. At present, reason
> code remains the same MR_CMA for either of these cases. Lets make it
> MR_CONTIG_RANGE which will appropr
Hi
On Fri, Feb 2, 2018 at 3:44 AM, Michael S. Tsirkin wrote:
> On Thu, Feb 01, 2018 at 02:03:00PM +0100, Marc-André Lureau wrote:
>> @@ -314,6 +359,37 @@ struct fw_cfg_sysfs_entry {
>> struct device *dev;
>> };
>>
>> +#ifdef CONFIG_CRASH_CORE
>> +static ssize_t write_vmcoreinfo(struct devi
On 02/02/2018 10:54 AM, Eduardo Otubo wrote:
On Wed, Jan 31, 2018 at 05:00:23PM +0200, Oleksandr Andrushchenko wrote:
Hi, Eduardo!
I am working on a frontend driver (PV DRM) and also seeing some strange
things on driver unloading:
xt# rmmod -f drm_xen_front.ko
[ 3236.462497] [drm] Unregisteri
Looks fine:
Reviewed-by: Christoph Hellwig
On Thu, Feb 01, 2018 at 02:43:28PM -0800, Linus Torvalds wrote:
> On Thu, Feb 1, 2018 at 12:45 PM, Tobin C. Harding wrote:
> >
> > It has just come to my attention that I should have pushed these changes
> > to Linux next before requesting you to pull them. Please feel free to
> > drop this reque
Existing option noverify disables both random src/dst address offset
setup and data verification. Sometimes, we need to control random
src/dst address setup and verification separately, such as disabling
random to make sure that test covers addresses in all interleaving
banks, but data verification
On Thu, Feb 01, 2018 at 04:00:36PM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> A few comments below. Besides that, looks good.
>
> > This patch adds fpga manager driver for FPGA Management Engine (FME). It
> > implements fpga_manager_ops for FPGA
> ??? I did that: either one patch per directory with the same type of change,
> or one patch per driver combining all the changes for that driver.
Do any contributors get into the mood to take another look at software updates
from my selection of change possibilities in a more constructive way?
On Fri, 2 Feb 2018, Jani Nikula wrote:
> Being brutally honest, please write shorter reports and shorter emails
> to the lists.
>
> The static analysis reports are welcome, but only when 1) we didn't
> already fix it in linux-next, or 2) it reveals an actual bug, not just a
> warning, warranting
On 01.02.2018 22:16, Radim Krčmář wrote:
> Guests on new hypersiors might set KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT
> bit when enabling async_PF, but this bit is reserved on old hypervisors,
> which results in a failure upon migration.
>
> To avoid breaking different cases, we are checking for CPUID
On Fri, Feb 02, 2018 at 10:56:36AM +0100, Lukas Bulwahn wrote:
> On Fri, 2 Feb 2018, Jani Nikula wrote:
>
> > Being brutally honest, please write shorter reports and shorter emails
> > to the lists.
> >
> > The static analysis reports are welcome, but only when 1) we didn't
> > already fix it in
On Thu, 1 Feb 2018, Mimi Zohar wrote:
> Hi James,
>
> Included in this pull request are three bug fixes, assuming the 2 FUSE
> patches are considered bugs and not new features, and a maintainer update.
> I'd appreciate your sending them to Linus for 4.16.
I'd like to see an acked-by or reviewed-
On Thu, Feb 01, 2018 at 03:09:41PM -0800, Paul E. McKenney wrote:
> On Thu, Feb 01, 2018 at 10:26:50AM -0500, Alan Stern wrote:
> > On Thu, 1 Feb 2018, Andrea Parri wrote:
> >
> > > Ingo pointed out that:
> > >
> > > "The "memory model" name is overly generic, ambiguous and somewhat
> > >mi
Il 02/02/2018 11:53, Maxime Ripard ha scritto:
Hi,
On Thu, Feb 01, 2018 at 05:17:11PM +0100, Giulio Benetti wrote:
What kernel version did you use?
Latest mainline.
I guess this patch could fix it:
http://code.bulix.org/1kitrq-268936?raw
This should prevent from modifying parent clock. Bu
Hi,
Yeah, you can add my
Acked-by: Martin Hundebøll
Thanks,
Martin
On February 2, 2018 8:00:27 AM GMT+01:00, Jean Delvare wrote:
>Hi Martin,
>
>On Thu, 1 Feb 2018 09:08:05 +0100, Martin Hundebøll wrote:
>> dmi_init() rightfully checks if dmi is available at all, and errors
>out
>> if not. Thi
Hi Linus,
Here is the pull-request for the RTC subsystem for 4.16.
Not much this cycle. I've pushed the at32ap700x removal late but it is
unlikely to cause any issue.
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are a
Hi,
On Thu, Feb 01, 2018 at 05:17:11PM +0100, Giulio Benetti wrote:
> > > > What kernel version did you use?
> > >
> > > Latest mainline.
> >
> > I guess this patch could fix it:
> > http://code.bulix.org/1kitrq-268936?raw
>
> This should prevent from modifying parent clock. But my problem was
Hi,
On 02/02/18 04:18, Daniel Jordan wrote:
On 02/01/2018 10:54 AM, Steven Whitehouse wrote:
Hi,
On 31/01/18 23:04, daniel.m.jor...@oracle.com wrote:
lru_lock, a per-node* spinlock that protects an LRU list, is one of the
hottest locks in the kernel. On some workloads on large machines,
On Thu, Feb 01, 2018 at 10:59:44PM +0100, KarimAllah Ahmed wrote:
Intel processors use MSR_IA32_ARCH_CAPABILITIES MSR to indicate RDCL_NO
(bit 0) and IBRS_ALL (bit 1). This is a read-only MSR. By default the
contents will come directly from the hardware, but user-space can still
override it.
[dw
Current implementation of mode_valid() and mode_fixup() callbacks
handle packed pixel modes improperly.
Fix it by using proper maximum clock values from the documentation.
Signed-off-by: Maciej Purski
---
Changes in v2:
- simplify is_packing_required() function
- fix uninitialized variable dete
Hi Gustavo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net/master]
[also build test ERROR on v4.15 next-20180202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Thursday, February 1, 2018 2:18:12 PM CET Srinivas Pandruvada wrote:
> On Thu, 2018-02-01 at 10:11 +0100, Peter Zijlstra wrote:
> > On Thu, Feb 01, 2018 at 08:50:28AM +0100, Rafael J. Wysocki wrote:
> > >
> > > On Wednesday, January 31, 2018 11:17:10 AM CET Peter Zijlstra
> > > wrote:
> > > >
Hi Mathieu,
On 01/02/18 09:51, Mathieu Poirier wrote:
> Introducing function partition_sched_domains_locked() by taking
> the mutex locking code out of the original function. That way
> the work done by partition_sched_domains_locked() can be reused
> without dropping the mutex lock.
>
> This pa
On Mon, Jan 29, 2018 at 01:13:32PM -0700, Shuah Khan wrote:
> On 01/28/2018 05:14 AM, Greg KH wrote:
> > On Fri, Jan 26, 2018 at 11:54:35AM -0700, Shuah Khan wrote:
> >> Upstream commit 1c9de5bf4286 ("usbip: vhci-hcd: Add USB3 SuperSpeed
> >> support")
> >
> > Hm, I think you have the wrong commit
+Knut, Fengguang
On Fri, 02 Feb 2018, Greg KH wrote:
> - If clang now builds the kernel "cleanly", yes, I want to take
> warning fixes in the stable tree. And even better yet, if you
> keep working to ensure the tree is "clean", that would be
> wonderful.
So we ca
On Fri, 2 Feb 2018, Chen Baozi wrote:
> Currently, if there is no spectre_v2= or nospectre_v2 specified in the boot
> parameter, the kernel will automatically choose mitigation by default.
> However, when selecting the auto mode, it doesn't check whether the
> retpoline has been built in the kerne
Loading IORT table from initrd is used to fix firmware IORT defects.
Moreover, it is very useful to debug SMMU node/device probe, MSI
allocation, stream id translation and IORT table from firmware. It
is also very useful to enable SMMU and devices behind SMMU before
firmware is ready.
This patch a
On Fri 2018-02-02 10:07:20, Sergey Senozhatsky wrote:
> On (02/01/18 13:00), Steven Rostedt wrote:
> > On Mon, 29 Jan 2018 11:29:18 +0900
> > Sergey Senozhatsky wrote:
> [..]
> > > If the system is in "big troubles" then what makes irq_work more
> > > possible? Local IRQs can stay disabled, just l
Hi Daniel,
I have gone through the other review comments, specially from Daniel T.. While I
share some of his concerns, I have few more of mine.
On 23-01-18, 16:34, Daniel Lezcano wrote:
> +late_initcall(cpu_cooling_init);
For example, this thing isn't going to fly nicely as you have assumed cpu
This reserved space isn't committed yet but cannot be used for allocations.
For userspace it has no difference from used space. XFS already does this.
Signed-off-by: Konstantin Khlebnikov
Fixes: 689c958cbe6b ("ext4: add project quota support")
---
fs/ext4/super.c |3 ++-
1 file changed, 2 in
On 02/02/18 10:55, SF Markus Elfring wrote:
>> ??? I did that: either one patch per directory with the same type of change,
>> or one patch per driver combining all the changes for that driver.
>
> Do any contributors get into the mood to take another look at software updates
> from my selection o
On Thu, Feb 01, 2018 at 07:37:04AM -0800, Mark Salyzyn wrote:
> In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE socket
> flag") and all the associated infrastructure changes to take advantage
> of a RCU grace period before freeing, there is a heightened
> possibility that a security
Most callers of put_cmsg() use a "sizeof(foo)" for the length argument.
But within put_cmsg(), the copy_to_user() call is made with a dynamic
length, as a result of the cmsg header calculations. This means that
hardened usercopy will examine the copy, even though it was technically
a fixed size and
On Thu, Feb 01, 2018 at 10:59:45PM +0100, KarimAllah Ahmed wrote:
[ Based on a patch from Ashok Raj ]
Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for
guests that will only mitigate Spectre V2 through IBRS+IBPB and will not
be using a retpoline+IBPB based approach.
To avo
On Fri, 2018-02-02 at 12:44 +0200, Jani Nikula wrote:
> +Knut, Fengguang
>
> On Fri, 02 Feb 2018, Greg KH wrote:
> > - If clang now builds the kernel "cleanly", yes, I want to take
> > warning fixes in the stable tree. And even better yet, if you
> > keep working to ensure the tr
On Thu, Feb 01, 2018 at 12:39:09PM -0800, Channa wrote:
> On 2018-02-01 02:44, Mark Rutland wrote:
> > On Thu, Jan 25, 2018 at 03:55:12PM -0800, Channagoud Kadabi wrote:
> > > Documentation for last level cache controller device tree bindings,
> > > client bindings usage examples.
> > >
> > > Sign
On Thu, Feb 01, 2018 at 10:59:46PM +0100, KarimAllah Ahmed wrote:
[ Based on a patch from Paolo Bonzini ]
... basically doing exactly what we do for VMX:
- Passthrough SPEC_CTRL to guests (if enabled in guest CPUID)
- Save and restore SPEC_CTRL around VMExit and VMEntry only if the guest
actu
On Thu, Feb 01, 2018 at 12:47:01PM -0800, Channa wrote:
> On 2018-02-01 02:48, Mark Rutland wrote:
> > On Thu, Jan 25, 2018 at 03:55:12PM -0800, Channagoud Kadabi wrote:
> > > Documentation for last level cache controller device tree bindings,
> > > client bindings usage examples.
> > >
> > > Sign
Hi,
On Fri, Feb 02, 2018 at 03:18:20PM +0800, Shawn Guo wrote:
> + Frank
>
> On Mon, Jan 15, 2018 at 05:07:22PM +0100, Sebastian Reichel wrote:
> > From: Peter Senna Tschudin
> >
> > Add secure-reg-access on device tree include file for Bx50 devices
> > to enable PMU and hardware counters for p
On 01/02/18 12:16, Horia Geantă wrote:
If the loop cannot exit based on value of "ret" != -EAGAIN, then it means
caam_probe() will eventually fail due to ret == -EAGAIN:
if (ret) {
dev_err(dev, "failed to instantiate RNG");
goto caam_remove;
}
For
On Thu, 2018-02-01 at 22:59 +0100, KarimAllah Ahmed wrote:
> [ Based on a patch from Ashok Raj ]
>
> Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for
> guests that will only mitigate Spectre V2 through IBRS+IBPB and will not
> be using a retpoline+IBPB based approach.
>
>
On 02/02/18 05:40, Sricharan R wrote:
Hi Robin/Vivek,
On 2/1/2018 2:23 PM, Vivek Gautam wrote:
Hi,
On 1/31/2018 6:39 PM, Robin Murphy wrote:
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runti
On Tue, Jan 30, 2018 at 03:39:58PM +0100, Michal Hocko wrote:
> On Tue 30-01-18 15:01:11, Florian Westphal wrote:
> > > From d48e950f1b04f234b57b9e34c363bdcfec10aeee Mon Sep 17 00:00:00 2001
> > > From: Michal Hocko
> > > Date: Tue, 30 Jan 2018 14:51:07 +0100
> > > Subject: [PATCH] net/netfilter/x
Hi Daniel,
On 2018/2/2 6:59, Daniel Lezcano wrote:
>
> Hi Wei Xu,
>
> I found in the MAINTAINERS file the hisilicon tree is at:
>
> https://github.com/hisilicon/linux-hisi
>
> But, (except I missed it) I didn't find any update since Nov, 2017.
>
> Is that tree maintained ?
Yes. It is still m
Hi Viresh,
One scenario is there where a kernel panic is observed in
cpufreq during suspend/resume.
pm_suspend()
suspend_devices_and_enter()
dpm_suspend_start()
dpm_prepare()
Failure in dpm_prepare() happend with following dmesg:
[ 3746.316062] PM: Device xyz not prepared for power
Since the Linux Audit project has transitioned completely over to
github, update the MAINTAINERS file and the primary audit source file to
reflect that reality.
Signed-off-by: Richard Guy Briggs
---
MAINTAINERS| 1 -
kernel/audit.c | 3 ++-
2 files changed, 2 insertions(+), 2 deletions(-)
d
On Thursday, February 1, 2018 10:11:04 AM CET Peter Zijlstra wrote:
> On Thu, Feb 01, 2018 at 08:50:28AM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, January 31, 2018 11:17:10 AM CET Peter Zijlstra wrote:
> > > On Wed, Jan 31, 2018 at 10:22:49AM +0100, Rafael J. Wysocki wrote:
> > > > On Tuesd
Commit-ID: 66f793099a636862a71c59d4a6ba91387b155e0c
Gitweb: https://git.kernel.org/tip/66f793099a636862a71c59d4a6ba91387b155e0c
Author: David Woodhouse
AuthorDate: Thu, 1 Feb 2018 11:27:20 +
Committer: Thomas Gleixner
CommitDate: Fri, 2 Feb 2018 12:28:27 +0100
x86/retpoline: Avoid
Commit-ID: 9005c6834c0ffdfe46afa76656bd9276cca864f6
Gitweb: https://git.kernel.org/tip/9005c6834c0ffdfe46afa76656bd9276cca864f6
Author: KarimAllah Ahmed
AuthorDate: Thu, 1 Feb 2018 11:27:21 +
Committer: Thomas Gleixner
CommitDate: Fri, 2 Feb 2018 12:28:27 +0100
x86/spectre: Simplif
> -Original Message-
> From: Chris Chiu [mailto:c...@endlessm.com]
> Sent: Friday, February 2, 2018 10:03 AM
> To: Hau
> Cc: nic_swsd ; net...@vger.kernel.org; Linux
> Kernel ; Linux Upstreaming Team
>
> Subject: Re: r8169 take too long to complete driver initialization
>
> On Tue, Jan
On Friday, February 2, 2018 12:41:58 PM CET Prateek Sood wrote:
> Hi Viresh,
>
> One scenario is there where a kernel panic is observed in
> cpufreq during suspend/resume.
>
> pm_suspend()
> suspend_devices_and_enter()
> dpm_suspend_start()
> dpm_prepare()
>
> Failure in dpm_prepare
On 2018/2/2 18:25, Yang Shunyong wrote:
> Loading IORT table from initrd is used to fix firmware IORT defects.
I don't think this fix "firmware defects", it just for debug purpose,
we will not use that for production purpose, right? I think above line
can be removed.
> Moreover, it is very useful
On Wednesday, January 24, 2018 9:53:14 PM CET Bo Yan wrote:
>
> On 01/23/2018 06:02 PM, Rafael J. Wysocki wrote:
> > On Tuesday, January 23, 2018 10:57:55 PM CET Bo Yan wrote:
> >> drivers/cpufreq/cpufreq.c | 4
> >> 1 file changed, 4 insertions(+)
> >>
> >> diff --git a/drivers/cpufreq/cp
On Fri, Feb 2, 2018 at 1:21 AM, Randy Dunlap wrote:
> On 02/01/2018 08:14 AM, Bartlomiej Zolnierkiewicz wrote:
>> On Monday, January 15, 2018 05:14:04 PM Arnd Bergmann wrote:
>>> Using a Kconfig 'select' statement for a user-visible symbol that other
>>> drivers depend on often causes circular dep
On Thu, Feb 1, 2018 at 4:45 PM, Andy Shevchenko
wrote:
> On Thu, Feb 1, 2018 at 9:57 AM, Rafael J. Wysocki wrote:
>> On Wed, Jan 31, 2018 at 4:43 PM, Andy Shevchenko
>> wrote:
>>> On Mon, Jan 29, 2018 at 5:02 AM, Rafael J. Wysocki
>>> wrote:
On Sun, Jan 28, 2018 at 4:04 PM, Andy Shevchenk
On 02/02/2018 12:42, Wei Xu wrote:
> Hi Daniel,
>
> On 2018/2/2 6:59, Daniel Lezcano wrote:
>>
>> Hi Wei Xu,
>>
>> I found in the MAINTAINERS file the hisilicon tree is at:
>>
>> https://github.com/hisilicon/linux-hisi
>>
>> But, (except I missed it) I didn't find any update since Nov, 2017.
>>
>>
Hi Alexandre,
On Wed, Jan 31, 2018 at 07:24:18PM +0900, Alexandre Courbot wrote:
> This is a quickly-put together revision that includes and uses Hans' work to
> use v4l2_ctrl_handler as the request state holder for V4L2 devices. Although
> minor fixes have also been applied, there are still a few
Hi Daniel,
On 2018/2/2 12:05, Daniel Lezcano wrote:
> On 02/02/2018 12:42, Wei Xu wrote:
>> Hi Daniel,
>>
>> On 2018/2/2 6:59, Daniel Lezcano wrote:
>>>
>>> Hi Wei Xu,
>>>
>>> I found in the MAINTAINERS file the hisilicon tree is at:
>>>
>>> https://github.com/hisilicon/linux-hisi
>>>
>>> But, (ex
Hey, Hanjun,
On 2018/2/2 19:54:24, "Hanjun Guo" wrote:
>On 2018/2/2 18:25, Yang Shunyong wrote:
>>Loading IORT table from initrd is used to fix firmware IORT defects.
>
>I don't think this fix "firmware defects", it just for debug purpose,
>we will not use that for production purpose, right? I t
On Thu 2018-02-01 11:46:47, Sergey Senozhatsky wrote:
> On (01/30/18 13:23), Petr Mladek wrote:
> [..]
> > > If the system is in "big troubles" then what makes irq_work more
> > > possible? Local IRQs can stay disabled, just like preemption. I
> > > guess when the troubles are really big our strate
> One last time: either post per-driver patches with all the cleanups for a
> driver
> in a single patch,
I preferred to offer source code adjustments according to specific
transformation
patterns mostly for each software module separately (also in small patch
series).
> or a per-directory pa
_minor_ is being dereferenced before it is null checked, hence there
is a potential null pointer dereference. Fix this by moving the pointer
dereference after _minor_ has been null checked.
Fixes: 024ad8df763f ("drm/msm: add a5xx specific debugfs")
Signed-off-by: Gustavo A. R. Silva
---
I wonder
1 - 100 of 975 matches
Mail list logo
