ping
On Sat, Sep 06, 2014 at 08:46:31PM +0200, Jiri Olsa wrote:
> hi,
> Jan Stancek found test 1 breakage, probably caused by following patch:
> 950b8354716e perf tools: Demangle kernel and kernel module symbols too
>
> it seems to break test 1:
> ---
> [jolsa@krava perf]$ ./perf test -v 1
>
On 09/12/2014 01:11 AM, Thomas Gleixner wrote:
> So what you are saying is, that if user space sets the pointer to NULL
> via the unregister prctl, kernel can safely ignore vmas which have the
> VM_MPX flag set. I really can't follow that logic.
>
> mmap_mpx();
> prctl(enable mpx);
>
On 2014-09-12 08:47, Ming Lei wrote:
@@ -31,7 +33,15 @@ extern struct ida blk_queue_ida;
static inline struct blk_flush_queue *blk_get_flush_queue(
struct request_queue *q, struct blk_mq_ctx *ctx)
{
- return q->fq;
+ struct blk_mq_hw_ctx *hctx;
+
+ if
On 2014-09-12 08:47, Ming Lei wrote:
Failure of initializing one hctx isn't handled, so this patch
introduces blk_mq_init_hctx() and its pair to handle it explicitly.
Also this patch makes code cleaner.
I like this, it's a good cleanup.
--
Jens Axboe
--
To unsubscribe from this list: send
On Fri, Sep 12, 2014 at 03:51:02PM +0100, Catalin Marinas wrote:
> On Fri, Sep 12, 2014 at 03:00:03PM +0100, Hanjun Guo wrote:
> > --- a/drivers/acpi/Makefile
> > +++ b/drivers/acpi/Makefile
> > @@ -23,7 +23,11 @@ acpi-y += nvs.o
> >
> > # Power management related
On 2014-09-12 08:47, Ming Lei wrote:
These two functions are introduced to initialize and de-initialize
flush stuff centrally.
I know you said these change later to more proper naming, but that only
happens further down. Lets get rid of these wrappers and just call
blk_alloc_flush_queue()
On Fri, Sep 12, 2014 at 04:56:18PM +0200, Krzysztof Kozlowski wrote:
> The AMBA bus driver defines runtime Power Management functions which
> disable and unprepare AMBA bus clock. This is problematic for runtime PM
> because unpreparing a clock might sleep so it is not interrupt safe.
>
> However
Hi,
On Fri, Sep 12, 2014 at 1:17 AM, Javier Martinez Canillas
wrote:
> From: Doug Anderson
>
> The max77686 includes an RTC that keeps power during suspend. It's
> convenient to be able to use it as a wakeup source.
>
> NOTE: due to wakeup ordering problems this patch alone doesn't work so
>
On Fri, Sep 12, 2014 at 3:48 AM, Dave Airlie wrote:
>
> Well I'm not shocked that an SMI GPU is out of spec, just not sure how
> we can workaround it.
Try just removing the
#define scr_memcpyw(d, s, c) memcpy(d, s, c)
#define VT_BUF_HAVE_MEMCPYW
(and perhaps MEMMOVEW case too) from the
On Fri 2014-09-12 10:16:21, Alan Stern wrote:
> On Fri, 12 Sep 2014, Petr Mladek wrote:
>
> > There is no need to have separate kthread for handling USB hub events.
> > It is more elegant to use the workqueue framework.
> >
> > The workqueue is allocated as unbound, cpu intensive, and freezable.
The AMBA bus driver defines runtime Power Management functions which
disable and unprepare AMBA bus clock. This is problematic for runtime PM
because unpreparing a clock might sleep so it is not interrupt safe.
However some drivers may want to implement runtime PM functions in
interrupt-safe way
Hi,
This is second request for comments for adding runtime PM to the pl330
driver.
The runtime PM of pl330 driver requires interrupt safe suspend/resume
callbacks which is in conflict with amba bus driver. The latter
also unprepares and prepares the AMBA bus clock which is not safe
for atomic
This patch adds both normal PM suspend/resume support and runtime PM
support to pl330 DMA engine driver.
The runtime power management for pl330 DMA driver allows gating of AMBA
clock (PDMA) in FSYS clock domain, when the device is not processing any
requests. This is necessary to enter W-AFTR low
On Thu, Sep 11, 2014 at 6:23 PM, Bjorn Helgaas wrote:
> These are intended to resolve problems on dual GPU systems where the radeon
> driver becomes unusable because of problems suspending or resuming a GPU.
> When the GPU is powered off, we may get hotplug remove events, and we
> would normally
Update fuse to support mounts from within user namespaces. This
is mostly a matter of translating uids and gids into the
namespace of the process reading requests before handing the
requests off to userspace.
Due to security concerns the namespace used should be fixed,
otherwise a user might be
On Fri, Sep 12, 2014 at 03:00:03PM +0100, Hanjun Guo wrote:
> --- a/drivers/acpi/Makefile
> +++ b/drivers/acpi/Makefile
> @@ -23,7 +23,11 @@ acpi-y += nvs.o
>
> # Power management related files
> acpi-y += wakeup.o
> +ifeq ($(ARCH),
On Fri, 2014-09-12 at 09:37 +0200, Peter Zijlstra wrote:
> On Thu, Sep 11, 2014 at 09:41:30PM -0700, Davidlohr Bueso wrote:
> > We can easily do so with our new reader lock support. Just an arbitrary
> > design default: readers have higher (5x) critical region latencies than
> > writers: 50 ms and
These fields are always used with the flush request, so
initialize them together.
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/blk-core.c |3 ---
block/blk-flush.c |4
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/block/blk-core.c
This patch introduces 'struct blk_flush_queue' and puts all
flush machinery related fields into this structure, so that
- flush implementation details aren't exposed to driver
- it is easy to convert to per dispatch-queue flush machinery
This patch is basically a mechanical
This patch supports to run one single flush machinery for
each blk-mq dispatch queue, so that:
- current init_request and exit_request callbacks can
cover flush request too, then the buggy copying way of
initializing flush request's pdu can be fixed
- flushing performance gets improved in case
This patch trys to use local variable to access flush request,
so that we can convert to per-queue flush machinery a bit easier.
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/blk-flush.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git
Failure of initializing one hctx isn't handled, so this patch
introduces blk_mq_init_hctx() and its pair to handle it explicitly.
Also this patch makes code cleaner.
Signed-off-by: Ming Lei
---
block/blk-mq.c | 114 ++--
1 file changed, 69
This patch adds 'blk_mq_ctx' parameter to blk_get_flush_queue(),
so that this function can find the corresponding blk_flush_queue
bound with current mq context since the flush queue will become
per hw-queue.
For legacy queue, the parameter can be simply 'NULL'.
For multiqueue case, the parameter
Just figuring out flush queue at the entry of kicking off flush
machinery and request's completion handler, then pass it through.
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/blk-flush.c | 30 --
1 file changed, 16 insertions(+), 14
Hi,
As recent discussion, especially suggested by Christoph, this patchset
implements per-distpatch_queue flush machinery, so that:
- current init_request and exit_request callbacks can
cover flush request too, then the buggy copying way of
initializing flush request's
These two functions are introduced to initialize and de-initialize
flush stuff centrally.
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/blk-core.c |5 ++---
block/blk-flush.c | 19 ++-
block/blk-mq.c|2 +-
block/blk-mq.h|1 -
It is reasonable to allocate flush req in blk_mq_init_flush().
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/blk-flush.c | 11 ++-
block/blk-mq.c| 16 ++--
block/blk-mq.h|2 +-
3 files changed, 17 insertions(+), 12 deletions(-)
diff --git
Hi,
On Friday 12 September 2014 07:37 PM, Heikki Krogerus wrote:
> On Thu, Sep 11, 2014 at 09:03:06PM +0530, Kishon Vijay Abraham I wrote:
>>> +static struct phy *phy_find(struct device *dev, const char *con_id)
>>> +{
>>> + const char *dev_id = dev ? dev_name(dev) : NULL;
>>> + int match,
On 12/09/14 15:16, Richard Weinberger wrote:
On Thu, Sep 11, 2014 at 6:25 PM, Rob Jones wrote:
On 01/09/14 16:36, Al Viro wrote:
On Mon, Sep 01, 2014 at 02:17:08PM +0100, Rob Jones wrote:
void *__seq_open_private(struct file *f, const struct seq_operations
*ops,
- int
Currently root is restricted from performing some modifications
to inodes whose owner is INVALID_UID or group is INVALID_GID
because this id doesn't map into any user namespace. Add a
special case to the relevant checks to make sure root is always
capable of performing these operations.
If the process reading on the fuse fd is executing in a pid
namespace then giving it the global pid of the process making
a request doesn't make sense. Instead, capture the pid namespace
when the filesystem is first mounted and translate pids into this
namespace before passing them to userspace.
Filesystem uids which don't map into a user namespace may result
in inode->i_uid being INVALID_UID. A symlink and its parent
could have different owners in the filesystem can both get
mapped to INVALID_UID, which may result in following a symlink
when this would not have otherwise been permitted.
Third round of patches for making it possible to mount with fuse from
within user namespaces. The only change since v2 is the addition of a
patch to ensure real root is capable towards inodes whose uid/gid is
invalid.
Thanks,
Seth
Seth Forshee (4):
vfs: Check for invalid i_uid in
Hi Linus,
Please can you pull these two arm64 fixes for -rc5? The IRQ migration fix
turned up late last time and there's also a TLS leaking issue that we
just fixed for arch/arm/ too.
To keep things interesting, I've signed the tag using my Yubikey from KS.
Given that it only supports 2048-bit
On 09/12/2014 02:24 AM, Thomas Gleixner wrote:
> On Fri, 12 Sep 2014, Thomas Gleixner wrote:
>> On Thu, 11 Sep 2014, Dave Hansen wrote:
>>> Well, we use it to figure out whether we _potentially_ need to tear down
>>> an VM_MPX-flagged area. There's no guarantee that there will be one.
>>
>> So
Replace ext_csd "enhanced_area_en" attribute by
"partition_setting_completed". It was used whether or
not enhanced user area is defined and without checks of
EXT_CSD_PARTITION_SETTING_COMPLETED bit.
Signed-off-by: Grégory Soutadé
---
drivers/mmc/core/mmc.c | 14 +-
Move code that manages user area and general purpose
partitions into functions.
Signed-off-by: Grégory Soutadé
---
drivers/mmc/core/mmc.c | 162 ++--
1 file changed, 89 insertions(+), 73 deletions(-)
diff --git a/drivers/mmc/core/mmc.c
JEDEC standard requires that EXT_CSD_PARTITION_SETTING_COMPLETED bit
must be set in order to take in account enhanced area and general purpose
partitions (gp) values.
Current code doesn't checks this bit and blindly trust enhanced area and
gp values. Moreover, "enhanced_area_en" attribute was set
Checks EXT_CSD_PARTITION_SETTING_COMPLETED bit before
computing enhanced user area offset and size, and
adding mmc general purpose partitions. The two needs
EXT_CSD_PARTITION_SETTING_COMPLETED bit be set to be
valid (as described in JEDEC standard).
Warn user in case of misconfiguration.
On Fri, 12 Sep 2014, Petr Mladek wrote:
> The USB hub events are proceed by workqueue instead of kthread now.
> The result is that hub_event() function processes only one event.
> The while cycle was not removed earlier to show the real changes when
> switching to the workqueue.
>
> This patch
On Fri, 12 Sep 2014, Petr Mladek wrote:
> There is no need to have separate kthread for handling USB hub events.
> It is more elegant to use the workqueue framework.
>
> The workqueue is allocated as unbound, cpu intensive, and freezable.
> There does not seem to be any big advantage to run it
Em Fri, Sep 12, 2014 at 04:16:32PM +0200, Jiri Olsa escreveu:
> On Fri, Sep 12, 2014 at 10:44:29AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Sep 12, 2014 at 02:58:22PM +0200, Jiri Olsa escreveu:
> > > On Wed, Sep 10, 2014 at 11:08:46AM -0300, Arnaldo Carvalho de Melo wrote:
> > > > +
On Fri 2014-09-12 10:06:03, Alan Stern wrote:
> On Fri, 12 Sep 2014, Petr Mladek wrote:
>
> > usb_autopm_put_interface() must be called only when
> > usb_autopm_get_interface()
> > succeeded before. There was wrong ordering of the goto targets.
>
> No, you are wrong. The code is correct as it
On Fri, Sep 12, 2014 at 10:44:29AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 12, 2014 at 02:58:22PM +0200, Jiri Olsa escreveu:
> > On Wed, Sep 10, 2014 at 11:08:46AM -0300, Arnaldo Carvalho de Melo wrote:
>
> > SNIP
>
> > > +struct fdarray *fdarray__new(int nr_alloc, int
On Thu, Sep 11, 2014 at 6:25 PM, Rob Jones wrote:
>
>
> On 01/09/14 16:36, Al Viro wrote:
>>
>> On Mon, Sep 01, 2014 at 02:17:08PM +0100, Rob Jones wrote:
>>
>>> void *__seq_open_private(struct file *f, const struct seq_operations
>>> *ops,
>>> - int psize)
>>> +
Hi,
On Friday 12 September 2014 07:19 PM, Heikki Krogerus wrote:
> On Thu, Sep 11, 2014 at 08:31:19PM +0530, Kishon Vijay Abraham I wrote:
>>> @@ -60,22 +59,33 @@ int dwc3_host_init(struct dwc3 *dwc)
>>> goto err1;
>>> }
>>>
>>> + phy_create_lookup(dwc->usb2_generic_phy,
On 2014-09-07 04:42, Ben Hutchings wrote:
> On Fri, 2014-09-05 at 09:09 -0300, Thadeu Lima de Souza Cascardo wrote:
>> On Fri, Sep 05, 2014 at 05:55:18PM +1000, Michael Neuling wrote:
>>> On Fri, 2014-09-05 at 09:13 +0200, Gabriel Paubert wrote:
On Fri, Sep 05, 2014 at 03:28:47PM +1000,
Em Fri, Sep 12, 2014 at 03:14:51PM +0900, Namhyung Kim escreveu:
> On Fri, 5 Sep 2014 12:44:02 -0300, Arnaldo Carvalho de Melo wrote:
> > It seems we need a way to state that an entry in the build-id table is
> > for the kernel, without looking at its file name.
> Maybe we can add a new
Reduce boilerplate code by using __seq_open_private() instead of seq_open().
Signed-off-by: Rob Jones
---
fs/proc/task_nommu.c | 22 --
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/fs/proc/task_nommu.c b/fs/proc/task_nommu.c
index 678455d..b141050 100644
Use __seq_open_private() to reduce boilerplate code in proc.
This function has been around, undocumented, for years. It can simplify
the set up code for seq file operations.
Signed-off-by: Rob Jones
Rob Jones (2):
fs: proc: use __seq_open_private()
fs: proc: use __seq_open_private()
Reduce boilerplate code by using __seq_open_private() instead of seq_open().
Signed-off-by: Rob Jones
---
fs/proc/task_mmu.c | 42 --
1 file changed, 16 insertions(+), 26 deletions(-)
diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
index
On Thu, Sep 11, 2014 at 09:03:06PM +0530, Kishon Vijay Abraham I wrote:
> > +static struct phy *phy_find(struct device *dev, const char *con_id)
> > +{
> > + const char *dev_id = dev ? dev_name(dev) : NULL;
> > + int match, best_found = 0, best_possible = 0;
> > + struct phy *phy =
From: Bartlomiej Zolnierkiewicz
ST SPEAR1340-MIPHY support should be available only on
ST SPEAr1340 machine.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
Cc: Pratyush Anand
Cc: Mohit Kumar
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/Kconfig |1 +
1 file
From: Lee Jones
We index the RX/TX speed select values in the following way:
rx_tx_spd[miphy_phy->sata_gen];
However rx_tx_spd[] starts at index zero and the SATA_GENx's start
at one. In this patch we pad out the first element in rx_tx_spd[]
in an attempt to realign the values.
Cc:
On Fri, 12 Sep 2014, Petr Mladek wrote:
> usb_autopm_put_interface() must be called only when usb_autopm_get_interface()
> succeeded before. There was wrong ordering of the goto targets.
No, you are wrong. The code is correct as it stands.
> The funny thing is that the names of the goto
Hi Greg,
here's one more PULL REQUEST for this -rc cycle. It consists of only
three fixes one in miphy365 PHY driver and the other two in Kconfig.
Please consider merging this in ths -rc cycle. Let me know if I have to
change something.
Cheers
Kishon
The following changes since commit
On 09/12/2014 10:22 AM, Ching Huang wrote:
> From: Ching Huang
>
> This patch is to modify previous patch 16/17 and it is relative to
> http://git.infradead.org/users/hch/scsi-queue.git/tree/arcmsr-for-3.18:/drivers/scsi/arcmsr
>
> change in v4:
> 1. clean up of duplicate variable declaration in
From: Bartlomiej Zolnierkiewicz
ST SPEAR1310-MIPHY support should be available only on
ST SPEAr1310 machine.
Signed-off-by: Bartlomiej Zolnierkiewicz
Acked-by: Kyungmin Park
Cc: Pratyush Anand
Cc: Mohit Kumar
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/Kconfig |1 +
1 file
Using the information presented by GTDT to initialize the arch
timer (not memory-mapped).
Originally-by: Amit Daniel Kachhap
Signed-off-by: Hanjun Guo
---
arch/arm64/kernel/time.c |7 ++
drivers/clocksource/arm_arch_timer.c | 117 --
From: Tomasz Nowicki
It is very useful to traverse all available table entries without max
number of expected entries type. Current acpi_parse_entries()
implementation gives that feature but it does not count those entries,
it returns 0 instead, so fix it to count matched and successfully
There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
the former signals to the OS that the firmware is PSCI compliant.
The latter selects the appropriate conduit for PSCI calls by
toggling between Hypervisor Calls (HVC) and Secure Monitor Calls
(SMC).
FADT table contains such
On Fri, Sep 12, 2014 at 11:27:41AM +0200, Andrzej Hajda wrote:
> On 09/12/2014 10:57 AM, Daniel Vetter wrote:
> > On Fri, Sep 12, 2014 at 05:34:50PM +0900, Inki Dae wrote:
> >> Hi Andrzej,
> >>
> >> On 2014년 09월 09일 22:16, Andrzej Hajda wrote:
> >>> Adding reference to framebuffer should be
From: Al Stone
Introduce one early parameters "off" for "acpi" to disable ACPI on
ARM64.
This ensures the kernel uses the DT on a platform that provides both
ACPI tables and DT.
Signed-off-by: Al Stone
Signed-off-by: Graeme Gregory
Signed-off-by: Hanjun Guo
---
From: Graeme Gregory
Add documentation for the guidelines of how to use ACPI
on ARM64.
Signed-off-by: Graeme Gregory
Signed-off-by: Hanjun Guo
---
Documentation/arm64/arm-acpi.txt | 218 ++
1 file changed, 218 insertions(+)
create mode 100644
From: Tomasz Nowicki
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
abstraction agnostic). In a similar way, FDT initialize GICv1/2.
When MADT is parsed, print GIC information to make the boot
log look pretty.
Signed-off-by: Hanjun Guo
Signed-off-by: Tomasz Nowicki
---
drivers/acpi/tables.c | 43 +++
1 file changed, 43 insertions(+)
diff --git a/drivers/acpi/tables.c
Introduce a new function map_gicc_mpidr() to allow MPIDRs to be obtained
from the GICC Structure introduced by ACPI 5.1.
MPIDR is the CPU hardware ID as local APIC ID on x86 platform, so we use
MPIDR not the GIC CPU interface ID to identify CPUs.
Signed-off-by: Hanjun Guo
---
From: Graeme Gregory
Add Kconfigs to build ACPI on ARM64, and make ACPI available on ARM64.
acpi_idle driver is x86/IA64 dependent now, so make CONFIG_ACPI_PROCESSOR
depend on X86 || IA64, and implement it on ARM64 in the future.
Reviewed-by: Grant Likely
Signed-off-by: Graeme Gregory
MADT contains the information for MPIDR which is essential for
SMP initialization, parse the GIC cpu interface structures to
get the MPIDR value and map it to cpu_logical_map(), and add
enabled cpu with valid MPIDR into cpu_possible_map.
ACPI 5.1 only has two explicit methods to boot up SMP, PSCI
Introduce ACPI_IRQ_MODEL_GIC which is needed for ARM64 as GIC is
used, and then register device's gsi with the core IRQ subsystem.
acpi_register_gsi() is similar to DT based irq_of_parse_and_map(),
since gsi is unique in the system, so use hwirq number directly
for the mapping.
Originally-by:
From: Al Stone
ACPI reduced hardware mode is disabled by default, but ARM64
can only run properly in ACPI hardware reduced mode, so select
ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled on ARM64.
Reviewed-by: Grant Likely
Signed-off-by: Al Stone
Signed-off-by: Hanjun Guo
---
From: Graeme Gregory
If the early boot methods of acpi are happy that we have valid ACPI
tables and acpi=off has not been passed. Then do not unflat
devicetree effectively disabling further hardware probing from DT.
Signed-off-by: Graeme Gregory
Signed-off-by: Hanjun Guo
---
As PCI for ARM64 is not ready, so introduce some stub functions
to make PCI optional for ACPI, and make ACPI core run without
CONFIG_PCI on ARM64.
Since ACPI on X86 and IA64 depends on PCI and this patch only makes
PCI optional for ARM64, it will not break anything on X86 and IA64.
From: Graeme Gregory
ACPI 5.1 does not currently support S states for ARM64 hardware but
ACPI code will call acpi_target_system_state() for device power
managment, so introduce sleep-arm.c to allow other drivers to function
until S states are defined.
Signed-off-by: Graeme Gregory
From: Al Stone
As we want to get ACPI tables to parse and then use the information
for system initialization, we should get the RSDP (Root System
Description Pointer) first, it then locates Extended Root Description
Table (XSDT) which contains all the 64-bit physical address that
pointer to
From: Ashwin Chaugule
The acpi_table_parse() function has a callback that
passes a pointer to a table_header. Add a new function
which takes this pointer and parses its entries. This
eliminates the need to re-traverse all the tables for
each call. e.g. as in acpi_table_parse_madt() which is
It always make sense to initialize CPU0's logical map entry from the
hardware values, so move the initialization of cpu_logical_map(0)
before unflatten_device_tree() which is needed by ACPI code later.
Signed-off-by: Hanjun Guo
---
arch/arm64/kernel/setup.c |2 +-
1 file changed, 1
ACPI 5.1 has been released and now be freely available for
download [1]. It fixed some major gaps to run ACPI on ARM,
this patch just follow the ACPI 5.1 spec and prepare the
code to run ACPI on ARM64.
ACPI 5.1 has some major changes for the following tables and
method which are essential for ARM
On 09/12/2014 08:57 AM, Pawel Moll wrote:
> On Fri, 2014-09-12 at 13:43 +0100, Christopher Covington wrote:
>> Just to ask the dumb questions in case the answers I've come up with are
>> wrong: What is PAGE_SIZE on an arm64 kernel?
>
> It's either 4 or 64k, depending on CONFIG_ARM64_64K_PAGES.
>
On Fri, 2014-09-12 at 14:49 +0100, Arnaldo Carvalho de Melo wrote:
> Perhaps both? I.e. an u64 followed from a string, if the u64 is zero,
> then there is a string right after it?
How would this look like in userspace? Something like this?
8<
struct perf_event_marker {
uint64_t
Peter,
On Thu, Sep 11, 2014 at 08:28:59AM +0800, Peter Chen wrote:
> On Wed, Sep 03, 2014 at 09:40:38AM +0200, Antoine Tenart wrote:
>
> Again, rebase my next-tree, and modify the msm part.
git://github.com/hzpeterchen/linux-usb.git ci-for-usb-next ?
I can do that. But that would be easier if
On Thu, Sep 11, 2014 at 08:56:15PM +0530, Kishon Vijay Abraham I wrote:
> > +static struct phy_lookup twl4030_usb_lookup = {
> > + .phy_name = "phy-twl4030_usb.0",
> > + .dev_id = "musb-hdrc.0",
> > + .con_id = "usb",
> > };
>
> Can use PHY_LOOKUP no?
I'll fix this.
On Thu, Sep 11, 2014 at 08:31:19PM +0530, Kishon Vijay Abraham I wrote:
> > @@ -60,22 +59,33 @@ int dwc3_host_init(struct dwc3 *dwc)
> > goto err1;
> > }
> >
> > + phy_create_lookup(dwc->usb2_generic_phy, "usb2-phy",
> > + dev_name(>dev));
> > +
> diff --git a/include/linux/i2c.h b/include/linux/i2c.h
> index 79b674d..c8240e5 100644
> --- a/include/linux/i2c.h
> +++ b/include/linux/i2c.h
> @@ -125,7 +125,8 @@ extern s32 i2c_smbus_write_i2c_block_data(const struct
> i2c_client *client,
> * struct i2c_driver - represent an I2C device
Em Fri, Sep 12, 2014 at 01:57:52PM +0100, Pawel Moll escreveu:
> On Fri, 2014-09-12 at 13:43 +0100, Christopher Covington wrote:
> > Just to ask the dumb questions in case the answers I've come up with are
> > wrong: What is PAGE_SIZE on an arm64 kernel?
> It's either 4 or 64k, depending on
Il 12/09/2014 07:43, guohliu ha scritto:
> This patch replace the set_bit method by kvm_make_request
> to makes it more readable and consistency.
>
> Signed-off-by: Guo Hui Liu
> ---
> arch/x86/kvm/x86.c | 15 +++
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git
Hi Linus,
The following changes since commit 69e273c0b0a3c337a521d083374c918dc52c666f:
Linux 3.17-rc3 (2014-08-31 18:23:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-fixes-v3.17-rc4
for you to fetch changes up to
On Thu, Aug 28, 2014 at 03:35:30PM +0100, Lee Jones wrote:
> Hi Wolfram,
>
> Placing this firmly back on your plate. I truly hope we don't miss
> another merge-window. This patch-set has the support of some pretty
> senior kernel maintainers, so I hope acceptance shouldn't be too
> difficult.
>
On Thu, Aug 28, 2014 at 03:35:32PM +0100, Lee Jones wrote:
> A great deal of I2C devices are currently matched via DT node name, and
> as such the compatible naming convention of ',' has gone
> somewhat awry - some nodes don't supply one, some supply an arbitrary
> string and others the correct
Em Fri, Sep 12, 2014 at 02:58:22PM +0200, Jiri Olsa escreveu:
> On Wed, Sep 10, 2014 at 11:08:46AM -0300, Arnaldo Carvalho de Melo wrote:
> SNIP
> > +struct fdarray *fdarray__new(int nr_alloc, int nr_autogrow)
> > +{
> > + struct fdarray *fda = calloc(1, sizeof(*fda));
> > + if (fda !=
On 09/12/14 at 08:04am, Vivek Goyal wrote:
> On Fri, Sep 12, 2014 at 02:20:31PM +0800, Baoquan He wrote:
> > Function handle_relocations() is used to do the relocations handling
> > for i686 and kaslr of x86_64. For 32 bit the relocation handling is
> > mandotary to perform. For x86_64 only when
1)Nobody calls pick_dl_task with negative cpu, it's old RT leftover.
2)If p->nr_cpus_allowed is 1, than the affinity has just been changed
in set_cpus_allowed_ptr(); we'll pick it just earlier than migration
thread.
Signed-off-by: Kirill Tkhai
---
kernel/sched/deadline.c |4 +---
1 file
_pick_next_task_rt() never returns NULL.
Signed-off-by: Kirill Tkhai
---
kernel/sched/rt.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
index 4feac8f..2e6a774 100644
--- a/kernel/sched/rt.c
+++ b/kernel/sched/rt.c
@@ -1468,8
new_cpu is reassigned below, so we do not need this here.
Signed-off-by: Kirill Tkhai
---
kernel/sched/fair.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index be9e97b..3d1c08a 100644
--- a/kernel/sched/fair.c
+++
schedule(), io_schedule() and schedule_timeout() always return
with TASK_RUNNING state set, so one more setting is unnecessary.
(All places in patch are visible good, only exception is
kiblnd_scheduler() from:
drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c
Its schedule() is one
Signed-off-by: Kirill Tkhai
---
kernel/sched/core.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 07d67dd..d4399b4 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -2998,7 +2998,7 @@ void
This is a series of scheduler-related cleanups which I were collecting
for some time.
Nothing interesting, just boring cleanups...
---
Kirill Tkhai (5):
cleanup, treewide: Remove set_current_state(TASK_RUNNING) after schedule
sched/fair: cleanup: Remove useless assignment in
On 09/12/2014 06:10 AM, Thomas Gleixner wrote:
>>
>> I'm not wedded to that concept, by the way, but using the generic parser had
>> a
>> whole bunch of its own problems, including the fact that you're getting bytes
>> from user space.
>
> Errm. The instruction decoder does not even know about
On 09/12/2014 09:29 AM, Ching Huang wrote:
> From: Ching Huang
>
> This patch is to modify previous patch 13/17 and it is relative to
> http://git.infradead.org/users/hch/scsi-queue.git/tree/arcmsr-for-3.18:/drivers/scsi/arcmsr
>
> change in v4:
> 1. for readability, rename firstindex to
From: Rik van Riel
The sig->stats_lock nests inside the tasklist_lock and the
sighand->siglock in __exit_signal and wait_task_zombie.
However, both of those locks can be taken from irq context,
which means we need to use the interrupt safe variant of
read_seqbegin_or_lock. This blocks
401 - 500 of 1556 matches
Mail list logo
