>> GDM7240 is in LE where as GDM7243 (currently under development) is in BE.
>
> But why does this information need to be sent to userspace?
>
GDM724x chips have different endianess because of their internal
architecture.The device sends out and accepts LTE protocol information
in its own
On Wed, Jul 24, 2013 at 04:22:58PM +0300, Tomas Winkler wrote:
> Clear pending connection after hw reset but before hw start
> and wake up the waiting task in poll. Signal POLLERR in select
> when device went through reset.
>
> Add wrapper mei_cl_is_connected for checking if
> the device and
On Wed, Jul 24, 2013 at 6:24 PM, Steven Rostedt wrote:
>
> On Wed, 2013-07-24 at 12:04 -0400, Jörn Engel wrote:
> > On Fri, 5 July 2013 10:53:54 -0400, Steven Rostedt wrote:
> > >
> > > Can you find an easy reproducer for this?
> >
> > We might have found something:
> >
> > Jul 23 19:00:59
Hi,
On Thu, Jul 25, 2013 at 10:49 AM, Prashant Shah wrote:
> Hi,
>
>> You should also remove the definition of DRV_NAME, since it is no longer
>> used. The changelog should probably mention that this will change the
>> interrupt name (which appears in /proc/interrupts for example) from "wd"
>>
The function tty_port_tty_hangup() could leak a reference to the tty_struct:
struct tty_struct *tty = tty_port_tty_get(port);
if (tty && (!check_clocal || !C_CLOCAL(tty))) {
tty_hangup(tty);
tty_kref_put(tty);
}
If tty != NULL and the
On Thu, Jul 25, 2013 at 1:10 PM, Eric Dumazet wrote:
> On Thu, 2013-07-25 at 10:28 +0800, Ming Lei wrote:
>
>>
>> It depends if size of sg buffer(except for last one) in the sg list can be
>> divided by usb endpoint's max packet size(512 or 1024), at least there
>> is the constraint:
>>
>>
Hi,
> You should also remove the definition of DRV_NAME, since it is no longer
> used. The changelog should probably mention that this will change the
> interrupt name (which appears in /proc/interrupts for example) from "wd"
> to "eth%d".
>
I will resend the patch.
Regards.
--
To unsubscribe
Hi all,
Changes since 20130724:
Removed tree:
arm-dt (at maintainer's request)
The wireless-next tree lost its build failure and gained a conflict
against Linus' tree.
The tty tree lost its build failure.
The staging tree gained a build failure for which I disabled a driver
Inspired by commit f09e2249c4f5c7c13261ec73f5a7807076af0c8e (macvtap: restore
vlan header on user read). This patch adds hardware vlan tx support for
tuntap. This is done by copying vlan header directly into userspace in
tun_put_user() instead of doing it through __vlan_put_tag() in
On Thu, 2013-07-25 at 10:28 +0800, Ming Lei wrote:
>
> It depends if size of sg buffer(except for last one) in the sg list can be
> divided by usb endpoint's max packet size(512 or 1024), at least there
> is the constraint:
>
>
On Wed, May 29, 2013 at 11:29:07AM +0200, Olaf Hering wrote:
> Remove HV_DRV_VERSION, it has no meaning for upstream drivers.
>
> Initially it was supposed to show the "Linux Integration Services"
> version, now it is not in sync anymore with the out-of-tree drivers
> available from the MSFT
On Thu, Jul 25, 2013 at 10:19:31AM +0530, navin patidar wrote:
> >> -pr_warning("Unable to start control thread\n");
> >> +struct device *dev;
> >> +
> >> +if (ud->side == USBIP_STUB)
> >> +dev = _of(ud, struct stub_device, ud)->udev->dev;
> >> +else
>
This patch extends move_pages() to handle vma with VM_HUGETLB set.
We will be able to migrate hugepage with move_pages(2) after
applying the enablement patch which comes later in this series.
We avoid getting refcount on tail pages of hugepage, because unlike thp,
hugepage is not split and we
Until now we can't offline memory blocks which contain hugepages because
a hugepage is considered as an unmovable page. But now with this patch
series, a hugepage has become movable, so by using hugepage migration we
can offline such memory blocks.
What's different from other users of hugepage
Now hugepages are definitely movable. So allocating hugepages from
ZONE_MOVABLE is natural and we have no reason to keep this parameter.
In order to allow userspace to prepare for the removal, let's leave
this sysctl handler as noop for a while.
ChangeLog v3:
- use WARN_ON_ONCE
ChangeLog v2:
-
This patch extends check_range() to handle vma with VM_HUGETLB set.
We will be able to migrate hugepage with migrate_pages(2) after
applying the enablement patch which comes later in this series.
Note that for larger hugepages (covered by pud entries, 1GB for
x86_64 for example), we simply skip
Here is the 4th version of hugepage migration patchset.
I added Reviewed/Acked tags and applied the feedbacks in the previous discussion
(thank you, all reviewers!):
- fixed macro (1/8)
- improved comment and readability (1/8, 3/8, 4/8, 7/8)
- improved node choice in allocating destination
Before enabling each user of page migration to support hugepage,
this patch enables the list of pages for migration to link not only
LRU pages, but also hugepages. As a result, putback_movable_pages()
and migrate_pages() can handle both of LRU pages and hugepages.
ChangeLog v4:
- make some
This patch enables hugepage migration from migrate_pages(2),
move_pages(2), and mbind(2).
Signed-off-by: Naoya Horiguchi
Acked-by: Hillf Danton
Acked-by: Andi Kleen
Reviewed-by: Wanpeng Li
---
include/linux/mempolicy.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
(2013/07/25 12:34), Hush Bensen wrote:
On 07/25/2013 11:08 AM, Yasuaki Ishimatsu wrote:
(2013/07/25 9:56), Hush Bensen wrote:
On 07/25/2013 12:02 AM, Toshi Kani wrote:
On Wed, 2013-07-24 at 08:18 +0800, Hush Bensen wrote:
On 07/24/2013 04:45 AM, Toshi Kani wrote:
On Tue, 2013-07-23 at 10:01
Currently migrate_huge_page() takes a pointer to a hugepage to be
migrated as an argument, instead of taking a pointer to the list of
hugepages to be migrated. This behavior was introduced in commit
189ebff28 ("hugetlb: simplify migrate_huge_page()"), and was OK
because until now hugepage
This patch extends do_mbind() to handle vma with VM_HUGETLB set.
We will be able to migrate hugepage with mbind(2) after
applying the enablement patch which comes later in this series.
ChangeLog v3:
- revert introducing migrate_movable_pages
- added alloc_huge_page_noerr free from ERR_VALUE
On Wed, Jul 24, 2013, Greg KH said:
> On Thu, Jun 27, 2013 at 03:34:52PM +0530, navin patidar wrote:
>> dev_warn() is preferred over pr_warning().
>>
>> container_of() is used to get usb_driver pointer from usbip_device container
>> (stub_device or vhci_device), to get device structure required
On Wed, Jul 24, 2013 at 08:31:35PM -0700, Sudeep Dutt wrote:
> +/*
> + * Intel MIC Platform Software Stack (MPSS)
> + *
> + * Copyright(c) 2013 Intel Corporation.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Jul 25, 2013 at 01:15:07PM +0900, Won Kang wrote:
> GDM7240 is in LE where as GDM7243 (currently under development) is in BE.
But why does this information need to be sent to userspace?
>
On Thu, Jul 25, 2013 at 01:19:59PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/gdm724x/built-in.o: In function `netlink_init':
> (.text+0x19b6): multiple definition of
A release candidate preview Git v1.8.4-rc0 is now available for
testing at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
8e0d93653633fcaffc829f607bd8c1077a855c1d git-1.8.4.rc0.tar.gz
On Wed, Jul 24, 2013 at 10:10:48PM -0500, li...@roeck-us.net wrote:
> Quoting Greg Kroah-Hartman :
>
> >This is the start of the stable review cycle for the 3.10.3 release.
> >There are 103 patches in this series, all will be posted as a response
> >to this one. If anyone has any issues with
GDM7240 is in LE where as GDM7243 (currently under development) is in BE.
User space applications needs to discover the endianess to properly
encode/decode LTE control protocols. We have existing customers
already deploying units in large volume, and want to avoid forcing
them to change SDK APIs
On Mon, 22 Jul 2013 16:16:07 -0500, Rob Herring wrote:
> On 07/21/2013 06:44 PM, Grant Likely wrote:
> > On Sun, Jul 21, 2013 at 9:48 PM, Rob Herring wrote:
> >> On 07/21/2013 09:42 AM, Rob Herring wrote:
> >>> On 07/19/2013 01:14 PM, Sebastian Andrzej Siewior wrote:
> So I called
On Sat, 20 Jul 2013 15:49:21 +0200, Tomasz Figa wrote:
> On Saturday 20 of July 2013 04:46:47 Grant Likely wrote:
> > A number of us had a face-to-face meeting in Dublin last week to talk
> > about DT maintainership and the fact that it simply isn't working right
> > now. Neither Rob nor I can
On Fri, 19 Jul 2013 18:29:39 -0700, Joe Perches wrote:
> On Fri, 2013-07-19 at 18:23 -0700, Grant Likely wrote:
> > The ozlabs devicetree list was requiring too much work to moderate, so
> > I'm closing down that list and replacing it with a list on
> > vger.kernel.org.
> >
> >
On Wed, 24 Jul 2013 01:21:44 +0200, Laurent Pinchart
wrote:
> Hello,
>
> I'm running into an issue on several Renesas SoC with IRQ domains and GPIOs.
>
> On sh73a0, r8a73a4 and r8a7740, GPIOs and external interrupts are handled by
> two separate IP cores, namely the PFC (Pin Function
On Tue, 23 Jul 2013 08:55:10 -0700, Stephen Warren
wrote:
> On 07/22/2013 02:57 PM, Tomasz Figa wrote:
> > On Monday 22 of July 2013 16:34:49 Jon Loeliger wrote:
>
> >>> My idea is to implement compile time verification in dtc, so I guess it
> >>> will be more like the latter. Since dts is what
On Thu, Jul 11, 2013 at 10:39:30PM -0400, Dave Jones wrote:
> Just saw this during boot after an unclean shutdown. It hung afterwards.
>
> [ 97.162665] XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT,
> file: fs/xfs/xfs_dir2_sf.c, line: 358
> [ 97.164646] [ cut here
On Wed, 2013-07-24 at 17:42 +0100, Luis Henriques wrote:
> Ben Hutchings writes:
>
> > 3.2.49-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Gavin Shan
> >
> > commit 6d446ec32f169c6a5d9bc90684a8082a6cbe90f6 upstream.
[...]
> > @@
On Wed, 2013-07-24 at 14:09 -0700, David Miller wrote:
> From: David Miller
> Date: Wed, 24 Jul 2013 12:45:04 -0700 (PDT)
>
> > From: Luis Henriques
> > Date: Wed, 24 Jul 2013 17:42:04 +0100
> >
> >> I believe you didn't want to have these two invocations to the
> >> pci_channel_offline()
On Mon, 22 Jul 2013 16:34:49 -0500, Jon Loeliger wrote:
>
> > > Is there a schema out there in the wild that exemplifies what you mean?
> >
> > Not really. The format of schemas is currently in design stage. I'm
> > currently rethinking some details of what I have in my mind. Give me some
> >
There were various perf_event related sysfs entries in the
/sys/bus/event_source/devices/*/ directories that were not
documented.
This is version 2 with fixes suggested by Jiri Olsa.
Acked-by: Jiri Olsa
Signed-off-by: Vince Weaver
diff --git
On 07/24/2013 05:25 AM, Tejun Heo wrote:
On Fri, Jul 19, 2013 at 03:59:31PM +0800, Tang Chen wrote:
Vasilis Liaskovitis found that before we parse SRAT and fulfill numa_meminfo,
the nids of all the regions in memblock.reserve[] are MAX_NUMNODES. That is
because nids have not been mapped at that
This clarifies some of the ABI, as there has been some confusion
and minor breakages lately. Most notably it documents that as of
3.10 the events entries can contain decimal values in addition to
hex.
This is version 2 containing whitespace fixes suggested by
Jiri Olsa.
Signed-off-by: Vince
On Thu, Jul 25, 2013 at 9:49 AM, Casey Schaufler wrote:
> Subject: [PATCH] Smack: IPv6 casting error fix
>
> The original implementation of the Smack IPv6 port based
> local controls works most of the time using a sockaddr as
> a temporary variable, but not always as it overflows in
> some
On 07/24/2013 05:21 AM, Tejun Heo wrote:
On Fri, Jul 19, 2013 at 03:59:34PM +0800, Tang Chen wrote:
Since we modify movablecore boot option to support
"movablecore=acpi", this patch adds doc for it.
Please fold this into the patch which makes the code chnage.
OK, followed.
Thanks.
--
To
Just a clean-up, but it gives us better readability.
Sign-off-by: Lai Jiangshan
---
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index 7d85429..a44f501 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -1827,13 +1827,13 @@ static void
On 07/24/2013 05:11 AM, Tejun Heo wrote:
On Tue, Jul 23, 2013 at 05:04:35PM -0400, Tejun Heo wrote:
On Fri, Jul 19, 2013 at 03:59:30PM +0800, Tang Chen wrote:
...
Users can specify "movablecore=acpi" in kernel commandline to enable this
functionality. For those who don't use memory hotplug or
On 07/25/2013 01:50 AM, Stephen Boyd wrote:
> drivers/gpio/gpio-msm-v1.c: In function 'gpio_msm_v1_probe':
> drivers/gpio/gpio-msm-v1.c:656:2:
> error: implicit declaration of function 'IS_ERR'
> [-Werror=implicit-function-declaration]
> drivers/gpio/gpio-msm-v1.c:657:3:
> error: implicit
Commit e21d2170f36602ae2708 removed the unnecessary platform_set_drvdata(),
but left the variable "dev" unused, delete it.
Signed-off-by: Gu Zheng
---
drivers/video/vga16fb.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/video/vga16fb.c
This patch does the following:
a) Initializes the Intel MIC X100 platform device and driver.
b) Sets up support to handle shutdown requests from the host.
c) Maps the device page after obtaining the device page address
from the scratchpad registers updated by the host.
d) Informs the host upon a
From: Ashutosh Dixit
This patch introduces the card "Virtio over PCIe" interface for
Intel MIC. It allows virtio drivers on the card to communicate with their
user space backends on the host via a device page. Ring 3 apps on the host
can add, remove and configure virtio devices. A thin MIC
From: Ashutosh Dixit
This patch introduces the host "Virtio over PCIe" interface for
Intel MIC. It allows creating user space backends on the host and
instantiating virtio devices for them on the Intel MIC card. A character
device per MIC is exposed with IOCTL, mmap and poll callbacks. This
On 07/25/2013 11:08 AM, Yasuaki Ishimatsu wrote:
(2013/07/25 9:56), Hush Bensen wrote:
On 07/25/2013 12:02 AM, Toshi Kani wrote:
On Wed, 2013-07-24 at 08:18 +0800, Hush Bensen wrote:
On 07/24/2013 04:45 AM, Toshi Kani wrote:
On Tue, 2013-07-23 at 10:01 +0200, Ingo Molnar wrote:
* Toshi Kani
An Intel MIC X100 device is a PCIe form factor add-in coprocessor
card based on the Intel Many Integrated Core (MIC) architecture
that runs a Linux OS. It is a PCIe endpoint in a platform and therefore
implements the three required standard address spaces i.e. configuration,
memory and I/O. The
bio->bi_private is not always needed. As in the reading data path,
end_read_io does not need bio_private for further using, so moving
bio_private allocation out of f2fs_bio_alloc(). Alloc it in the
submit_write_page(), and ignore it in the f2fs_readpage().
Signed-off-by: Gu Zheng
---
checkpatch can generate a false positive when inserting
a new kernel-doc block and function above an existing
kernel-doc block.
Fix it by checking that the context line is also a newly
inserted line.
Reported-by: Darren Hart
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 1 +
1 file
On 07/24/2013 11:11 PM, Stephen Hemminger wrote:
> On Wed, 24 Jul 2013 13:55:14 +0800
> Jason Wang wrote:
>
>> On 07/23/2013 11:53 PM, Stephen Hemminger wrote:
>>> On Tue, 23 Jul 2013 15:15:48 +0800
>>> Jason Wang wrote:
>>>
+ struct {
+ __be16 h_vlan_proto;
On Wed, 2013-07-24 at 10:58 -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Jul 24, 2013 at 12:05:05PM +0100, Stefano Stabellini wrote:
> > On Tue, 23 Jul 2013, Konrad Rzeszutek Wilk wrote:
> > > On Tue, Jul 23, 2013 at 07:00:09PM +0100, Ian Campbell wrote:
> > > > On Tue, 2013-07-23 at 18:27 +0100,
Add pfuze100 regulator driver.
Signed-off-by: Robin Gong
---
.../devicetree/bindings/regulator/pfuze100.txt | 113 +
drivers/regulator/Kconfig |7 +
drivers/regulator/Makefile |1 +
drivers/regulator/pfuze100-regulator.c
Sent from my iPhone
On Jul 24, 2013, at 2:15 PM, "Lars-Peter Clausen" wrote:
> On 07/24/2013 08:55 PM, Joel Fernandes wrote:
>> On 07/24/2013 03:40 AM, Lars-Peter Clausen wrote:
>>> On 07/24/2013 10:28 AM, Fernandes, Joel wrote:
On Jul 24, 2013, at 3:23 AM, "Lars-Peter Clausen"
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/staging/gdm724x/built-in.o: In function `netlink_init':
(.text+0x19b6): multiple definition of `netlink_init'
drivers/staging/gdm72xx/built-in.o:(.text+0x19d5): first defined here
On 07/24/2013 09:57 PM, Rakib Mullick wrote:
> On Wed, Jul 24, 2013 at 2:34 PM, Michael Wang
[snip]
>>
>> I think you missed this in PeterZ's suggestion:
>>
>> - cpu_attach_domain(NULL, _root_domain, i);
>>
>> With this change, it will be safe since you will still get an un-freed
>>
Quoting Greg Kroah-Hartman :
This is the start of the stable review cycle for the 3.10.3 release.
There are 103 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu Jul 25
(2013/07/25 9:56), Hush Bensen wrote:
On 07/25/2013 12:02 AM, Toshi Kani wrote:
On Wed, 2013-07-24 at 08:18 +0800, Hush Bensen wrote:
On 07/24/2013 04:45 AM, Toshi Kani wrote:
On Tue, 2013-07-23 at 10:01 +0200, Ingo Molnar wrote:
* Toshi Kani wrote:
Could we please also fix it to never
-stable according to the previous conversation.
> From: Rafael J. Wysocki [mailto:r...@sisk.pl]
> Sent: Thursday, July 25, 2013 7:38 AM
>
> On Tuesday, July 23, 2013 04:09:15 PM Lv Zheng wrote:
> > This patch fixes races caused by unprotected ACPI IPMI transfers.
> >
> > We can see the following
Using the extern keyword on function prototypes is superfluous
visual noise so suggest removing it.
Using extern can cause unnecessary line wrapping at 80 columns
and unnecessarily long multi-line function prototypes.
Suggested-by: Hannes Frederic Sowa
Signed-off-by: Joe Perches
---
On Thu,
On 07/24/2013 06:49 PM, Peter Zijlstra wrote:
> On Wed, Jul 24, 2013 at 04:34:39PM +0800, Michael Wang wrote:
>> But your patch will run the risk to get a freed sd, since you make
>> 'sd_llc' wrong for a period of time (between destroy and rebuild) IMO.
>>
>> I guess I get you point, you are
On 07/25/2013 03:33 AM, Scott Wood wrote:
On 07/24/2013 01:21:09 AM, hongbo.zh...@freescale.com wrote:
From: Hongbo Zhang
The variable cookie is initialized in a list_for_each_entry loop,
if(unlikely)
the list is empty, this variable will be used uninitialized, so we
get a gcc
compiling
On Thu, Jul 25, 2013 at 4:07 AM, Greg Kroah-Hartman
wrote:
> On Thu, Jul 25, 2013 at 02:08:19AM +0800, Peng Tao wrote:
>> From: Peng Tao
>>
>> Should be y instead of true.
>>
>> Reported-by: Paul Bolle
>> Cc: Andreas Dilger
>> Signed-off-by: Peng Tao
>> ---
>>
On Thu, Jul 25, 2013 at 3:35 AM, Sam Ravnborg wrote:
> On Wed, Jul 24, 2013 at 04:31:30PM +0800, mail-agent-nore...@emc.com wrote:
>> From: Peng Tao
>>
>> Should be y instead of true.
>>
>> Reported-by: Paul Bolle
>> Cc: Andreas Dilger
>> Signed-off-by: Peng Tao
>> ---
>>
On 07/24/2013 05:00 AM, Tejun Heo wrote:
On Fri, Jul 19, 2013 at 03:59:29PM +0800, Tang Chen wrote:
We reserved hotpluggable memory in memblock at early time. And when memory
initialization is done, we have to free it to buddy system.
This patch free memory reserved by memblock with flag
On 07/24/2013 04:59 AM, Tejun Heo wrote:
..
+static bool __init kernel_resides_in_range(phys_addr_t base, u64 length)
+{
+ int i;
+ struct memblock_type *reserved =
+ struct memblock_region *region;
+ phys_addr_t start, end;
+
+ for (i = 0; i< reserved->cnt;
Use bit fields, and the size of struct ftrace_event_field can be
shrunk from 48 bytes to 40 bytes on 64bit kernel.
slab_name active_obj nr_obj size obj_per_slab
-
ftrace_event_field 1105 1105 48 85 (before)
ftrace_event_field 1224 1224
init_syscall_trace() can be called during kernel bootup only, so we can
mark it and the functions it calls as __init.
Signed-off-by: Li Zefan
---
this was sent 4 months ago.
---
kernel/trace/trace_syscalls.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
On Tue, Jul 23, 2013 at 2:10 PM, Eric Dumazet wrote:
> On Mon, 2013-07-22 at 20:47 +0100, Ben Hutchings wrote:
>> On Mon, 2013-07-22 at 11:47 -0700, Eric Dumazet wrote:
>> > On Mon, 2013-07-22 at 19:38 +0100, Ben Hutchings wrote:
>> > > On Mon, 2013-07-22 at 11:29 -0700, Grant Grundler wrote:
>>
On Fri, Jul 12, 2013 at 09:19:12PM -0700, Yinghai Lu wrote:
> On Thu, Jul 11, 2013 at 7:03 PM, Robin Holt wrote:
> > During boot of large memory machines, a significant portion of boot
> > is spent initializing the struct page array. The vast majority of
> > those pages are not referenced during
2013/7/5 Vinod Koul :
> On Tue, Jun 18, 2013 at 02:21:58PM +0800, Xiang Wang wrote:
>> From: Xiang Wang
>>
>> pdev->phy is of type "struct mmp_pdma_phy *". But when
>> allocating memory for it, "struct mmp_pdma_chan" is used
>> by mistake.
>>
>> Signed-off-by: Xiang Wang
>> ---
>>
Hi, maintainers
What's the status of this patch set V3? Sorry for pushing. Thanks!
2013/6/18 Xiang Wang :
> From: Xiang Wang
>
> This patch set deals with the issues that 1) phy channels are not protected
> in mmp_pdma. 2) dma request<->channel mapping is not cleared when a phy chan
> is freed.
On 07/24/2013 05:32 AM, Tejun Heo wrote:
On Tue, Jul 23, 2013 at 04:55:57PM -0400, Tejun Heo wrote:
On Fri, Jul 19, 2013 at 03:59:27PM +0800, Tang Chen wrote:
+ /*
+* In such an early time, we don't have nid. We specify pxm
+* instead of
Hello All,
I met the below error on b3a3a9c441 with s390x arch:
# make
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CALLscripts/checksyscalls.sh
CHK include/generated/compile.h
CHK include/generated/uapi/linux/version.h
LINK
On Thu, Jul 25, 2013 at 09:32:02AM +0930, Rusty Russell wrote:
> Herbert Xu writes:
> > Hi Rusty:
> >
> > I don't know why this patch never went into the kernel, even
> > though the corresponding features have been added to modprobe
> > in most if not all distros.
>
> Because Andreas never sent
On Monday, July 15, 2013 10:10 AM, Jingoo Han wrote:
> On Tuesday, July 09, 2013 6:12 PM, Kim, Milo wrote:
> >
> > LP8555 is one of LP855x family device.
> > This device needs pre_init_device() and post_init_device() driver structure.
> > It's same as LP8557, so the device configuration code is
Yes, I agree.
As what I've said, it's up to the others to determine if the patch is OK.
I just need to make my concerns visible in the community. :-)
Thanks and best regards
-Lv
From: ben.gut...@gmail.com [mailto:ben.gut...@gmail.com] On Behalf Of Ben Guthro
Sent: Thursday, July 25, 2013 9:38 AM
vfs guarantees the cgroup won't be destroyed, so it's redundant
to get a css reference.
Signed-off-by: Li Zefan
---
mm/memcontrol.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 03c8bf7..aa3e478 100644
--- a/mm/memcontrol.c
+++
On Thursday, July 25, 2013 7:06 AM, Greg Kroah-Hartman wrote:
>
> The dev_attrs field of struct class is going away soon, dev_groups
> should be used instead. This converts the video backlight class code to
> use the correct field.
>
> Cc: Richard Purdie
> Cc: Jingoo Han
> Signed-off-by: Greg
On Thursday, July 25, 2013 7:06 AM, Greg Kroah-Hartman wrote:
>
> The dev_attrs field of struct class is going away soon, dev_groups
> should be used instead. This converts the video backlight lcd class
> code to use the correct field.
>
> Cc: Richard Purdie
> Cc: Jingoo Han
> Signed-off-by:
On Wed, Jul 24, 2013 at 06:41:20PM -0700, Joe Perches wrote:
> On Thu, 2013-07-25 at 01:27 +, Cong Wang wrote:
> > On Tue, 23 Jul 2013 at 17:58 GMT, Joe Perches wrote:
>
> You dropped the author from the cc list.
> Always reply to the author.
>
> > > Function prototypes don't need to be
On Thu, 2013-07-25 at 01:27 +, Cong Wang wrote:
> On Tue, 23 Jul 2013 at 17:58 GMT, Joe Perches wrote:
You dropped the author from the cc list.
Always reply to the author.
> > Function prototypes don't need to be declared
> > extern in .h files. It's assumed by the compiler
> > and is as
Daniel Vetter writes:
> We could just unconditionally increase the alignement in
> intel_pin_and_fence_fb_obj - we already have more strict requirements due
> to a bunch of w/a in other places. So shouldn't hurt at all really.
That seems like a fine plan; 32kB isn't that onerous. Do you want
Hi John,
Today's linux-next merge of the wireless-next tree got a conflict in
drivers/net/ethernet/broadcom/Kconfig between commit 31bd29776b85
("bgmac: add dependency to phylib") from Linus' tree and commit
72bb2f267887 ("bgmac: make bgmac depend on bcm47xx") from the
wireless-next tree.
I
On 07/23/2013 07:53 PM, Greg Kroah-Hartman wrote:
On Sat, Jun 15, 2013 at 10:04:26AM -0400, Peter Hurley wrote:
Byte-by-byte echo output is painfully slow, requiring a lock/unlock
cycle for every input byte.
Instead, perform the echo output in blocks of 256 characters, and
at least once per
Let me just give an example to let you know the difficulties for ACPICA
developers to merge Xen's acpi_os_prepare_sleep.
The original logic in the acpi_hw_legacy_sleep is:
111 /* Get current value of PM1A control */
112
113 status =
On Tue, 23 Jul 2013 at 17:58 GMT, Joe Perches wrote:
> Function prototypes don't need to be declared
> extern in .h files. It's assumed by the compiler
> and is as unnecessary as using auto is when
> declaring automatic/local variables in a block.
>
Since we all know this, why bother it? Having
On Wed, 2013-07-24 at 12:04 -0400, Jörn Engel wrote:
> On Fri, 5 July 2013 10:53:54 -0400, Steven Rostedt wrote:
> >
> > Can you find an easy reproducer for this?
>
> We might have found something:
>
> Jul 23 19:00:59 [28253.487058,08] WARNING: at kernel/trace/ftrace.c:1529
>
On Jul 24, 2013, at 9:01 PM, "Zheng, Lv"
wrote:
>> From: Moore, Robert
>> Sent: Wednesday, July 24, 2013 10:39 PM
>>
>> I haven't found a high-level description of "acpi_os_prepare_sleep", perhaps
>> I
>> missed it.
>
> If we take a look at the declaration of this new OSL API, its name is
On Thursday, July 25, 2013 12:42 AM, Olof Johansson wrote:
>
> The device-tree enablement for max8925 has several problems, but besides
> the bindings being wrong (and not having seen review) there's also some
> bad coding practices on how to fill in the platform_data from device tree.
>
> I
On Wed, 2013-07-24 at 17:06 -0700, Andy Grover wrote:
> On 07/24/2013 01:54 PM, Nicholas A. Bellinger wrote:
> > Yes, which is why I've been accepting his kernel patches the entire time
> > that user-space has been forked into -fb. Now that the user-space code
> > has been relicensed as promised,
On 07/02/2013 11:31 AM, Dean Jenkins wrote:
This is an issue when SLIP is bound to a PTY/TTY. If
TTY_DO_WRITE_WAKEUP is set, pty_write() calls tty_wakeup()
then slip_write_wakeup() can be called. slip_write_wakeup() can
be called by pty_write(). This is a recursion loop.
pty_write() is called
On 2013/7/24 22:07, Michal Hocko wrote:
> On Wed 24-07-13 17:59:12, Li Zefan wrote:
>> This enables us to lookup a cgroup by its id.
>>
>> Signed-off-by: Li Zefan
>
> Reviewed-by: Michal Hocko
Thanks for the review! I'll wait a couple of days for other comments,
and then update the patchset.
On Wed, 24 July 2013 17:03:53 -0400, Dhaval Giani wrote:
>
> I am posting this series early in its development phase to solicit some
> feedback.
At this state, a good description of the format would be nice.
> We are implementing transparent decompression with a focus on ext4. One
> of the main
Okay as I warned, the qxl driver was running a bit free and loose with its
ttm object reservations and the new lockdep enabled reservation tracking
shone a bright light into it, it also with the new reservations mutexes
hits a possible deadlock during boot.
the first patch is a real fix to
> From: Moore, Robert
> Sent: Wednesday, July 24, 2013 10:39 PM
>
> I haven't found a high-level description of "acpi_os_prepare_sleep", perhaps I
> missed it.
If we take a look at the declaration of this new OSL API, its name is
acpi_os_prepare_sleep, but originally it only hacks two
1 - 100 of 1714 matches
Mail list logo
