xHCI compatible USB3 host controller may provide debug capability
which enables low-level system debug over USB. In order to probing
this debug capability, Linux kernel needs to map and access the
mmio of the host controller during early boot.
This patch adds permenent fixmap pages in fixed_addres
After DbC setup, debug target needs to wait until tty driver and
application (e.g. mincom) on debug taget start. Otherwise, out
messages might be ignored.
This patch adds a ping/pong mechanism between debug target and
host. Debug target will be waiting there until user presses 'Y'
or 'y' in the t
Add Documentation/usb/xhci-dbc.txt. This document includes
development status and user guide for USB3 debug port.
Signed-off-by: Lu Baolu
---
Documentation/usb/xhci-dbc.txt | 350 +
MAINTAINERS| 1 +
drivers/usb/early/xhci-dbc.c |
This patch adds interfaces for bulk out and bulk in ops. These
interfaces could be used to implement early printk bootconsole
or hook to various system debuggers.
Signed-off-by: Lu Baolu
---
drivers/usb/early/xhci-dbc.c | 373 +++
include/linux/usb/xhci-db
Hi,
This patch series adds support for early printk through USB3 debug port.
USB3 debug port is described in xHCI specification as an optional extended
capability.
Patch 1 to 9 add the driver for xHCI debug capability. It interfaces with
the register set and provides the required ops (read/write/
"printk" is not suitable for dbc debugging especially when console
is in usage. This patch adds a debug buffer in dbc driver and puts
the debug messages in this local buffer. The debug buffer could be
dumped whenever the console is not in use. This part of code will
not be visible unless DBC_DEBUG
xHCI debug capability (DbC) is an optional functionality provided
by an xHCI host controller. Software learns this capability by
walking through the extended capability list in mmio of the host.
This patch introduces the code to probe and initialize the debug
capability hardware during early boot.
On Intel platforms, if the debug target is connected with debug
host, enabling DCE bit in command register leads to a port hung
state. In the hung state, the host system will not see a port
connected status bit set. Hence debug target fails to be probed.
The state could be resolved by performing a
rol algorithm
The latest version of the test-suite contains 3000+ tests for the Linux
and can be downloaded at:
https://github.com/linux-test-project/ltp/releases/tag/20160126
The project pages as well as GIT repository are hosted on GitHub:
https://github.com/linux-test-project/ltp
http://linux-t
Hi Alexander,
Am Dienstag, 26. Januar 2016, 15:44:10 schrieb Alexander Kochetkov:
> In order to make peripherals (rom, i2s0 or spdif) accessible via cpu,
> hclk_cpubus gate must be opened. Without that all accesses (readl/writel)
> return wrong data.
The clock hierarchy does reflect the hardware
On Tue 26-01-16 07:48:12, Matthew Wilcox wrote:
> On Mon, Jan 25, 2016 at 02:59:21PM +0100, Jan Kara wrote:
> > On Mon 25-01-16 09:01:07, Dave Chinner wrote:
> > > What happens if we get rid of that DAX write fault optimisation that
> > > skips the initial read fault? The write fault will always ru
On Tuesday 26 January 2016 10:24:22 Johannes Berg wrote:
> On Tue, 2016-01-26 at 10:09 +0100, Arnd Bergmann wrote:
> > * On 32-bit architectures, you generally cannot do 64-bit atomic I/O
> > operations, and we have two implementations that do it
> > nonatomically,
> > depending on how a device
Hi,
On Tue, 2016-01-19 at 10:42 -0500, João Paulo Rechi Vita wrote:
> This series contains a few general improvements to the RFKill code,
> found while
> I was writing the rfkill-all / airplane mode LED trigger. All were
> points where
> I had to read twice or do some other kind of extra effort to
Patch 9f01cd4a91 (regulator: core: introduce function to lock
regulators and its supplies) introduces function
regulator_lock_supply(). On my kernel it causes compile-time
error:
drivers/regulator/core.c: In function ‘regulator_lock_supply’:
drivers/regulator/core.c:142:6: warning: unused variable
-handler-for-usb-uart-functionality/20160126-082429
base:
https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
for-next
config: arm-defconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O
On Thu, 2016-01-21 at 11:06 +0530, Sunil Shahu wrote:
> Remove unnecessory "if" statement and club it with previos "if"
> block.
>
Applied.
johannes
On Tue, 26 Jan 2016, Petr Mladek wrote:
> On Tue 2016-01-26 10:34:00, Jan Kara wrote:
> > On Sat 23-01-16 17:11:54, Thomas Gleixner wrote:
> > > On Sat, 23 Jan 2016, Ben Hutchings wrote:
> > > > On Fri, 2016-01-22 at 11:09 -0500, Tejun Heo wrote:
> > > > > > Looks like it requires more than trivial
-Port-Power-Controller/20160126-171717
base: git://git.infradead.org/battery-2.6.git master
coccinelle warnings: (new ones prefixed by >>)
>> drivers/power/ucs1002_power.c:203:40-49: ERROR: info -> pdata is NULL but
>> dereferenced.
vim +203 drivers/power/uc
On 01/25/2016 12:58 PM, Javier González wrote:
> When an I/O finishes, full blocks are moved from the open to the closed
> list - a lock is taken to protect the list. This happens at the moment
> in the interrupt context, which is not correct.
>
> This patch moves this logic to the GC workqueue in
Some platforms require the MSI address programmed in the PCI
device to be an IOVA and not a host physical address.
This is typically the case for ARM and PowerPC, as opposed
to x86. This patch allocates an IOVA page and maps it onto
the physical page which contains the target MSI write transaction
This patch adds a reserved iova_domain to the vfio_domain struct.
This iova domain will enable to allocate iova within the reserved
iova region.
alloc_reserved_iova_domain makes possible to allocate and initialize
this iova domain. The user will be introduced in subsequent patches.
Signed-off-by:
This series addresses KVM PCIe passthrough with MSI enabled on ARM/ARM64.
It pursues the efforts done on [1], [2], [3]. It also aims at covering the
same need on some PowerPC platforms.
On x86 all accesses to the 1MB PA region [FEE0_h - FEF0_000h] are directed
as interrupt messages: accesses t
The user is allowed to register a reserved IOVA range by using the
DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA.
It provides the base address and the size. This region is stored in the
vfio_dma rb tree. At that point the iova range is not mapped to any target
address ye
We introduce a vfio_dma type since we will need to discriminate
legacy vfio_dma's from new reserved ones. Since those latter are
not mapped at registration, some handlings must be unplugged:
removal, replay. They will be enhanced later on.
Signed-off-by: Eric Auger
---
drivers/vfio/vfio_iommu_ty
This new function enables to know whether msi write transaction
addresses must be mapped.
Signed-off-by: Eric Auger
---
drivers/vfio/vfio.c | 22 ++
drivers/vfio/vfio_iommu_type1.c | 8
include/linux/vfio.h| 2 ++
3 files changed, 32 inserti
Add a new set_group operation which allows to cache the vfio_group
handle within the vfio_pci_device struct. This is useful to do
iommu operations from the vfio_pci device.
Signed-off-by: Eric Auger
---
drivers/vfio/pci/vfio_pci.c | 8
drivers/vfio/pci/vfio_pci_private.h | 1 +
This patch introduces vfio_group_alloc_map_/unmap_free_reserved_iova
and implements corresponding vfio_iommu_type1 operations.
alloc_map allows to allocate a new reserved iova page and map it
onto the physical page that contains a given PA. It returns the iova
that is mapped onto the provided PA.
-for-Intel-Baytrail-and-Braswell/20160126-192113
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi for-next
config: arm-zeus_defconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin
This patch allows the user-space to retrieve whether msi write
transaction addresses must be mapped. This is returned through the
VFIO_IOMMU_GET_INFO API using a new flag: VFIO_IOMMU_INFO_REQUIRE_MSI_MAP.
Signed-off-by: Bharat Bhushan
Signed-off-by: Eric Auger
---
RFC v1 -> RFC v2:
- derived f
Legacy dma_list is just used to insert the reserved iova region and
check mapping of reserved iova happens in this window. As opposed to
other vfio_dma slots, the reserved one is not necessarily mapped.
We will need to track which host physical addresses are mapped to
reserved IOVA. In that prospe
Introduce new DOMAIN_ATTR_MSI_MAPPING domain attribute. If supported,
this means the MSI addresses need to be mapped in the IOMMU. ARM SMMUS
and FSL PAMU, at least expose this attribute.
x86 IOMMUs typically don't expose the attribute since on x86 MSI write
transaction addresses always are within
On Tuesday 26 January 2016 11:36:52 Mark Brown wrote:
> On Tue, Jan 26, 2016 at 10:24:22AM +0100, Johannes Berg wrote:
> > On Tue, 2016-01-26 at 10:09 +0100, Arnd Bergmann wrote:
>
> > > However, we have some freedom at the regmap-mmio level, which we can
> > > sanitize in 4.6 if we want to make i
> 26 янв. 2016 г., в 16:04, Heiko Stübner написал(а):
>
> Can you instead try to add hclk_cpubus to the critical clock list please?
Yes, adding hclk_cpubus to rk3188_critical_clocks also fixes problem.
So, I’ll send another patch now.
Thank, you.
> I was thinking about adding the patch below, but it sounds like we
> can just remove the parsing completely.
Yeah, that code looks almost identical in regmap.c.
Let me know if you want anything tested btw - it's pretty simple to
build and tftpboot a kernel now that I have the setup :)
johanne
Em Tue, Jan 26, 2016 at 02:05:20PM +0200, Adrian Hunter escreveu:
> Fix segmentation fault using:
>
> perf record -e intel_pt//u uname
>
> Back trace:
>
> 0 tracepoint_error (err=13, err@entry=-13, sys=sys@entry=0x18706c0
> "sched", name=name@entry=0x1871c70 "sched_switch", e=,
> e=)
On Tue, Jan 26, 2016 at 12:42:43PM +, Ocean HY1 He wrote:
> Hi Alan,
>
> Thanks for your comments!
>
> Lenovo SWRAID driver is a closed source driver at this time, I am afraid
> it's not possible to submit it to kernel.
So you're violating our copyright and want help for that? Be ashamed!
On 01/25/2016 08:58 AM, Herbert Xu wrote:
> On Mon, Jan 25, 2016 at 07:14:20AM -0500, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running the latest -next
>> kernel
>> I've hit:
>>
>> [ 828.386074] UBSAN: Undefined behaviour in crypto/algif_hash.c:185:7
On Tue, Jan 26, 2016 at 09:51:59PM +0900, Namhyung Kim wrote:
> On Tue, Jan 26, 2016 at 01:14:47PM +0100, Jiri Olsa wrote:
> > On Sun, Jan 24, 2016 at 10:53:23PM +0900, Namhyung Kim wrote:
> > > Hello,
> > >
> > > This patchset tries to implement percent limit to callchains which was
> > > request
On Tue, Jan 26, 2016 at 01:18:29PM +0200, Mika Westerberg wrote:
> #else /* !CONFIG_ACPI */
> static int pxa2xx_spi_get_port_id(struct acpi_device *adev)
> {
> return -1;
> }
> +#define pxa2xx_spi_fw_translate_cs NULL
I need to move this elsewhere because it is still guarded by CONFIG_
On Mon, Jan 25, 2016 at 6:52 PM, Marcelo Ricardo Leitner
wrote:
> Great. Dmitry, please give this a run. Local tests looked good but who
> knows what syzkaller may find.
Now running with this patch.
> Thanks
>
> --8<--
>
> Dmitry reported that sctp_add_bind_addr may read more bytes than
> expect
On 1/25/2016 8:28 PM, John Stultz wrote:
From: Ruchi Kandoi
This allows power/performance management software to set timer
slack for other threads according to its policy for the thread
(such as when the thread is designated foreground vs. background
activity)
Second argument is similar to PR_
> Hi Michał,
>
> [auto build test ERROR on platform-drivers-x86/for-next]
> [also build test ERROR on v4.4 next-20160122]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improving the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Micha-K-pie/C
hclk_cpubus needs to keep running because it is needed for devices like
the rom, i2s0 or spdif to be accessible via cpu. Without that all
accesses to devices (readl/writel) return wrong data. So add it
to the list of critical clocks.
Fixes: 78eaf6095cc763c ("clk: rockchip: disable unused clocks")
From: Mohamed Jamsheeth Hajanajubudeen
Change instance id of DBGU to 45.
Signed-off-by: Mohamed Jamsheeth Hajanajubudeen
Fixes: 7c661394c56c ("ARM: at91: dt: add device tree file for SAMA5D4 SoC")
Cc: sta...@vger.kernel.org # 3.18+
Signed-off-by: Nicolas Ferre
---
arch/arm/boot/dts/sama5d
On Tue 26-01-16 07:54:56, Matthew Wilcox wrote:
> On Tue, Jan 26, 2016 at 03:42:34AM +, Williams, Dan J wrote:
> > @@ -2907,7 +2912,12 @@ extern void replace_mount_options(struct super_block
> > *sb, char *options);
> >
> > static inline bool io_is_direct(struct file *filp)
> > {
> > - r
On 26/01/16 15:23, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 26, 2016 at 02:05:20PM +0200, Adrian Hunter escreveu:
>> Fix segmentation fault using:
>>
>> perf record -e intel_pt//u uname
>>
>> Back trace:
>>
>> 0 tracepoint_error (err=13, err@entry=-13, sys=sys@entry=0x18706c0
>> "sche
On 26.01.2016 11:54, Dmitriy Baranov wrote:
> Sorry, we should have added selecting this in our patch.
> The following fixes it:
>
> Subject: [PATCH] Select I2C_SLAVE for i2c-imx driver because it uses the
> generic slave interface.
>
> Signed-off-by: Dmitriy Baranov
> Signed-off-by: Maxim Syrc
Hey,
Commit ce657b1cddf1f88c56 ("component: add support for releasing match data")
causes
a general protection fault when unloading snd-hda-intel with the i915 module
loaded
on a recent skylake machine.
This breaks one of the i915 acceptance tests that performs a module
unload/reload on
snd-hd
gcc correctly warns that the printk output contains a variable that
it thinks is not initialized in some cases:
drivers/crypto/sunxi-ss/sun4i-ss-cipher.c: In function 'sun4i_ss_cipher_poll':
drivers/crypto/sunxi-ss/sun4i-ss-cipher.c:254:76: warning: 'todo' may be used
uninitialized in this functi
On Tue, Jan 26, 2016 at 09:28:23AM +0100, Ingo Molnar wrote:
>
> * Huang Rui wrote:
>
> > +/*
> > + * Acc power status counters
> > + */
> > +#define AMD_POWER_PKG_ID 0
> > +#define AMD_POWER_EVENTSEL_PKG 1
>
> > +/*
> > + * the ratio of compute unit power accumulator samp
When building the jitterentropy driver by itself, we get a link error
when CRYPTO_RNG is not enabled as well:
crypto/built-in.o: In function `jent_mod_init':
jitterentropy-kcapi.c:(.init.text+0x98): undefined reference to
`crypto_register_rng'
crypto/built-in.o: In function `jent_mod_exit':
jitte
On 1/26/2016 7:38 AM, Andy Shevchenko wrote:
> On Mon, Jan 25, 2016 at 11:29 PM, Sinan Kaya wrote:
>
> Few comments below.
>
>> Generic Event Device described in ACPI 6.1 allows platforms to handle
>> platform interrupts in ACPI ASL statements. It borrows constructs like
>> _EVT from GPIO events
Hi all,
I've added a little "heartbeat" code to my testing which simply sysrq-t every
two
minutes to get a snapshot of what's going on, which I added in hopes of tracking
down an odd lockup.
However, this sysrq call seems to produce the following quite often:
[4628498.116069] BUG: KASAN: stack-
This short series addresses a couple of shortcomings of the irqdomain
subsystem:
(1) The use of DOMAIN_BUS_ANY for looking up wired interrupts can
result in interesting situations if a given interrupt controller
implements both wired and message interrupts...
(2) Using DOMAIN_BUS_ANY for
Let's take the (outlandish) example of an interrupt controller
capable of handling both wired interrupts and PCI MSIs.
With the current code, the PCI MSI domain is going to be tagged
with DOMAIN_BUS_PCI_MSI, and the wired domain with DOMAIN_BUS_ANY.
Things get hairy when we start looking up the d
So far, when trying to associate a device with its MSI domain,
we first lookup the domain using a MSI token, and if this
doesn't return anything useful, we pick up any domain matching
the same node.
This logic is broken for two reasons:
1) Only the generic MSI code (PCI or platform) sets this toke
Hi Jung,
I'm interested in this patch series and I'll try to test on my RK3288 board.
Please, see my comments below to improve some things that helped me to
upstream some other patches, based on feedback from others
maintainers. Also I tend to use checkpatch with --strict option, it's
not a must
From: Thomas Petazzoni
The new function platform_msi_domain_{alloc,free}_irqs are meant to be
used in platform drivers, which can be built as modules. Therefore, it
makes sense to export them to be used from kernel modules.
Acked-by: Marc Zyngier
Signed-off-by: Thomas Petazzoni
---
drivers/ba
Em Tue, Jan 26, 2016 at 03:34:15PM +0200, Adrian Hunter escreveu:
> On 26/01/16 15:23, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jan 26, 2016 at 02:05:20PM +0200, Adrian Hunter escreveu:
> >> Fix segmentation fault using:
> >>
> >>perf record -e intel_pt//u uname
> >>
> >> Back trace:
> >>
>
On Tue, Jan 26, 2016 at 01:48:53PM +0100, Petr Mladek wrote:
> On Tue 2016-01-26 11:50:25, Miroslav Benes wrote:
> >
> > We still need Petr's patch from [1] to make livepatch work, right? Could
> > you, please, add it to this patch set to make it self-sufficient?
It's Petr's patch, I don't want
Geert,
Am 26.01.2016 um 12:00 schrieb Geert Uytterhoeven:
> Hi Richard,
>
> On Mon, Jan 25, 2016 at 11:24 PM, Richard Weinberger wrote:
>> Not every arch has io memory nor can this driver ever work
>> on UML/i386.
>> So, unbreak the build by fixing the dependencies.
>>
>> Signed-off-by: Richard
Hi!
> > Power consumption seems to be in 500mA range, regardless of
> > off_mode. That would mean about 2 hours of battery life, AFAICT.
>
> Sounds like you have USB connected and charging? You can
> get into just few mW range with the mainline kernel for sure
> on omap3. It's just a quetion of f
On Tue, 26 Jan 2016, John Crispin wrote:
>
>
> On 26/01/2016 09:34, Lee Jones wrote:
> > On Tue, 26 Jan 2016, John Crispin wrote:
> >> On 26/01/2016 04:07, Henry Chen wrote:
> >>> On Mon, 2016-01-25 at 19:59 +0100, John Crispin wrote:
>
> On 25/01/2016 19:44, Matthias Brugger wrote:
>
On Tue, Jan 26, 2016 at 11:50:25AM +0100, Miroslav Benes wrote:
> > + */
> > +int klp_write_module_reloc(struct module *mod, unsigned long type,
> > + unsigned long loc, unsigned long value)
> > +{
> > + /* This requires infrastructure changes; we need the loadinfos. */
> >
Hi Jung,
2016-01-26 10:30 GMT+01:00 Shawn Lin :
> Hi jun,
>
> Where is the dt-bingding documentation about your VP8 controller?
>
> And would you please share some info about rk3229? I can just find
> rk3228 in mainline, otherwise may someone think it's a misspell.
>
> Thanks.
>
>
> On 2016/1/26 1
On Tue, Jan 26, 2016 at 12:54 PM, Yan, Zheng wrote:
>
>> On Jan 26, 2016, at 19:40, Ilya Dryomov wrote:
>>
>> On Tue, Jan 26, 2016 at 12:16 PM, Yan, Zheng wrote:
>>>
On Jan 26, 2016, at 18:30, Ilya Dryomov wrote:
On Tue, Jan 26, 2016 at 10:24 AM, Dan Carpenter
wrote:
>
On Mon, 25 Jan 2016, Andrew F. Davis wrote:
> The TPS65086 PMIC contains several regulators and a GPO controller.
> Add bindings for the TPS65086 PMIC.
>
> Signed-off-by: Andrew F. Davis
> Acked-by: Rob Herring
> ---
> Documentation/devicetree/bindings/mfd/tps65086.txt | 55
>
On Mon, 25 Jan 2016, Andrew F. Davis wrote:
> Add support for the TPS65086 PMIC GPOs.
>
> TPS65086 has four configurable GPOs that can be used for several
> purposes. These are output only.
>
> Signed-off-by: Andrew F. Davis
> ---
> drivers/gpio/Kconfig | 6 ++
> drivers/gpio/Makefil
On 26/01/16 15:54, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 26, 2016 at 03:34:15PM +0200, Adrian Hunter escreveu:
>> On 26/01/16 15:23, Arnaldo Carvalho de Melo wrote:
>>> Em Tue, Jan 26, 2016 at 02:05:20PM +0200, Adrian Hunter escreveu:
Fix segmentation fault using:
perf rec
On 25/01/16 15:53, Marc Zyngier wrote:
With ARMv8.1 VHE, the architecture is able to (almost) transparently
run the kernel at EL2, despite being written for EL1.
This patch takes care of the "almost" part, mostly preventing the kernel
from dropping from EL2 to EL1, and setting up the HYP configu
On 2016/1/13 13:02, Xishi Qiu wrote:
> On 2016/1/12 19:15, Mark Rutland wrote:
>
>> On Tue, Jan 12, 2016 at 09:20:54AM +0800, Xishi Qiu wrote:
>>> On 2016/1/11 21:31, Mark Rutland wrote:
>>>
Hi,
On Mon, Jan 11, 2016 at 08:59:44PM +0800, zhong jiang wrote:
>
> http://www.spin
On Tue, Jan 26, 2016 at 08:26:41AM -0500, Sasha Levin wrote:
>
> This seems to be happening with "digest_null".
In that case this is expected as digest_null obviously has no
state. So why is a zero-length array disallowed by ubsan?
Cheers,
--
Email: Herbert Xu
Home Page: http://gondor.apana.or
do_read_cache_page and __read_cache_page duplicates page filler code
when filling the page for the first time. This patch simply removes the
duplicate logic.
Signed-off-by: Mel Gorman
Reviewed-by: Jan Kara
---
mm/filemap.c | 43 ---
1 file changed, 12 ins
In the generic read paths the kernel looks up a page in the page cache
and if it's up to date, it is used. If not, the page lock is acquired to
wait for IO to complete and then check the page. If multiple processes
are waiting on IO, they all serialise against the lock and duplicate the
checks. Th
Changelog since V1
o Use lock_page_killable consistently do_generic_file_read (jan)
A long time ago there was an attempt to merge a patch that reduced the
cost of unlock_page by avoiding the page_waitqueue lookup if there were no
waiters. It was rejected on the grounds of complexity b
The pwc driver causes a warning when CONFIG_USB_PWC_INPUT_EVDEV is unset:
drivers/media/usb/pwc/pwc-if.c: In function 'usb_pwc_probe':
drivers/media/usb/pwc/pwc-if.c:1115:1: warning: label 'err_video_unreg' defined
but not used [-Wunused-label]
Obviously, the cleanup of &pdev->vdev is not needed
The i2c client pointer is only used when CONFIG_I2C is set, and
otherwise produces a compile-time warning:
drivers/media/usb/hdpvr/hdpvr-core.c: In function 'hdpvr_probe':
drivers/media/usb/hdpvr/hdpvr-core.c:276:21: error: unused variable 'client'
[-Werror=unused-variable]
This uses the same #i
On Tue, Jan 26, 2016 at 02:27:26PM +0100, Jiri Olsa wrote:
> On Tue, Jan 26, 2016 at 09:51:59PM +0900, Namhyung Kim wrote:
> > On Tue, Jan 26, 2016 at 01:14:47PM +0100, Jiri Olsa wrote:
> > > On Sun, Jan 24, 2016 at 10:53:23PM +0900, Namhyung Kim wrote:
> > > > Hello,
> > > >
> > > > This patchset
When CONFIG_INPUT is disabled, multiple gspca backend drivers
print compile-time warnings about unused variables:
media/usb/gspca/cpia1.c: In function 'sd_stopN':
media/usb/gspca/cpia1.c:1627:13: error: unused variable 'sd'
[-Werror=unused-variable]
media/usb/gspca/konica.c: In function 'sd_stopN
If MEDIA_SUBDRV_AUTOSELECT and VIDEO_GO7007 are both set, we
automatically select VIDEO_OV7640, but that depends on MEDIA_CAMERA_SUPPORT,
so we get a Kconfig warning if that is disabled:
warning: (VIDEO_GO7007) selects VIDEO_OV7640 which has unmet direct
dependencies (MEDIA_SUPPORT && I2C && VIDE
The flexcop driver has two functions that are normally used, except
when multiple frontend drivers are disabled:
drivers/media/common/b2c2/flexcop-fe-tuner.c:42:12: warning:
'flexcop_set_voltage' defined but not used [-Wunused-function]
drivers/media/common/b2c2/flexcop-fe-tuner.c:71:12: warning:
In randconfig builds that select VIDEO_EM28XX_V4L2 and
MEDIA_SUBDRV_AUTOSELECT, but not MEDIA_CAMERA_SUPPORT, we get
a Kconfig warning:
warning: (VIDEO_EM28XX_V4L2) selects VIDEO_MT9V011 which has unmet direct
dependencies (MEDIA_SUPPORT && I2C && VIDEO_V4L2 && MEDIA_CAMERA_SUPPORT)
This avoids
em28xx selects VIDEO_TUNER, which has a dependency on MEDIA_TUNER,
so we get a Kconfig warning if that is disabled:
warning: (VIDEO_PVRUSB2 && VIDEO_USBVISION && VIDEO_GO7007 && VIDEO_AU0828_V4L2
&& VIDEO_CX231XX && VIDEO_TM6000 && VIDEO_EM28XX && VIDEO_IVTV && VIDEO_MXB &&
VIDEO_CX18 && VIDEO_C
Em Tue, Jan 26, 2016 at 05:11:28PM +0800, Wangnan (F) escreveu:
> Hi Arnaldo,
>
> We didn't make too much progress on this patchset for several weeks.
> Kernel support of bpf-output has already been merged by v4.4, but perf
> side code is still missing in v4.5. Do you have any plan on it?
Yes, I
Vladimir,
Thanks for the comment.
We are both the authors of this patch.
Could you please squash the changes (care about indentation in Kconfig also)
and resend it as v2 (probably you may want to wait for review comments some
more time)?
I suppose that after review, there will be many other thi
[ Jessica added to CC list so she is aware that there are plans to
implement livepatch on ppc64le ]
On Tue, 26 Jan 2016, Torsten Duwe wrote:
> On Tue, Jan 26, 2016 at 11:50:25AM +0100, Miroslav Benes wrote:
> > > + */
> > > +int klp_write_module_reloc(struct module *mod, unsigned long type,
> >
On Tue, Jan 26, 2016 at 02:42:16PM +0100, Maarten Lankhorst wrote:
> Commit ce657b1cddf1f88c56 ("component: add support for releasing match
> data") causes a general protection fault when unloading snd-hda-intel
> with the i915 module loaded on a recent skylake machine.
I'm no good at interpreting
Em Tue, Jan 26, 2016 at 09:08:22AM +0100, Ingo Molnar escreveu:
>
> * Arnaldo Carvalho de Melo wrote:
>
> > Em Mon, Jan 25, 2016 at 04:43:33PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Mon, Jan 25, 2016 at 07:35:11PM +0100, Ingo Molnar escreveu:
> > > >
> > > > So it appears it broke s
Am 26.01.2016 um 12:19 schrieb Srinivas Kandagatla:
>
>
> On 25/01/16 22:24, Richard Weinberger wrote:
>> Not every arch has io memory.
>> So, unbreak the build by fixing the dependencies.
>>
>> Signed-off-by: Richard Weinberger
>
> Acked-by: Srinivas Kandagatla
>
> Am happy to pick this one,
When the programming of a GITS_BASERn register fails because of
an unsupported ITS page size, we retry it with a smaller page size.
Unfortunately, we don't recompute the number of allocated ITS pages,
indicating the wrong value computed in the original allocation.
A convenient fix is to free the p
On 25/01/16 15:53, Marc Zyngier wrote:
Having both VHE and non-VHE capable CPUs in the same system
is likely to be a recipe for disaster.
diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
index b1adc51..bc7650a 100644
--- a/arch/arm64/kernel/smp.c
+++ b/arch/arm64/kernel/smp.c
@@
Op 26-01-16 om 15:15 schreef Russell King - ARM Linux:
> On Tue, Jan 26, 2016 at 02:42:16PM +0100, Maarten Lankhorst wrote:
>> Commit ce657b1cddf1f88c56 ("component: add support for releasing match
>> data") causes a general protection fault when unloading snd-hda-intel
>> with the i915 module load
On Sat, 9 Jan 2016, Piotr Sawuk wrote:
> added support for my pid so I can test the changes:
> 3 events were mapped to one, this allows discerning which is which.
> on my mouse there is a button with a 3 colour-led.
> I can now determine in user-space which colour is visible.
> this patch replaces
On 26/01/16 14:04, Suzuki K. Poulose wrote:
On 25/01/16 15:53, Marc Zyngier wrote:
With ARMv8.1 VHE, the architecture is able to (almost) transparently
run the kernel at EL2, despite being written for EL1.
This patch takes care of the "almost" part, mostly preventing the kernel
from dropping fr
Em Tue, Jan 26, 2016 at 04:00:56PM +0200, Adrian Hunter escreveu:
> On 26/01/16 15:54, Arnaldo Carvalho de Melo wrote:
> > [acme@ssdandy linux]$
> > So, this needs:
> > 1) A machine that supports Intel PT
> > 2) A kernel that supports Intel PT
> > 3) A kernel that doesn't have perf_event_attr.co
On 01/26/2016 09:07 AM, Herbert Xu wrote:
> On Tue, Jan 26, 2016 at 08:26:41AM -0500, Sasha Levin wrote:
>> >
>> > This seems to be happening with "digest_null".
> In that case this is expected as digest_null obviously has no
> state. So why is a zero-length array disallowed by ubsan?
The C spec
On 01/25/2016 5:11 PM, Guenter Roeck wrote:
>> +dev_warn(dev, "Invalid timeout (%u seconds), using default (%u
>> seconds)\n",
>> +timeout, WATCHDOG_TIMEOUT);
>
> Multi-line alignment is off by one character.
I used tabs to align the lines to 8-character boundaries
On 25/01/16 23:08, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jan 25, 2016 at 01:48:28PM -0700, Mathieu Poirier escreveu:
>> On 14 January 2016 at 14:46, Mathieu Poirier
>> wrote:
>>> On some architecture the size of the private header may
>>> be dependent on the number of tracers used in the sess
On Tue, Jan 26, 2016 at 08:33:07AM +0200, mika.pentt...@nextfour.com wrote:
> Recent changes (4.4.0+) in module loader triggered oops on ARM.
>
> The module in question is in-tree module :
> drivers/misc/ti-st/st_drv.ko
I don't see a reason for these to be applied together, they each look
like st
From: Markus Trippelsdorf
The while loop was spinning. Fix by removing a semicolon.
The issue was pointed out by gcc-6's -Wmisleading-indentation.
Signed-off-by: Markus Trippelsdorf
Reviewed-by: Matt Fleming
Acked-by: Ingo Molnar
Cc: Ben Hutchings
Cc: Peter Zijlstra
Fixes: 035827e9f2bd ("p
901 - 1000 of 1189 matches
Mail list logo
