This patch fixes the warning generated when a timeout occurs
on the request and socket is closed from a non-sleep context
by
1. Moving the socket closing on a timeout to nbd_thread_send
2. Make sock lock to be a mutex instead of a spin lock, since
nbd_xmit_timeout doesn't need to hold it anymo
When an nbd request times out then the nbd_xmit_timeout
tries to close the socket by taking a spin_lock over the
socket. This however generates a warning on
kernel_sock_shutdown. This patch fixes this issue.
Pranay Kr. Srivastava (1):
fix might_sleep warning on socket shutdown
drivers/block/n
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Tom Lendacky
> Sent: Tuesday, April 26, 2016 5:56 PM
> Subject: [RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD)
>
> This RFC patch series provides support fo
Hi All,
Using microSD card when I try to write into /dev/watchdog device
it triggers reboot of the board after timer expires.
---
root@odroidxu4l:~# echo 3 > /dev/watchdog
[ 1659.021844] watchdog: watchdog0
Hi Josh,
On Fri, 29 Apr 2016 09:03:42 -0500 Josh Poimboeuf wrote:
>
> On Fri, Apr 29, 2016 at 08:32:19AM -0500, Josh Poimboeuf wrote:
> > On Fri, Apr 29, 2016 at 04:45:43PM +1000, Stephen Rothwell wrote:
> > > Hi Andrew,
> > >
> > > After merging the akpm-current tree, today's linux-next build
Mathieu Poirier writes:
> I see two things in this work:
[trimmed 700+ lines of context that had no purpose]
> 1) A framework to deal with filters described in user space.
> 2) An implementation for address filtering that will work for both
> Intel and ARM.
>
> This will work well for address f
On 04/29/16 at 02:21P, Andrew Morton wrote:
> On Fri, 29 Apr 2016 13:47:04 +0800 Minfei Huang wrote:
>
> > It's more convenient to use existing function helper to convert string
> > "on/off" to boolean.
> >
> > ...
> >
> > --- a/lib/kstrtox.c
> > +++ b/lib/kstrtox.c
> > @@ -326,7 +326,7 @@ EXPOR
I apologize if there is some more specialized mailing list to which I
should have first directed this unreviewed patch. Please feel free to
redirect me.
The undefined behavior sanitizer ("UBSAN") on 32-bit i386 detected a
case in linux-4.6-rc5/kernel/signal/signal.c where complete_signal
called t
On Wed, Apr 27, 2016 at 6:34 AM, oulijun wrote:
> On 2016/4/26 22:25, Jiri Pirko wrote:
>> Tue, Apr 26, 2016 at 04:18:21PM CEST, l...@kernel.org wrote:
I appreciate your keen eye. this code is meant for ARM64bit therefore
should run corretly for 64-bit AARCH64.
>> The driver shoul
> Not doing it for 64-bit constants makes no sense if it just uses the
> trivial Booth's algorithm version.
AFAICT, gcc 5 *does* optimize 64-bit multiplies by constants.
Does the belief that it doesn't date back to some really old
version?
There's still a threshold where it just punts to the mult
Hi,
On Fri, Apr 29, 2016 at 5:31 PM, Peter Hurley wrote:
> On 04/29/2016 05:03 PM, Doug Anderson wrote:
>> Hi,
>>
>> On Fri, Apr 29, 2016 at 4:58 PM, Peter Hurley
>> wrote:
>>
>> On 04/29/2016 04:01 PM, Doug Anderson wrote:
>> > * serial allows numbering devices by alias.
>>
>> Whic
On Thu, Feb 18, 2016 at 09:37:26AM -0800, Kees Cook wrote:
> On Thu, Feb 18, 2016 at 6:04 AM, Geliang Tang wrote:
> > Like zlib compression in pstore, this patch added lzo and lz4
> > compression support so that users can have more options and better
> > compression ratio.
> >
> > The original cod
A bug in the CRTSCTS handling caused RTS to alternate between
CRTSCTS=0 => "RTS transmits active signal" and
CRTSCTS=1 => "RTS receives flow control"
instead of
CRTSCTS=0 => "RTS is statically active" and
CRTSCTS=1 => "RTS receives flow control"
This only happened after first having enabled CRTSCTS
The CRTSCTS flag code cleared (and inconsistently) bits unrelated to
CRTSCTS functionality. It was also harder than necessary to read.
Signed-off-by: Konstantin Shkolnyy
---
Changes in v2:
Improved CRTSCTS fix based on feedback. Dropped get_termios error handling.
drivers/usb/serial/cp210x.c |
Replaced magic numbers used in the CRTSCTS flag code with symbolic names
from the chip specification.
Signed-off-by: Konstantin Shkolnyy
---
Changes in v2:
Improved CRTSCTS fix based on feedback. Dropped get_termios error handling.
drivers/usb/serial/cp210x.c | 93 ++
Removal of ssi controller debugfs directory must
happen after the clients have been removed from
it.
Signed-off-by: Sebastian Reichel
---
drivers/hsi/controllers/omap_ssi.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/hsi/controllers/omap_ssi.c
b/drivers/hsi
Merge omap_ssi and omap_ssi_port into one module. This
fixes problems with module cycle dependencies introduced
by future patches.
Signed-off-by: Sebastian Reichel
---
drivers/hsi/controllers/Kconfig | 5 -
drivers/hsi/controllers/Makefile| 4
This adds support for frequency changes of the SSI
functional clock, which may occur due to DVFS.
Signed-off-By: Sebastian Reichel
---
drivers/hsi/controllers/omap_ssi.h | 6
drivers/hsi/controllers/omap_ssi_core.c | 63 +
drivers/hsi/controllers/omap_s
This avoids removal of the HSI port device when
only the platform port device should be removed
and clears the POPULATED bit in the DT node, so
that a new platform device is created when the
driver is probed again.
Signed-off-by: Sebastian Reichel
---
drivers/hsi/controllers/omap_ssi.c | 4
Simplify driver by switching to new gpio descriptor based API.
Signed-off-by: Sebastian Reichel
---
drivers/hsi/controllers/omap_ssi.c | 1 -
drivers/hsi/controllers/omap_ssi.h | 4 ++--
drivers/hsi/controllers/omap_ssi_port.c | 31 ++-
3 files changed, 12
device can be unbind/rebind, so probe should
stay available.
Signed-off-by: Sebastian Reichel
---
drivers/hsi/controllers/omap_ssi.c | 17 +
drivers/hsi/controllers/omap_ssi_port.c | 19 ++-
2 files changed, 19 insertions(+), 17 deletions(-)
diff --git a/dri
Hi,
The following patches add a few cleanups to the omap-ssi driver,
fix module unloading (and reloading) and merge omap-ssi and
omap-ssi-port into the same module to avoid a circular dependency
introduced by the last patch.
P.S.: The last patch has already been sent in this patchset
(https://lkm
On 2016-04-29 02:45, Dong Aisheng wrote:
> During kernel early booting(e.g. in time_init()), there's only one
> init idle task running, and the idle sched class indicates that it's
> not valid to schedule for idle task. If it happens the kernel
> will complain with a error message as follows:
> [
On Fri, 2016-04-29 at 16:51 -0700, Linus Torvalds wrote:
> There's presumably a few optimal values from a "spread bits out
> evenly" standpoint, and they won't have anything to do with random
> irrational constants, and will have everything to do with having nice
> bitpatterns.
>
> I'm adding Rik
On Fri, Apr 29, 2016 at 5:32 PM, George Spelvin wrote:
>
> Odd is important. If the multiplier is even, the msbit of the input
> doesn't affect the hash result at all.
Fair enough. My test-set was incomplete.
>> Yeah. gcc will actually do the clever stuff for the 32-bit case, afaik.
>
> It's no
I am Mr. Hirano Nobuyuki , from Japan, I will like to seek your
partnership and
mutual understanding regarding a beneficial transaction.
Reply Immediately to my email below for Details .
( hiranonobuyuki...@lycos.com )
Regards For Hirano
Sincerely,
Mr.Nobuyuki Hirano
Bank Of Tokyo-Mitsubishi U
On Mon, Apr 11, 2016 at 11:48:25AM -0500, Stuart Yoder wrote:
> From: Stuart Yoder
>
> This patch series makes further progress towards completing the fsl-mc
> TODO list.
I don't seem to have gotten patch 14/14, can you resend just that one?
thanks,
greg k-h
From: Andi Kleen
Everything the same as Skylake, just new model numbers.
Signed-off-by: Andi Kleen
---
arch/x86/events/intel/core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
index 79b59437f5ee..90ba3ae3074e 100644
--- a/ar
On Mon, Apr 18, 2016 at 10:35:28AM +1000, Tobin C Harding wrote:
> drivers/staging/android/ion/ion.c checkpatch produces alignment checks.
>
> This patch is whitespace only and fixes these checks.
>
> Signed-off-by: Tobin C Harding
> ---
> drivers/staging/android/ion/ion.c | 64
> +
On Fri, Apr 29, 2016 at 11:15:27AM +0530, Manav Batra wrote:
> Removes unnecessary parantheses around chip->sd_card
> Signed-off-by: Manav Batra
> ---
> drivers/staging/rts5208/sd.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
HTML patches do not work, sorry :(
Also, put a blan
On Thu, Apr 28, 2016 at 10:42:07PM -0700, Manav Batra wrote:
> Signed-off-by: Manav Batra
>
> Separates out assignment in one line to two lines.
signed-off-by goes at the end of the text, not at the top.
Please fix all of these and resend.
thanks,
greg k-h
On 04/29/2016 04:12 PM, Yu-cheng Yu wrote:
> On Fri, Apr 29, 2016 at 01:32:15PM -0700, Dave Hansen wrote:
>> The reason I haven't acked this patch is that I want to be _sure_ that
>> we've audited all of the call paths that access the XSAVE buffer to
>> ensure that they can all either handle the XS
On Thu, Apr 28, 2016 at 10:46:47AM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Hi,
>
> This patchset sits on top of Sync ABI Rework v13:
>
> https://www.spinics.net/lists/dri-devel/msg105667.html
>
> The first eight clean up and prepare sync_file for de-staging. The last four
> p
On 04/29/2016 03:43 PM, Yu-cheng Yu wrote:
> On Fri, Apr 29, 2016 at 01:09:07PM -0700, Dave Hansen wrote:
>> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
>>> +static int may_copy_fpregs_to_sigframe(void)
>>> +{
>>> + /*
>>> +* In signal handling path, the kernel already checks if
>>> +* FPU
> At least for my tests, even that seems to actually be a total
> non-issue. Yes, odd values *might* be better, but as mentioned in my
> crossing email, it doesn't actually seem to matter for any case the
> kernel cares about, since we tend to want to hash down to 10-20 bits
> of data, so the least
On 04/29/2016 05:03 PM, Doug Anderson wrote:
> Hi,
>
> On Fri, Apr 29, 2016 at 4:58 PM, Peter Hurley
> wrote:
>
> On 04/29/2016 04:01 PM, Doug Anderson wrote:
> > * serial allows numbering devices by alias.
>
> Which is in fact a total nightmare.
>
> While stable device order
On Fri, Apr 29, 2016 at 02:04:18PM +0200, Michal Hocko wrote:
> I would also like to revisit generic inode/dentry shrinker and see
> whether it could be more __GFP_FS friendly. As you say many FS might
> even not depend on some FS internal locks so pushing GFP_FS check down
> the layers might make
On 2016-04-12 03:15:44, Ricky Zhou wrote:
> In LSMs such as SELinux, files can be associated with state from the
> credentials of the task that opens it. Since ecryptfs shares a single
> handle to lower files across tasks that access it, others tasks can
> later be denied access to the lower file a
Hi Peter,
On Fri, Apr 22, 2016 at 11:04:27AM +0200, Peter Zijlstra wrote:
> Implement FETCH-OP atomic primitives, these are very similar to the
> existing OP-RETURN primitives we already have, except they return the
> value of the atomic variable _before_ modification.
>
> This is especially usef
On Fri, Apr 29, 2016 at 03:35:42PM +1000, NeilBrown wrote:
> On Tue, Apr 26 2016, Michal Hocko wrote:
>
> > Hi,
> > we have discussed this topic at LSF/MM this year. There was a general
> > interest in the scope GFP_NOFS allocation context among some FS
> > developers. For those who are not aware
On Apr 29, 2016 4:27 PM, "Josh Poimboeuf" wrote:
>
> On Fri, Apr 29, 2016 at 02:38:02PM -0700, Andy Lutomirski wrote:
> > On Fri, Apr 29, 2016 at 1:50 PM, Josh Poimboeuf wrote:
> > > On Fri, Apr 29, 2016 at 12:39:16PM -0700, Andy Lutomirski wrote:
> > >> On Thu, Apr 28, 2016 at 1:44 PM, Josh Poim
On Apr 29, 2016 3:11 PM, "Jiri Kosina" wrote:
>
> On Fri, 29 Apr 2016, Andy Lutomirski wrote:
>
> > > NMI, MCE and interrupts aren't a problem because they have dedicated
> > > stacks, which are easy to detect. If the tasks' stack is on an
> > > exception stack or an irq stack, we consider it unr
On Apr 29, 2016 3:41 PM, "Josh Poimboeuf" wrote:
>
> On Fri, Apr 29, 2016 at 02:37:41PM -0700, Andy Lutomirski wrote:
> > On Fri, Apr 29, 2016 at 2:25 PM, Josh Poimboeuf wrote:
> > > I think the easiest way to make it work would be to modify the idtentry
> > > macro to put all the idt entries in
On Fri, Apr 29, 2016 at 4:31 PM, George Spelvin wrote:
>
> After researching it, I think that the "high bits of a multiply" is
> in fact a decent way to do such a hash.
Our emails crossed. Yes. My test harness actually likes the
multiplication more than most of the specialized "spread out bits"
v
On 04/29/2016 04:01 PM, Doug Anderson wrote:
> * serial allows numbering devices by alias.
Which is in fact a total nightmare.
While stable device order is mandatory in serial because of
console command line parameters and existing userspace expectations,
it is the number one barrier to providing
On 04/30/2016 01:36 AM, Dmitry Torokhov wrote:
> Hi Ksenija,
Hi all,
> On Fri, Apr 29, 2016 at 01:49:11PM +0200, Ksenija Stanojevic wrote:
>> Add mxs-lradc touchscreen driver.
>>
>> Signed-off-by: Ksenija Stanojevic
>> ---
>> drivers/input/touchscreen/Kconfig| 14 +-
>> drivers/input/t
On Fri, Apr 29, 2016 at 2:10 PM, Linus Torvalds
wrote:
> On Thu, Apr 28, 2016 at 11:32 AM, Linus Torvalds
> wrote:
>>
>> hash_long/ptr really shouldn't care about the low bits being zero at
>> all, because it should mix in all the bits (using a prime multiplier
>> and taking the high bits).
>
> L
On 04/29/2016 11:27 AM, Konrad Rzeszutek Wilk wrote:
> On Fri, Apr 29, 2016 at 10:12:45AM -0500, Tom Lendacky wrote:
>> On 04/29/2016 02:17 AM, Konrad Rzeszutek Wilk wrote:
>>> On Tue, Apr 26, 2016 at 05:58:12PM -0500, Tom Lendacky wrote:
Since DMA addresses will effectively look like 48-bit a
On Fri, 29 Apr 2016, David Carrillo-Cisneros wrote:
When an event is terminated, intel_cqm_event_stop calls
pqr_cache_update_rmid and sets state->next_rmid to the rmid of its
parent in the RMID hierarchy. That would make next call to
__pqr_update to update PQR_ASSOC.
What about all the cases
On Fri, Apr 29, 2016 at 02:12:20PM +0200, Michal Hocko wrote:
> On Fri 29-04-16 07:51:45, Dave Chinner wrote:
> > On Thu, Apr 28, 2016 at 10:17:59AM +0200, Michal Hocko wrote:
> > > [Trim the CC list]
> > > On Wed 27-04-16 08:58:45, Dave Chinner wrote:
> > > [...]
> > > > Often these are to silence
Hi Ksenija,
On Fri, Apr 29, 2016 at 01:49:11PM +0200, Ksenija Stanojevic wrote:
> Add mxs-lradc touchscreen driver.
>
> Signed-off-by: Ksenija Stanojevic
> ---
> drivers/input/touchscreen/Kconfig| 14 +-
> drivers/input/touchscreen/Makefile | 1 +
> drivers/input/touchscreen/mx
On Fri, Apr 29, 2016 at 9:32 PM, Linus Torvalds
wrote:
wrote:
> For example, that _long_ range of bits set ("7fffc" in the middle)
> is effectively just one bit set with a subtraction. And it's *right*
> in that bit area that is supposed to shuffle bits 14-40 to the high bits
> (which is what
[+cc Matt, because I'm out of my depth in this UEFI stuff]
On Fri, Apr 29, 2016 at 11:52:47PM +0200, Alexander Graf wrote:
> On 29.04.16 23:37, Bjorn Helgaas wrote:
> > On Fri, Apr 29, 2016 at 10:51:34PM +0200, Alexander Graf wrote:
> >> I think the only thing we can really take as granted is the
On Fri, Apr 29, 2016 at 02:38:02PM -0700, Andy Lutomirski wrote:
> On Fri, Apr 29, 2016 at 1:50 PM, Josh Poimboeuf wrote:
> > On Fri, Apr 29, 2016 at 12:39:16PM -0700, Andy Lutomirski wrote:
> >> On Thu, Apr 28, 2016 at 1:44 PM, Josh Poimboeuf
> >> wrote:
> >> > Thanks to all the recent x86 entr
On Fri, 29 Apr 2016 16:15:23 -0700 Yu Zhao wrote:
> struct page->flags is unsigned long, so when shifting bits we should
> use UL suffix to match it.
>
> Found this problem after I added 64-bit CPU specific page flags and
> failed to compile the kernel:
> mm/page_alloc.c: In function '__free_o
On Fri, Apr 29, 2016 at 01:32:15PM -0700, Dave Hansen wrote:
> The reason I haven't acked this patch is that I want to be _sure_ that
> we've audited all of the call paths that access the XSAVE buffer to
> ensure that they can all either handle the XSAVES format *or* don't care
> for whatever reaso
struct page->flags is unsigned long, so when shifting bits we should
use UL suffix to match it.
Found this problem after I added 64-bit CPU specific page flags and
failed to compile the kernel:
mm/page_alloc.c: In function '__free_one_page':
mm/page_alloc.c:672:2: error: integer overflow in ex
On Fri, Apr 29, 2016 at 02:39:32PM -0600, Toshi Kani wrote:
> When a partition is not aligned by 4KB, mount -o dax succeeds,
> but any read/write access to the filesystem fails, except for
> metadata update.
>
> Add alignment check to ext4, ext2, and xfs.
>
> ---
> Toshi Kani (3):
> 1/3 ext4: Ad
Tegra is one of the remaining platforms that still use the
traditional pci_common_init_dev() interface for probing PCI
host bridges.
This demonstrates how to convert it to the pci_register_host
interface I just added in a previous patch. This leads to
a more linear probe sequence that can handle e
As mentioned in another thread, I have tried to come up with
a way to make the PCI host driver registration more flexible
and simpler.
We have actually discussed this multiple times in the past,
but always ended up elsewhere, so this is a proof of concept
work, leaving all the existing interfaces
This changes the pci-host-common implementation to call the
new pci_register_host() interface instead of pci_scan_root_bus().
As a result, we get to share the pci_host_bridge structure
as it was originally intended anyway: We ended up having two
copies of pci_host_bridge here because we never got
This patch makes the existing 'pci_host_bridge' structure a proper device
that is usable by PCI host drivers in a more standard way. In addition
to the existing pci_scan_bus, pci_scan_root_bus, pci_scan_root_bus_msi,
and pci_create_root_bus interfaces, this unfortunately means having to
add yet ano
Hi,
On Fri, Apr 29, 2016 at 3:44 PM, Russell King - ARM Linux
wrote:
> My reply would be... why should MMC have special handling that no
> other subsystem has?
No other subsystem?
* i2c allows numbering devices by alias
* rtc allows numbering devices by alias.
* serial allows numbering devices
On Sat, Apr 30, 2016 at 12:11:45AM +0200, Jiri Kosina wrote:
> On Fri, 29 Apr 2016, Andy Lutomirski wrote:
> > > NMI, MCE and interrupts aren't a problem because they have dedicated
> > > stacks, which are easy to detect. If the tasks' stack is on an
> > > exception stack or an irq stack, we consi
On Thursday 28 April 2016 17:34:10 Arnd Bergmann wrote:
> On Thursday 28 April 2016 10:12:12 Bjorn Helgaas wrote:
> > Right, we don't have a good mechanism for passing more info into
> > pci_create_root_bus(). Maybe the caller could fill in a struct so we
> > have a chance to extend it without hav
On Fri, Apr 29, 2016 at 01:09:07PM -0700, Dave Hansen wrote:
> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
> > diff --git a/arch/x86/kernel/fpu/signal.c b/arch/x86/kernel/fpu/signal.c
> > index 0fbf60c..09945f1 100644
> > --- a/arch/x86/kernel/fpu/signal.c
> > +++ b/arch/x86/kernel/fpu/signal.c
> >
Hi,
On 30.04.2016 01:20, Pali Rohár wrote:
On Saturday 30 April 2016 00:13:59 Pavel Machek wrote:
Any other application I should look at? Thanks,
Maybe camera-ui, which is part of CSSU?
https://github.com/community-ssu/camera-ui
This is based on gdigicam, are you sure it is compatible wit
On Fri, Apr 29, 2016 at 03:22:50PM -0700, Doug Anderson wrote:
> Hi,
>
> On Fri, Apr 29, 2016 at 3:16 PM, Russell King - ARM Linux
> wrote:
> > On Fri, Apr 29, 2016 at 02:56:38PM -0700, Doug Anderson wrote:
> >> Russell,
> >>
> >> On Fri, Apr 29, 2016 at 2:50 PM, Russell King - ARM Linux
> >> wr
On Fri, Apr 29, 2016 at 03:36:12PM -0700, Dave Hansen wrote:
> On 04/29/2016 03:30 PM, Yu-cheng Yu wrote:
> > On Fri, Apr 29, 2016 at 01:25:34PM -0700, Dave Hansen wrote:
> >> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
> >>> + for (i = 0; i < XFEATURE_MAX; i++) {
> >>> + /*
> >>> +
Hello Russell,
On Fri, Apr 29, 2016 at 6:16 PM, Russell King - ARM Linux
wrote:
> On Fri, Apr 29, 2016 at 02:56:38PM -0700, Doug Anderson wrote:
>> Russell,
>>
>> On Fri, Apr 29, 2016 at 2:50 PM, Russell King - ARM Linux
>> wrote:
>> > On Fri, Apr 29, 2016 at 02:39:35PM -0700, Doug Anderson wrot
On 04/29/2016 01:49 PM, Andy Lutomirski wrote:
>> >
>> > But I also think it would be pretty nice if 'ls' didn't pay the 2k cost
>> > to have AVX-512 state if it's not using AVX-512. We also don't have to
>> > do this with CR0.TS. We'd actually use a combination of out-of-line
>> > (not appended
On Fri, Apr 29, 2016 at 02:37:41PM -0700, Andy Lutomirski wrote:
> On Fri, Apr 29, 2016 at 2:25 PM, Josh Poimboeuf wrote:
> > I think the easiest way to make it work would be to modify the idtentry
> > macro to put all the idt entries in a dedicated section. Then the
> > unwinder could easily det
When driver unbinds while media_ioctl is in progress, cdev_put() fails with
when app exits after driver unbinds.
Add a kobject to the media_devnode structure and set this kobject as the
cdev parent kobject. This allows cdev_add() to hold a reference to it and
release the reference in cdev_del() en
On 04/29/2016 03:30 PM, Yu-cheng Yu wrote:
> On Fri, Apr 29, 2016 at 01:25:34PM -0700, Dave Hansen wrote:
>> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
>>> + for (i = 0; i < XFEATURE_MAX; i++) {
>>> + /*
>>> +* Copy only in-use xstates.
>>> +*/
>>> + if
acpi device id table name for this driver is bxtwc_acpi_ids.But
in module device table pmic_acpi_ids is used. This patch fixes
this problem.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
drivers/mfd/intel_soc_pmic_bxtwc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
On Fri, Apr 29, 2016 at 01:25:34PM -0700, Dave Hansen wrote:
> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
> > + for (i = 0; i < XFEATURE_MAX; i++) {
> > + /*
> > +* Copy only in-use xstates.
> > +*/
> > + if (((header.xfeatures >> i) & 1) && xfeature_en
On Fri, 29 Apr 2016 18:34:44 +0200
Andrea Arcangeli wrote:
> On Fri, Apr 29, 2016 at 10:06:11AM +0300, Kirill A. Shutemov wrote:
> > Hm. I just woke up and haven't got any coffee yet, but I don't why my
> > approach would be worse for performance. Both have the same algorithmic
> > complexity.
In the following code block, BXTWC_DEVICE1_ADDR value is
already fixed and hence there no need to check for
if (!i2c_addr) in every ipc read/write calls. Even if this
check is required it can be moved to probe function.
i2c_addr = BXTWC_DEVICE1_ADDR;
if (!i2c_addr) {
dev_err(pmic->dev, "I2
> I think we can agree that we disagree.
Yes, we agree on that, at least!
The problem is, this is supposed to be a matter of fact, not opinion,
so there should be one right answer.
I suppose it's possible it's still an issue of terminology, but we've
exhausted
> Though, I will get back to the d
On Fri, Apr 29, 2016 at 3:48 AM, Daniel Stone wrote:
> Hi,
>
> On 28 April 2016 at 23:28, Rob Clark wrote:
>> On Wed, Apr 27, 2016 at 2:39 AM, Daniel Vetter wrote:
>>> On Tue, Apr 26, 2016 at 01:48:02PM -0700, Greg Hackmann wrote:
A (per-CRTC?) array of fences would be more flexible. And e
On 29-04-16 13:04, Jarkko Sakkinen wrote:
>>> Why would you want to do that?
>>
>> ...
>
> Do you see this as a performance issue or why do you think that this
> would hurt that much?
I don't think it's a performance issue at all. I'm just giving an example of why
you'd want to do this. I'm sure p
Hi,
On Fri, Apr 29, 2016 at 3:16 PM, Russell King - ARM Linux
wrote:
> On Fri, Apr 29, 2016 at 02:56:38PM -0700, Doug Anderson wrote:
>> Russell,
>>
>> On Fri, Apr 29, 2016 at 2:50 PM, Russell King - ARM Linux
>> wrote:
>> > On Fri, Apr 29, 2016 at 02:39:35PM -0700, Doug Anderson wrote:
>> > [di
On Saturday 30 April 2016 00:13:59 Pavel Machek wrote:
> Any other application I should look at? Thanks,
Maybe camera-ui, which is part of CSSU?
https://github.com/community-ssu/camera-ui
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Fri, Apr 29, 2016 at 03:13:33PM -0700, Dave Hansen wrote:
> On 04/29/2016 03:07 PM, Yu-cheng Yu wrote:
> > On Fri, Apr 29, 2016 at 01:28:31PM -0700, Dave Hansen wrote:
> >> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
> >>> The arrays xstate_offsets[] and xstate_sizes[] record XSAVE area
> >>> of
On Fri, Apr 29, 2016 at 02:56:38PM -0700, Doug Anderson wrote:
> Russell,
>
> On Fri, Apr 29, 2016 at 2:50 PM, Russell King - ARM Linux
> wrote:
> > On Fri, Apr 29, 2016 at 02:39:35PM -0700, Doug Anderson wrote:
> > [didn't read most of your reply]
> >
> >> Really I just reposted it several times
Hi!
What is reasonable camera application for testing?
N900 looks like a low-end digital camera. I have now have the hardware
working (can set focus to X cm using command line), but that's not
going to be useful for taking photos.
In particular, who is going to do computation neccessary for
auto
The latest maintenance release Git v2.8.2 is now available at
the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.8.2'
tag and the 'maint' branch that the tag points at:
url = https://kernel
On 04/29/2016 03:07 PM, Yu-cheng Yu wrote:
> On Fri, Apr 29, 2016 at 01:28:31PM -0700, Dave Hansen wrote:
>> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
>>> The arrays xstate_offsets[] and xstate_sizes[] record XSAVE area
>>> offsets and sizes. Values for legacy components i387 and XMMs were
>>> no
If driver_register() failed there is no sense to call driver_unregister().
unregister_chrdev() should be called here.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/ide/ide-tape.c | 6 +++---
1 file changed, 3 insertions(+), 3 deleti
On Fri, 29 Apr 2016, Andy Lutomirski wrote:
> > NMI, MCE and interrupts aren't a problem because they have dedicated
> > stacks, which are easy to detect. If the tasks' stack is on an
> > exception stack or an irq stack, we consider it unreliable.
>
> Only on x86_64.
Well, MCEs are more or less
On Fri, Apr 29, 2016 at 01:28:31PM -0700, Dave Hansen wrote:
> On 03/04/2016 10:12 AM, Yu-cheng Yu wrote:
> > The arrays xstate_offsets[] and xstate_sizes[] record XSAVE area
> > offsets and sizes. Values for legacy components i387 and XMMs were
> > not initialized. Fix it.
>
> Is this just a com
On Tue, Apr 26, 2016 at 09:00:10PM +0200, Pavel Machek wrote:
> On Mon 2016-04-25 20:34:07, Jarkko Sakkinen wrote:
> > Intel(R) SGX is a set of CPU instructions that can be used by
> > applications to set aside private regions of code and data. The code
> > outside the enclave is disallowed to acc
On Thu, 28 Apr 2016, Miroslav Benes wrote:
> Current object-walking helper checks the presence of obj->funcs to
> determine the end of objs array in klp_object structure. This is
> somewhat fragile because one can easily forget about funcs definition
> during livepatch creation. In such a case the
When an event is terminated, intel_cqm_event_stop calls
pqr_cache_update_rmid and sets state->next_rmid to the rmid of its
parent in the RMID hierarchy. That would make next call to
__pqr_update to update PQR_ASSOC.
On Fri, Apr 29, 2016 at 2:32 PM Vikas Shivappa
wrote:
>
>
>
> On Fri, 29 Apr 2016
Add preliminary UV4 defines.
Signed-off-by: Mike Travis
Tested-by: John Estabrook
Tested-by: Gary Kroening
Tested-by: Nathan Zimmer
---
arch/x86/include/asm/uv/uv_hub.h | 64 +++---
arch/x86/include/asm/uv/uv_mmrs.h | 22 +
2 files changed, 62
The major portion of the hub info is common to all cpus on that hub.
This is step one of moving the per cpu hub info to a per node hub info
struct. This patch creates the small per cpu info struct that will
contain only information specific to each CPU.
Signed-off-by: Mike Travis
Reviewed-by: Di
Move references to blade local processor ID to the new per cpu info
structs. Create an access function that makes this move, and other
potential moves opaque to callers of this function. Define a flag
that indicates to callers in external GPL modules that this function
replaces any local definiti
This patch set primarily updates the Linux kernel to support the next
generation SGI Ultraviolet system, UV4. This architecture change is a
larger incremental change than previous UV updates because of a major
change to the addressing scheme. Previous UV architectures used a fixed
address width
Change the references to the SCIR fields to the new per cpu info structs.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Tested-by: John Estabrook
Tested-by: Gary Kroening
Tested-by: Nathan Zimmer
---
arch/x86/include/asm/uv/uv_hub.h | 17 ++---
arch/x86/kernel/apic
Allocate and setup per node hub info structs. CPU 0/Node 0 hub info
is statically allocated to be accessible early in system startup. The
remaining hub info structs are allocated on the node's local memory,
and shared among the CPU's on that node. This leaves the small amount
of info unique to e
1 - 100 of 791 matches
Mail list logo
