On 11/25/2013 11:35 PM, Cesar Eduardo Barros wrote:
Disabling compiler optimizations can be fragile, since a new
optimization could be added to -O0 or -Os that breaks the assumptions
the code is making.
Instead of disabling compiler optimizations, use a dummy inline assembly
(based on
Rafael,
As you pointed out, ata_tport_delete() should be after
scsi_remove_host(), consistent with ata_tport_add() currently before
ata_scsi_add_host().
Thanks for fixing it,
Gwendal.
On Mon, Nov 25, 2013 at 2:41 AM, Rafael J. Wysocki wrote:
>
> On Monday, November 25, 2013 12:11:54 PM Mika
On Sun, 24 Nov 2013 18:38:26 -0500 Johannes Weiner wrote:
> ...
>
> + * Access frequency and refault distance
> + *
> + * A workload is trashing when its pages are frequently used but they
> + * are evicted from the inactive list every time before another access
> + * would have
On Sun, Nov 24, 2013 at 06:38:28PM -0500, Johannes Weiner wrote:
> Previously, page cache radix tree nodes were freed after reclaim
> emptied out their page pointers. But now reclaim stores shadow
> entries in their place, which are only reclaimed when the inodes
> themselves are reclaimed. This
On Mon, Nov 25, 2013 at 3:16 PM, H. Peter Anvin wrote:
> On 11/25/2013 02:14 PM, Kees Cook wrote:
>> Build the kernel with -fstack-protector-strong when it is available
>> (gcc 4.9 and later). This increases the coverage of the stack protector
>> without the heavy performance hit of
On Mon, Nov 25, 2013 at 3:35 PM, Andy Lutomirski wrote:
> I'm trying to arrange for a process to have a different memory policy
> on its stack as compared to everything else (e.g. mapped libraries).
> Before I start looking for kludges, is there any clean way to do this?
>
> So far, the best I
Naveen,
On Mon, Nov 18, 2013 at 10:18 PM, Naveen Krishna Chatradhi
wrote:
> For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
> on a fixed 66 MHz peripheral clock, and therefore is completely
> independent of the cpu frequency.
> Thus, registering for a CPU freq notifier is very
On Saturday, November 23, 2013 07:27:27 AM Lv Zheng wrote:
> From: Lv Zheng
>
> The header file is the top level header for other kernel
> subsystems to include. It contains environemnt settings and architecture
> specific implementation that should be included before including other
> ACPICA
Hi Olof,
On Mon, 25 Nov 2013 11:41:16 -0800 Olof Johansson wrote:
>
> I'm starting a git repo for the chromeos platform glue (x86 and ARM down
> the road, so far just x86 contents). Can you please add to linux-next?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/olof/chrome-platform.git
>
>
Am Montag, 25. November 2013, 13:01:25 schrieb Mark Rutland:
> [...]
>
> > +static int hym8563_probe(struct i2c_client *client,
> > +const struct i2c_device_id *id)
> > +{
> > + struct hym8563 *hym8563;
> > + int ret, gpio_int;
> > +
> > + hym8563 =
On Tue, Nov 19, 2013 at 10:47:05AM +0530, Bharat Bhushan wrote:
> In Aperture type of IOMMU (like FSL PAMU), VFIO-iommu system need to know
> the MSI region to map its window in h/w. This patch just defines the
> required weak functions only and will be used by followup patches.
>
>
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a cpufreq change. That means we don't need
to constantly adjust the watchdog timer, so avoid registering for and
dealing with cpufreq transitions unless we've actually got
CONFIG_ARM_S3C24XX_CPUFREQ
I'm trying to arrange for a process to have a different memory policy
on its stack as compared to everything else (e.g. mapped libraries).
Before I start looking for kludges, is there any clean way to do this?
So far, the best I can come up with is to either parse /proc/self/maps
on startup or to
On Monday 25 of November 2013 15:28:29 Doug Anderson wrote:
> Guenter,
>
> On Mon, Nov 25, 2013 at 3:23 PM, Guenter Roeck wrote:
> > On 11/25/2013 02:55 PM, Doug Anderson wrote:
> >>
> >> On modern SoCs the watchdog timer is parented on a clock that doesn't
> >> change every time we have a
I was looking at the stack expansion code, and I'm not convinced it's
safe. Aside from the obvious scariness of down_read(_sem) not
actually preventing vma changes, I think there's a real race. Suppose
that you have a VM_GROWSDOWN vma above a VM_GROWSUP vma with a
single-page gap between them.
On Mon, Nov 25, 2013 at 04:12:48PM -0700, Bjorn Helgaas wrote:
> On Tue, Oct 29, 2013 at 11:30:30AM +0100, Veaceslav Falico wrote:
> > Currently, we first do kobject_put(>kobj) and the kfree(entry),
> > however kobject_put() doesn't guarantee us that it was the last reference
> > and that the kobj
On Monday 25 of November 2013 15:23:27 Guenter Roeck wrote:
> On 11/25/2013 02:55 PM, Doug Anderson wrote:
> > On modern SoCs the watchdog timer is parented on a clock that doesn't
> > change every time we have a cpufreq change. That means we don't need
> > to constantly adjust the watchdog
Guenter,
On Mon, Nov 25, 2013 at 3:23 PM, Guenter Roeck wrote:
> On 11/25/2013 02:55 PM, Doug Anderson wrote:
>>
>> On modern SoCs the watchdog timer is parented on a clock that doesn't
>> change every time we have a cpufreq change. That means we don't need
>> to constantly adjust the watchdog
On Mon, Nov 25, 2013 at 7:36 AM, Shawn Landden wrote:
> Commit 35f9c09fe (tcp: tcp_sendpages() should call tcp_push() once)
> added an internal flag MSG_SENDPAGE_NOTLAST, similar to
> MSG_MORE.
>
> algif_hash, algif_skcipher, and udp used MSG_MORE from tcp_sendpages()
> and need to see the new
Olof Johansson wrote:
>
> On Mon, Nov 25, 2013 at 3:11 PM, Doug Anderson
> wrote:
> > Olof or Kukjin,
> >
> > On Wed, Oct 23, 2013 at 6:11 AM, Doug Anderson
> wrote:
> >> Without the interrupt you'll get problems if you enable
> >> CONFIG_RTC_DRV_MAX77686. Setup the interrupt properly in the
From: Ralf Baechle
Now that we have a CONFIG_PANIC_TIMEOUT=x setting, remove the mips settings. The
default is 0, which means don't reboot on panic.
Signed-off-by: Ralf Baechle
Acked-by: Shinya Kuribayashi
Signed-off-by: Jason Baron
---
arch/mips/ar7/setup.c | 1 -
Default CONFIG_PANIC_TIMEOUT to 180 seconds on powerpc. The pSeries continue
to set the timeout to 10 seconds at run-time. Thus, there's a small window
where we don't have the correct value on pSeries, but if this is only run-time
discoverable we don't have a better option. In any case, if the
On 11/25/2013 02:55 PM, Doug Anderson wrote:
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a cpufreq change. That means we don't need
to constantly adjust the watchdog timer, so avoid registering for and
dealing with cpufreq transitions unless
The panic_timeout value can be set via the command line option 'panic=x', or via
/proc/sys/kernel/panic, however that is not sufficient when the panic occurs
before we are able to set up these values. Thus, add a CONFIG_PANIC_TIMEOUT
so that we can set the desired value from the .config.
The
Hi,
I've now separated out the arch bits into separate patches. Hopefully, it makes
review easier. I also didn't address moving the 'panic_timeout' command-line
parameter up as an 'early_param()'. I think it might make sense to move it up,
especially for distro kernels, but its not a need here,
The following build error is seen if CONFIG_32BIT is undefined,
CONFIG_64BIT is defined, and CONFIG_MIPS32_O32 is undefined.
asm/syscall.h: In function 'mips_get_syscall_arg':
arch/mips/include/asm/syscall.h:32:16: error: unused variable 'usp'
[-Werror=unused-variable]
cc1: all warnings being
On Sun, Nov 24, 2013 at 06:38:25PM -0500, Johannes Weiner wrote:
> Reclaim will be leaving shadow entries in the page cache radix tree
> upon evicting the real page. As those pages are found from the LRU,
> an iput() can lead to the inode being freed concurrently. At this
> point, reclaim must
On 11/25/2013 02:14 PM, Kees Cook wrote:
> Build the kernel with -fstack-protector-strong when it is available
> (gcc 4.9 and later). This increases the coverage of the stack protector
> without the heavy performance hit of -fstack-protector-all.
What is the difference between the various
On Monday, November 25, 2013 07:41:41 PM Viresh Kumar wrote:
>
> This patch adds cpufreq callbacks to dpm_{suspend|resume}() for handling
> suspend/resume of cpufreq governors. This is required for early suspend and
> late resume of governors and cpufreq core.
>
> There are multiple problems
On Mon, Nov 25, 2013 at 3:11 PM, Doug Anderson wrote:
> Olof or Kukjin,
>
> On Wed, Oct 23, 2013 at 6:11 AM, Doug Anderson wrote:
>> Without the interrupt you'll get problems if you enable
>> CONFIG_RTC_DRV_MAX77686. Setup the interrupt properly in the device
>> tree.
>>
>> Signed-off-by: Doug
On Tue, Oct 29, 2013 at 11:30:30AM +0100, Veaceslav Falico wrote:
> Currently, we first do kobject_put(>kobj) and the kfree(entry),
> however kobject_put() doesn't guarantee us that it was the last reference
> and that the kobj isn't used currently by someone else, so after we
> kfree(entry) with
Olof or Kukjin,
On Wed, Oct 23, 2013 at 6:11 AM, Doug Anderson wrote:
> Without the interrupt you'll get problems if you enable
> CONFIG_RTC_DRV_MAX77686. Setup the interrupt properly in the device
> tree.
>
> Signed-off-by: Doug Anderson
> ---
> arch/arm/boot/dts/cros5250-common.dtsi | 12
On Mon, Nov 11, 2013 at 6:40 AM, Michal Marek wrote:
> Pasting the verbatim PCI_(VENDOR|DEVICE)_* macros in the __pci_fixup_*
> symbol names results in insanely long names such as
>
>
Hi Olof,
On Mon, Nov 25, 2013 at 1:13 PM, Olof Johansson wrote:
> I've applied patch 1-3. Since the naming seems to still be up in the
> air on the i2c side, I can't apply 4-6 yet.
>
> I also switched the subject to platform/chrome: ... since that's what
> I've picked to use on the other
> What's LTO? I guess it's Link Time Optimization? Is there any
Yes. Link Time Optimization with modern gcc.
> documentation about how it works or how to use it?
It's still a separate tree, but bits'n'pieces are slowly
making it into the kernel.
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a cpufreq change. That means we don't need
to constantly adjust the watchdog timer, so avoid registering for and
dealing with cpufreq transitions unless we've actually got
CPU_FREQ_S3C24XX defined.
On Monday, November 25, 2013 02:15:55 PM Paul Drews wrote:
> This adds the new ACPI ID (INT33FC) for the BayTrail GPIO
> banks as seen on a BayTrail M System-On-Chip platform. This
> ACPI ID is used by the BayTrail GPIO (pinctrl) driver to
> manage the Low Power Subsystem (LPSS).
>
>
Disabling compiler optimizations can be fragile, since a new
optimization could be added to -O0 or -Os that breaks the assumptions
the code is making.
Instead of disabling compiler optimizations, use a dummy inline assembly
(based on RELOC_HIDE) to block the problematic kinds of optimization,
So we get to delete our hacky workaround.
Signed-off-by: Kent Overstreet
---
drivers/md/bcache/bcache.h| 18
drivers/md/bcache/io.c| 100 +-
drivers/md/bcache/journal.c | 4 +-
drivers/md/bcache/request.c | 16 +++
Em 25-11-2013 14:26, Daniel Borkmann escreveu:
On 11/25/2013 04:59 PM, James Yonan wrote:
This approach using __asm__ ("" : "=r" (var) : "0" (var)) to try to
prevent compiler optimizations of var is interesting.
I like the fact that it's finer-grained than -Os and doesn't preclude
inlining.
We get a measurable performance increase by handling this in the driver when
we're already looping over the biovec, instead of handling it separately in
generic_make_request() (or bio_add_page() originally)
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
Cc: Asai Thambi S P
Cc: Sam Bradshaw
---
Since generic_make_request() can now handle arbitrary size bios, all we
have to do is make sure the bvec array doesn't overflow.
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
---
fs/bio.c | 137 ++-
1 file changed, 57 insertions(+),
generic_make_request() will now do for us what the code in blk-lib.c was
doing manually, with the bio_batch stuff - we still need some looping in
case we're trying to discard/zeroout more than around a gigabyte, but
when we can submit that much at a time doing the submissions in parallel
really
The way the block layer is currently written, it goes to great lengths
to avoid having to split bios; upper layer code (such as bio_add_page())
checks what the underlying device can handle and tries to always create
bios that don't need to be split.
But this approach becomes unwieldy and
This builds off of immutable biovecs; it's a small enough patch series that I'd
like to try to get it into 3.14 but it is a pretty significant change in
behaviour for the block layer so it should definitely be considered separately
from that series.
What the series does is pretty simple - like
Em 25-11-2013 13:59, James Yonan escreveu:
On 24/11/2013 14:12, Cesar Eduardo Barros wrote:
Disabling compiler optimizations can be fragile, since a new
optimization could be added to -O0 or -Os that breaks the assumptions
the code is making.
Instead of disabling compiler optimizations, use a
On 11/25/2013 04:11 PM, Tony Lindgren wrote:
> * Joel Fernandes [131125 13:45]:
>> +
>> +static struct omap_hwmod_addr_space omap4_des_addrs[] = {
>> +{
>> +.pa_start = 0x480A4000,
>> +.pa_end = 0x481A4000,
>> +.flags = ADDR_TYPE_RT
On 11/25/2013 04:12 PM, Tony Lindgren wrote:
> * Joel Fernandes [131125 13:46]:
>> Here are patches adding hwmod for AES/DES crypto modules for OMAP4, DRA7
>> SoCs.
>>
>> Also included is a fix that disables POSTED mode when dmtimer is requested.
>>
>> Joel Fernandes (7):
>> ARM: OMAP: hwmod:
On Mon, 25 Nov 2013, Benjamin Tissoires wrote:
> > When an I2C HID device is powered of during system sleep, as a result of
> > removing its power resources (by the ACPI core) the interrupt line might go
> > low as well. This results inadvertent interrupt and wakes the system from
> > sleep
On Tue, Nov 12, 2013 at 1:40 AM, Michal Marek wrote:
> On 11.11.2013 14:40, Michal Marek wrote:
>> Pasting the verbatim PCI_(VENDOR|DEVICE)_* macros in the __pci_fixup_*
>> symbol names results in insanely long names such as
>>
>>
On 11/25/2013 04:14 PM, Tony Lindgren wrote:
> * Joel Fernandes [131125 13:46]:
>> Enabling of Posted mode is seen to cause problems on dmtimer modules on
>> AM33xx
>> (much like other OMAPs). Reference discussions on forums [1] [2]. Earlier
>> patch solving this on other OMAPs [3].
>>
>> For
This adds the new ACPI ID (INT33FC) for the BayTrail GPIO
banks as seen on a BayTrail M System-On-Chip platform. This
ACPI ID is used by the BayTrail GPIO (pinctrl) driver to
manage the Low Power Subsystem (LPSS).
Signed-off-by: Paul Drews
---
drivers/acpi/acpi_lpss.c | 1 +
Build the kernel with -fstack-protector-strong when it is available
(gcc 4.9 and later). This increases the coverage of the stack protector
without the heavy performance hit of -fstack-protector-all.
On a Chrome OS kernel build, this grows the uncompressed kernel image
by less than 0.16% on x86:
* Joel Fernandes [131125 13:46]:
> Enabling of Posted mode is seen to cause problems on dmtimer modules on AM33xx
> (much like other OMAPs). Reference discussions on forums [1] [2]. Earlier
> patch solving this on other OMAPs [3].
>
> For OMAP SoCs with this errata, the fix has been to not
Hi,
On Mon, Nov 25, 2013 at 04:07:49PM -0600, Felipe Balbi wrote:
> On Sat, Nov 16, 2013 at 02:01:18AM +0200, Taras Kondratiuk wrote:
> > From: Victor Kamensky
> >
> > All OMAP IP blocks expect LE data, but CPU may operate in BE mode.
> > Need to use endian neutral functions to read/write h/w
On Mon, 25 Nov 2013 16:22:31 + "Jan Beulich" wrote:
> Commit fad1a86e ("procfs: call default get_unmapped_area on MMU-present
> architectures"), as its title says, took care of only the MMU case,
> leaving the !MMU side still in the regressed state (returning -EIO in
> all cases where
From: Stephen Warren
clk_get() returns an error pointer, or a valid token to pass back to the
clock API. Hence, the result must be checked with IS_ERR(), not by
comparison against NULL.
Signed-off-by: Stephen Warren
---
drivers/base/regmap/regmap-mmio.c | 11 ++-
1 file changed, 6
* Joel Fernandes [131125 13:46]:
> Here are patches adding hwmod for AES/DES crypto modules for OMAP4, DRA7 SoCs.
>
> Also included is a fix that disables POSTED mode when dmtimer is requested.
>
> Joel Fernandes (7):
> ARM: OMAP: hwmod: Add SYSC offsets for AES IP
> ARM: DRA7xx: hwmod: Add
* Joel Fernandes [131125 13:45]:
> +
> +static struct omap_hwmod_addr_space omap4_des_addrs[] = {
> + {
> + .pa_start = 0x480A4000,
> + .pa_end = 0x481A4000,
> + .flags = ADDR_TYPE_RT
> + },
> + { }
> +};
Let's not add new
On Sat, Nov 16, 2013 at 02:01:18AM +0200, Taras Kondratiuk wrote:
> From: Victor Kamensky
>
> All OMAP IP blocks expect LE data, but CPU may operate in BE mode.
> Need to use endian neutral functions to read/write h/w registers.
> I.e instead of __raw_read[lw] and __raw_write[lw] functions code
On 11/25/2013 09:26 AM, Vlastimil Babka wrote:
Currently there are several functions to manipulate the deferred compaction
state variables. The remaining case where the variables are touched directly
is when a successful allocation occurs in direct compaction, or is expected
to be successful in
On Monday, November 25, 2013 02:59:44 PM Bjorn Helgaas wrote:
> On Sat, Nov 23, 2013 at 5:17 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > After commit bcdde7e221a8 (sysfs: make __sysfs_remove_dir() recursive)
> > I'm seeing traces analogous to the one below in Thunderbolt
On Sunday, November 24, 2013 08:37:01 AM Geyslan G. Bem wrote:
> Free 'ctx_str' when necessary.
>
> Signed-off-by: Geyslan G. Bem
> ---
> security/selinux/xfrm.c | 11 +++
> 1 file changed, 7 insertions(+), 4 deletions(-)
Nice catch, applied.
> diff --git a/security/selinux/xfrm.c
Hello,
Using 3.12.0 and ext4fs with 2 x SSDs in a RAID-1 configuration on a
3ware HW RAID card, no md/dm, I noticed the following recently:
[178339.353565] sda2: WRITE SAME failed. Manually zeroing.
It seems to be similar to this issue here:
http://permalink.gmane.org/gmane.linux.kernel/1494512
On Sat, Nov 23, 2013 at 5:17 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> After commit bcdde7e221a8 (sysfs: make __sysfs_remove_dir() recursive)
> I'm seeing traces analogous to the one below in Thunderbolt testing:
>
> WARNING: CPU: 3 PID: 76 at
On Wed, Nov 20, 2013 at 9:47 PM, Bjorn Helgaas wrote:
> [+cc Jiri]
>
> On Wed, Nov 20, 2013 at 9:26 PM, Sasha Levin wrote:
>> On 11/18/2013 03:39 PM, Bjorn Helgaas wrote:
>>>
>>> On Mon, Nov 18, 2013 at 11:29:32AM -0800, Yinghai Lu wrote:
On Mon, Nov 18, 2013 at 10:14 AM, Bjorn Helgaas
From: Fabio Estevam
Commit 22c1 (pwm-backlight: Add power supply support) introduced the usage
of regulator API into the pwm backlight driver and caused a regression on some
boards like mx28evk and mx6qsabresd, resulting in blank display output:
pwm-backlight backlight.18: dummy supplies
Jens - here's immutable biovecs, rebased and ready for 3.14. Changes since the
last version of the series:
* bio_clone_bioset() retains the old behaviour, as previously discussed -
bio_clone_fast() is being used by bcache, dm and the new bio_split().
There aren't that many users of the
Hi,
On Mon, Nov 25, 2013 at 08:32:46PM +0200, Ивайло Димитров wrote:
> So, AIUI there are 2 options:
>
> 1. charger driver polls the battery driver every n (60?) seconds.
> 2. battery driver sends PSY_EVENT_PROP_CHANGED on every degree
>up or down.
>
> In both cases if the temperature is
DRA7xx SoC has an AES IP found also on OMAP4. Add hwmod data for the same.
Signed-off-by: Joel Fernandes
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
Crypto modules AES0/1 belong to:
PD_L4_PER power domain
CD_L4_SEC clock domain
On the L3, the AES modules are mapped to
L3_CLK2: Peripherals and multimedia sub clock domain
We add hwmod data for the same.
Signed-off-by: Joel Fernandes
---
Use the newly added sysc type4 for AES module.
Signed-off-by: Joel Fernandes
---
arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c
Enabling of Posted mode is seen to cause problems on dmtimer modules on AM33xx
(much like other OMAPs). Reference discussions on forums [1] [2]. Earlier
patch solving this on other OMAPs [3].
For OMAP SoCs with this errata, the fix has been to not enable Posted mode.
However, on some SoCs
OMAP4 has a DES IP for DES and 3DES encryption, Add hwmod data for the same.
Signed-off-by: Joel Fernandes
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 47 ++
1 file changed, 47 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
Here are patches adding hwmod for AES/DES crypto modules for OMAP4, DRA7 SoCs.
Also included is a fix that disables POSTED mode when dmtimer is requested.
Joel Fernandes (7):
ARM: OMAP: hwmod: Add SYSC offsets for AES IP
ARM: DRA7xx: hwmod: Add hwmod data for DES IP
ARM: DRA7xx: hwmod: Add
DRA7xx SoC has a DES module. Add hwmod data for the same.
Signed-off-by: Joel Fernandes
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
The AES IP has the SIDLE offset by 2 and not 3, to allow SIDLE modes
to work for AES, we add a new SYSC type to hwmod.
Signed-off-by: Joel Fernandes
---
arch/arm/mach-omap2/omap_hwmod.h | 11 +++
arch/arm/mach-omap2/omap_hwmod_common_data.c | 10 ++
2 files changed,
On 11/25/2013 08:11 AM, Viresh Kumar wrote:
> This patchset adds cpufreq callbacks to dpm_{suspend|resume}() for handling
> suspend/resume of cpufreq governors and core. This is required for early
> suspend
> and late resume of governors and cpufreq core.
>
> There are multiple problems that are
Hi,
On Mon, Nov 11, 2013 at 08:06:12PM +0530, Kishon Vijay Abraham I wrote:
> >> diff --git a/drivers/usb/dwc3/platform_data.h
> >> b/drivers/usb/dwc3/platform_data.h
> >> index 7db34f0..49ffa6d 100644
> >> --- a/drivers/usb/dwc3/platform_data.h
> >> +++ b/drivers/usb/dwc3/platform_data.h
> >>
On Mon, 2013-11-25 at 13:54 -0700, Shuah Khan wrote:
> Mimi,
>
> Do you have fix for the following build error as well.
>
> CC security/integrity/digsig.o
> security/integrity/digsig.c:70:5: error: redefinition of
> ‘integrity_init_keyring’
> int integrity_init_keyring(const unsigned int
On 11/22/2013 05:29 AM, Viresh Kumar wrote:
> This patch adds cpufreq callbacks to dpm_{suspend|resume}_noirq() for handling
> suspend/resume of cpufreq governors. This is required for early suspend and
> late
> resume of governors.
>
> There are multiple problems that are fixed by this patch:
>
Commit-ID: ac01810c9d2814238f08a227062e66a35a0e1ea2
Gitweb: http://git.kernel.org/tip/ac01810c9d2814238f08a227062e66a35a0e1ea2
Author: Laxman Dewangan
AuthorDate: Mon, 25 Nov 2013 19:39:47 +0530
Committer: Thomas Gleixner
CommitDate: Mon, 25 Nov 2013 22:20:02 +0100
irq: Enable all
Hi,
On Fri, Nov 22, 2013 at 03:55:59PM +, Mark Jackson wrote:
> The IDDIG input pin is normally used to determine the USB mode
> (i.e. HOST or DEVICE).
>
> On some systems (e.g. AM335x) leaving this pin floating allows
> the USB mode to be set via software.
>
> This patch adds support for
On Mon, Nov 25, 2013 at 1:14 PM, Olof Johansson wrote:
> Not used outside of the file, so declaration should be static. Picked up by
> sparse:
>
> drivers/platform/chrome/chromeos_laptop.c:44:12: warning: symbol
> 'i2c_adapter_names' was not declared. Should it be static?
>
> Signed-off-by:
On Mon, Nov 25, 2013 at 04:00:23PM -0500, Peter Hurley wrote:
> On 11/25/2013 03:43 PM, Greg Kroah-Hartman wrote:
> >On Fri, Nov 22, 2013 at 01:06:07PM -0500, Peter Hurley wrote:
> >>**This patchset requires 'Halve tty buffer memory consumption' patchset **
> >
> >Requires it to build or just work
On 11/25/2013 12:56 AM, dyo...@redhat.com wrote:
>
> For efi runtime mapping I add a new directory /sys/firmware/efi/
> runtime-map/ like below
> [dave@darkstar ~]$ tree /sys/firmware/efi/runtime-map/
> /sys/firmware/efi/runtime-map/
> ├── 0
> │ ├── attribute
> │ ├──
On Mon, Nov 25, 2013 at 03:31:24PM +0530, Kishon Vijay Abraham I wrote:
> There can be systems which does not have an external phy, so get
> phy only if no quirks are added that indicates the PHY is not present.
> Introduced two quirk flags to indicate the *absence* of usb2 phy and
> usb3 phy.
On 25/11/2013 16:34, Linus Walleij wrote:
On Wed, Nov 20, 2013 at 1:02 AM, Kyungmin Park wrote:
On Wed, Nov 20, 2013 at 4:16 AM, Stephen Warren wrote:
I think that last point should be addressed by having a driver that owns
the GPIO set it to the desired output level, and the implementation
Not used outside of the file, so declaration should be static. Picked up by
sparse:
drivers/platform/chrome/chromeos_laptop.c:44:12: warning: symbol
'i2c_adapter_names' was not declared. Should it be static?
Signed-off-by: Olof Johansson
Cc: Benson Leung
---
Hi Benson,
On Sun, Oct 20, 2013 at 8:58 PM, Benson Leung wrote:
> The following patch series refactors the dmi check system and
> returns -EPROBE_DEFER when an expected i2c adapter is not present
> at probe time.
>
> This will allow the touchpad, touchscreen, and light sensors on
> Pixel to load
> Reported-by: Nicholas
> Signed-off-by: Michele Baldessari
> Tested-by: Nicholas
Acked-by: Alan Cox
Going for a dig in google turns this up against multiple controllers,
multiple kernels, multiple distros..
> ---
> drivers/ata/libata-core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
>
On Mon, Nov 25, 2013 at 9:40 AM, Mark Brown wrote:
>
> Mark Brown (4):
> Merge remote-tracking branch 'regulator/fix/arizona' into
> regulator-linus
> Merge remote-tracking branch 'regulator/fix/fixed' into regulator-linus
> Merge remote-tracking branch 'regulator/fix/gpio'
Hi,
On Tue, Nov 12, 2013 at 01:04:46PM -0800, David Cohen wrote:
> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> index 5452c0fce360..7c2d36f6ad4b 100644
> --- a/drivers/usb/dwc3/gadget.c
> +++ b/drivers/usb/dwc3/gadget.c
> @@ -1130,6 +1130,14 @@ static int
On Mon, Nov 25, 2013 at 12:05 PM, Mateusz Guzik wrote:
> On Mon, Nov 25, 2013 at 11:53:24AM -0800, Shawn Landden wrote:
>> On Mon, Nov 25, 2013 at 10:05 AM, Jason Baron wrote:
>> > On 11/22/2013 12:53 PM, Shawn Landden wrote:
>> >> Hello, when running the attached program on 3.12 child processes
On Monday, November 25, 2013 09:43:59 AM Dirk Brandewie wrote:
> On 11/25/2013 09:01 AM, Viresh Kumar wrote:
> > On 25 November 2013 22:08, Dirk Brandewie wrote:
> >> IMHO this issue should be fixed in the scaling driver for the platform.
> >>
> >> The scaling driver sets policy->cur and fills in
On 11/25/2013 03:43 PM, Greg Kroah-Hartman wrote:
On Fri, Nov 22, 2013 at 01:06:07PM -0500, Peter Hurley wrote:
**This patchset requires 'Halve tty buffer memory consumption' patchset **
Requires it to build or just work properly?
I'm trying to figure out what tree to take this in, (tty-next
From: Jason Low
- Remove unnecessary head variables.
- Delete unused parameter in queue_unlock().
Signed-off-by: Jason Low
Signed-off-by: Davidlohr Bueso
Link: http://lkml.kernel.org/r/1385168197-8612-2-git-send-email-davidl...@hp.com
Signed-off-by: Thomas Gleixner
---
kernel/futex.c | 40
The patch set from Davidlohr [1] tried to attempt the same via an
atomic counter of waiters in a hash bucket. The atomic counter access
provided enough serialization for x86 so that a failure is not
observable in testing, but does not provide any guarantees.
The same can be achieved with a
Preparatory patch for a lockless empty check of the hash bucket plist
in futex_wake().
No functional change.
Signed-off-by: Thomas Gleixner
---
kernel/futex.c | 24
1 file changed, 16 insertions(+), 8 deletions(-)
Index: linux-2.6/kernel/futex.c
This changes the queue ordering on the waiter side from
lock(hash_bucket);
validate user space value();
queue();
unlock(hash_bucket);
to
lock(hash_bucket);
queue();
validate user space value();
unlock(hash_bucket);
This is a preparatory patch for a
201 - 300 of 1960 matches
Mail list logo
