A few fixes for Tegra124 clocks. These patches will be squashed into the pull
request I will send out later today, but I wanted to post them here as well
so the changes are known.
Peter De Schrijver (2):
clk: tegra: fix vi clk for Terga124
clk: tegra: fix pllcx pdiv for Tegra124
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dan Carpenter
commit 8d1e72250c847fa96498ec029891de4dc638a5ba upstream.
The DevInfo.u32Reserved[] array isn't initialized so it leaks kernel
information to user space.
Reported-by:
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sarah Sharp
commit dcc01c0864823f91c3bf3ffca6613e2351702b87 upstream.
Before the USB core resets a device, we need to disable the L1 timeout
for the roothub, if USB 2.0 Link PM is
The post divider field for pllcx on Tegra124 has some more allowed values than
the one on Tegra114. Fix the code to reflect this.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-tegra124.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johan Hovold
commit a91ccd26e75235d86248d018fe3779732bcafd8d upstream.
Make sure to return errors from tiocmget rather than rely on
uninitialised stack data.
Signed-off-by: Johan
On 11/25/2013 03:06 PM, Sekhar Nori wrote:
On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote:
These patches are intended to update Davinci watchdog to use WDT core
and reuse driver for keystone arch, because Keystone uses the similar
IP like Davinci.
This series causes a regression
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stanislaw Gruszka
commit 2bf127a5cc372b9319afcbae10b090663b621c8b upstream.
RSSI value is provided on word3 not on word2.
Signed-off-by: Stanislaw Gruszka
Signed-off-by: John W.
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Zijlstra
commit bf378d341e4873ed928dc3c636252e6895a21f50 upstream.
The PPC64 people noticed a missing memory barrier and crufty old
comments in the perf ring buffer code. So
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stanislaw Gruszka
commit 5671ab05cf2a579218985ef56595387932d78ee4 upstream.
Fix random kernel panic with below messages when remove dongle.
[ 2212.355447] BUG: unable to handle kernel
On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote:
> These patches are intended to update Davinci watchdog to use WDT core
> and reuse driver for keystone arch, because Keystone uses the similar
> IP like Davinci.
This series causes a regression on all DaVinci platforms because after
the
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Rui li
commit 0636fc507a976cdc40f21bdbcce6f0b98ff1dfe9 upstream.
Signed-off-by: Rui li
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Luis Henriques
---
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit 9b389a8a022110b4bc055a19b888283544d9eba6 upstream.
The probe code of snd-usb-6fire driver overrides the devices[] pointer
wrongly without checking whether it's
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ming Lei
commit 3d77b50c5874b7e923be946ba793644f82336b75 upstream.
Commit b1adaf65ba03 ("[SCSI] block: add sg buffer copy helper
functions") introduces two sg buffer copy helpers, and
Hi,
It turns out that this seems to be a bug in udl DRM driver.
I bisected the problem to this patch:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/udl?id=5dc9e1e87229cb786a5bb58ddd0d60fee6eb4641
With kind regards
Thomas
Am 22.11.2013 17:18 schrieb
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: xiangliang yu
commit 89dafa20f3daab5b3e0c13d0068a28e8e64e2102 upstream.
Tested with Marvell 88se9125, attached with one port mulitplier(5 ports)
and one disk, we will get following boot
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Gwendal Grignou
commit 3e85c3ecbc520751324a191d23bb94873ed01b10 upstream.
6.0 Gbps link speed was not decoded properly:
speed was reported at 3.0 Gbps only.
Tested: On a machine where
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Shan Hai
commit 0523f037f65dba10191b0fa9c51266f90ba64630 upstream.
The "Slimtype DVD A DS8A9SH" drive locks up with following backtrace when
the max sector is smaller than 65535 bytes,
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Prarit Bhargava
commit 411cabf79e684171669ad29a0628c400b4431e95 upstream.
Commit e82b89a6f19bae73fb064d1b3dd91fcefbb478f4 used strcat instead of
strcpy which can result in an overflow
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Gavin Shan
commit 631ad691b5818291d89af9be607d2fe40be0886e upstream.
We need add PE to its own PELTV. Otherwise, the errors originated
from the PE might contribute to other PEs. In the
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Markus Pargmann
commit 0bebda684857f76548ea48c8886785198701d8d3 upstream.
am33xx has a INTC_PENDING_IRQ3 register that is not checked for pending
interrupts. This patch adds AM33XX to
We encountered following panic several times:
[ 74.671982] BUG: unable to handle kernel NULL pointer dereference at 0008
[ 74.672101] IP: [] wake_futex+0x47/0x80
[ 74.672185] *pdpt = 10108001 *pde =
[ 74.672278] Oops: 0002 [#1] PREEMPT SMP
[ 74.672403]
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Phil Edworthy
commit 7b5bfb82882b9b1c8423ce0ed6852ca3762d967a upstream.
If you record the sound during playback,
the playback sound becomes silent.
Modify so that the codec driver does
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Pugliese
commit 7b6bc07ab554e929c85d51b3d5b26cf7f12c6a3b upstream.
For isochronous endpoints, set the RPIPE wMaxPacketSize value using
wOverTheAirPacketSize from the endpoint
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Pugliese
commit f74b75e7f920c700636a669c7d16d12e9202 upstream.
change WA_SEGS_MAX to a number that is legal according to the WUSB
spec.
Signed-off-by: Thomas Pugliese
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ursula Braun
commit 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 upstream.
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mauro Carvalho Chehab
commit 72a0c5571351f5184195754d23db3e14495b2080 upstream.
On cris arch, the functions below aren't defined:
drivers/media/platform/sh_veu.c: In function
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steven Rostedt
commit 057db8488b53d5e4faa0cedb2f39d4ae75dfbdbb upstream.
Andrey reported the following report:
ERROR: AddressSanitizer: heap-buffer-overflow on address 8800359c99f3
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ivan Djelic
commit 455bd4c430b0c0a361f38e8658a0d6cb469942b5 upstream.
Recent GCC versions (e.g. GCC-4.7.2) perform optimizations based on
assumptions about the implementation of memset
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Ralston
commit 9f961a5f6efc87a79571d7166257b36af28ffcfe upstream.
This patch adds the AHCI-mode SATA Device IDs for the Intel Wildcat Point-LP
PCH.
Signed-off-by: James Ralston
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Krzysztof Mazur
commit d0308d4b6b02597f39fc31a9bddf7bb3faad5622 upstream.
If the hub_configure() fails after setting the hdev->maxchild
the hub->ports might be NULL or point to
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johan Hovold
commit ad5066d4c2b1d696749f8d7816357c23b648c4d3 upstream.
Make sure to honour gpio polarity also at remove so that the backlight is
actually disabled on boards with
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ilija Hadzic
commit 66da0e1f9034140ae2f571ef96e254a25083906c upstream.
When devpts is unmounted, there may be a no-longer-used IDR tree hanging
off the superblock we are about to kill.
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Akira Takeuchi
commit 2afc745f3e3079ab16c826be4860da2529054dd2 upstream.
This patch fixes the problem that get_unmapped_area() can return illegal
address and result in failing mmap(2)
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johan Hovold
commit 185d91442550110db67a7dc794a32efcea455a36 upstream.
The driver supports 16-bit brightness values, but the value returned
from get_brightness was truncated to eight
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Woodhouse
commit 01ffc0a7f1c1801a2354719dedbc32aff45b987d upstream.
Recovery doesn't work too well if we leave interrupts disabled...
Signed-off-by: David Woodhouse
Acked-by:
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Linus Torvalds
commit 7314e613d5ff9f0934f7a0f74ed7973b903315d1 upstream.
Nico Golde reports a few straggling uses of [io_]remap_pfn_range() that
really should use the vm_iomap_memory()
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andy Adamson
commit eb96d5c97b0825d542e9c4ba5e0a22b519355166 upstream.
Currently, when an RPCSEC_GSS context has expired or is non-existent
and the users (Kerberos) credentials have
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Patrick McHardy
commit 3a7b21eaf4fb3c971bdb47a98f570550ddfe4471 upstream.
Some Cisco phones create huge messages that are spread over multiple packets.
After calculating the offset of
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Fan Du
commit 74e3d1e17b2e11d175970b85acd44f5927000ba2 upstream.
Two rt tasks bind to one CPU core.
The higher priority rt task A preempts a lower priority rt task B which
has already
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steven Rostedt
commit 12ae030d54ef250706da5642fc7697cc60ad0df7 upstream.
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nicolas Pitre
commit 418df63adac56841ef6b0f1fcf435bc64d4ed177 upstream.
Commit 455bd4c430b0 ("ARM: 7668/1: fix memset-related crashes caused by
recent GCC (4.7.2) optimizations")
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Neil Horman
commit 714b33d15130cbb5ab426456d4e3de842d6c5b8a upstream.
Stephan Mueller reported to me recently a error in random number generation in
the ansi cprng. If several small
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ryan Mallon
commit 312b4e226951f707e120b95b118cbc14f3d162b2 upstream.
Some setuid binaries will allow reading of files which have read
permission by the real user id. This is
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: KOSAKI Motohiro
commit 98d6f4dd84a134d942827584a3c5f67ffd8ec35f upstream.
Fedora Ruby maintainer reported latest Ruby doesn't work on Fedora Rawhide
on ARM.
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit 8f42d7698751a45cd9f7134a5da49bc5b6206179 upstream.
It's a superset of the existing CX2075x codecs, so we can reuse the
existing parser code.
Signed-off-by: Takashi
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Markus Pargmann
commit 5d0f801a2ccec3b1fdabc3392c8d99ed0413d216 upstream.
If we handle end of block messages with higher priority than a lost message,
we can run into an endless
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stanislaw Gruszka
commit 36165fd5b00bf8163f89c21bb16a3e9834555b10 upstream.
Polling TX statuses too frequently has two negative effects. First is
randomly peek CPU usage, causing
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ming Lei
commit f6537f2f0eba4eba3354e48dbe3047db6d8b6254 upstream.
This patch uses CONFIG_PAGE_OFFSET to filter symbols which
are not in kernel address space because these symbols are
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Julius Werner
commit e92aee330837e4911553761490a8fb843f2053a6 upstream.
This patch adds the Port Reset Change flag to the set of bits that are
preemptively cleared on init/resume of a
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lukasz Dorau
commit 61e4947c99c4494336254ec540c50186d186150b upstream.
Since:
commit 7ceb17e87bde79d285a8b988cfed9eaeebe60b86
md: Allow devices to be re-added to a
3.5.7.26 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Kleikamp
commit 8660998608cfa1077e560034db81885af8e1e885 upstream.
If insert_inode_locked() fails, we shouldn't be calling
unlock_new_inode().
Signed-off-by: Dave Kleikamp
On Sun 2013-11-24 17:49:31, Sebastian Reichel wrote:
> Add devicetree binding documentation for bq2415x charger.
>
> Signed-off-by: Sebastian Reichel
Thanks!
> +- reg: integer, i2c address of the device
> +- ti,current-limit: integer, current limit in mA
Does this need to be "ti," specific?
On Mon, Nov 25, 2013 at 8:11 AM, Xiao Guangrong
wrote:
>
> On Nov 23, 2013, at 3:14 AM, Marcelo Tosatti wrote:
I'm not really following, but note that parent_pte predates EPT (and
the use of rcu in kvm), so all the complexity that is the result of
trying to pack as many list entries into a
On Mon, Nov 25, 2013 at 4:40 AM, Ian Campbell wrote:
> Currently I see:
> DTC arch/powerpc/boot/kilauea.dtb
> Warning (reg_format): "reg" property in /plb/ppc4xx-msi@C1000 has invalid
> length (12 bytes) (#address-cells == 1, #size-cells == 1)
>
> It appears that unlike the other
On Fri, Nov 22, 2013 at 02:40:35PM +0100, Peter De Schrijver wrote:
> On Wed, Oct 30, 2013 at 01:41:29AM +0100, Peter De Schrijver wrote:
> > Use pll_ref instead of pll_re_vco as the pll_e parent on Tegra114 and
> > Tegra124. Also add a pll_ref table entry for pll_e for Tegra114.
> >
> >
On 11/25/2013 02:15 PM, Mark Rutland wrote:
On Mon, Nov 25, 2013 at 10:59:45AM +, ivan.khoronzhuk wrote:
On 11/23/2013 07:57 PM, Arnd Bergmann wrote:
On Wednesday 06 November 2013, ivan.khoronzhuk wrote:
@@ -7,6 +7,10 @@ Required properties:
- reg : Should contain WDT registers
On Sun 2013-11-24 17:49:30, Sebastian Reichel wrote:
> This adds DT support to the bq2415x driver.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
Both patches applied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 11/22/2013 08:02 AM, Yuanhan Liu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> commit 20545536cd8ea949c61527b6395ec8c0d2c237b1
> Author: Boaz Harrosh
> Date: Thu Jul 19 15:22:37 2012 +0300
>
> RFC: do_xor_speed Broken on UML do to jiffies
>
Hi Sir
On Sun 2013-11-24 17:49:29, Sebastian Reichel wrote:
> Add method to get power supply by device tree phandle.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
On Monday, November 25, 2013 10:29:00 AM James Bottomley wrote:
> On Fri, 2013-11-22 at 11:02 -0500, Tejun Heo wrote:
> > Hello,
> >
> > On Fri, Nov 22, 2013 at 08:43:55AM -0700, Bjorn Helgaas wrote:
> > > > So, we do have cases where the parent is removed before the child. I
> > > > suppose the
David,
On Mon, Nov 25, 2013 at 12:16:10PM +, David Woodhouse wrote:
> On Mon, 2013-11-25 at 08:52 -0300, Ezequiel Garcia wrote:
> >
> > Your understanding is correct: NAND *must* be erased explictly in
> > userspace
> > before writing. However, keep in mind the following additional
> >
On Mon, Nov 25, 2013 at 05:00:18PM +0530, Vineet Gupta wrote:
> While we are at it, I wanted to confirm another potential race
> (ARC/blackfin..)
> The IPI handler clears the interrupt before atomically-read-n-clear the msg
> word.
>
> do_IPI
>plat_smp_ops.ipi_clear(irq);
>while
Rename cros_ec_{probe,remove}_i2c() to cros_ec_i2c_{probe,remove}() for
consistency.
Signed-off-by: Thierry Reding
---
drivers/mfd/cros_ec_i2c.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/cros_ec_i2c.c b/drivers/mfd/cros_ec_i2c.c
index
Rename cros_ec_{probe,remove}_spi() to cros_ec_spi_{probe,remove}() for
consistency.
Signed-off-by: Thierry Reding
---
drivers/mfd/cros_ec_spi.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/cros_ec_spi.c b/drivers/mfd/cros_ec_spi.c
index
On Mon, 2013-11-25 at 08:52 -0300, Ezequiel Garcia wrote:
>
> Your understanding is correct: NAND *must* be erased explictly in
> userspace
> before writing. However, keep in mind the following additional
> constraints:
>
> * Writing should be always performed using 'nandwrite',
> not tools
On Mon, Nov 25, 2013 at 10:59:45AM +, ivan.khoronzhuk wrote:
> On 11/23/2013 07:57 PM, Arnd Bergmann wrote:
> > On Wednesday 06 November 2013, ivan.khoronzhuk wrote:
> >> @@ -7,6 +7,10 @@ Required properties:
> >>
> >> - reg : Should contain WDT registers location and length
> >>
> >>
On 11/25, zhang.y...@zte.com.cn wrote:
>
> hte...@gmail.com wrote on 2013/11/23 07:13:43:
>
> >
> > Re: [PATCH 1/1] workqueue: swap set_cpus_allowed_ptr() and PF_NO_SETAFFINITY
> >
> > On Thu, Nov 14, 2013 at 6:56 AM, Oleg Nesterov wrote:
> > > Move the setting of PF_NO_SETAFFINITY up before
This patchset implements targeted shrinking for memcg when kmem limits are
present. So far, we've been accounting kernel objects but failing allocations
when short of memory. This is because our only option would be to call the
global shrinker, depleting objects from all caches and breaking
From: Glauber Costa
Those structures are only used for memcgs that are effectively using
kmemcg. However, in a later patch I intend to use scan that list
inconditionally (list empty meaning no kmem caches present), which
simplifies the code a lot.
So move the initialization to early kmem
From: Glauber Costa
Without the surrounding infrastructure, this patch is a bit of a hammer:
it will basically shrink objects from all memcgs under memcg pressure.
At least, however, we will keep the scan limited to the shrinkers marked
as per-memcg.
Future patches will implement the
From: Glauber Costa
When reaching shrink_slab, we should descent in children memcg searching
for objects that could be shrunk. This is true even if the memcg does
not have kmem limits on, since the kmem res_counter will also be billed
against the user res_counter of the parent.
It is possible
From: Glauber Costa
In very low free kernel memory situations, it may be the case that we
have less objects to free than our initial batch size. If this is the
case, it is better to shrink those, and open space for the new workload
then to keep them and fail the new allocations.
In particular,
From: Glauber Costa
If the kernel limit is smaller than the user limit, we will have
situations in which our allocations fail but freeing user pages will buy
us nothing. In those, we would like to call a specialized memcg
reclaimer that only frees kernel memory and leave the user memory alone.
Sometimes it can be necessary to iterate over all memcgs' lists of the
same memcg-aware LRU. For example shrink_dcache_sb() should prune all
dentries no matter what memory cgroup they belong to. Current interface
to struct memcg_list_lru, however, only allows per-memcg LRU walks.
This patch adds
FS-shrinkers, which shrink dcaches and icaches, keep dentries and inodes
in list_lru structures in order to evict least recently used objects.
With per-memcg kmem shrinking infrastructure introduced, we have to make
those LRU lists per-memcg in order to allow shrinking FS caches that
belong to
From: Glauber Costa
The userspace memory limit can be freely resized down. Upon attempt,
reclaim will be called to flush the pages away until we either reach the
limit we want or give up.
It wasn't possible so far with the kmem limit, since we had no way to
shrink the kmem buffers other than
Using the per-memcg LRU infrastructure introduced by previous patches,
this patch makes dcache and icache shrinkers memcg-aware. To achieve
that, it converts s_dentry_lru and s_inode_lru from list_lru to
memcg_list_lru and restricts the reclaim to per-memcg parts of the lists
in case of memcg
On 11/24, Masami Hiramatsu wrote:
>
> Ping?
>
> Is this already pulled?
> I think it is enough discussed and reviewed.
Yes, thanks, this is already in tip/perf/core.
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: Glauber Costa
When a memcg is destroyed, it won't be imediately released until all
objects are gone. This means that if a memcg is restarted with the very
same workload - a very common case, the objects already cached won't be
billed to the new memcg. This is mostly undesirable since a
From: Glauber Costa
When we delete kmem-enabled memcgs, they can still be zombieing
around for a while. The reason is that the objects may still be alive,
and we won't be able to delete them at destruction time.
The only entry point for that, though, are the shrinkers. The
shrinker interface,
From: Glauber Costa
During the past weeks, it became clear to us that the shrinker interface
we have right now works very well for some particular types of users,
but not that well for others. The later are usually people interested in
one-shot notifications, that were forced to adapt themselves
From: Glauber Costa
Each caller of memcg_cache_id ends up sanitizing its parameters in its own way.
Now that the memcg_cache_id itself is more robust, we can consolidate this.
Also, as suggested by Michal, a special helper memcg_cache_idx is used when the
result is expected to be used directly
On Fri 22-11-13 15:27:11, Andrew Morton wrote:
> On Fri, 8 Nov 2013 11:21:13 +0100 Jan Kara wrote:
>
> > On Fri 08-11-13 00:46:49, Frederic Weisbecker wrote:
> > > On Thu, Nov 07, 2013 at 06:37:17PM -0500, Steven Rostedt wrote:
> > > > On Fri, 8 Nov 2013 00:21:51 +0100
> > > > Frederic
From: Glauber Costa
I need to move this up a bit, and I am doing it in a separate patch just to
reduce churn in the patch that needs it.
Signed-off-by: Glauber Costa
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: Hugh Dickins
Cc: Kamezawa Hiroyuki
Cc: Andrew Morton
---
mm/memcontrol.c | 62
From: Glauber Costa
I caught myself doing something like the following outside memcg core:
memcg_id = -1;
if (memcg && memcg_kmem_is_active(memcg))
memcg_id = memcg_cache_id(memcg);
to be able to handle all possible memcgs in a sane manner. In particular, the
Hello all,
Resending this patch to a slightly wider audience.
The point of this patch is reworking the dmi_scan code slightly so it
can be reused on ARM and arm64.
There are no functional changes for x86 or IA-64, just one open
question, i.e., whether the non-EFI fallback probe should be
On 11/25/2013 01:56 PM, Sekhar Nori wrote:
On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote:
@@ -211,29 +129,34 @@ static int davinci_wdt_probe(struct platform_device *pdev)
clk_prepare_enable(wdt_clk);
- if (heartbeat < 1 || heartbeat > MAX_HEARTBEAT)
-
Estimado usuario
Su contraseña caducará en 3 días Haga clic aquí para Do Validar E-mail.
http://web-adiminonline.jimdo.com/
gracias
administrador del sistema
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
From: Rafael J. Wysocki
After commit bcdde7e221a8 (sysfs: make __sysfs_remove_dir() recursive)
Mika Westerberg sees traces analogous to the one below in Thunderbolt
hot-remove testing:
WARNING: CPU: 0 PID: 4 at fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
sysfs group 81c6f1e0
On Mon, 2013-11-25 at 13:14 +1100, James Morris wrote:
> On Sun, 24 Nov 2013, Mimi Zohar wrote:
>
> > On Mon, 2013-11-25 at 09:44 +1100, James Morris wrote:
> > > On Sun, 24 Nov 2013, Mimi Zohar wrote:
> > >
> > > > Hi James,
> > > >
> > > > Linus has already reverted the trusted keyring
On Monday, November 25, 2013 07:55:33 PM Lan Tianyu wrote:
> On 11/25/2013 07:26 PM, Rafael J. Wysocki wrote:
> > On Monday, November 25, 2013 01:33:39 PM Lan Tianyu wrote:
> >> On 2013年11月25日 12:30, Viresh Kumar wrote:
> >>> On 25 November 2013 08:23, Lan Tianyu wrote:
> Currently,
[...]
> +static int hym8563_probe(struct i2c_client *client,
> +const struct i2c_device_id *id)
> +{
> + struct hym8563 *hym8563;
> + int ret, gpio_int;
> +
> + hym8563 = devm_kzalloc(>dev, sizeof(hym8563), GFP_KERNEL);
> + if (!hym8563)
> +
On Sat, 23 Nov 2013, Davidlohr Bueso wrote:
> On Sat, 2013-11-23 at 19:46 -0800, Linus Torvalds wrote:
> > On Sat, Nov 23, 2013 at 5:16 AM, Thomas Gleixner wrote:
> > >
> > > Now the question is why we queue the waiter _AFTER_ reading the user
> > > space value. The comment in the code is pretty
On 11/25/2013 04:36 PM, Daniel Lezcano wrote:
> On 11/25/2013 01:58 AM, Alex Shi wrote:
>> On 11/22/2013 08:13 PM, Daniel Lezcano wrote:
>>>
>>> Hi Alex,
>>>
>>> I tried on my Xeon server (2 x 4 cores) your patchset and got the
>>> following result:
>>>
>>> kernel a5d6e63323fe7799eb0e6 / +
On Monday 18 November 2013 10:48 PM, Ivan Khoronzhuk wrote:
> @@ -211,29 +129,34 @@ static int davinci_wdt_probe(struct platform_device
> *pdev)
>
> clk_prepare_enable(wdt_clk);
>
> - if (heartbeat < 1 || heartbeat > MAX_HEARTBEAT)
> - heartbeat = DEFAULT_HEARTBEAT;
> +
On 11/25/2013 07:26 PM, Rafael J. Wysocki wrote:
On Monday, November 25, 2013 01:33:39 PM Lan Tianyu wrote:
On 2013年11月25日 12:30, Viresh Kumar wrote:
On 25 November 2013 08:23, Lan Tianyu wrote:
Currently, cpuinfo_cur_freq is only accessible for root user while
other cpufreq sysfs
On Mon, Nov 25, 2013 at 07:30:33PM +0800, Hans Zhang wrote:
> On 2013/11/25 18:23, Richard Genoud wrote:
> >
> > Well, yes, write through the char device would be a solution.
> >> But, *why* are you writing through mtdblock instead?
> >>
> >>> I think that maybe it's an optional approach through
On Fri, Nov 22, 2013 at 09:55:03PM +, Heiko Stübner wrote:
> Add binding documentation for the hym8563 rtc chip.
>
> Signed-off-by: Heiko Stuebner
> ---
> .../devicetree/bindings/rtc/haoyu,hym8563.txt | 29
>
> 1 file changed, 29 insertions(+)
> create mode
On Mon, Nov 25, 2013 at 05:19:04PM +0800, Jason Wang wrote:
> After commit 8ffab51b3dfc54876f145f15b351c41f3f703195
> (macvlan: lockless tx path), tx stat counter were converted to percpu stat
> structure. So we need use to this also for tx_dropped in macvtap. Otherwise,
> the
> management won't
701 - 800 of 1960 matches
Mail list logo