Hello,
Ping!
On 06/01/2015 10:51 AM, Bhuvanchandra DV wrote:
Changes since V1:
Use common get/set mctrl control methods for both lpuart, lpuart32
and fix indention.
Bhuvanchandra DV (3):
ARM: dts: colibri-vf: Add pinmux for UART_0 aka UART_A RTS/CTS pins
tty: serial: fsl_lpuart: remove
On failure, v9fs_session_init() returns with the v9fs_session_info
struct partially initialized and expects the caller to invoke
v9fs_session_close() to clean it up; however, it doesn't track whether
the bdi is initialized or not and curiously invokes bdi_destroy() in
both vfs_session_init()
all,
On Sat, Jun 06, 2015 at 08:09:34PM -0700, Jeremiah Mahler wrote:
> all,
>
> On all my machines with Intel graphics I get the following warning
> in the logs when the machine is suspended. Apparently some part of
> the graphics system is busy when it should be idle. This is present
> on the
Hi Hn,
On Fri, May 29, 2015 at 12:27:29PM +0800, HungNien Chen wrote:
> Signed-off-by: HungNien Chen
Thank you for making changes, I have some more comments. By the way,
have you tried running scripts/checkpatch.pl over your patch? It often
picks up some common issues.
> ---
>
Acked-By: Devesh Sharma
On Fri, Jun 5, 2015 at 8:17 PM, Colin King wrote:
> From: Colin Ian King
>
> A reorganisation of the PD allocation and deallocation in commit
> 9ba1377daa ("RDMA/ocrdma: Move PD resource management to driver.")
> introduced a double free on pd, as detected by static
On Jun 7, 2015, at 6:17 PM, Linus Torvalds
wrote:
> On Sun, Jun 7, 2015 at 5:00 PM, Tejun Heo wrote:
>> On Sun, Jun 07, 2015 at 05:54:30PM -0600, Louis Langholtz wrote:
>>> @@ -853,6 +853,7 @@ static void __init version_sysfs_builtin(void)
>>> mk =
Hello,
This patchset adds a dt binding for specifying sample time
for the vybrid adc driver and takes this into account for
sampling frequency calculation and related configuration in
the driver.
The patchset is based on top of Stefan's patches here
The driver currently does not take into account the minimum sample time
as per the Figure 6-8 Chapter 9.1.1 12-bit ADC electrical characteristics.
We set a static amount of cycles instead of considering the sample time as
a given value, which depends on hardware characteristics.
Determine
Add a device tree property which allows to specify the minimum sample
time which can be used to calculate the actual ADC cycles required
depending on the hardware.
Signed-off-by: Sanchayan Maity
---
arch/arm/boot/dts/vfxxx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git
Spake Linus:
> Hell no.
>
> Stop with the random BUG_ON() additions.
>
> I have said this before, and apparently I need to sat this again, and
> probably I will have to say it in the future.
>
> We don't add BUG_ON's for random reasons.
>
> The *ONLY* acceptable reason for a BUG_ON() is if
* Linus Torvalds wrote:
> On Jun 7, 2015 11:42 AM, "Denys Vlasenko" wrote:
> >
> > Rename it to ia32_int80_target.
>
> Btw, could we arrive to get rid of the idiotic "ia32" naming too? It's wrong,
> and it harkens back to the days when intel thought itanium makes sense and
> wanted to talk
In recovery procedure for superblock, we try to write data of valid
superblock into invalid one for recovery, work should be finished here,
but then still we will write the valid one with its original data.
This operation is not needed. Let's skip doing this unnecessary work.
Signed-off-by: Chao
This patch collects transaction state transition code into one function. We
then could have a single function to maintain transaction related
behaviors. No functional changes.
Signed-off-by: Lv Zheng
Tested-by: Gabriele Mazzotta
Tested-by: Tigran Gabrielyan
Tested-by: Adrien D
---
We've been suffering from the uncertainty of the SCI_EVT clearing timing.
This patch implements 4 possible modes to handle SCI_EVT clearing
variations. The old behavior is kept in this patch.
Status: QR_EC is re-checked as early as possible after checking previous
SCI_EVT. This always
During the period that a work queue is scheduled (queued up for run) but
hasn't been run, second schedule_work() could fail. This may not lead to
the loss of queries because QR_EC is always ensured to be submitted after
the work queue has been in the running state.
Thus except the logging message
When the QR_EC transaction fails, the EC_FLAGS_QUERY_PENDING flag prevents
the event handling work queue from being scheduled again.
Though there shouldn't be failed QR_EC transactions, and this gap was
efficiently used for catching and learning the SCI_EVT clearing timing
compliance issues, we
The _Qxx evaluation work item can be eliminated and _Qxx can be evaluated
right in the same work item as the QR_EC transaction. This patch cleans up
the code to achieve this.
Originally, QR_EC transaction and _Qxx evaluation were all done in the same
work queue flushed by
It is reported that on several platforms, EC firmware will not respond
non-expected QR_EC (see EC_FLAGS_QUERY_HANDSHAKE, only write QR_EC when
SCI_EVT is set).
Unfortunately, ACPI specification doesn't define when the SCI_EVT should be
cleared by the firmware, thus the original implementation
ACPI specification doesn't define the SCI_EVT clearing timing for the EC
firmware. There could be 4 possible positions the firmware may use to clear
the SCI_EVT indication:
STATUS: After indicating SCI_EVT to the host via the status register
(EC_SC), the target can clear SCI_EVT at any
While Rusty Russell wants the return value of sysfs_create_file
ignored, it's annotated '__must_check'. Tejun Heo made the annotaion
and suggests just using WARN_ON_ONCE(). Meanwhile the compiler warns that
the 'err' variable is set but unused. This patch uses Tejun's
suggestion. This eliminates
For the first mount of f2fs image with realtime discard option, we will
disable discard option if device is not supported, but for remount
operation, our discard option can still be set, this should be avoided.
This patch moves configuring of discard option to parse_options() to fix
this issue.
2015-06-08 13:21 GMT+09:00 Anand Moon :
> Hi Krzysztof ,
>
> On 8 June 2015 at 07:40, Krzysztof Kozlowski wrote:
>> On 07.06.2015 22:20, Anand Moon wrote:
>>> Facilitate getting required 3.3V and 1.0V VDD supply for
>>> EHCI controller on Exynos.
>>>
>>> With the patches for regulators' nodes
On 05/27/2015 07:05 PM, David Vrabel wrote:
On 27/05/15 17:25, David Vrabel wrote:
On 20/04/15 06:23, Juergen Gross wrote:
64 bit pv-domains under Xen are limited to 512 GB of RAM today. The
main reason has been the 3 level p2m tree, which was replaced by the
virtual mapped linear p2m list.
在 2015年06月06日 04:24, Doug Anderson 写道:
Russell,
On Fri, Jun 5, 2015 at 11:29 AM, Russell King - ARM Linux
wrote:
1) v7_coherency_exit() is specific to v7 CPUs and can't be used by
generic code.
Oh, I see. So (I think) you're saying that perhaps the reason that
Caesar needed his patch
On Fri, Jun 05, 2015 at 08:13:01PM +1000, Michael Ellerman wrote:
> Hi Darren,
>
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig)
> failed like this:
>
> ERROR: "acpi_bus_get_status_handle" [drivers/platform/x86/pvpanic.ko]
> undefined!
>
> Caused by
Hello Paul,
On 15-06-06 12:26:07, Paul Bolle wrote:
> On Fri, 2015-06-05 at 14:52 +0530, Sanchayan Maity wrote:
> > --- /dev/null
> > +++ b/drivers/soc/fsl/Kconfig
>
> > +config SOC_BUS_VF610
> > + tristate "SoC bus device for the Freescale Vybrid platform"
> > + depends on SOC_VF610
>
Hello Maxime,
On 15-06-06 13:58:33, Maxime Ripard wrote:
> Hi,
>
> On Fri, Jun 05, 2015 at 02:52:37PM +0530, Sanchayan Maity wrote:
> > Add a device tree node for the On-Chip One Time Programmable
> > Controller (OCOTP) and the On-Chip ROM.
> >
> > Signed-off-by: Sanchayan Maity
> > ---
> >
Hi, All
Recently I met one race condition related to debugfs.
Take an example from ion.c in kernel3.14:
static int ion_debug_client_open(struct inode *inode, struct file *file)
{
return single_open(file, ion_debug_client_show, inode->i_private);
}
static const struct file_operations
On Thu, Jun 04, 2015 at 07:51:36PM +0200, Radim Krčmář wrote:
> 2015-06-04 18:13+1000, Stephen Rothwell:
> > After merging the drivers-x86 tree, today's linux-next build (x86_64
> > allmodconfig)
> > failed like this:
> >
> > ERROR: "acpi_bus_get_status_handle" [drivers/platform/x86/pvpanic.ko]
Hi Krzysztof ,
On 8 June 2015 at 07:40, Krzysztof Kozlowski wrote:
> On 07.06.2015 22:20, Anand Moon wrote:
>> Facilitate getting required 3.3V and 1.0V VDD supply for
>> EHCI controller on Exynos.
>>
>> With the patches for regulators' nodes merged in 3.15:
>> c8c253f ARM: dts: Add regulator
On Fri, Jun 5, 2015 at 3:51 PM, Romain Baeriswyl
wrote:
> ---
Your patch is missing a detailed commit message.
> .../devicetree/bindings/gpio/gpio-generic.txt | 19 +
> drivers/gpio/gpio-generic.c| 81 ++-
> 2 files changed, 78
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi folks,
Is there some way to make the kernel automatically recognize a
USB stick as a non-rotational device?
(My hope is that the CFQ IOPS mode patch might improve performance
of a USB stick as well :-)
Regards
Harri
-BEGIN PGP
On Sat, Jun 06, 2015 at 10:23:27AM +0200, Pali Rohár wrote:
> This patch series add new acpi Dell Airplane Mode Switch driver (DELLABCE and
> DELRBTN acpi devices). It provides radio HW switch events (together with
> current
> state of radio devices) and export them via rfkill interface. These
Ping?
Anything missing from my side?
On 04/30/2015 12:53 PM, Juergen Gross wrote:
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer just one
On 2015年06月05日 00:29, Jiang Liu wrote:
On 2015/6/4 23:51, Mark Salter wrote:
On Thu, 2015-06-04 at 14:41 +0800, Jiang Liu wrote:
On 2015/6/4 14:31, Hanjun Guo wrote:
Hi Jiang,
On 2015年06月04日 09:54, Jiang Liu wrote:
On 2015/6/4 4:27, Al Stone wrote:
On 06/02/2015 12:12 AM, Jiang Liu wrote:
您好:
您还在用ali平台开发外贸客户?
还在使用展会宣传企业和产品?
你out了!!!
当前外贸客户开发难，您是否也在寻找展会，B2B之外好的渠道？
行业全球十几万客户，平时最多也就联系了三千家，您是否想把剩下的也开发到？
加QQ2821117472给您演示下主动开发客户的方法，先用先受益，已经有近万家企业领先您使用！！。
广东省商业联合会推荐，主动开发客户第一品牌，近万家企业正在获益。您可以没有使用，但是不能没有了解。
--
To unsubscribe from this list: send the line "unsubscribe
On Sat, Jun 06, 2015 at 03:10:09PM +0200, Pavel Machek wrote:
> On Tue 2015-06-02 07:37:31, NeilBrown wrote:
> > On Mon, 1 Jun 2015 19:06:52 +0530 Kishon Vijay Abraham I
> > wrote:
> >
> > > Hi,
> > >
> > > On Thursday 16 April 2015 01:33 PM, NeilBrown wrote:
> > > > From: NeilBrown
> > > >
>
On Sat, Jun 06, 2015 at 10:04:55AM +0200, Pali Rohár wrote:
> On Friday 05 June 2015 22:17:09 Felipe Balbi wrote:
> > Hi,
> >
> > On Fri, Jun 05, 2015 at 10:09:03PM +0200, Pali Rohár wrote:
> > > On Friday 29 May 2015 18:57:06 Felipe Balbi wrote:
> > > > All right, I tried merging it and it added
Another Sunday, another rc release.
Normally rc7 tends to be the last rc release, and there's not a lot
going on to really merit anything else this time around. However, we
do still have some pending regressions, and as mentioned last week I
also have my yearly family vacation coming up, so we'll
Help-desk Service Center requires your immediate re-activation of your Email
account. This is to upgrade email account to the new anti spam virus detector
sever 2014. Inability to complete this procedure will render your account
inactivate. Activate by completing the survey procedure.
CLICK LINK:
On Mon, Jun 08, 2015 at 12:09:32PM +0900, Tejun Heo wrote:
> For things we want to pack together, I suppose our only option is
> packing them into a struct and defining access macros into it. It's
> unfortunately clumsier but expresses the intended effect clearer to
> both readers and toolchain.
I saw your email address during the course of my research today. My name is
Bill William Groner my wife and I won a Jackpot Lottery in December 2013, we
are donating the part of our winnings to 6 lucky individual all over the world
as part of our charity project and if you received this email
Hello, Eric.
On Sun, Jun 07, 2015 at 09:55:07AM -0700, Eric Dumazet wrote:
> In commit bdf977b37418cdf8a2252504779a7e12a09b7575
> ("x86, percpu: Collect hot percpu variables into one cacheline")
>
> You wrote that forcing cacheline_aligned on
> current_task would put all hot variables
On 2015年06月04日 20:28, Hanjun Guo wrote:
On 2015年06月04日 18:22, Lorenzo Pieralisi wrote:
Hi Hanjun,
On Thu, Jun 04, 2015 at 10:28:17AM +0100, Hanjun Guo wrote:
Hi Lorenzo,
On 2015???06???02??? 21:32, Lorenzo Pieralisi wrote:
On Wed, May 27, 2015 at 09:06:26AM +0100, Tomasz Nowicki wrote:
On
From: Vaishali Thakkar
Date: Sat, 6 Jun 2015 06:44:00 +0530
> In big endian cases, macro cpu_to_le16 unfolds to __swab16 which
> provides special case for constants. In little endian cases,
> __constant_cpu_to_le16 and cpu_to_le16 expand directly to the
> same expression. So, replace
On Sat, Jun 06, 2015 at 01:22:30PM +0900, Greg KH wrote:
>On Thu, Jun 04, 2015 at 10:13:50AM +0800, Wei Yang wrote:
>> kobj->parent is changed only when it is NULL originally.
>>
>> This patch moves the assignment in the "if" to avoid unnecessary assignment.
>>
>> Signed-off-by: Wei Yang
>> ---
From: Antonio Murdaca
Date: Fri, 5 Jun 2015 18:58:38 +0200
> use time_is_before_eq_jiffies macro for time comparison
>
> Signed-off-by: Antonio Murdaca
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: Jonas Jensen
Date: Fri, 5 Jun 2015 15:46:18 +0200
> desc = priv->tx_desc_base + (TX_REG_DESC_SIZE * tx_head);
>
> - spin_lock_irq(>txlock);
> + if (CIRC_SPACE(tx_head, tx_tail, TX_DESC_NUM) == 0) {
> + priv->stats.tx_dropped++;
> + goto out_unlock;
On 07.06.2015 22:20, Anand Moon wrote:
> Facilitate getting required 3.3V and 1.0V VDD supply for
> EHCI controller on Exynos.
>
> With the patches for regulators' nodes merged in 3.15:
> c8c253f ARM: dts: Add regulator entries to smdk5420
> 275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
> -Original Message-
> From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> Sent: Saturday, June 06, 2015 5:59 AM
> To: Wu, Feng
> Cc: h...@zytor.com; t...@linutronix.de; mi...@redhat.com; x...@kernel.org;
> g...@kernel.org; pbonz...@redhat.com; dw...@infradead.org;
> j...@8bytes.org;
During probe the regulator (if present) was enabled but not disabled in
case of failure. So an unsuccessful probe lead to enabling the
regulator which was actually not needed because the device was not
enabled.
Additionally each deferred probe lead to increase of regulator enable
count so it
>
> On 06/05/2015 01:54 PM, MyungJoo Ham wrote:
> >>
> >> IRQ signal before driver probe is needless because driver sends
> >> current state after platform booting done.
> >> So, this patch clears MUIC IRQ bits before request IRQ.
> >>
> >> Signed-off-by: Jaewon Kim
> >> ---
> >>
2015-05-24 12:41 GMT+09:00 Ramakrishna Pallala :
> This patch adds the support for following battery properties
> to max17042 fuel gauge driver.
>
> POWER_SUPPLY_PROP_TEMP_ALERT_MIN
> POWER_SUPPLY_PROP_TEMP_ALERT_MAX
> POWER_SUPPLY_PROP_TEMP_MIN
> POWER_SUPPLY_PROP_TEMP_MAX
>
> -Original Message-
> From: Joerg Roedel [mailto:j...@8bytes.org]
> Sent: Friday, June 05, 2015 9:34 PM
> To: Thomas Gleixner
> Cc: Wu, Feng; dw...@infradead.org; jiang@linux.intel.com;
> io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> Subject: Re: [v9 0/9] Add VT-d
Add some safe values for over head and over voltage. The Trats2 uses 3.8
V battery and during testing it operated properly under 4.48 V.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos4412-trats2.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git
The commit edd4ab055931 ("power: max17042_battery: add HEALTH and TEMP_*
properties support") added support for setting voltage and temperature
thresholds with platform data. For DeviceTree default of 0 was always
used.
This caused reporting battery health always as over voltage or
over heated.
The fix for NULL pointer exception related to calling uevent for not
finished probe caused to set all writeable properties as non-writeable.
This was caused by checking if property is writeable before the initial
increase of power supply usage counter and in the same time using
wrapper over
On Sat, 6 Jun 2015, Borislav Petkov wrote:
> On Fri, Jun 05, 2015 at 04:40:29PM -0500, Thor Thayer wrote:
> > Yes, in our case, it is a hardware issue but I'm still gathering
> > information.
> >
> > The IRQ vectors for OCRAM reside on DDR and in Suspend-to-RAM mode we're
> > executing out of
On Sun, Jun 07, 2015 at 05:17:20PM -0700, Linus Torvalds wrote:
> At most, it could be a "WARN_ON_ONCE()". Maybe even just silently
> ignore the error. But BUG_ON()? Hell no.
Yeah, WARN_ON_ONCE() is the right one. The short history here is that
sysfs_create_file() has __must_check on it which
While Rusty Russell wants the return value of sysfs_create_file
ignored, it's annotated '__must_check'. Tejun Heo made the annotaion
and suggests just using BUG_ON(). Meanwhile the compiler warns that
the 'err' variable is set but unused. This patch uses Tejun's
suggestion. This eliminates the
Source and destination have the same little-endian annotation: this
patch removes incorrect byte-swap on non-LE cpus.
This addresses the following sparse warning:
drivers/staging/rtl8723au/core/rtw_mlme_ext.c:3911:56: warning: incorrect type
in argument 1 (different base types)
This fixes bitwise arithmetic performed on the host on a variable
previously converted to little-endian, and subsequently converted
again to little-endian:
- issue_action_BA23a() called with "status" crafted in host byte order
- "status" converted to LE
- bitwise arithmetic on the (LE)
The code shows a couple inconsistencies (described in commit
descriptions) which would not be an issue on little-endian cpus, but
could cause breakage on non-LE cpus. Note: I could not test on real
hardware, these patches created based on sparse reports.
Hostory:
- resending the same patches to
This was introduced by kernel bulk commit 5e93f3520 "staging: r8723au:
Add source files for new driver - part 1", initially from github
according to commit description. On github, this traces back to
another bulk commit: 2896bda04353 "Add new files in core directory",
which is the 1st version of
On Sun, Jun 7, 2015 at 2:05 AM, Grant Likely wrote:
> On Tue, 19 May 2015 10:17:32 -0700
> , Greg Kroah-Hartman
> wrote:
>> On Tue, May 19, 2015 at 01:29:16PM +0100, Sudeep Holla wrote:
>> > Hi Rob/Greg,
>> >
>> > On 14/05/15 15:28, Sudeep Holla wrote:
>> > >Commit 5590f3196b29
On Sun, Jun 7, 2015 at 5:00 PM, Tejun Heo wrote:
> On Sun, Jun 07, 2015 at 05:54:30PM -0600, Louis Langholtz wrote:
>> @@ -853,6 +853,7 @@ static void __init version_sysfs_builtin(void)
>> mk = locate_module_kobject(vattr->module_name);
>> if (mk) {
>>
On Sun, Jun 07, 2015 at 05:54:30PM -0600, Louis Langholtz wrote:
> While Rusty Russell wants the return value of sysfs_create_file
> ignored, it's annotated '__must_check'. Tejun Heo made the annotaion
> and suggests just using BUG_ON(). Meanwhile the compiler warns that
> the 'err' variable is
Invert Y is needed (together with swap XY) for some touchscreens :
- LeadingTouch screens (at least for some of them)
- cartft 8in4 (USB ID=0eef:0001)
Signed-off-by: Ondrej Zary
Bug-Link: https://bugs.tizen.org/jira/browse/TC-2522
Cc: linux-in...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
On 06/08, Oleg Nesterov wrote:
>
> And I simply can not understand the complication in hrtimer_active(),
> please help!
Sorry for another off-topic email, but I don't even understand the
usage of hrtimer_active().
Say, do_nanosleep()
hrtimer_start_expires(>timer, mode);
Not sure I read this patch correctly, it doesn't apply to Linus's tree.
And I simply can not understand the complication in hrtimer_active(),
please help!
On 06/05, Peter Zijlstra wrote:
>
> +bool hrtimer_active(const struct hrtimer *timer)
> +{
> + struct hrtimer_cpu_base *cpu_base;
> +
From: Michal Simek
Date: Fri, 5 Jun 2015 10:49:17 +0200
> Remove sparse warnings:
> drivers/net/ethernet/xilinx/ll_temac_main.c:65:16: warning: cast removes
> address space of expression
> drivers/net/ethernet/xilinx/ll_temac_main.c:70:9: warning: cast removes
> address space of expression
>
[Re: metag test failure in -next due to commit 'module: relocate module_init
from init.h to module.h'] On 05/06/2015 (Fri 17:39) Guenter Roeck wrote:
> On 06/05/2015 02:39 PM, James Hogan wrote:
> [ ... ]
> >
> > From e12856c559d7dff2ad4f6497996610e12e7c7e2d Mon Sep 17 00:00:00 2001
> >From:
On Sun, 7 Jun 2015, Drokin, Oleg wrote:
> Hello!
>
> You are right, set_pga seems to be a dead member. It was alive a once, but
> somehow not fully removed now,
> so it's safe to drop the whole if and also the struct member itself.
> set_oabufs could be dropped as well.
Thanks. I will do
Hello!
You are right, set_pga seems to be a dead member. It was alive a once, but
somehow not fully removed now,
so it's safe to drop the whole if and also the struct member itself.
set_oabufs could be dropped as well.
Thanks.
Bye,
Oleg
On Jun 7, 2015, at 4:11 PM, Julia Lawall
Hello,
The function lov_finish_set in
drivers/staging/lustre/lustre/lov/lov_request.c contains the code:
if (set->set_pga) {
int len = set->set_oabufs * sizeof(*set->set_pga);
OBD_FREE_LARGE(set->set_pga, len);
}
If I change the call to
Clear pending interrupts before requesting interrupts and move
interrupt initialization after channels have been initialized.
This avoids a NULL pointer dereference panic when using kexec
while DMA requests were running.
Signed-off-by: Stefan Agner
---
drivers/dma/fsl-edma.c | 9 +
1
Robert Jarzmik writes:
> Hi Vinod and Maxime,
>
> This very same patch was already submitted in [1]. It enables the reuse of
> transfers through their lifetime. I added to this serie the documentation
> patch
> Maxime has been commenting, as it is tighly linked.
>
> The "RESEND" is a bit
On 06/05, Peter Zijlstra wrote:
>
> #define HRTIMER_STATE_INACTIVE 0x00
> #define HRTIMER_STATE_ENQUEUED 0x01
> -#define HRTIMER_STATE_CALLBACK 0x02
> -#define HRTIMER_STATE_MIGRATE0x04
> +#define HRTIMER_STATE_MIGRATE0x02
Slightly pff-topic, but I do not
On 04.06.2015 15:52, Dan Carpenter wrote:
> On Tue, Jun 02, 2015 at 10:48:10PM +0200, Mateusz Kulikowski wrote:
>> - Remove unused fields in dig_t structures. Some of them were only
>> initialized and never accessed.
>> - Remove unused enums/macros/defines in rtl_dm.h
>> - Remove duplicated
On 04.06.2015 08:06, Sudip Mukherjee wrote:
> On Thu, Jun 04, 2015 at 07:50:07AM +0200, Mateusz Kulikowski wrote:
>> On 04.06.2015 07:18, Sudip Mukherjee wrote:
>>> On Wed, Jun 03, 2015 at 08:21:02PM +0200, Mateusz Kulikowski wrote:
On 03.06.2015 09:26, Sudip Mukherjee wrote:
> On Tue,
On 2015-06-07 18:56, Jonathan Cameron wrote:
> On 27/05/15 13:47, Stefan Agner wrote:
>> The ADC clock frequency is limited depending on modes used. Add
>> device tree property which allow to set the mode used and the
>> maximum frequency ratings for the instance. These allows to
>> set the ADC
Guennadi Liakhovetski writes:
> Hi Robert,
>
> Please, correct me if I am wrong, but doesn't this patch have to be
> updates? Elgl looking at this:
>> +for (i = 0; i < 3 && buf->descs[i]; i++) {
>> +async_tx_ack(buf->descs[i]);
>> +
Hi Robert,
I've sent you two replies, did you get them? Spam filter?
Thanks
Guennadi
On Sat, 6 Jun 2015, Robert Jarzmik wrote:
> Robert Jarzmik writes:
>
> > Robert Jarzmik writes:
> >
> >> Hi Guennadi,
> >>
> >> I've been cooking this since 2012. At that time, I thought the dmaengine
> >>
Hi Robert,
Please, correct me if I am wrong, but doesn't this patch have to be
updates? Elgl looking at this:
On Sun, 22 Mar 2015, Robert Jarzmik wrote:
> From: Robert Jarzmik
>
> Convert pxa_camera to dmaengine. This removes all DMA registers
> manipulation in favor of the more generic
"ia32_syscall" label name (entry point for INT 80) is inconsistent with
"ia32_sysenter_target" (entry point for SYSENTER insn) and
"ia32_cstar_target" (entry point for SYSCALL insn).
It is especially misleading since we do have code in this file which
handles SYSCALL insn, and it's _not this
From: Dave Hansen
There are two basic things that can happen as the result of
a bounds exception (#BR):
1. We allocate a new bounds table
2. We pass up a bounds exception to userspace.
This patch adds a trace point for the case where we are
passing the exception up to
From: Dave Hansen
Currently, to get from a bounds directory entry to the virtual
address of a bounds table, we simply mask off a few low bits.
However, the set of bits we mask off is different for 32 and
64-bit binaries.
This breaks the operation out in to a helper function and also
adds a
From: Dave Hansen
When we allocate a bounds table, we call mmap(), then add a
"valid" bit to the value before storing it in to the bounds
directory.
If we fail along the way, we go and mask that valid bit
_back_ out. That seems a little silly, and this makes it
much more clear when we have a
From: Dave Hansen
Bounds tables are a significant consumer of memory. It is important
to know when they are being allocated. Add a trace point to trace
whenever an allocation occurs and also its virtual address.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
---
From: Dave Hansen
There are two different events being traced here. They are
doing similar things so share a trace "EVENT_CLASS" and are
presented together.
1. Trace when MPX is zapping pages "mpx_unmap_zap":
When MPX can not free an entire bounds table, it will
instead try
From: Dave Hansen
Right now, the kernel can only switch between 64-bit and 32-bit
binaries at compile time. This patch adds support for 32-bit
binaries on 64-bit kernels when we support ia32 emulation.
We essentially choose which set of table sizes to use when doing
arithmetic for the bounds
From: Dave Hansen
We explicitly disable allowing 32-bit binaries to enable
MPX on 64-bit kernels. Re-allow that.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
---
b/arch/x86/mm/mpx.c |6 --
1 file changed, 6 deletions(-)
diff -puN
From: Dave Hansen
The comment pretty much says it all.
I wrote a test program that does lots of random allocations
and forces bounds tables to be created. It came up with a
layout like this:
| BOUNDS DIRECTORY ENTRY COVERS |
|BOUNDS TABLE COVERS|
| BOUNDS
From: Dave Hansen
user_atomic_cmpxchg_inatomic() actually looks at sizeof(*ptr) to
figure out how many bytes to copy. If we run it on a 64-bit
kernel with a 64-bit pointer, it will copy a 64-bit bounds
directory entry. That's fine, except when we have 32-bit
programs with 32-bit bounds
From: Dave Hansen
The MPX code needs to clear out bounds tables for memory which
is no longer in use. We do this when a userspace mapping is
torn down (unmapped).
There are two modes:
1. An entire bounds table becomes unused, and can be freed
and its pointer removed from the bounds
From: Qiaowei Ren
MPX_BNDCFG_ADDR_MASK is defined two times, so this patch removes
redundant one.
Signed-off-by: Qiaowei Ren
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
---
b/arch/x86/include/asm/mpx.h |1 -
1 file changed, 1 deletion(-)
diff -puN
From: Dave Hansen
The comment and code here are confusing. We do not currently
allocate the bounds directory in the kernel.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
---
b/arch/x86/mm/mpx.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN
From: Dave Hansen
MPX has the _potential_ to cause some issues. Say part of your init
system tried to protect one of its components from buffer overflows
with MPX. If there were a false positive, it's possible that MPX
could keep a system from booting.
MPX could also potentially cause
From: Dave Hansen
The uprobes code has a nice helper, is_64bit_mm(), that consults both
the runtime and compile-time flags for 32-bit support. Instead of
reinventing the wheel, pull it in to an x86 header so we can use it
for MPX.
I prefer passing the mm around to test_thread_flag(TIF_IA32)
From: Dave Hansen
get_xsave_addr() assumes that if an xsave bit is present in the
hardware (pcntxt_mask) that it is present in a given xsave
buffer. Due to an bug in the xsave code on all of the systems
that have MPX (and thus all the users of this code), that has
been a true assumption.
But,
1 - 100 of 516 matches
Mail list logo
