> From: Ric Mason [mailto:ric.mas...@gmail.com]
> Sent: Saturday, February 16, 2013 11:19 PM
> To: Minchan Kim
> Cc: Greg Kroah-Hartman; linux...@kvack.org; linux-kernel@vger.kernel.org;
> Andrew Morton; Seth
> Jennings; Nitin Gupta; Dan Magenheimer; Konrad Rzeszutek Wilk
> Subject: Re: [PATCH v2]
On 02/17/2013 12:19 AM, Ric Mason wrote:
> On 02/06/2013 10:17 AM, Minchan Kim wrote:
>> Zsmalloc has two methods 1) copy-based and 2) pte-based to access
>> allocations that span two pages. You can see history why we supported
>> two approach from [1].
>>
>> In summary, copy-based method is 3 time
On Mon, Feb 18, 2013 at 7:53 AM, Frederic Weisbecker wrote:
>
> Here is an updated version. It cleans up things a bit and boots fine with my
> usual
> config. There might be still some small details to work on but here is the
> big picture.
>
> What do you think?
Looks fine to me. Did this get
On 02/18/2013 11:37 PM, Michel Lespinasse wrote:
> On Tue, Feb 19, 2013 at 1:56 AM, Srivatsa S. Bhat
> wrote:
>> On 02/18/2013 09:51 PM, Srivatsa S. Bhat wrote:
>>> On 02/18/2013 09:15 PM, Michel Lespinasse wrote:
I don't see anything preventing a race with the corresponding code in
perc
On Thu, Feb 14, 2013 at 10:30:15AM -0500, Mimi Zohar wrote:
> On Thu, 2013-02-14 at 10:03 -0500, Vivek Goyal wrote:
> > On Wed, Feb 13, 2013 at 05:27:01PM -0500, Mimi Zohar wrote:
> >
> > [..]
> > > > Yep, I got that. Default policy gets overruled when a new policy is
> > > > loaded.
> > > >
> >
Hi,
On Mon, Feb 18, 2013 at 05:08:16PM +0530, Afzal Mohammed wrote:
> + uart1: serial@44e09000 {
> + compatible = "ti,am4372-uart","ti,omap2-uart";
> + clock-frequency = <4800>;
> + reg = <0x44e09000 0x2000>;
> +
This is the start of the stable review cycle for the 3.4.33 release.
There is 1 patch in this series, which will be posted as a response to
this one. If anyone has any issues with it being applied, please let me
know.
Responses should be made by Wed Feb 20 18:13:44 UTC 2013.
Anything received aft
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre SIMON
This patch corrects a buffer overflow in kernels from 3.0 to 3.4 when calling
log_prefix() function from call_console_drivers().
This bug existed in previous releases but has be
This is the start of the stable review cycle for the 3.0.66 release.
There is 1 patch in this series, which will be posted as a response to
this one. If anyone has any issues with it being applied, please let me
know.
Responses should be made by Wed Feb 20 18:22:38 UTC 2013.
Anything received aft
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre SIMON
This patch corrects a buffer overflow in kernels from 3.0 to 3.4 when calling
log_prefix() function from call_console_drivers().
This bug existed in previous releases but has be
On 02/16/2013 12:28 AM, Ric Mason wrote:
> On 02/04/2013 08:23 AM, Minchan Kim wrote:
>> Zsmalloc has two methods 1) copy-based and 2) pte based to access
>> allocations that span two pages.
>> You can see history why we supported two approach from [1].
>>
>> But it was bad choice that adding hard
Junio C Hamano writes:
> Git v1.8.2 Release Notes (draft)
>
>
> Backward compatibility notes
>
>
> In the upcoming major release (tentatively called 1.8.2), we will
> change the behavior of the "git push" command.
>
> When "git push [$there]"
Hi David,
On Fri, Feb 15, 2013 at 12:46:55PM +0100, David Herrmann wrote:
> Hi Kirill
>
> On Fri, Feb 15, 2013 at 12:29 PM, Kirill A. Shutemov
> wrote:
> > Hi David and all,
> >
> > There's claim in uhid.h that the interface is "compatible even between
> > architectures". But it obviously is not
On Mon, Feb 18, 2013 at 11:28:40AM +0100, Jiri Kosina wrote:
> On Fri, 15 Feb 2013, Dmitry Torokhov wrote:
>
> > > Here's my attempt to fix the issue.
> > >
> > > Not sure if tricks with padding in a good idea. We can just use __u64
> > > instead of pointer, but it will require update of userspa
On 2/18/2013 6:46 AM, Mel Gorman wrote:
On Sat, Feb 16, 2013 at 10:26:30AM -0800, Linus Torvalds wrote:
On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar wrote:
c060f943d092 may be related as you config does not have
CONFIG_SPARSEMEM defined.
Right, that's the commit causing the x86 regression:
Hi, On Mon, Feb 18, 2013 at 09:49:16AM -0800, Greg KH wrote:
> > Input/output error - /sys/devices/cpu/power/autosuspend_delay_ms
>
> The issue with this file is, if the power.use_autosuspend flag is not
> set for the device, then it can't be read or written to. This flag
> changes dynamically wi
On Mon, Feb 18, 2013 at 06:45:27PM +0100, Borislav Petkov wrote:
> On Mon, Feb 18, 2013 at 07:27:00PM +0200, Felipe Balbi wrote:
> > No such device - /sys/devices/system/edac/mc/mc0/sdram_scrub_rate
>
> Looks like your edac module doesn't allow scrub rate setting. Which edac
> driver is that? dmes
This is based on v7 of the full Haswell PMU support, but
ported to the latest perf/core and stripped down to the
bare bones
Only for very extremly basic usage.
Most interesting new features are not in this patchkit
(full version is
git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git
From: Andi Kleen
Add basic Haswell PMU support.
Similar to SandyBridge, but has a few new events and two
new counter bits.
There are some new counter flags that need to be prevented
from being set on fixed counters, and allowed to be set
for generic counters.
Also we add support for the counte
From: Andi Kleen
This avoids some problems with spurious PMIs on Haswell.
Haswell seems to behave more like P4 in this regard. Do
the same thing as the P4 perf handler by unmasking
the NMI only at the end. Shouldn't make any difference
for earlier family 6 cores.
Tested on Haswell, IvyBridge, We
From: Andi Kleen
Add support for the Haswell extended (fmt2) PEBS format.
It has a superset of the nhm (fmt1) PEBS fields, but has a longer record so
we need to adjust the code paths.
The main advantage is the new "EventingRip" support which directly
gives the instruction, not off-by-one instru
From: Andi Kleen
Add basic PEBS support for Haswell.
The constraints are similar to SandyBridge with a few new events.
v2: Readd missing pebs_aliases
v3: Readd missing hunk. Fix some constraints.
v4: Fix typo in PEBS event table (Stephane Eranian)
Reviewed-by: Stephane Eranian
Signed-off-by: An
From: Andi Kleen
Recent Intel CPUs like Haswell and IvyBridge have a new alternative MSR
range for perfctrs that allows writing the full counter width. Enable this
range if the hardware reports it using a new capability bit.
This lowers the overhead of perf stat slightly because it has to do les
On Sat, Feb 16, 2013 at 10:35:52AM +0200, Robert Berger wrote:
> As per Joe's suggestion:
> "Perhaps it'd be better to use KBUILD_MODNAME all the time
> instead of adding the prefix. Also, to me mixing "ramster: "
> and "zcache: " for the prefixes is odd. Just using zcache
> all the time would be s
On 02/18/2013 10:51 PM, Michel Lespinasse wrote:
> On Tue, Feb 19, 2013 at 12:43 AM, Srivatsa S. Bhat
> wrote:
>> On 02/18/2013 09:53 PM, Michel Lespinasse wrote:
>>> I am wondering though, if you could take care of recursive uses in
>>> get/put_online_cpus_atomic() instead of doing it as a proper
On 2/18/13 8:16 AM, Stephane Eranian wrote:
Hi,
I think the advantage of the ioctl() is that is reuses existing infrastructure.
The downside is that to get the timestamp you need at a minimum:
uint64_t get_perf_timestamp(void)
{
struct perf_event_attr attr;
uint64_t ts = 0;
int fd;
On 02/15/2013 09:26 PM, Ric Mason wrote:
> On 02/14/2013 02:38 AM, Seth Jennings wrote:
>> =
>> DO NOT MERGE, FOR REVIEW ONLY
>> This patch introduces zsmalloc as new code, however, it already
>> exists in drivers/staging. In order to build successfully, you
>> must select EITHER to driver
those two sysfs files don't have a 'show' method,
so they shouldn't have a read permission. Thanks
to Greg Kroah-Hartman for actually looking into
the source code and figuring out we had a real bug
with these two files.
Signed-off-by: Felipe Balbi
---
drivers/base/memory.c | 4 ++--
1 file chang
Whenever a struct device_attribute is registered
with mismatched permissions - read permission without
a show routine or write permission without store
routine - we will issue a big warning so we catch
those early enough.
Signed-off-by: Felipe Balbi
---
This is completely untested. I have only c
Several printk's were missing KERN_INFO and KERN_CONT flags.
In addition, a printk that was outside a #if/#endif should have
been inside, which would result in stray blank line on non-x86 boxes.
Signed-off-by: Valdis Kletnieks
--- linux-next/kernel/signal.c.orig 2013-02-15 19:09:29.451843219
On 02/16/2013 12:21 AM, Ric Mason wrote:
> On 02/14/2013 02:38 AM, Seth Jennings wrote:
>> This patch adds a documentation file for zsmalloc at
>> Documentation/vm/zsmalloc.txt
>>
>> Signed-off-by: Seth Jennings
>> ---
>> Documentation/vm/zsmalloc.txt | 68
>> ++
On Mon, Feb 18, 2013 at 09:09:04PM +0200, Felipe Balbi wrote:
> Whenever a struct device_attribute is registered
> with mismatched permissions - read permission without
> a show routine or write permission without store
> routine - we will issue a big warning so we catch
> those early enough.
>
>
On Mon, Feb 18, 2013 at 11:17:19AM -0800, Greg KH wrote:
> On Mon, Feb 18, 2013 at 09:09:04PM +0200, Felipe Balbi wrote:
> > Whenever a struct device_attribute is registered
> > with mismatched permissions - read permission without
> > a show routine or write permission without store
> > routine -
> This is the original report descriptor as reported by lsusb -vd 046d:c294.
>
> Signed-off-by: Paul Sbarra
Looks good to me.
Simon
Signed-off-by: Simon Wood
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More m
>
> Signed-off-by: Paul Sbarra
Looks good to me.
Signed-off-by: Simon Wood
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ a
On 02/15/2013 10:04 PM, Ric Mason wrote:
> On 02/14/2013 02:38 AM, Seth Jennings wrote:
>> + * The statistics below are not protected from concurrent access for
>> + * performance reasons so they may not be a 100% accurate. However,
>> + * the do provide useful information on roughly how many tim
On 02/16/2013 12:11 AM, Ric Mason wrote:
> On 02/14/2013 02:38 AM, Seth Jennings wrote:
>> +/***
>> +* page pool for temporary compression result
>> +/
>> +#define ZSWAP_TMPPAGE_POOL_PAGES 16
>
> Why not the numbe
Dear RT Folks,
I'm pleased to announce the 3.6.11-rt30 release.
Changes since 3.6.11-rt29:
1) Fix a deadlock on imx serial
2) Fix a ACPI scheduling while atomic issue (Steven)
3) Fix a longstanding mainline issue in printk (Yitian Bu)
I know I said that a few days ago already,
On 02/15/2013 09:20 PM, Ric Mason wrote:
> On 02/14/2013 02:38 AM, Seth Jennings wrote:
>>
>> Some addition performance metrics regarding the performance
>> improvements and I/O reductions that can be achieved using zswap as
>> measured by SPECjbb are provided here:
>>
>> http://ibm.co/VCgHvM
>
>
On Mon, Feb 18, 2013 at 08:47:35PM +0200, Felipe Balbi wrote:
> On Mon, Feb 18, 2013 at 06:45:27PM +0100, Borislav Petkov wrote:
> > On Mon, Feb 18, 2013 at 07:27:00PM +0200, Felipe Balbi wrote:
> > > No such device - /sys/devices/system/edac/mc/mc0/sdram_scrub_rate
> >
> > Looks like your edac mo
From: Kumar Amit Mehta
Date: Sat, 16 Feb 2013 09:56:34 -0800
> fix for a potential NULL pointer dereference and removal of a redundant
> assignment operation. Found using smatch.
>
> Signed-off-by: Kumar Amit Mehta
Obviously whoever wrote this code intended for ALARM_CLEARED
and EVENT_UNKNOWN
Em Mon, 18 Feb 2013 20:46:33 +0200
Felipe Balbi escreveu:
> Hi, On Mon, Feb 18, 2013 at 09:49:16AM -0800, Greg KH wrote:
> > > Input/output error - /sys/devices/cpu/power/autosuspend_delay_ms
> >
> > The issue with this file is, if the power.use_autosuspend flag is not
> > set for the device, th
On Tue, 2013-02-19 at 03:33 +1100, Amnon Shiloh wrote:
> Yes, Randy Dunlap already raised this point, but I have no dealings with
> any particular Linux distribution or the right connections to chase them
> all, one by one - I develop generic software for the general Linux community,
> that is int
Hello, Lai.
On Tue, Feb 19, 2013 at 12:12:14AM +0800, Lai Jiangshan wrote:
> +/**
> + * get_work_cwq - get cwq of the work
> + * @work: the work item of interest
> + *
> + * CONTEXT:
> + * spin_lock_irq(&pool->lock), the work must be queued on this pool
> + */
> +static struct cpu_workqueue_struct
On 02/18/2013 11:24 AM, Seth Jennings wrote:
On 02/15/2013 10:04 PM, Ric Mason wrote:
On 02/14/2013 02:38 AM, Seth Jennings wrote:
+/* invalidates all pages for the given swap type */
+static void zswap_frontswap_invalidate_area(unsigned type)
+{
+struct zswap_tree *tree = zswap_trees[typ
On Mon, 2013-02-18 at 17:50 +0100, Vincent Guittot wrote:
> yes for sure.
> The problem is more linked to cpuidle and function tracer.
>
> cpu hotplug and function tracer work when cpuidle is disable.
> cpu hotplug and cpuidle works if i don't enable function tracer.
> my platform is dead as soon
On Mon, 2013-02-18 at 17:50 +0100, Vincent Guittot wrote:
> yes for sure.
> The problem is more linked to cpuidle and function tracer.
>
> cpu hotplug and function tracer work when cpuidle is disable.
> cpu hotplug and cpuidle works if i don't enable function tracer.
> my platform is dead as soon
BugLink: http://bugs.launchpad.net/bugs/1128840
It appears that when this register read fails it never recovers, so
I think there is no need to repeat the same error message ad infinitum.
Cc: Ivo van Doorn
Cc: Gertjan van Wingerde
Cc: Helmut Schaa
Cc: "John W. Linville"
Cc: linux-wirel...@vge
On Mon, 18 Feb 2013, Frederic Weisbecker wrote:
> On Sun, Feb 17, 2013 at 10:02:11PM +0100, Frederic Weisbecker wrote:
> > 2013/2/17 Frederic Weisbecker :
> > > 2013/2/17 Linus Torvalds :
> > >> On Sun, Feb 17, 2013 at 7:11 AM, Frederic Weisbecker
> > >> wrote:
> > >>>
> > >>> preempt_value_in_in
From: Philip J Kelleher
This patch include a few driver fixes for the IBM RamSan 70/80 driver.
Signed-off-by: Philip J Kelleher
-
This update address issues raise thus far. Changes include:
o Changed the creg_ctrl lock from a m
> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> Subject: Re: [PATCHv5 4/8] zswap: add to mm/
>
> On 02/15/2013 10:04 PM, Ric Mason wrote:
> > On 02/14/2013 02:38 AM, Seth Jennings wrote:
>
> >> + * The statistics below are not protected from concurrent access for
> >> + * performance
From: Andy King
Date: Mon, 18 Feb 2013 08:04:09 -0800
> Minor vSockets fixes, two of which were reported on LKML.
Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http:
On Mon, Feb 18, 2013 at 08:40:32PM +0100, Borislav Petkov wrote:
> On Mon, Feb 18, 2013 at 08:47:35PM +0200, Felipe Balbi wrote:
> > On Mon, Feb 18, 2013 at 06:45:27PM +0100, Borislav Petkov wrote:
> > > On Mon, Feb 18, 2013 at 07:27:00PM +0200, Felipe Balbi wrote:
> > > > No such device - /sys/dev
Hi,
On Mon, Feb 18, 2013 at 04:46:38PM -0300, Mauro Carvalho Chehab wrote:
> > > > No such device - /sys/devices/system/edac/mc/mc0/sdram_scrub_rate
> > >
> > > Odd, go ask the edac developers
> >
> > will do ;-)
>
> Well, the question is missing ;) /me assumes that you want to talk about
> sus
On 02/18/2013 01:49 PM, Cody P Schafer wrote:
> On 02/18/2013 11:24 AM, Seth Jennings wrote:
>> On 02/15/2013 10:04 PM, Ric Mason wrote:
>>> On 02/14/2013 02:38 AM, Seth Jennings wrote:
>>
+/* invalidates all pages for the given swap type */
+static void zswap_frontswap_invalidate_area(u
Hi Pali,
> Like other watchdog drivers, this patch adds new option nowayout
> which overwrite WATCHDOG_NOWAYOUT.
Added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
netbk_fatal_tx_err() calls xenvif_carrier_off(), which does
a xenvif_put(). As callers of netbk_fatal_tx_err should only
have one reference to the vif at this time, then the xenvif_put
in netbk_fatal_tx_err is one too many.
Signed-off-by: Andrew Jones
---
drivers/net/xen-netback/netback.c | 1 -
On Feb 18, 2013 7:11 AM, "Zhang, Rui" wrote:
>
> Sorry I missed that patch.
>
> So the problem happens when the acerhdf thermal zone is registered when the
> fan has already been spinning, right?
Correct, when the acerhdf driver is switched into kernel controlled
mode and the fan is spinning, it
On Tue, 5 Feb 2013, John Stultz wrote:
> On 02/05/2013 02:13 PM, Stephane Eranian wrote:
> > But if people are strongly opposed to the clock_gettime() approach, then
> > I can go with the ioctl() because the functionality is definitively needed
> > ASAP.
>
> I prefer the ioctl method, since its le
do_ida_request() can be called from within interrupt context.
A stack frame of more then 1K runs the risk of overflowing the
kernel stack. Correct this situation by dynamically allocating
the large (and temporary) scatter/gather array. A failure from kmalloc()
will leave a stack trace in the kernel
Fix the following compiler warning (also a checkpatch error):
net/ipv6/xfrm6_mode_tunnel.c: In function ‘xfrm6_mode_tunnel_input’:
net/ipv6/xfrm6_mode_tunnel.c:72:2: warning: suggest parentheses around
assignment used as truth value [-Wparentheses]
Signed-off-by: Stratos Karafotis
---
net/ipv6/
On 02/18/2013 01:55 PM, Dan Magenheimer wrote:
>> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
>> Subject: Re: [PATCHv5 4/8] zswap: add to mm/
>>
>> On 02/15/2013 10:04 PM, Ric Mason wrote:
>>> On 02/14/2013 02:38 AM, Seth Jennings wrote:
>>
+ * The statistics below are not protec
Hi Jiri,
> > so, here is the hid drivers cleanup. The aim is to remove as much as
> > possible
> > direct calls to usbhid for hid drivers. Thus, other transport layers can use
> > the existing hid drivers (like I2C or uhid).
> >
> > Henrik, patches 1 to 5 are yours. I just rebased and double-che
On Sat, Feb 16, 2013 at 05:44:09PM +0530, anish kumar wrote:
> From: anish kumar
>
> This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
> multifold.
> Uses are:
> 1. Check if smpboot_register_percpu_thread function passed.
> 2. Makes sure that user enables and disables the
Over the weekend, I had a number of occurrences of my laptop becoming
unresponsive for periods of up to several minutes. gkrellm monitors showed
near 100% system time for both CPUs (and the way X and other userspace programs
were behaving was consistent with them being starved for CPU for extended
'firewire: convert to idr_alloc()' accidentally orphaned 'minor'.
drivers/firewire/core-device.c: In function ‘fw_device_init’:
drivers/firewire/core-device.c:1029:24: warning: ‘minor’ may be used
uninitialized in this function [-Wuninitialized]
Cc: Stefan Richter
Cc: linux1394-de...@lists.sour
'firewire: convert to idr_alloc()' accidentally orphaned 'minor'.
drivers/firewire/core-device.c: In function ‘fw_device_init’:
drivers/firewire/core-device.c:1029:24: warning: ‘minor’ may be used
uninitialized in this function [-Wuninitialized]
Cc: Stefan Richter
Cc: linux1394-de...@lists.sour
On Wed, Jan 30, 2013 at 8:26 PM, Dave Kleikamp wrote:
> By the way, I have updated the patchset in git. I removed the version
> from the name of the branch and will keep this one updated:
>
> git://github.com/kleikamp/linux-shaggy.git aio_loop
What's the status of this patchset?
Will it go into L
On Mon, 18 Feb 2013, Felipe Balbi wrote:
> Hi, On Mon, Feb 18, 2013 at 09:49:16AM -0800, Greg KH wrote:
> > > Input/output error - /sys/devices/cpu/power/autosuspend_delay_ms
> >
> > The issue with this file is, if the power.use_autosuspend flag is not
> > set for the device, then it can't be rea
Em Mon, 18 Feb 2013 22:05:42 +0200
Felipe Balbi escreveu:
> Hi,
>
> On Mon, Feb 18, 2013 at 04:46:38PM -0300, Mauro Carvalho Chehab wrote:
> > > > > No such device - /sys/devices/system/edac/mc/mc0/sdram_scrub_rate
> > > >
> > > > Odd, go ask the edac developers
> > >
> > > will do ;-)
> >
>
On Mon, Feb 18, 2013 at 06:47:42PM -0300, Mauro Carvalho Chehab wrote:
> In the past, the sysfs node creation was done using the raw sysfs support.
> Doing dynamic creation with the old code were much more complex. I guess
> that's the reason why the code was written this way. Now that the code
>
Patches to fix this have already been applied to net-next, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.
On Mon, 18 Feb 2013, Aaron Lu wrote:
> Placing a WARN_ON there seems to suggest drivers should not return
> -EAGAIN, so I think I'll just add back those dropped code to
> sdev_runtime_suspend as you have suggested like this:
>
> static int sdev_runtime_suspend(struct device *dev)
> {
> cons
Hello,
On Mon, 18 Feb 2013, Zhang Yanfei wrote:
> 于 2013年02月16日 05:39, Julian Anastasov 写道:
> >
> > Hello,
> >
> > On Thu, 14 Feb 2013, Andrew Morton wrote:
> >
> >> Redarding this patch:
> >> net-change-type-of-netns_ipvs-sysctl_sync_qlen_max.patch and
> >> net-fix-functions-and-
On Mon, Feb 18, 2013 at 04:48:06PM -0500, Alan Stern wrote:
> On Mon, 18 Feb 2013, Felipe Balbi wrote:
>
> > Hi, On Mon, Feb 18, 2013 at 09:49:16AM -0800, Greg KH wrote:
> > > > Input/output error - /sys/devices/cpu/power/autosuspend_delay_ms
> > >
> > > The issue with this file is, if the power.
> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> Subject: Re: [PATCHv5 4/8] zswap: add to mm/
>
> On 02/18/2013 01:55 PM, Dan Magenheimer wrote:
> >> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> >> Subject: Re: [PATCHv5 4/8] zswap: add to mm/
> >>
> >> On 02/15/2013 10:04
On Sun, 10 Feb 2013, Otavio Salvador wrote:
> On Sun, Feb 10, 2013 at 12:47 PM, Alan Stern
> wrote:
> > On Sun, 10 Feb 2013, Otavio Salvador wrote:
> >> I do have EHCI and PCI enabled so it should be working. Any clue about
> >> why it breaks it?
> >
> > Perhaps your system is not loading the ne
On Mon, Feb 18, 2013 at 7:09 PM, Alan Stern wrote:
> On Sun, 10 Feb 2013, Otavio Salvador wrote:
>
>> On Sun, Feb 10, 2013 at 12:47 PM, Alan Stern
>> wrote:
>> > On Sun, 10 Feb 2013, Otavio Salvador wrote:
>> >> I do have EHCI and PCI enabled so it should be working. Any clue about
>> >> why it
On Mon, Feb 18, 2013 at 01:54:34PM -0800, Greg KH wrote:
> Because sysfs is "one value per file" the lack of a file showing up
> shouldn't cause any userspace tools any problems, that is why we did
> things this way.
>
> But, of course, userspace programmers do know how to mess things up...
How ab
On 02/18/2013 03:42 PM, Sedat Dilek wrote:
> On Wed, Jan 30, 2013 at 8:26 PM, Dave Kleikamp
> wrote:
>> By the way, I have updated the patchset in git. I removed the version
>> from the name of the branch and will keep this one updated:
>>
>> git://github.com/kleikamp/linux-shaggy.git aio_loop
>
On Mon, Feb 18, 2013 at 11:13:06PM +0100, Borislav Petkov wrote:
> On Mon, Feb 18, 2013 at 01:54:34PM -0800, Greg KH wrote:
> > Because sysfs is "one value per file" the lack of a file showing up
> > shouldn't cause any userspace tools any problems, that is why we did
> > things this way.
> >
> > B
On Monday 18 February 2013, Dongjin Kim wrote:
>
> This patch adds the compatible string for MSHC controller of Exynos4412, and
> share the controller specific properties with Exynos5250 since they have same
> features. Its driver data name is changed to exynos_drv_data instead SoC
> specific name
On Mon, 18 Feb 2013, Otavio Salvador wrote:
> >> I thought the ehci-pci module would be load for every ehci PCI; What
> >> do you think?
> >
> > The kernel can't guarantee anything about what driver modules are
> > loaded. That's up to userspace. In particular, the initramfs image
> > must be se
On Mon, Feb 18, 2013 at 7:38 PM, Alan Stern wrote:
> On Mon, 18 Feb 2013, Otavio Salvador wrote:
>
>> >> I thought the ehci-pci module would be load for every ehci PCI; What
>> >> do you think?
>> >
>> > The kernel can't guarantee anything about what driver modules are
>> > loaded. That's up to u
On Mon, Feb 18, 2013 at 02:26:18PM -0800, Greg KH wrote:
> I don't know, it depends on if userspace can handle this properly or
> not. What tools rely on this sysfs file? WHat happens when they get a
> non-number in the file?
I'm not aware of any, frankly speaking.
If there are any, those tools s
Hi Steve,
I noticed this commit in the cifs tree today:
cc67d17bffd7 "This patch applies to the kernel version of linux-3.8-rc6."
That really is not a good summary line for the commit and this commit
appears to be authored by you and committed by you, but has no
Signed-off-by line from you.
--
On 02/18/2013 03:59 PM, Dan Magenheimer wrote:
>> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
>> Subject: Re: [PATCHv5 4/8] zswap: add to mm/
>>
>> On 02/18/2013 01:55 PM, Dan Magenheimer wrote:
From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
Subject: Re: [PATCHv5 4/
Fix the following compilation warnings (in Simon Horman's renesas.git repo):
In file included from arch/arm/mach-shmobile/setup-r8a7779.c:24:0:
include/linux/of_platform.h:107:13: warning: ‘struct of_device_id’ declared
inside parameter list [enabled by default]
include/linux/of_platform.h:107:13:
Instead of assigning the pm_ops fields individually we can simply use
SIMPLE_DEV_PM_OPS.
Signed-off-by: Peter Huewe
---
drivers/staging/sm7xxfb/sm7xxfb.c | 10 +-
1 files changed, 1 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/sm7xxfb/sm7xxfb.c
b/drivers/staging/sm7xxfb
Matthieu Moy writes:
> Junio C Hamano writes:
>
>> Git v1.8.2 Release Notes (draft)
>>
>>
>> Backward compatibility notes
>>
>>
>> In the upcoming major release (tentatively called 1.8.2), we will
>> change the behavior of the "git push" comm
I will fix it - the patch had to be hand edited due to formatting
issues, and obviously screwed up the subject line.
On Mon, Feb 18, 2013 at 4:47 PM, Stephen Rothwell wrote:
>
> Hi Steve,
>
> I noticed this commit in the cifs tree today:
>
> cc67d17bffd7 "This patch applies to the kernel version
> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> Subject: Re: [PATCHv5 4/8] zswap: add to mm/
>
> On 02/18/2013 03:59 PM, Dan Magenheimer wrote:
> > please document in Documentation/kernel-parameters.txt.
>
> Will do.
> >>>
> >>> Is that a good idea? Konrad's frontswap/c
On Mon, Feb 18, 2013 at 11:27:43AM +0100, Jiri Slaby wrote:
> Hi,
>
> we have a report of WARNING from 3.7.6 in nouveau at
> drivers/gpu/drm/nouveau/core/core/mm.c:242 here:
> https://bugzilla.novell.com/show_bug.cgi?id=802347#c11
>
> There is an order 4 allocation failure in nouveau_drm_open ->
On 02/19/2013 12:23 AM, Marcin Slusarz wrote:
> On Mon, Feb 18, 2013 at 11:27:43AM +0100, Jiri Slaby wrote:
>> Hi,
>>
>> we have a report of WARNING from 3.7.6 in nouveau at
>> drivers/gpu/drm/nouveau/core/core/mm.c:242 here:
>> https://bugzilla.novell.com/show_bug.cgi?id=802347#c11
>>
>> There is
> > Not-yet-signed-off-by: Steven Rostedt
> >
> > ... so I was holding off on doing anything with it.
>
> Heh, and I was waiting for comments from you before doing anything further
> with it ;-)
>
> Email review deadlock!
So, how do you plan to push ahead with this patch?
https://lkml.org/lkm
> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> Subject: Re: [PATCH] zsmalloc: Add Kconfig for enabling PTE method
>
> On 02/16/2013 12:28 AM, Ric Mason wrote:
> > On 02/04/2013 08:23 AM, Minchan Kim wrote:
> >> + for object mapping. You can check speed with zsmalloc
> >> benchma
On 02/18/2013 03:45 PM, Seiji Aguchi wrote:
Not-yet-signed-off-by: Steven Rostedt
... so I was holding off on doing anything with it.
Heh, and I was waiting for comments from you before doing anything further with
it ;-)
Email review deadlock!
So, how do you plan to push ahead with this p
On Sat, Feb 16, 2013 at 11:46 AM, Oleg Nesterov wrote:
> On 02/16, Oleg Nesterov wrote:
>>
>> On 02/16, Mandeep Singh Baines wrote:
>> >
>> > +static int sigkill_pending(struct task_struct *tsk)
>> > +{
>> > + return signal_pending(tsk) &&
>> > + (sigismember(&tsk->pending.signal, SIG
Hi,
This might be a stupid question, but I'm somehow stuck here. I'm using a
driver with the following DTS sub-node:
ref25: ref25M {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <2500>;
};
clock-gene
Junio C Hamano writes:
>> I don't understand: wasn't this supposed to happen in Git 2.0? Did you
>> mean "In the upcoming major release (tentatively called *2.0*)"?
>
> Thanks. I am not sure what I was thinking. Perhaps when we started
> this cycle we did want to merge the push-2.0-default-to-s
1 - 100 of 552 matches
Mail list logo