On Tue, 21 Jul 2015 04:56:21 +0900,
Guenter Roeck wrote:
>
> Hi,
>
> Commit 52b2512d507d ("asm-generic: {get,put}_user ptr argument evaluate only
> 1 time")
> causes the following compile error with various architectures (arc, arcv2,
> c6x, hexagon,
> um, unicore32) in -next.
>
>
On 07/21/2015 09:30 AM, Zheng, Lv wrote:
> Hi,
>
> If the issue is already identified and confirmed:
> For example, you've confirmed the QR_EC(0x14) can only arrive when the
> keyboard accessory is plugged in.
> Then please ignore my previous reply.
> I don't have idea about handling a LID that
On Tue, Jul 21, 2015 at 2:45 PM, Masahiro Yamada
wrote:
> This variable is used as an iterator and initialized in the
> list_for_each() loop.
>
Looks good, thanks!
Reviewed-by: Alexandre Courbot
> Signed-off-by: Masahiro Yamada
> ---
>
> drivers/gpio/gpiolib.c | 2 +-
> 1 file changed, 1
On Mon, 2015-07-20 at 08:41 -0500, Segher Boessenkool wrote:
> On Mon, Jul 20, 2015 at 04:24:22PM +0530, Ananth N Mavinakayanahalli wrote:
> > There is a potential gain to be had with a direct
> > jump instead of a breakpoint, but the caveats need to be traded off
> > with the complexity it brings
On Tue, Jul 21, 2015 at 12:05:56AM -0400, Ming Lei wrote:
> On Mon, Jul 20, 2015 at 9:59 PM, Dave Chinner wrote:
> > Hi Ming,
> >
> > With the recent merge of the loop device changes, I'm now seeing
> > XFS deadlock on my single CPU, 1GB RAM VM running xfs/073.
> >
> > The deadlocked is as
This variable is used as an iterator and initialized in the
list_for_each() loop.
Signed-off-by: Masahiro Yamada
---
drivers/gpio/gpiolib.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index bf4bd1d..adb03c6 100644
---
2015-07-21 14:13 GMT+09:00 Krzysztof Kozlowski :
> 2015-07-21 14:02 GMT+09:00 Kukjin Kim :
>> Krzysztof Kozlowski wrote:
>>>
>>> Dear Kukjin,
>>>
>>> Exynos mach-code related improvements. Description along with a tag.
>>> You can find them also on the lists with my reviewed-by.
>>>
>>> Best
Hi all,
Changes since 20150720:
The nfsd tree gained a build failure so I used the version from
next-20150720.
The sound-asoc tree lost its build failure.
The gpio tree gained a build failure for which I added a merge fix patch.
The akpm tree lost a patch that turned up elsewhere.
Non-merge
2015-07-21 14:02 GMT+09:00 Kukjin Kim :
> Krzysztof Kozlowski wrote:
>>
>> Dear Kukjin,
>>
>> Exynos mach-code related improvements. Description along with a tag.
>> You can find them also on the lists with my reviewed-by.
>>
>> Best regards,
>> Krzysztof
>>
>>
>> The following changes since
Hi,
On Monday 20 July 2015 05:34 PM, Tero Kristo wrote:
> On 07/17/2015 04:47 PM, Roger Quadros wrote:
>> scm_conf1 maps the control register address space after the
>> padconf till the end.
>>
>> Fix the scm_conf and pmx_core resource lengths. We need to add
>> 4 bytes to include the last 32-bit
On Mon, Jul 20, 2015 at 08:45:51PM +1000, Alexey Kardashevskiy wrote:
> The existing code stores the amount of memory allocated for a TCE table.
> At the moment it uses @offset which is a virtual offset in the TCE table
> which is only correct for a one level tables and it does not include
>
; [-Wreturn-type]
> }
> ^
>
> Caused by commit
>
> 395b297af7bf ("nfsd: Add layouts checking in client_has_state()")
>
> cl_lo_states is only defined when CONFIG_NFSD_PNFS is set.
>
> I have used the nsfd tree from next-20150720 for today.
>
--
T
Krzysztof Kozlowski wrote:
>
> Dear Kukjin,
>
> Exynos mach-code related improvements. Description along with a tag.
> You can find them also on the lists with my reviewed-by.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 1c4c7159ed2468f3ac4ce5a7f08d79663d381a93:
>
>
Krzysztof Kozlowski wrote:
>
> Dear Kukjin,
>
Hi Krzysztof,
> DTS related improvements. Description along with a tag.
> You can find them also on the lists with my reviewed-by.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit a419d78a6f97f8c977fe55d5d590cd0654ecd1ee:
>
Using a 64 bit constant generates "warning: integer constant is too
large for 'long' type" on 32 bit platforms. Instead use ~0ul and
BITS_PER_LONG.
Detected by Andrew Morton on ARMD.
Signed-off-by: Sowmini Varadhan
---
v2: use BITS_PER_LONG and ulong as discussed on mailing list.
Hi MM maintainers,
this patch is the last requiring an ack for the series to go in.
Could you please comment?
Juergen
On 07/17/2015 06:51 AM, Juergen Gross wrote:
During early boot as Xen pv domain the kernel needs to map some page
tables supplied by the hypervisor read only. This is needed
On Mon, Jul 20, 2015 at 11:46:28AM +0300, Andy Shevchenko wrote:
> >> +static void idma64_chan_init(struct idma64 *idma64, struct idma64_chan
> >> *idma64c)
> >> +{
> >> + u32 cfghi = IDMA64C_CFGH_SRC_PER(1) | IDMA64C_CFGH_DST_PER(0);
> >> + u32 cfglo = 0;
> >> +
> >> + /* Enforce
On Sun, Jul 19, 2015 at 09:01:34PM +0200, Michal Suchanek wrote:
> Hello,
>
> On 15 July 2015 at 17:59, Brian Norris wrote:
> > Hi Michal,
> >
> > On Wed, Jul 15, 2015 at 01:52:27PM +0200, Marek Vasut wrote:
> >> The problem is, if you add a new DT binding, you'd have to support it
> >> forever,
On Mon, Jul 20, 2015 at 10:50:12AM -0700, Mike Kravetz wrote:
...
> > ...
> >> @@ -3236,11 +3360,14 @@ retry:
> >> * any allocations necessary to record that reservation occur outside
> >> * the spinlock.
> >> */
> >> - if ((flags & FAULT_FLAG_WRITE) && !(vma->vm_flags & VM_SHARED))
>
On Mon, Jul 20, 2015 at 10:28:14AM +0200, Julia Lawall wrote:
> On Mon, 20 Jul 2015, Alex Smith wrote:
>
> > On 19/07/2015 10:08, Julia Lawall wrote:
> > > The file drivers/dma/dma-jz4780.c has a probe function that sets up irqs
> > > using devm_request_irq. The probe function then ends with:
>
On Mon, Jul 20, 2015 at 9:59 PM, Dave Chinner wrote:
> Hi Ming,
>
> With the recent merge of the loop device changes, I'm now seeing
> XFS deadlock on my single CPU, 1GB RAM VM running xfs/073.
>
> The deadlocked is as follows:
>
> kloopd1: loop_queue_read_work
> xfs_file_iter_read
>
On 20 July 2015 21:42:39 CEST, Luis de Bethencourt
wrote:
>On Mon, Jul 20, 2015 at 09:54:56PM +0300, Dan Carpenter wrote:
>> On Mon, Jul 20, 2015 at 06:35:42PM +0200, Luis de Bethencourt wrote:
>> > Remove explicit true/false comparisons to bool variables.
>> >
>> > Signed-off-by: Luis de
> On Mon, Jul 20, 2015 at 03:04:20PM +, Liang, Kan wrote:
>
> SNIP
>
> > break;
> > + case PARSE_EVENTS__TERM_TYPE_TIME:
> > + if (time_set)
> > + *time_set = true;
> > + CHECK_TYPE_VAL(NUM);
> > + if (term->val.num > 1)
> > +
From: Murali Karicheri
Date: Thu, 16 Jul 2015 15:32:14 -0400
> The keystone qmss will raise interrupt when packet arrive at the
> receive queue. Only control available to avoid interrupt from happening
> is to keep the free descriptor queue (FDQ) empty in the receive side.
> So the filling of
From: Nicolas Schichan
Date: Thu, 16 Jul 2015 18:46:29 +0200
> This serie fixes issues with the ARM BPF JIT and adds support for more
> instructions to the ARM BPF JIT.
>
> The first three patches are fixing bugs in the ARM JIT and should
> probably find their way to a stable kernel.
>
> The
There is a bug when migrate from !feature-persistent host to feature-persistent
host, because domU still think new host/backend don't support persistent.
Dmesg like:
backed has not unmapped grant: 839
backed has not unmapped grant: 773
backed has not unmapped grant: 773
backed has not unmapped
This BUG_ON() will be triggered when previous purge work haven't finished.
It's reasonable under pretty extreme load and should not panic the system.
Signed-off-by: Bob Liu
---
drivers/block/xen-blkback/blkback.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
This BUG_ON() in blkif_free() is incorrect, because indirect page can be added
to list info->indirect_pages in blkif_completion() no matter feature_persistent
is true or false.
Signed-off-by: Bob Liu
---
drivers/block/xen-blkfront.c |1 -
1 file changed, 1 deletion(-)
diff --git
Hi Linus,
After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/regulator/rk808-regulator.c: In function
'rk808_regulator_dt_parse_pdata':
drivers/regulator/rk808-regulator.c:543:24: error: too few arguments to
function 'gpiod_get_index'
On Mon, Jul 20, 2015 at 06:58:03PM -0700, Joe Perches wrote:
> On Mon, 2015-07-20 at 18:29 -0700, Paul E. McKenney wrote:
> > On Mon, Jul 20, 2015 at 06:06:19PM -0700, Joe Perches wrote:
> > > On Mon, 2015-07-20 at 20:55 -0400, Steven Rostedt wrote:
> > > > On Fri, 17 Jul 2015 15:37:54 -0700
> > >
On 20-07-15, 19:50, Guenter Roeck wrote:
> This patch fixes the problem.
Thanks for doing this quickly. Daniel isn't around right now and may
take some time to get this commited.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, Jul 20, 2015 at 8:49 AM, Kan Liang wrote:
> From: Andy Lutomirski
>
> This patch adds freq PMU to support time and freq related counters
> includes TSC, IA32_APERF, IA32_MPERF and IA32_PPERF.
>
> The events are exposed in sysfs for use by perf stat and other tools.
> The files are under
Hi,
Previous patch v5 url:
http://thread.gmane.org/gmane.linux.kernel/1995274
The bugfix of dynamic array length in trace event goes to
kernel/git/rostedt/linux-trace.git ftrace/urgent and confirms that the
return value of __get_dynamic_array_len() is the total allocated
length of the dynamic
>
> Only change in this revision is the fix to the self-discovered
> issue in region_chg(). Functional and stress tests passing.
> Full changelog below.
>
> As suggested during the RFC process, tests have been proposed to
> libhugetlbfs as described at:
>
Support helper function __get_dynamic_array_len() in libtraceevent,
this function is used accompany with __print_array() or __print_hex(),
but currently it is not an available function in the function list of
process_function().
The total allocated length of the dynamic array is embedded in the
There're scenarios that we need an eBPF program to record not only
kprobe point args, but also the PMU counters, time latencies or the
number of cache misses between two probe points and other information
when the probe point is entered.
This patch adds a new trace event to establish
On Mon, Jul 20, 2015 at 11:28:03AM -0500, Alex Thorlton wrote:
> I've got some time on the large machine later today. I'll give this a
> try then.
I ran a boot with this patch applied:
diff --git a/include/linux/mlx4/device.h b/include/linux/mlx4/device.h
index 83e80ab..c84aea0 100644
---
On 07/20/2015 07:31 PM, Viresh Kumar wrote:
On 20-07-15, 14:07, Guenter Roeck wrote:
Hi,
Commit 991a7f4970ed1 ("clockevents/drivers/sh_tmu: Migrate to new 'set-state'
interface")
in -next causes the following traceback. This is seen with qemu runs for the sh
target.
[ cut here
Full sync for drbd initial usually take a long time,
allow "--zap-devices" on "new-current-uuid" to zero
out device on both side.
Signed-off-by: Nick Wang
CC: Philipp Reisner
CC: Lars Ellenberg
CC: drbd-...@lists.linbit.com
CC: linux-kernel@vger.kernel.org
---
documentation/v84/drbdsetup.xml
On 21-07-15, 00:12, Rafael J. Wysocki wrote:
> On Saturday, July 18, 2015 03:13:41 AM Rafael J. Wysocki wrote:
> > Hi,
> >
> > The following two patches clean up a couple of things in the ACPI processor
> > driver and the ACPI cpufreq driver:
> >
> > [1/2] Drop the unused first argument of
> >
On 20-07-15, 14:07, Guenter Roeck wrote:
> Hi,
>
> Commit 991a7f4970ed1 ("clockevents/drivers/sh_tmu: Migrate to new 'set-state'
> interface")
> in -next causes the following traceback. This is seen with qemu runs for the
> sh target.
>
> [ cut here ]
> WARNING: at
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 2015?7?21? 8:15
> To: Dudley Du
> Cc: mark.rutl...@arm.com; robh...@kernel.org; rydb...@euromail.se;
> ble...@google.com; jmmah...@gmail.com; devicet...@vger.kernel.org;
> linux-in...@vger.kernel.org;
This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
Features:
1. F81534 is 1-to-4 & F81532 is 1-to-2 serial ports IC
2. Support Baudrate from B50 to B150 (excluding B100).
3. The RTS signal can be transformed their behavior with
configuration by default ioctl
Hi Ming,
With the recent merge of the loop device changes, I'm now seeing
XFS deadlock on my single CPU, 1GB RAM VM running xfs/073.
The deadlocked is as follows:
kloopd1: loop_queue_read_work
xfs_file_iter_read
lock XFS inode XFS_IOLOCK_SHARED (on image file)
page cache
On Mon, 2015-07-20 at 18:29 -0700, Paul E. McKenney wrote:
> On Mon, Jul 20, 2015 at 06:06:19PM -0700, Joe Perches wrote:
> > On Mon, 2015-07-20 at 20:55 -0400, Steven Rostedt wrote:
> > > On Fri, 17 Jul 2015 15:37:54 -0700
> > > Joe Perches wrote:
> > >
> > > > > + if ($line =~
> >
Dmitry,
Yes, It cannot report the distance per-contact.
Thanks for the update.
Thanks,
Dudley
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 2015?7?21? 8:07
> To: Dudley Du
> Cc: mark.rutl...@arm.com; robh...@kernel.org; rydb...@euromail.se;
>
Gera diena,
Tai DIAMOND ŠVEICARIJOS paskola bendrovei Paskolos pasiūlymas.
DIAMOND ŠVEICARIJOS paskola bendrovei siūlo lanksčias ir prieinamas paskolas
bet kokiam tikslui, siekiant padėti jums pasiekti savo tikslus. mes paskola
mažomis palūkanų norma 1,5%. Štai keletas svarbių bruožai
Hi,
If the issue is already identified and confirmed:
For example, you've confirmed the QR_EC(0x14) can only arrive when the keyboard
accessory is plugged in.
Then please ignore my previous reply.
I don't have idea about handling a LID that always returns "closed" when the
keyboard accessory is
On Mon, Jul 20, 2015 at 06:06:19PM -0700, Joe Perches wrote:
> On Mon, 2015-07-20 at 20:55 -0400, Steven Rostedt wrote:
> > On Fri, 17 Jul 2015 15:37:54 -0700
> > Joe Perches wrote:
> >
> > > > + if ($line =~
> > > > /\b(synchronize_rcu_expedited|synchronize_sched_expedited)\(/) {
On 20 July 2015 at 19:52, Richard Yao wrote:
>
> From: Richard Yao
>
> I noticed that genksyms will segfault when it sees duplicate function
> pointer type declaration when I placed the same function pointer
> definition in two separate headers in a local branch as an intermediate
> step of some
2015-07-21 8:02 GMT+09:00 Dmitry Torokhov :
> Instead of creating an attribute manually, after the device has been
> registered, let's rely on facilities provided by the attribute groups to
> control which attributes are visible and which are not. This allows to to
> create all needed attributes
From: Xunlei Pang
As part of addressing the "y2038 problem" for in-kernel uses,
convert update_persistent_clock() to update_persistent_clock64(),
read_persistent_clock() to read_persistent_clock64() using
timespec64 for MN10300.
Add the common weak version of update_persistent_clock() to make
On Mon, 20 Jul 2015 18:06:19 -0700
Joe Perches wrote:
> On Mon, 2015-07-20 at 20:55 -0400, Steven Rostedt wrote:
> > On Fri, 17 Jul 2015 15:37:54 -0700
> > Joe Perches wrote:
> >
> > > > + if ($line =~
> > > > /\b(synchronize_rcu_expedited|synchronize_sched_expedited)\(/) {
> >
On Tue, Jul 21, 2015 at 2:47 AM, Rafael J. Wysocki wrote:
> Hi Russell,
>
> On Mon, Jul 20, 2015 at 12:36 PM, Russell King - ARM Linux
> wrote:
>> On Mon, Jul 20, 2015 at 03:17:10PM +0530, Viresh Kumar wrote:
>>> Consider a dual core (0/1) system with two CPUs:
>>> - sharing clock/voltage rails
Gera diena,
Tai DIAMOND ŠVEICARIJOS paskola bendrovei Paskolos pasiūlymas.
DIAMOND ŠVEICARIJOS paskola bendrovei siūlo lanksčias ir prieinamas paskolas
bet kokiam tikslui, siekiant padėti jums pasiekti savo tikslus. mes paskola
mažomis palūkanų norma 1,5%. Štai keletas svarbių bruožai
Hi Yuyang,
On Wed, Jul 15, 2015 at 08:04:41AM +0800, Yuyang Du wrote:
> The cfs_rq's load_avg is composed of runnable_load_avg and blocked_load_avg.
> Before this series, sometimes the runnable_load_avg is used, and sometimes
> the load_avg is used. Completely replacing all uses of
On Mon, 2015-07-20 at 20:55 -0400, Steven Rostedt wrote:
> On Fri, 17 Jul 2015 15:37:54 -0700
> Joe Perches wrote:
>
> > > + if ($line =~
> > > /\b(synchronize_rcu_expedited|synchronize_sched_expedited)\(/) {
> >
> > It'd be faster perl without capture groups:
>
> Is checkpatch such a
On Mon, Jul 20, 2015 at 05:48:40PM -0700, Joe Perches wrote:
> On Mon, 2015-07-20 at 17:41 -0700, Paul E. McKenney wrote:
> > On Fri, Jul 17, 2015 at 03:37:54PM -0700, Joe Perches wrote:
> > > It'd be faster perl without capture groups:
> > >
> > > if ($line =~
On Fri, 17 Jul 2015 15:37:54 -0700
Joe Perches wrote:
> > + if ($line =~
> > /\b(synchronize_rcu_expedited|synchronize_sched_expedited)\(/) {
>
> It'd be faster perl without capture groups:
Is checkpatch such a critical code path that we could possibly notice
the difference in
2015-07-21 8:02 GMT+09:00 Dmitry Torokhov :
> struct rtc embeds both struct dev and struct cdev. Unfortunately character
> device structure may outlive the parent rtc structure unless we set it up
> as parent of character device so that it will stay pinned until character
> device is freed.
>
>
The SF2 driver currently overrides speed settings for its port
configured using a fixed PHY, this is both unnecessary and incorrect,
because we keep feedback to the hardware parameters that we read from
the PHY device, which in the case of a fixed PHY cannot possibly change
speed.
This is a
From: Stas Sergeev
Currently the PHY management type is selected by the MAC driver arbitrary.
The decision is based on the presence of the "fixed-link" node and on a
will of the driver's authors.
This caused a regression recently, when mvneta driver suddenly started
to use the in-band status for
Hi all,
Changes in v5:
- removed an invalid use of the link_update callback in the SF2 driver
was appeared after merging "net: phy: fixed_phy: handle link-down case"
- reworded the commit message for patch 2 to make it clear what it fixes and
why this is required
Initial cover letter from
From: Stas Sergeev
The commit 898b2970e2c9 ("mvneta: implement SGMII-based in-band link state
signaling") implemented the link parameters auto-negotiation unconditionally.
Unfortunately it appears that some HW that implements SGMII protocol,
doesn't generate the inband status, so it is not
From: Stas Sergeev
fixed_phy_register() currently hardcodes the fixed PHY link to 1, and
expects to find a "speed" parameter to provide correct information
towards the fixed PHY consumer.
In a subsequent change, where we allow "managed" (e.g: (RS)GMII in-band
status auto-negotiation) fixed
On Mon, 2015-07-20 at 17:41 -0700, Paul E. McKenney wrote:
> On Fri, Jul 17, 2015 at 03:37:54PM -0700, Joe Perches wrote:
> > It'd be faster perl without capture groups:
> >
> > if ($line =~ /\b(?:synchronize_(?:rcu|sched)_expedited)\s*\(/) {
>
> Fair enough, but this pattern is used
On Sun, Jul 19, 2015 at 11:58:18AM +0200, Marcin Ślusarz wrote:
> On Thu, Jul 16, 2015 at 02:01:56PM -0700, David Rientjes wrote:
> > On Wed, 15 Jul 2015, Paul E. McKenney wrote:
> >
> > > On Tue, Jul 14, 2015 at 04:48:24PM -0700, David Rientjes wrote:
> > > > On Tue, 14 Jul 2015, Paul E.
On 2015. 7. 21., at AM 6:11, Jacek Anaszewski
wrote:
>> On 20.07.2015 16:15, Jingoo Han wrote:
>>> On Thursday, July 16, 2015 5:01 PM, Jacek Anaszewski wrote:
On 07/15/2015 10:02 PM, Bjorn Andersson wrote:
The Qualcomm PM8941 WLED block is used for backlight and should therefor
Hi Russell,
On Mon, Jul 20, 2015 at 12:36 PM, Russell King - ARM Linux
wrote:
> On Mon, Jul 20, 2015 at 03:17:10PM +0530, Viresh Kumar wrote:
>> Consider a dual core (0/1) system with two CPUs:
>> - sharing clock/voltage rails and hence cpufreq-policy
>> - CPU1 is offline while the cpufreq
On Mon, Jul 20, 2015 at 5:32 PM, Krzysztof Kozlowski
wrote:
> 2015-07-21 8:02 GMT+09:00 Dmitry Torokhov :
>> Commit 59cca865f21e9e7beab73fcf79ba4eb776a4c228 correctly noted that naked
>> kfree() should not be used after failed device_register() call, however,
>> while it added the needed
On Fri, Jul 17, 2015 at 03:37:54PM -0700, Joe Perches wrote:
> On Fri, 2015-07-17 at 15:20 -0700, Paul E. McKenney wrote:
> > The synchronize_rcu_expedited() and synchronize_sched_expedited()
> > expedited-grace-period primitives induce OS jitter, which can degrade
> > real-time response. This
Hi Morten,
On 07/07/2015 11:24 AM, Morten Rasmussen wrote:
> In mainline find_idlest_group() selects the wake-up target group purely
> based on group load which leads to suboptimal choices in low load
> scenarios. An idle group with reduced capacity (due to RT tasks or
> different cpu type) isn't
2015-07-21 8:02 GMT+09:00 Dmitry Torokhov :
> Technically the address of rtc->dev can never be NULL, so get_device()
> can never fail. Also caller of rtc_device_unregister() supposed to be
> the owner of the device and thus have a valid reference. Therefore
> call to get_device() is not needed
On Mon, Jul 20, 2015 at 07:20:58PM -0400, Mike Snitzer wrote:
> On Mon, Jul 20 2015 at 6:36pm -0400,
> Dave Chinner wrote:
>
> > On Mon, Jul 20, 2015 at 11:18:49AM -0400, Mike Snitzer wrote:
> > > If XFS fails to write metadata it will retry the write indefinitely
> > > (with the hope that the
On 07/20/2015 04:48 PM, Darren Hart wrote:
> An earlier (pre-kernel-integration) refactoring of this code mistakenly
> replaced the error condition, <, with a >. Use < to detect an error as
> opposed to a successful requeue or signal race.
>
> Reported-by: David Binderman
> Cc: Shuah Khan
>
es cleanly to efi-next-14364 of efi/next and
arm64-upstream-13521 of arm64/master, but needed slight change
to apply to next-20150720 of linux-next/master and
pm+acpi-4.2-rc3 of linux-pm/master. The later two branches
has newer arch/arm64/include/asm/acpi.h with following patch:
b6cfb277378e ACPI /
From: "Jonathan (Zhixiong) Zhang"
... to allow arch specific implementation of getting page
protection type associated with a physical address.
If the physical address has memory attributes defined by EFI
memmap as EFI_MEMORY_UC, the page protection type is
PAGE_KENERL_NOCACHE. Otherwise, the
From: "Jonathan (Zhixiong) Zhang"
With ACPI APEI firmware first handling, generic hardware error
record is updated by firmware in GHES memory region. When firmware
updated GHES memory region with uncached access attribute, Linux
reads stale data from cache.
GHES memory region should be mapped
function.
2. Rebased to efi-next-14364 of efi/next, pm+acpi-4.2-rc3 of
linux-pm/master, arm64-upstream-13521 of arm64/master,
next-20150720 of linux-next/master.
V5:
1. Rebased to next-20150713 of linux-next/master, efi-next-14359 of
efi/next, pm+acpi-4.2-rc2 of linux-pm/master,
arm64-
From: "Jonathan (Zhixiong) Zhang"
x86 and ia64 implement efi_mem_attributes() differently. This
function needs to be available for other arch (such as arm64)
as well, such as for the purpose of ACPI/APEI.
ia64 efi does not setup memmap variable and does not set
EFI_MEMMAP flag, so it needs to
2015-07-21 8:02 GMT+09:00 Dmitry Torokhov :
> Commit 59cca865f21e9e7beab73fcf79ba4eb776a4c228 correctly noted that naked
> kfree() should not be used after failed device_register() call, however,
> while it added the needed put_device() it forgot to remove the original
> kfree() causing
On 07/20/2015 04:28 PM, Andrew Morton wrote:
On Mon, 20 Jul 2015 19:57:18 +0200 Rasmus Villemoes
wrote:
On Mon, Jul 20 2015, Guenter Roeck wrote:
So either case ~0l appears to be wrong; it should be ~0ul.
Yes, right-shifting -1 of any type is probably always wrong, as it will
always
I'd like input on whether or not using different PGP subkeys for purposes of
making new software releases but *also* a different subkey for purposes of
deprecating software releases might be a reasonable way forward to help with
automation of figuring out what releases to list as supported / eol.
Hi,
The _LID returns LIDS:
Device (LID)
{
Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware
ID
Name (LIDS, Zero)
Method (_LID, 0, NotSerialized) // _LID: Lid Status
{
Return (LIDS) /*
Hi Matt/Borislav, thanks for the discussion. I am sorry that somehow
I did not see this message in my inbox. I found it by surprise through
an internet search.
On Mon, 22 Jun, at 06:11:31AM, Matt Fleming wrote:
Right, but see my previous comment about x86 discarding a bunch of
attributes for
From: Alexei Potashnik
Current implementation assumes that all the buffers of an IO are linked
with a single SG list. Which makes it fail if SG chaining is used.
Signed-off-by: Alexei Potashnik
---
drivers/target/iscsi/iscsi_target.c | 9 -
1 file changed, 4 insertions(+), 5
On Mon, Jun 15, 2015 at 05:01:37PM +0800, Dudley Du wrote:
> Add CYTP0002 name for Gen6 device for ACPI configuration
> TEST=test on Chromebook.
>
> Signed-off-by: Dudley Du
Applied, thank you.
> ---
> drivers/input/mouse/cyapa.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On Mon, Jun 15, 2015 at 05:01:36PM +0800, Dudley Du wrote:
> Add of_match_device mechanism support for Cypress trackpad device, and
> add the sample description document of adding the trackpad device node in
> device tree.
> TEST=test on Chromebook.
>
> Signed-off-by: Dudley Du
> ---
>
Vendor ID 0x10de007d is used by a yet-to-be-named GPU chip.
Signed-off-by: Aaron Plattner
---
This chip also has the 2-ch audio swapping bug, so patch_nvhdmi is appropriate
here.
sound/pci/hda/patch_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/pci/hda/patch_hdmi.c
On Mon, Jun 15, 2015 at 05:01:34PM +0800, Dudley Du wrote:
> Fix the the runtime suspend power management not working issue when system
> starts up and before user touches the trackpad device.
> TEST=test on Chromebook.
>
> Signed-off-by: Dudley Du
Applied, thank you.
> ---
>
On Mon, Jul 20, 2015 at 11:52 AM, Andy Lutomirski wrote:
> It has never had any effect. Remove it for comprehensibility.
>
> Cc'd to stable because whatever to do with improve the NMI mess will
> probably depend on this.
>
> Cc: sta...@vger.kernel.org
Peter, if you've already queued this up,
Hi Dudley,
On Mon, Jun 15, 2015 at 05:01:33PM +0800, Dudley Du wrote:
>
> +static void cyapa_pip_report_proximity(struct cyapa *cyapa,
> + const struct cyapa_pip_report_data *report_data)
> +{
> + struct input_dev *input = cyapa->input;
> + u8 distance =
On Mon, Jun 15, 2015 at 05:01:32PM +0800, Dudley Du wrote:
> Based on the cyapa core, add the gen6 trackpad device's basic functions
> supported, so gen6 trackpad device can work with kernel input system.
> And also based on the state parse interface, the cyapa driver can
> automatically determine
On Mon, Jun 15, 2015 at 05:01:31PM +0800, Dudley Du wrote:
> Change strings 'gen5' to 'pip' for all macros, variables and functions when
> they are shared in gen5 and gen6 modules. The change of these strings is
> aimed to keep name definition much more clear and readable.
> Also the spelling
ree from next-20150720 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.h
From: Richard Yao
I noticed that genksyms will segfault when it sees duplicate function
pointer type declaration when I placed the same function pointer
definition in two separate headers in a local branch as an intermediate
step of some refactoring. This can be reproduced by piping the
Hi
So i don't have to repost my patch here. Please use the original
commit log message[1/3] as is.
But please keep in mind that there is still an issue that I mentioned
in the cover letter; 'Size' field is inaccurate.
=
+
and
= +
-
From: Spencer Baugh
From: Chris Zankel
The lun_flags field is not used, so drop it.
Signed-off-by: Chris Zankel
---
include/target/target_core_base.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/target/target_core_base.h
b/include/target/target_core_base.h
index
From: Spencer Baugh
From: Chris Zankel
The initiatorname field in se_acl_lun is only a copy of the same field
in se_node_acl, so remove it and use the version in se_node_acl where
needed (it's actually only used for pr_debug)
Signed-off-by: Chris Zankel
---
On Mon, 20 Jul 2015 19:57:18 +0200 Rasmus Villemoes
wrote:
> On Mon, Jul 20 2015, Guenter Roeck wrote:
>
> > So either case ~0l appears to be wrong; it should be ~0ul.
>
> Yes, right-shifting -1 of any type is probably always wrong, as it will
> always give -1 again.
Not for unsigned types.
1 - 100 of 1498 matches
Mail list logo
