The patch
ASoC: wm_adsp: factor out getting region name from type
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
Since commit 87a18a6a5652 ("mmc: mmc: Use ->card_busy() to detect busy
cards in __mmc_switch()") the ESDHC driver is broken:
mmc0: Card stuck in programming state! __mmc_switch
mmc0: error -110 whilst initialising MMC card
Since this commit __mmc_switch() uses ->card_busy(), which is
sdhci_car
On Fri, 11 Nov 2016 08:50:56 -0700
Alex Williamson wrote:
> On Fri, 11 Nov 2016 12:19:44 +0100
> Joerg Roedel wrote:
>
> > On Thu, Nov 10, 2016 at 10:46:01AM -0700, Alex Williamson wrote:
> > > In the case of x86, we know that DMA mappings overlapping the MSI
> > > doorbells won't be translat
On Fri, Nov 11, 2016 at 12:29:10PM +0100, Peter Rosin wrote:
> When this driver masters BCLK and/or LRCLK, and noone has stated
> differently, assume that all the bits of a frame are used.
>
> This relieves the cpu dai users from the duty to fill in the dividers for
> the common case.
This looks
Hi Eva,
[auto build test WARNING on iio/togreg]
[also build test WARNING on next-2016]
[cannot apply to v4.9-rc4]
[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/commits/Eva-Rachel-Retuya/staging
This old mail came up in a discussion today so let me comment on this:
On 04/27/2016 09:12 PM, Javier Martinez Canillas wrote:
> Hello Laurent,
>
> Thanks a lot for your feedback.
>
> On 04/27/2016 10:29 AM, Laurent Pinchart wrote:
>> Hi Javier,
>>
>> Thank you for the patch.
>>
>> On Tuesday 12
Hi Stephen,
Thanks for the comments!
On 11/10/2016 11:43 PM, Stephen Boyd wrote:
> On 11/07, Stanimir Varbanov wrote:
>> diff --git a/drivers/media/platform/qcom/venus/core.c
>> b/drivers/media/platform/qcom/venus/core.c
>> new file mode 100644
>> index ..7b14b1f12e20
>> --- /dev/nul
On Wed, 2016-11-09 at 18:36 -0600, Tom Lendacky wrote:
> Boot data (such as EFI related data) is not encrypted when the system
> is booted and needs to be accessed unencrypted. Add support to apply
> the proper attributes to the EFI page tables and to the
> early_memremap and memremap APIs to iden
[adding Kevin as cc since he was interested in this feature as well]
Hello Hans,
On 11/11/2016 01:11 PM, Hans Verkuil wrote:
> This old mail came up in a discussion today so let me comment on this:
>
Thanks a lot for the feedback.
> On 04/27/2016 09:12 PM, Javier Martinez Canillas wrote:
>> He
On 11/11/16 15:22, Joerg Roedel wrote:
> On Wed, Nov 09, 2016 at 02:19:36PM +, Lorenzo Pieralisi wrote:
>> +struct iommu_fwentry {
>> +struct list_head list;
>> +struct fwnode_handle *fwnode;
>> +const struct iommu_ops *ops;
>> +};
>
> Is there a reason the iommu_ops need to be sto
On Fri, Nov 11, 2016 at 12:28:38PM +0800, Jason Wang wrote:
>
>
> On 2016年11月11日 12:17, John Fastabend wrote:
> > On 16-11-10 07:31 PM, Michael S. Tsirkin wrote:
> > > >On Fri, Nov 11, 2016 at 10:07:44AM +0800, Jason Wang wrote:
> > > > >>
> > > > >>
> > > > >>On 2016年11月10日 00:38, Michael S. Tsi
On Fri, Nov 11, 2016 at 12:18:50PM +0800, Jason Wang wrote:
>
>
> On 2016年11月11日 11:41, Michael S. Tsirkin wrote:
> > On Fri, Nov 11, 2016 at 10:18:37AM +0800, Jason Wang wrote:
> > > >
> > > >
> > > >On 2016年11月10日 03:57, Michael S. Tsirkin wrote:
> > > > > >On Wed, Nov 09, 2016 at 03:38:32PM +0
Hi Eric,
On Fri, Nov 11, 2016 at 04:47:01PM +0100, Auger Eric wrote:
> Effectively in passthrough use case, the userspace defines the address
> space layout and maps guest RAM PA=IOVA to PAs (using
> VFIO_IOMMU_MAP_DMA). But this address space does not comprise the MSI
> IOVAs. Userspace does not
On Fri, Nov 11, 2016 at 04:42:37PM +0100, Martin Schwidefsky wrote:
> On Fri, 11 Nov 2016 10:16:22 +0100
> Heiko Carstens wrote:
> > > On Wed, Nov 02, 2016 at 03:56:26PM +, Mark Rutland wrote:
> > > > On Wed, Oct 26, 2016 at 06:43:05PM +0100, Mark Rutland wrote:
> > > > [1] git://git.kernel.o
On 11/11/2016 10:50 AM, Alex Williamson wrote:
On Fri, 11 Nov 2016 12:19:44 +0100
Joerg Roedel wrote:
On Thu, Nov 10, 2016 at 10:46:01AM -0700, Alex Williamson wrote:
In the case of x86, we know that DMA mappings overlapping the MSI
doorbells won't be translated correctly, it's not a valid ma
From: Colin Ian King
drm_get_format_name allocates memory that is not currently free'd
when printing the state. Fix this by kfree'ing the memory after
use.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/drm_atomic.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/dr
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Friday, November 11, 2016 5:23 AM
> To: Shiva Kerdel
> Cc: Stuart Yoder ; de...@driverdev.osuosl.org;
> german.riv...@freescale.com;
> gre...@linuxfoundation.org; Nipun Gupta ;
> linux-kernel@vger.kern
On Fri, Nov 11, 2016 at 04:17:37PM +, Robin Murphy wrote:
> In the original of_iommu_configure design, the thought was that an ops
> structure could be IOMMU-instance-specific (hence the later-removed
> "priv" member), so I suppose right now it is mostly a hangover from
> that. However, it's al
On 11/09/2016, 09:01 AM, Gerd Hoffmann wrote:
> On Di, 2016-11-08 at 22:37 +0200, Michael S. Tsirkin wrote:
>> On Mon, Nov 07, 2016 at 09:43:24AM +0100, Jiri Slaby wrote:
>>> Hi,
>>>
>>> I can relatively easily reproduce this bug:
>
> How?
Run dmesg -w in the qemu window (virtio_gpu) to see a lot
On Nov 11 2016, Miklos Szeredi wrote:
> On Fri, Nov 11, 2016 at 5:57 AM, Nikolaus Rath wrote:
>> On Nov 11 2016, Miklos Szeredi wrote:
>>> On Thu, Nov 10, 2016 at 11:31 PM, Nikolaus Rath wrote:
Hi Andrew,
In commit d7afaec0b564f0609e116f5 you added a new FUSE_NO_OPEN_SUPPORT
On Fri, Nov 11, 2016 at 05:42:11PM +0530, Aneesh Kumar K.V wrote:
> "Kirill A. Shutemov" writes:
>
> > On Mon, Nov 07, 2016 at 02:04:41PM +0530, Aneesh Kumar K.V wrote:
> >> @@ -2953,6 +2966,13 @@ static int do_set_pmd(struct fault_env *fe, struct
> >> page *page)
> >>ret = VM_FAULT_FALLBACK
* Rafael J. Wysocki [161110 16:06]:
> On Thu, Nov 10, 2016 at 7:49 PM, Brian Norris
> wrote:
> > On Thu, Nov 10, 2016 at 10:13:55AM -0800, Dmitry Torokhov wrote:
> >> On Thu, Nov 10, 2016 at 10:07 AM, Brian Norris
> >> wrote:
> >> > It's important that user space can figure out what device wok
On Fri, Nov 11, 2016 at 01:22:24PM +0100, Jan Kara wrote:
> On Fri 11-11-16 13:59:21, Kirill A. Shutemov wrote:
> > On Tue, Nov 08, 2016 at 11:12:45AM -0500, Johannes Weiner wrote:
> > > On Tue, Nov 08, 2016 at 10:53:52AM +0100, Jan Kara wrote:
> > > > On Mon 07-11-16 14:07:36, Johannes Weiner wrot
2016-11-11 14:55 GMT+01:00 Mauro Carvalho Chehab :
> Em Thu, 10 Nov 2016 12:15:39 +0100
> Jörg Otte escreveu:
>
>> 2016-11-10 9:40 GMT+01:00 Mauro Carvalho Chehab :
>> > Em Wed, 9 Nov 2016 11:07:35 -0800
>> > Linus Torvalds escreveu:
>> >
>> >> On Wed, Nov 9, 2016 at 3:09 AM, Jörg Otte wrote:
>>
Hi Joerg,
On 11/11/2016 17:22, Joerg Roedel wrote:
> Hi Eric,
>
> On Fri, Nov 11, 2016 at 04:47:01PM +0100, Auger Eric wrote:
>> Effectively in passthrough use case, the userspace defines the address
>> space layout and maps guest RAM PA=IOVA to PAs (using
>> VFIO_IOMMU_MAP_DMA). But this address
On Mon, Nov 07, 2016 at 04:47:38PM +0100, Maxime Ripard wrote:
> Since regulator_get returns a struct regulator pointer, it felt
> logical to try to add the list of parent regulators to it, especially
> as this structure is per-consumer, and different consumers might have
> different combinations
* Brian Norris [161110 13:30]:
> On Thu, Nov 10, 2016 at 01:49:11PM -0700, Tony Lindgren wrote:
> > * Brian Norris [161110 11:49]:
> > > On Thu, Nov 10, 2016 at 10:13:55AM -0800, Dmitry Torokhov wrote:
> > > > On Thu, Nov 10, 2016 at 10:07 AM, Brian Norris
> > > > wrote:
> > > > > It's importan
On Fri, Nov 11, 2016 at 9:15 AM, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Support DRM out-fences by creating a sync_file with a fence for each CRTC
> that sets the OUT_FENCE_PTR property.
>
> We use the out_fence pointer received in the OUT_FENCE_PTR prop to send
> the sync_file fd back
I try to choose error codes from the appropriate man
page when vfs calls into Orangefs with
whatever_operations.action... there's probably better
ways, like reading the vfs code and seeing what it
expects ...
-Mike
On Fri, Nov 11, 2016 at 11:28 AM, Nikolaus Rath wrote:
> On Nov 11 2016, Miklos S
Sachin Shukla writes:
> From: "Sachin Shukla"
>
> There is no need to call kfree() if memdup_user_nul() fails, as no memory
> was allocated and the error in the error-valued pointer should be
> returned.
Nacked-by: "Eric W. Biederman"
This is stupid, unnecesary gratituous change that makes th
On 11/10, Oleg Nesterov wrote:
>
> And the 3rd case which I didn't think about yesterday. And now I really hope
> it can explain the vmcore we have.
>
> If sysctl_sched_autogroup_enabled was enabled and then disabled, it is
> possible that the "autogrouped" process runs with ag->kref.refcount == 1,
On Wed, Nov 9, 2016 at 8:52 PM, Paul E. McKenney
wrote:
> On Wed, Nov 09, 2016 at 05:44:02PM -0800, Andy Lutomirski wrote:
>> On Wed, Nov 9, 2016 at 9:38 AM, Paul E. McKenney
>> wrote:
>>
>> Are you planning on changing rcu_nmi_enter()? It would make it easier
>> to figure out how they interact
On 11/11/2016 01:01 PM, Pavel Machek wrote:
On Thu 2016-11-10 22:34:07, Jacek Anaszewski wrote:
Hi,
On 11/10/2016 09:29 PM, Pavel Machek wrote:
On Thu 2016-11-10 10:55:37, Tony Lindgren wrote:
* Pavel Machek [161110 09:29]:
Hi!
Looks like commit 883d32ce3385 ("leds: core: Add support for
Hi, Liviu,
On 11/11/2016 10:45 PM, liviu.du...@arm.com wrote:
> On Fri, Nov 11, 2016 at 01:39:35PM +, Gabriele Paoloni wrote:
>> Hi Arnd
>>
>>> -Original Message-
>>> From: Arnd Bergmann [mailto:a...@arndb.de]
>>> Sent: 10 November 2016 16:07
>>> To: Gabriele Paoloni
>>> Cc: linux-arm
On Sun, Nov 6, 2016 at 2:39 PM, Dmitry Vyukov wrote:
> Hello,
>
> This is notes from the discussion we had at Linux Plumbers this week
> regarding providing a formal description of system calls (user API).
>
> The idea come up in the context of syzkaller, syscall fuzzer, which
> has descriptions f
On Fri, Nov 11, 2016 at 11:48:09AM -0500, Sean Paul wrote:
> On Fri, Nov 11, 2016 at 9:15 AM, Gustavo Padovan wrote:
> > +static void complete_crtc_signaling(struct drm_device *dev,
> > +struct drm_atomic_state *state,
> > +st
On Thu, Nov 10, 2016 at 8:44 AM, Arnd Bergmann wrote:
>
> Please merge these directly if you are happy with the result.
I will take this.
I do see two warnings, but they both seem to be valid and recent,
though, so I have no issues with the spurious cases.
Warning #1:
sound/soc/qcom/lpass-pl
On 11/11/2016, 04:30 PM, Josh Poimboeuf wrote:
> Does it work if you use KCFLAGS instead of EXTRA_CFLAGS?
Yes, the kernel builds with the flags now.
But objtool is unexpectedly still built by a different compiler.
I would also prefer the flags (like the warning above) to be passed even
when buil
On Friday, 2016-11-11 16:26:22 +, Colin King wrote:
> From: Colin Ian King
>
> drm_get_format_name allocates memory that is not currently free'd
> when printing the state. Fix this by kfree'ing the memory after
> use.
You are correct, but there are more cases of this, and another fix
has bee
Stephen Warren writes:
> On 10/27/2016 10:52 AM, Eric Anholt wrote:
>> From: Linus Walleij
>>
>> The idea is to give useful names to GPIO lines that an implementer
>> will be using from userspace, e.g. for maker type projects. These are
>> user-visible using tools/gpio/lsgpio.c
>
>> arch/arm/b
On Fri, Nov 11, 2016 at 12:11 PM, Daniel Vetter wrote:
> On Fri, Nov 11, 2016 at 11:48:09AM -0500, Sean Paul wrote:
>> On Fri, Nov 11, 2016 at 9:15 AM, Gustavo Padovan wrote:
>> > +static void complete_crtc_signaling(struct drm_device *dev,
>> > +struct drm_ato
On Fri, Nov 11, 2016 at 06:08:24PM +0100, Jiri Slaby wrote:
> On 11/11/2016, 04:30 PM, Josh Poimboeuf wrote:
> > Does it work if you use KCFLAGS instead of EXTRA_CFLAGS?
>
> Yes, the kernel builds with the flags now.
>
> But objtool is unexpectedly still built by a different compiler.
>
> I woul
Hi! I will open discussion about mac address and calibration data for
wl1251 wireless chip again...
Problem: Mac address & calibration data for wl1251 chip on Nokia N900
are stored on second nand partition (mtd1) in special proprietary format
which is used only for Nokia N900 (probably on N8x0
On Mon, Nov 07, 2016 at 02:01:00PM +0100, Martin Schwidefsky wrote:
> The per-cpu preempt count of x86 contains two values, the actual preempt
> count and the inverted PREEMPT_NEED_RESCHED bit. If a corrupted preempt
> count is detected the preempt_count_set function is used to reset the
> preempt
On Fri, Nov 11, 2016 at 1:41 AM, Thomas Gleixner wrote:
> On Fri, 11 Nov 2016, Peter Zijlstra wrote:
>> Well, its very hard to suggest alternatives, because there simply isn't
>> anything of content here. This patch just adds locks, and the next few
>> patches don't describe much either.
>>
>> Why
On Thu, Nov 10, 2016 at 10:05 PM, Al Viro wrote:
> Christoph's and Jan's aio fixes, fixup for generic_file_splice_read
> (removal of pointless detritus that actually breaks it when used for gfs2
> ->splice_read()) and fixup for generic_file_read_iter() interaction with
> ITER_PIPE destinat
On 11/03/2016 08:28 PM, Bjorn Andersson wrote:
On Wed 02 Nov 15:55 PDT 2016, Stephen Boyd wrote:
On 11/02, Bjorn Andersson wrote:
On Thu 27 Oct 18:54 PDT 2016, Stephen Boyd wrote:
On 10/19, Georgi Djakov wrote:
Add a driver for the A53 Clock Controller. It is a hardware block that
implement
On Nov 11 2016, Mike Marshall wrote:
> On Fri, Nov 11, 2016 at 11:28 AM, Nikolaus Rath wrote:
>> On Nov 11 2016, Miklos Szeredi wrote:
>>> On Fri, Nov 11, 2016 at 5:57 AM, Nikolaus Rath wrote:
On Nov 11 2016, Miklos Szeredi wrote:
> On Thu, Nov 10, 2016 at 11:31 PM, Nikolaus Rath wro
On Wed, 9 Nov 2016 13:41:28 +0100
Petr Mladek wrote:
> /*
> @@ -135,8 +170,8 @@ static void __printk_nmi_flush(struct irq_work *work)
> __RAW_SPIN_LOCK_INITIALIZER(read_lock);
> struct nmi_seq_buf *s = container_of(work, struct nmi_seq_buf, work);
> unsigned long flag
On Fri 2016-11-11 11:07:13, Petr Mladek wrote:
> I am going to do some more tests and will send a fix. It should
> be enough to remove the KTW_FREEZABLE flag from the
> kthread_create_worker_on_cpu() call.
Please, find below an updated patch that fixes the suspend with
kidle_inject kthreads runnin
Spotted one more thing on a cleanup path...
On Fri, Nov 11, 2016 at 11:15:59PM +0900, Gustavo Padovan wrote:
From: Gustavo Padovan
Support DRM out-fences by creating a sync_file with a fence for each CRTC
that sets the OUT_FENCE_PTR property.
We use the out_fence pointer received in the OUT_F
From: Andrea Merello
We are incorrectly defining the pwr LED, attaching it to a gpio line
that is wired to the Wi-Fi SDIO module (which fails due to this).
The actual power LED is connected to the GPIO expander, which we don't
expose currently.
Thanks-to: Eric Anholt [for clarifying we can't c
You still have to post the complete series along with this cover
letter, rather than just the cover letter by itself.
Please don't try to take short-cuts.
On Fri, Nov 11, 2016 at 6:02 AM, Baoquan He wrote:
> On 11/11/16 at 09:46pm, Baoquan He wrote:
>> Hi bnx2 experts,
>>
>> In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
>> firmware requesting code was moved from open stage to probe stage.
>> The reason is in kdump kernel har
On Wed, 9 Nov 2016 13:41:30 +0100
Petr Mladek wrote:
> The commit 4bcc595ccd80decb4245096e ("printk: reinstate KERN_CONT for
> printing continuation lines") allows to define more message headers
> for a single message. The motivation is that continuous lines might
> get mixed. Therefore it make
On Wed, 9 Nov 2016 13:41:29 +0100
Petr Mladek wrote:
> diff --git a/include/linux/printk.h b/include/linux/printk.h
> index eac1af8502bb..a0859e169bc3 100644
> --- a/include/linux/printk.h
> +++ b/include/linux/printk.h
> @@ -31,6 +31,14 @@ static inline const char *printk_skip_level(const char
This adds support for configuring max_brightness when setting up a
userspace LED device. It also requires changing the brightness value
returned from a single byte to an integer. Since the uleds driver has
not made it into the mainline kernel yet, this is not breaking userspace.
Signed-off-by: Dav
On 11/11/16 16:27, Joerg Roedel wrote:
> On Fri, Nov 11, 2016 at 04:17:37PM +, Robin Murphy wrote:
>> In the original of_iommu_configure design, the thought was that an ops
>> structure could be IOMMU-instance-specific (hence the later-removed
>> "priv" member), so I suppose right now it is mos
Hello,
when I execute
mkfs.ext4 -J device=UUID=625d871f-c278-4acb-916d-774dc78dbd8a -v -b 4096 -E
stride=$((512/4)),stripe_width=$((512/4*3)),lazy_itable_init=0 -O
inline_data,mmp -L dyn -m .01 /dev/test/big
the command hangs and the kernel (4.4.30) complains:
block drbd1: ASSERT( (unsigned)(
There was a memorable place in the Orangefs code where
the original programmer did that (pick something appropriate
from errno.h) and put in a comment about how it was a more
reasonable return code...
When Al Viro saw it, he said it was:
... stupid. Expected error value is not EOPNOTSUPP; pardon
On Wed, 9 Nov 2016 13:41:31 +0100
Petr Mladek wrote:
> The commit 4bcc595ccd80decb4245096e ("printk: reinstate KERN_CONT for
> printing continuation lines") allows to define more message headers
> for a single message. The motivation is that continuous lines might
> get mixed. Therefore it make
jfs uses nanosecond granularity for filesystem timestamps.
Only this assignment is not using nanosecond granularity.
Use current_time() to get the right granularity.
Signed-off-by: Deepa Dinamani
Acked-by: Dave Kleikamp
Reviewed-by: Arnd Bergmann
---
fs/jfs/ioctl.c | 2 +-
1 file changed, 1 in
On Fri, Nov 11, 2016 at 6:25 PM, Linus Torvalds
wrote:
> On Thu, Nov 10, 2016 at 10:05 PM, Al Viro wrote:
>> Christoph's and Jan's aio fixes, fixup for generic_file_splice_read
>> (removal of pointless detritus that actually breaks it when used for gfs2
>> ->splice_read()) and fixup for g
On 11/10/2016 08:08 PM, Ricardo Neri wrote:
> Thanks for the suggestions. Perhaps I can include these metrics in my
> V2. On th other hand, Dave Hansen gave a good argument on potential
> conflicts when, of instance running on an AMD CPU. UMIP is enabled by
> setting a bit in CR4. If that bit is no
On Fri 2016-11-11 12:28:51, Steven Rostedt wrote:
> On Wed, 9 Nov 2016 13:41:28 +0100
> Petr Mladek wrote:
>
>
> > /*
> > @@ -135,8 +170,8 @@ static void __printk_nmi_flush(struct irq_work *work)
> > __RAW_SPIN_LOCK_INITIALIZER(read_lock);
> > struct nmi_seq_buf *s = container_
On panic, all other CPUs are stopped except the one which had
hit panic. To keep console alive, we need to migrate hvcons irq
to panicked CPU.
Signed-off-by: Vijay Kumar
---
arch/sparc/include/asm/setup.h |1 +
arch/sparc/kernel/smp_64.c |6 +-
drivers/tty/serial/sunhv.c |
Documented the steps for sending break on sunhv console.
Signed-off-by: Vijay Kumar
---
Documentation/sparc/console.txt |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/Documentation/sparc/console.txt b/Documentation/sparc/console.txt
new file mode 100644
index 00
CPU needs to be marked offline before stopping it. When not marked
offline, the xcall receives HV_EWOULDBLOCK and so assumes that not all
CPUs received the message, and retries. After 1 retries, it finally
fails with fatal mondo timeout.
Signed-off-by: Vijay Kumar
---
arch/sparc/kernel/smp_6
Currently Stop-A (L1A) does not make the kernel switch to OBP on panic. This
patchset addresses this issue. Also, now we can cause a jump to OBP by sending
'break' twice from sunhv console. On bare metal, one can send a break by
typing Esc + 'B' + Sysrq (or whatever). On LDOM, press Ctrl + ] in tel
Now we can also jump to boot prom from sunhv console by sending
break twice on console for both running and panicked kernel
cases.
Signed-off-by: Vijay Kumar
---
drivers/tty/serial/sunhv.c |6 +-
kernel/panic.c |3 ++-
2 files changed, 7 insertions(+), 2 deletions(-)
dif
On Fri 2016-11-11 12:35:13, Steven Rostedt wrote:
> On Wed, 9 Nov 2016 13:41:29 +0100
> Petr Mladek wrote:
>
> > diff --git a/include/linux/printk.h b/include/linux/printk.h
> > index eac1af8502bb..a0859e169bc3 100644
> > --- a/include/linux/printk.h
> > +++ b/include/linux/printk.h
> > @@ -31,6
On 10/27/2016 10:26 AM, Eric Dumazet wrote:
> On Wed, 2016-10-26 at 11:09 +1100, Jon Maxwell wrote:
>> We recently encountered a bug where a few customers using ibmveth on the
>> same LPAR hit an issue where a TCP session hung when large receive was
>> enabled. Closer analysis revealed that the se
On Fri 2016-11-11 12:41:34, Steven Rostedt wrote:
> On Wed, 9 Nov 2016 13:41:30 +0100
> Petr Mladek wrote:
>
> > The commit 4bcc595ccd80decb4245096e ("printk: reinstate KERN_CONT for
> > printing continuation lines") allows to define more message headers
> > for a single message. The motivation
On Fri, Nov 11, 2016 at 03:53:53PM +, Gabriele Paoloni wrote:
> Hi Liviu
Hi Gabriele,
>
> > -Original Message-
> > From: liviu.du...@arm.com [mailto:liviu.du...@arm.com]
> > Sent: 11 November 2016 14:46
> > To: Gabriele Paoloni
> > Cc: Arnd Bergmann; linux-arm-ker...@lists.infradead.
On Thu, Nov 10, 2016 at 4:10 PM, Kees Cook wrote:
> On Thu, Oct 20, 2016 at 12:34 AM, Joel Fernandes wrote:
>> In preparation of not locking at all for certain buffers depending on if
>> there's contention, make locking optional depending if caller requested it.
>>
>> Signed-off-by: Joel Fernande
On Thu, Nov 10, 2016 at 4:16 PM, Joel Fernandes wrote:
> On Thu, Nov 10, 2016 at 4:13 PM, Kees Cook wrote:
>> On Thu, Oct 20, 2016 at 12:34 AM, Joel Fernandes wrote:
>>> If FTRACE_PER_CPU flag is passed to ramoops pdata, split the space into
>>> multiple zones depending on the number of CPUs.
>>
On Thu, Nov 10, 2016 at 4:21 PM, Joel Fernandes wrote:
> On Thu, Nov 10, 2016 at 4:15 PM, Kees Cook wrote:
>> On Thu, Oct 20, 2016 at 12:34 AM, Joel Fernandes wrote:
>>> In preparation for merging the per CPU buffers into one buffer when we
>>> retrieve
>>> the pstore ftrace data, we store the
=
> [1.699188] suspicious RCU usage. ]
> [1.699340] 4.9.0-rc4-next-2016 #4 Not tainted
> [1.699462] ---
> [1.699554] ./include/trace/events/irq.h:69 suspicious
> rcu_dereference_check() usage!
> [
CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe.
current_time() will be transitioned to be y2038 safe
along with vfs.
current_time() returns timestamps according to the
granularities set in the super_block.
The granularity check in ext4_current_time() to call
current_time() or CURRENT_TIME_SE
Made suggested modifications from checkpatch in reference
to: CHECK: Alignment should match open parenthesis
Signed-off-by: Walt Feasel
---
drivers/staging/speakup/i18n.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/speakup/i18n.c b/drivers/staging/speakup/
On 10/31/2016 02:16 PM, Florian Fainelli wrote:
> Hi,
>
> These two patches are against Thomas' irq/core branch as of today:
>
> 4cd13c21b207e80ddb1144c576500098f2d5f882 ("softirq: Let ksoftirqd do its job")
>
> Patches can be taken indepdently or together, your call.
Thomas, Jason, any feedbac
Made suggested modifications from checkpatch in reference
to: CHECK: Alignment should match open parenthesis
Signed-off-by: Walt Feasel
---
drivers/staging/speakup/keyhelp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/speakup/keyhelp.c
b/drivers/stagi
PCI fixes:
- Update MAINTAINERS for Intel VMD driver filename
- Update Rockchip rk3399 host bridge driver DTS and resets
- Fix ROM shadow problem that made some video device initialization fail
The following changes since commit 416379f9ebded501eda882e6af0a7aafc1866700:
PCI: designware:
On 11/11/2016 12:00 PM, Deepa Dinamani wrote:
> jfs uses nanosecond granularity for filesystem timestamps.
> Only this assignment is not using nanosecond granularity.
> Use current_time() to get the right granularity.
I had thought these were being handled as a group. I'll push this one
through th
Made suggested modifications from checkpatch in reference
to: WARNING: Block comments should align the * on each line
Signed-off-by: Walt Feasel
---
drivers/staging/speakup/i18n.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/speakup/i18n.c b/
On Thu, 10 Nov 2016, Daniel Vacek wrote:
> I believe Daniel's patches are the best thing we can do in current
> situation as the behavior now seems rather buggy and does not provide above
> mentioned expectations set when rt throttling was merged with default
> budget of 95% of CPU time. Nor if yo
On Fri, Nov 11, 2016 at 10:42 AM, Dave Kleikamp
wrote:
> On 11/11/2016 12:00 PM, Deepa Dinamani wrote:
>> jfs uses nanosecond granularity for filesystem timestamps.
>> Only this assignment is not using nanosecond granularity.
>> Use current_time() to get the right granularity.
>
> I had thought th
On Thu, Nov 10, 2016 at 06:44:45PM +0100, Sebastian Andrzej Siewior wrote:
> Initially I wanted to remove mcheck_cpu_init() from identify_cpu() and let it
> become an independent early hotplug callback. The main problem here was that
> the init on the boot CPU may happen too late
> (device_initcall
e the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Markus-Mayer/cpufreq-brcmstb-cpufreq-CPUfreq-driver-for-older-Broadcom-STB-SoCs/2016-075914
> base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> linux-next
> config: arm-allmodconfi
commit b98abe52fa8e ("Input: add common DT binding for touchscreens")
introduced common DT bindings for touchscreens [1] and a helper function to
parse the DT.
commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted /
swapped axes")
added another helper for parsing axis inversion a
While we fix the GTA04 we add proper pinmux for the
penirq gpio.
Tested on: GTA04A4 and Pyra-Handheld
Signed-off-by: H. Nikolaus Schaller
Acked-by: Tony Lindgren
---
arch/arm/boot/dts/omap3-gta04.dtsi | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git
Changes V7:
* rearranged the include files (asked for by Jonathan Cameron
)
* forward reference struct iio_dev * instead of condition in tsc2007.h (asked
for by Jonathan Cameron )
* add some Acked-by:
2016-10-27 10:44:29: Changes V6:
* iio patch (no changes elsewhere)
- tsc2007_iio: fix
CURRENT_TIME is not y2038 safe.
Replace it with ktime_get_real_ts64().
Inode time formats are already 64 bit long and
accommodates time64_t.
Signed-off-by: Deepa Dinamani
---
fs/ufs/ialloc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/ufs/ialloc.c b/fs/ufs/ialloc
On Fri, Nov 11, 2016 at 04:32:17PM +0100, Yves-Alexis Perez wrote:
> When wait_for_completion_interruptible_timeout() is called from
> _request_firmware_load() with a large timeout value (here, MAX_JIFFY_OFFSET
> because it's a an explicit call to the user helper), its return value (a
> long) will
Fix module table so that the driver is loaded if compiled
as module and requested by DT.
Signed-off-by: H. Nikolaus Schaller
---
drivers/input/touchscreen/ads7846.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/ads7846.c
b/drivers/inpu
The standard touch screen bindings [1] replace the private ti,swap-xy
with touchscreen-swaped-x-y. And for the Openpandora we use
touchscreen-size etc. to match the LCD screen size.
[1]: Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt
Tested with OpenPandora.
Signed-off-by: H
Hi Linus,
Here's a bunch of fixes for ARC for latest RC. Please pull.
Thx,
-Vineet
>
Linux 4.9-rc3 (2016-10-29 13:52:02 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git/ tags/arc-4.9-rc5
for you to fetch changes up to
this should reduce unnecessary input events.
Signed-off-by: H. Nikolaus Schaller
---
drivers/input/touchscreen/tsc2007.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/drivers/input/touchscreen/tsc2007.c
b/drivers/input/touchscreen/tsc2007.c
index c1d9593
The tsc2007 chip not only has a resistive touch screen controller but
also an external AUX adc imput which can be used for an ambient
light sensor, battery voltage monitoring or any general purpose.
Additionally it can measure the chip temperature.
This extension provides an iio interface for the
commit b98abe52fa8e ("Input: add common DT binding for touchscreens")
introduced common DT bindings for touchscreens [1] and a helper function to
parse the DT.
commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted /
swapped axes")
added another helper for parsing axis inversion a
301 - 400 of 627 matches
Mail list logo
