On Mon, Sep 7, 2015 at 12:12 PM, Sedat Dilek wrote:
>
> is it possible to use a different compiler at build-time?
>
> I have here a problem with mm/percpu.c and wanted to build everything
> with LLVM/Clang but this single file with GCC.
>
> Is that possible?
It should work
The recently added endpoint capabilities flags verification breaks Atmel
USBA because the endpoint configuration was only added when the driver
is bound using the legacy pdata interface.
Convert endpoint configuration to new capabilities model when driver is
bound to a device tree as well.
[un]register_interest and reading cable state by
name have been deprecated. Switch to new API.
Signed-off-by: Ivan T. Ivanov
---
drivers/usb/phy/phy-qcom-8x16-usb.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git
On 09/07/15 13:08, Gerd Hoffmann wrote:
> Hi,
>
>> It's just simplicity. If you want to read a few times from the same
>> field (like in ACPI tables, read the data size and then the data), you
>> need a way to enable and disable the selector and manage the current
>> offset for that entry. This
On Thu, Sep 03, 2015 at 08:30:56AM -0400, kan.li...@intel.com wrote:
> From: Kan Liang
>
> This patch set supports per-sample freq/CPU%/CORE_BUSY% print in perf
> report -D and --stdio.
> For printing these information, the perf.data file must have been obtained
> by group
On Fri, 2015-06-05 at 17:26 +0800, Peter Chen wrote:
> On Fri, Jun 05, 2015 at 10:37:07AM +0300, Ivan T. Ivanov wrote:
>
> > > > +
> > > > +static int ci_id_notifier(struct notifier_block *nb, unsigned long
> > > > event,
> > > > + void *ptr)
> > > > +{
Thierry,
On 08/21/2015 11:39 AM, Archit Taneja wrote:
On 08/20/2015 05:18 PM, Thierry Reding wrote:
On Thu, Aug 20, 2015 at 09:46:14AM +0530, Archit Taneja wrote:
Hi Thierry, Lucas,
On 08/19/2015 08:32 PM, Thierry Reding wrote:
On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote:
On recent Qualcomm platforms VBUS and ID lines are not routed to
USB PHY LINK controller. Use extcon framework to receive connect
and disconnect ID and VBUS notification.
Signed-off-by: Ivan T. Ivanov
---
Changes sice v3 [1]:
* Migrate to new extcon framework API
*
On Fri, Sep 04, 2015 at 04:22:04PM +0530, Sudip Mukherjee wrote:
> The platform driver core will set the owner value, we do not need to do
> it in the module.
>
> Signed-off-by: Sudip Mukherjee
> ---
> drivers/staging/most/hdm-dim2/dim2_hdm.c | 1 -
> 1 file changed, 1
On Sun, Sep 06, 2015 at 10:00:57PM -0700, Alexander Duyck wrote:
> On 09/03/2015 05:35 AM, Kirill A. Shutemov wrote:
> >Since 8456a648cf44 ("slab: use struct page for slab management") nobody
> >uses slab_page field in struct page.
> >
> >Let's drop it.
> >
> >Signed-off-by: Kirill A. Shutemov
Hi Linus,
Please pull fbdev changes for 4.3. Not much this time.
The following changes since commit 2c6625cd545bdd66acff14f3394865d43920a5c7:
Linux 4.2-rc7 (2015-08-16 16:34:13 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git
Add a field to struct device that instructs the device-driver core to
defer the probe of this device until the late_initcall level.
By letting all built-in drivers to register before starting to probe, we
can avoid any deferred probes by probing dependencies on demand.
Signed-off-by: Tomeu
When looking up a clock through its OF node, probe it if it hasn't
already.
The goal is to reduce deferred probes to a minimum, as it makes it very
cumbersome to find out why a device failed to probe, and can introduce
very big delays in when a critical device is probed.
Signed-off-by: Tomeu
When looking up a DMA controller through its OF node, probe it if it
hasn't already.
The goal is to reduce deferred probes to a minimum, as it makes it very
cumbersome to find out why a device failed to probe, and can introduce
very big delays in when a critical device is probed.
Signed-off-by:
When looking up a power supply through its OF node, probe it if it
hasn't already.
The goal is to reduce deferred probes to a minimum, as it makes it very
cumbersome to find out why a device failed to probe, and can introduce
very big delays in when a critical device is probed.
Signed-off-by:
On Sat, Sep 05, 2015 at 08:02:21PM +0100, Matt Fleming wrote:
SNIP
> };
>
> +static struct test *tests[] = {
> + generic_tests,
> + arch_tests,
> +};
> +
> static bool perf_test__matches(struct test *test, int curr, int argc, const
> char *argv[])
> {
> int i;
> @@ -237,7
On Mon, Aug 31, 2015 at 11:24:49AM +0200, Peter Zijlstra wrote:
> A quick run here gives:
>
> IVB-EP (2*20*2):
As noted by someone; that should be 2*10*2, for a total of 40 cpus in
this machine.
>
> perf stat --null --repeat 10 -- perf bench sched messaging -g 50 -l 5000
>
> Before:
On Mon, Sep 7, 2015 at 10:15 PM, Linus Torvalds
wrote:
> On Mon, Sep 7, 2015 at 12:12 PM, Sedat Dilek wrote:
>>
>> is it possible to use a different compiler at build-time?
>>
>> I have here a problem with mm/percpu.c and wanted to build
Added user configuration option to enable/disable RDMA resource tracking
feature of device cgroup as sub module.
Signed-off-by: Parav Pandit
---
init/Kconfig | 12
1 file changed, 12 insertions(+)
diff --git a/init/Kconfig b/init/Kconfig
index
Currently user space applications can easily take away all the rdma
device specific resources such as AH, CQ, QP, MR etc. Due to which other
applications in other cgroup or kernel space ULPs may not even get chance
to allocate any rdma resources.
This patch-set allows limiting rdma resources to
Extension of device cgroup for RDMA device resources.
This implements RDMA resource tracker to limit RDMA resources such as
AH, CQ, PD, QP, MR, SRQ etc resources for processes of the cgroup.
It implements RDMA resource limit module to limit consuming RDMA
resources for processes of the cgroup.
1. Moved necessary functions and data structures to header file to
reuse them at device cgroup white list functionality and for rdma
functionality.
2. Added infrastructure to invoke RDMA specific routines for resource
configuration, query and during fork handling.
3. Added sysfs interface files
Added RDMA device resource tracking object per task.
Added comments to capture usage of task lock by device cgroup
for rdma.
Signed-off-by: Parav Pandit
---
include/linux/sched.h | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git
RDMA uverbs modules now queries associated device cgroup rdma controller
before allocating device resources and uncharge them while freeing
rdma device resources.
Since fput() sequence can free the resources from the workqueue
context (instead of task context which allocated the resource),
it
Added RDMA resource tracking object of device cgroup.
Signed-off-by: Parav Pandit
---
security/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/security/Makefile b/security/Makefile
index c9bfbc8..c9ad56d 100644
--- a/security/Makefile
+++ b/security/Makefile
Hi,
is it possible to use a different compiler at build-time?
I have here a problem with mm/percpu.c and wanted to build everything
with LLVM/Clang but this single file with GCC.
Is that possible?
Regards,
- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Hi Antoine,
Just one observation below.
El 26/08/15 a las 05:07, Antoine Tenart escribió:
> Add a PWM controller driver for the Marvell Berlin SoCs. This PWM
> controller has 4 channels.
>
> Signed-off-by: Antoine Tenart
> Acked-by: Sebastian Hesselbarth
On Mon, 7 Sep 2015, Arnd Bergmann wrote:
> On Thursday 03 September 2015 21:24:00 Nicolas Pitre wrote:
> > If 768MB targets were common place then it could be worth changing the
> > default vmalloc size to accommodate this memory size and testing all the
> > other targets to make sure no
2015-09-07 18:24 GMT+02:00 Javier Martinez Canillas :
> Only the IGEPv2 boards have a LAN9221i chip connected to the GPMC
> so the pinmux configuration for the GPIO connected to the IRQ line
> of the LAN chip should not be defined in the IGEP common dtsi but
> in the one
On Mon, 2015-09-07 at 19:08 +0100, Maitesin wrote:
> The coding style issue is the white spaces after and before the
> brackets in the for. The change in the conditional is to make it
> consistence with the other ones in the file. All other conditionals are
> tested like that.
[]
> diff --git
On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
>
> Hi Linus,
>
> This is the main pull request for the drm for 4.3. Nouveau is probably the
> biggest
> amount of changes in here, since it missed 4.2. Highlights below, along with
> the usual
> bunch of fixes. There are a
On 07/09/15 17:21, Vincent Guittot wrote:
> On 7 September 2015 at 17:37, Dietmar Eggemann
> wrote:
>> On 04/09/15 00:51, Steve Muckle wrote:
>>> Hi Morten, Dietmar,
>>>
>>> On 08/14/2015 09:23 AM, Morten Rasmussen wrote:
>>> ...
+ * cfs_rq.avg.util_avg is the sum
Hi Florian,
I wrote some observations below that maybe can be useful.
El 28/08/15 a las 22:21, Florian Fainelli escribió:
> Add support for the BCM7038-style PWM controller found in all BCM7xxx STB
> SoCs.
> This controller has a hardcoded 2 channels per controller, and cascades a
> variable
412758cb2670 (jump label, locking/static_keys: Update docs) introduced a
typo that might as well get fixed.
Signed-off-by: Jonathan Corbet
---
Documentation/static-keys.txt | 2 +-
include/linux/jump_label.h| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On Mon, 7 Sep 2015, Andy Lutomirski wrote:
> > These are all implementation-specific details, including the INT1
> > instruction, which is why I am not at all surprised that they are omitted
> > from architecture manuals.
>
> That bit is BS, though. The INT1 instruction, executed in user mode
On Mon, Sep 07, 2015 at 07:54:18PM +0100, Dietmar Eggemann wrote:
> I would vote for removing this SCHED_LOAD_RESOLUTION thing completely so that
> we can
> assume that load/util and capacity are always using 1024/10.
Ha!, I just requested Google look into moving it to 20 again ;-)
--
To
1101 - 1136 of 1136 matches
Mail list logo