3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Amitkumar Karwar
commit d7b9c5204e9c6810a20d509ee47bc70419096e59 upstream.
Currently "adapter->config_bands" is updated during infra
association only if channel is provided by user in "iw
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Avinash Patil
commit 83f0c6d1f502bd75bb4a9e31e8d64e59c6894ad1 upstream.
Add missing "!" as we are supposed to check "!card->adapter"
in PCIe suspend handler.
Signed-off-by: Avinash Patil
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jerome Glisse
commit e521a29014794d139cca46396d1af8faf1295a26 upstream.
Aruba and newer gpu does not need the avivo cursor work around,
quite the opposite this work around lead to corruption.
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Piotr Haber
commit c4dea35e34f5f46e1701156153a09cce429d1ea9 upstream.
The .tx() callback function can drop packets when there is no
space in the DMA fifo. Propagate that information to caller
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jonathan Brassow
commit 55ebbb59c1c6eb1b040f62b8c4ae0b724de6e55a upstream.
Before attempting to activate a RAID array, it is checked for sufficient
redundancy. That is, we make sure that
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit aacde9ee45225f7e0b90960f479aef83c66bfdc0 upstream.
Since:
commit b23b025fe246f3acc2988eb6d400df34c27cb8ae
Author: Ben Greear
Date: Fri Feb 4 11:54:17 2011 -0800
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Sujith Manoharan
commit 0981c3b24ef664f5611008a6e6d0622fac6d892b upstream.
SKBs that are allocated in the HTC layer do not have callbacks
registered and hence ended up not being freed, Fix
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit a3dc48e82bb146ef11cf75676c8410c1df29b0c4 upstream.
On AR9300 the rx FIFO needs to be empty during reset to ensure that no
further DMA activity is generated, otherwise it
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 1adb2e2b5f85023d17eb4f95386a57029df27c88 upstream.
When the next beacon is sent, the ath_buf from the previous run is reused.
If getting a new beacon from mac80211 fails,
From: Bjorn Mansson
Adding ftrace to the mmc layer facilitates debugging,
making it easier to debug commend sequences without
rebuilding the kernel.
It is also possible to parse the ftrace output into
VCD format and visualize it in GTKWave.
Patch is for the 3.7.5 Kernel.
Signed-off-by: Bjorn
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 24171dd92096fc370b195f3f6bdc0798855dc3f9 upstream.
Chain swapping should only be enabled when the EEPROM chainmask is set to 5,
regardless of what the runtime chainmask
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit fea92cbf0850d788683827990670d3968f893327 upstream.
Signed-off-by: Felix Fietkau
Signed-off-by: John W. Linville
Signed-off-by: Greg Kroah-Hartman
---
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Ladisch
commit d56268fb108c7c21e19933588ca4d94652585183 upstream.
Commit 23caaf19b11e (ALSA: usb-mixer: Add support for Audio Class v2.0)
forgot to adjust the length check for UAC 2.0
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit fcd8f3b1d43c645e291638bc6c80a1c680722869 upstream.
This patch enables internal mic input on the machine.
BugLink: https://bugs.launchpad.net/bugs/1107477
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Rattray
commit a80cc734282805e15b5e023751a4d02f7ffbcc91 upstream.
Signed-off-by: Chris Rattray
Signed-off-by: Mark Brown
Signed-off-by: Greg Kroah-Hartman
---
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Anderson Lizardo
commit 0a9ab9bdb3e891762553f667066190c1d22ad62b upstream.
The length parameter should be sizeof(req->name) - 1 because there is no
guarantee that string provided by userspace
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 9ddf1aeb2134e72275c97a2c6ff2e3eb04f2f27a upstream.
For non-snoop mode, we fiddle with the page attributes of CORB/RIRB
and the position buffer, but also the ring buffers.
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Vetter
commit 9452618e7462181ed9755236803b6719298a13ce upstream.
DMAR support on g4x/gm45 integrated gpus seems to be totally busted.
So don't bother, but instead disable it by default
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 4ae19c2dd713edb7b8ad3d4ab9d234ed5dcb6b98 upstream.
The reference counting in nfs4_init_client assumes wongly that it
is safe for nfs4_discover_server_trunking() to
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 65436ec0c8e344d9b23302b686e418f2a7b7cf7b upstream.
We do need to start the lease recovery thread prior to waiting for the
client initialisation to complete in NFSv4.1.
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Wang YanQing
commit f44310b98ddb7f0d06550d73ed67df5865e3eda5 upstream.
I get the following warning every day with v3.7, once or
twice a day:
[ 2235.186027] WARNING: at
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Cox
commit c903f0456bc69176912dee6dd25c6a66ee1aed00 upstream.
At the moment the MSR driver only relies upon file system
checks. This means that anything as root with any capability set
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Fleming
commit e0094244e41c4d0c7ad69920681972fc45d8ce34 upstream.
It has been reported that running this driver on some Samsung laptops
with EFI can cause those machines to become bricked
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: David Woodhouse
commit f791620fa7517e1045742c475a7f005db9a634b8 upstream.
If the bootloader calls the EFI handover entry point as a standard function
call, then it'll have a return address on
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Chinner
commit eb178619f930fa2ba2348de332a1ff1c66a31424 upstream.
When _xfs_buf_find is passed an out of range address, it will fail
to find a relevant struct xfs_perag and oops with a
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Ilija Hadzic
commit 1da80cfa8727abf404fcee44d04743febea54069 upstream.
If one (but not both) allocations of p->chunks[].kpage[]
in radeon_cs_parser_init fail, the error path will free
the
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: David Woodhouse
commit 70a479cbe80296d3113e65cc2f713a5101061daf upstream.
When booting under OVMF we have precisely one GOP device, and it
implements the ConOut protocol.
We break out of the
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: "H. Peter Anvin"
commit e43b3cec711a61edf047adf6204d542f3a659ef8 upstream.
early_pci_allowed() and read_pci_config_16() are only available if
CONFIG_PCI is defined.
Signed-off-by: H. Peter
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Bellinger
This is to fix a regression that only affect the stable (not for the mainline)
that the stable commit fdf9d86 was incorrectly placed dev->dev_link_magic check
before the *dev
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Chinner
[Please take this patch for -stable in kernels 3.5-3.7. It doesn't have an
equivalent upstream commit because the code was removed before the bug was
discovered. See f661f1e0bf50
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Hockney
commit 0c36b48b36dc84d4215dc9d1cde1bda829214ba6 upstream.
For tunnelled ipv6in4 packets, the LOG target (xt_LOG.c) adjusts
the start of the mac field to start at the ethernet
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Pablo Neira Ayuso
commit e035edd16ee834989beedfc215e15cab3a07 upstream.
In (0c36b48 netfilter: nfnetlink_log: fix mac address for 6in4 tunnels)
the include file that defines ARPD_SIT was
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Pablo Neira Ayuso
commit 10db9069eb5c60195170a4119bdbcbce69a4945f upstream.
Florian Westphal reported that the removal of the NOTRACK target
(9655050 netfilter: remove xt_NOTRACK) is breaking
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Pablo Neira Ayuso
commit 757ae316fb35811cfd8c67de0e0b8680ec4c1f37 upstream.
warning: (NETFILTER_XT_TARGET_NOTRACK) selects NETFILTER_XT_TARGET_CT which has
unmet direct
+dependencies (NET &&
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: "Vitaly E. Lavrov"
commit 32263dd1b43378b4f7d7796ed713f77e95f27e8a upstream.
recent_net_exit() is called before recent_mt_destroy() in the
destroy path of network namespaces. Make sure there
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Haibo Xi
commit 97cf00e93cc24898493e7a058105e3215257ee04 upstream.
Commit b836c99fd6c9 (ipv6: unify conntrack reassembly expire
code with standard one) use the standard IPv6 reassembly
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: "Vitaly E. Lavrov"
commit 665e205c16c1f902ac6763b8ce8a0a3a1dcefe59 upstream.
recent_net_exit() is called before recent_mt_destroy() in the
destroy path of network namespaces. Make sure there
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jesper Juhl
commit 1310b955c804975651dca6c674ebfd1cb2b4c7ff upstream.
This patch fixes a leak in one of the error paths of
ctnetlink_create_expect if no helper and no timeout is specified.
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Engelhardt
commit 5b76c4948fe6977bead2359c2054f3e6a2dcf3d0 upstream.
arptables 0.0.4 (released on 10th Jan 2013) supports calling the
CLASSIFY target, but on adding a rule to the wrong
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jani Nikula
commit b514407547890686572606c9dfa4b7f832db9958 upstream.
We stopped reading FORCEWAKE for posting reads in
commit 8dee3eea3ccd3b6c00a8d3a08dd715d6adf737dd
Author: Ben Widawsky
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 3adcf20afb585993ffee24de36d1975f6b26b120 upstream.
During teardown, mac80211 will not return a new beacon. This is normal and
handled properly in the driver, so there's no
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Santos
commit 320cde19a4e8f122b19d2df7a5c00636e11ca3fb upstream.
Patch to add the Formosa Industrial Computing, Inc. Infrared Receiver
[IR605A/Q] to hid-ids.h and hid-quirks.c. This
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit c489ee290bdbbace6bb63ebe6ebd4dd605819495 upstream.
NFS4ERR_DELAY is a legal reply when we call DESTROY_SESSION. It
usually means that the server is busy handling an
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 202c312dba7d95b96493b412c606163a0cd83984 upstream.
If walking the list in nfs4[01]_walk_client_list fails, then the most
likely explanation is that the server dropped
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Ilija Hadzic
commit 25d8999780f8c1f53928f4a24a09c01550423109 upstream.
Index into chunks[] array doesn't look right.
Signed-off-by: Ilija Hadzic
Signed-off-by: Alex Deucher
Signed-off-by:
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Mukund Jampala
commit c6f408996c625cb950cad024f90e50519f94713c upstream.
The problem occurs when iptables constructs the tcp reset packet.
It doesn't initialize the pointer to the tcp header
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 2727de76041b2064c0b74f00a2a89678fb3efafc upstream.
xt_recent can try high order page allocations and this can fail.
iptables: page allocation failure: order:9, mode:0xc0d0
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Pablo Neira Ayuso
commit 1e47ee8367babe6a5e8adf44a714c7086657b87e upstream.
canqun zhang reported that we're hitting BUG_ON in the
nf_conntrack_destroy path when calling kfree_skb while
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: CAI Qian
This is for stable-3.7.y only and this problem has already been solved
in mainline through some slab/slub re-work which isn't suitable to
backport here. See create_kmalloc_cache() in
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Pablo Neira Ayuso
commit 09181842b000344b1205801df3aa5b726c03cc62 upstream.
Two packets may race to create the same entry in the hashtable,
double check if this packet lost race. This double
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
commit 49f8a1a5394d8baee5e56fb71e5cf993c228689a upstream.
Typo for the next pointer means we're walking random data here.
Signed-off-by: Alex Williamson
Signed-off-by:
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Fleming
commit 712ba9e9afc4b3d3d6fa81565ca36fe518915c01 upstream.
efi.runtime_version is erroneously being set to the value of the
vendor's firmware revision instead of that of the
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Nathan Zimmer
commit b8f2c21db390273c3eaf0e5308faeaeb1e233840 upstream.
Update efi_call_phys_prelog to install an identity mapping of all available
memory. This corrects a bug on very large
On Thu, 31 Jan 2013, H. Peter Anvin wrote:
> On 01/30/2013 12:53 AM, Jan Beulich wrote:
> >
> > I'm not convinced that's the right approach - any hypervisor
> > could do similar emulation, and hence you either want to make
> > sure you run on Hyper-V (by excluding all others), or you
> > tolerate
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Fleming
commit 83e68189745ad931c2afd45d8ee3303929233e7f upstream.
Originally 'efi_enabled' indicated whether a kernel was booted from
EFI firmware. Over time its semantics have changed,
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit dee972b967ae111ad5705733de17a3bfc4632311 upstream.
Currently, nfs_xdev_mount converts all errors from clone_server() to
ENOMEM, which can then leak to userspace (for
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 1626e0fa740dec8665a973cf2349405cdfeb46dc upstream.
During FT roaming, wpa_supplicant attempts to set the
key before association. This used to be rejected, but
as a side
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 4b883f021b9ccf2df3d14425e6e610281fb6a35e upstream.
Right now the rx flush is not doing anything useful on AR9003+, as it only
works if the buffers in the rx FIFO have not
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 463e3ed3eacc8f47866e5d612bd8ee0bcee5e2f0 upstream.
The commit "ath9k: fix rx flush handling" added a deadlock that happens
because ath_rx_tasklet is called in a section
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit b59e0f82aa350e380142353fbd30706092ba6312 upstream.
Otherwise we'll get the wrong LRCLK if we need to pick a higher BCLK than
is required.
Signed-off-by: Mark Brown
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 8024c4c0b1057d1cd811fc9c3f88f81de9729fcd upstream.
We're testing for ->show but calling ->store().
Signed-off-by: Dan Carpenter
Signed-off-by: Borislav Petkov
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit ab225417825963b6dc66be7ea80f94ac1378dfdf upstream.
Ensure that any setattr and getattr requests for junctions and/or
mountpoints are sent to the server. Ever since
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 7fc00a3054b70b1794c2d64db703eb467ad0365c upstream.
Ensure that the rx tasklet is no longer running when entering the reset path.
Also remove the distinction between flush
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 0712eea349d8e2b6d0e44b94a752d999319027fb upstream.
A Packard-Bell desktop machine gives no proper pin configuration from
BIOS. It's almost equivalent with the 6stack+fp
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 4668cce527acb3bd048c5e6c99b157a14b214671 upstream.
Fixes a reported CPU soft lockup where the tasklet tries to acquire the
lock and blocks while ath_prepare_reset (holding
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Piotr Haber
commit a1fe52801a992e590cdaee2fb47a94bac9b5da90 upstream.
On hardware reintialization reference count of
already existing timers would be increased again.
This leads to problems on
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 1c8c38c588ea91f8deeae21284840459d1bb58e3 upstream.
This is a required workarounds for all products, especially on gen6+
where it causes the command streamer to fail to
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Dimitris Papastamos
commit b86dc0d8c12bbb9fed3f392c284bdc7114ce00c1 upstream.
We are using S3C_EINT(4) instead of S3C_EINT(5).
Signed-off-by: Dimitris Papastamos
Signed-off-by: Mark Brown
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
commit 6e484be1ccca3ea495db45900fd42aac8d49d754 upstream.
Secondary CPUs should use the __hyp_stub_install_secondary entry
point, so boot mode inconsistencies can be detected.
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit ee50e135aeb048b90fab662e661c58b67341830b upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Ding
commit 10b8c7dff5d3633b69e77f57d404dab54ead3787 upstream.
When it goes to error through line 144, the memory allocated to *devname is
not freed, and the caller doesn't free it either
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 15653371c67c3fbe359ae37b720639dd4c7b42c5 upstream.
Subhash Jadavani reported this partial backtrace:
Now consider this call stack from MMC block driver (this is on the
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Luciano Coelho
commit 7662a9c60fee25d7234da4be6d8eab2b2ac88448 upstream.
Add the UART2 muxing data to the board file (this used to be,
erroneously, done in the bootloader).
Signed-off-by:
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit 71088c4bd9b8f8cbffb0e66f2abc14297e4b2ca8 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
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 watchdog in sequence
i.e. enable watchdog->disable watchdog->enable
On Thu, Jan 31, 2013 at 8:11 PM, Thomas Gleixner wrote:
> +/**
> + * __cpuhp_setup_state - Setup the callbacks for an hotplug machine state
> + * @state: The state to setup
> + * @invoke:If true, the startup function is invoked for cpus where
> + * cpu state >= @state
> + *
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 watchdog in sequence
i.e. enable watchdog->disable watchdog->enable
Please ignore this patch.
On Fri, 2013-02-01 at 19:03 +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
Cho,
On Wed, Jan 02, 2013 at 02:53:49PM +0900, KyongHo Cho wrote:
> On Tuesday, January 1, 2013, Sylwester Nawrocki
> > Cc: devicetree-disc...@lists.ozlabs.org
Since patch 7 of this set is already merged, do you mind to re-post the
rest of this patch-set with the latest comments addressed? I
B1;2601;0cOn Fri, 1 Feb 2013, Tommi Rantala wrote:
> Hello,
>
> Trinity discovered a task_struct leak with clock_nanosleep(), reproducible
> with:
>
> -8<-8<-8<-
> #include
>
> static const struct timespec req;
>
> int main(void) {
> return
On Fri, 1 Feb 2013, Hillf Danton wrote:
> On Thu, Jan 31, 2013 at 8:11 PM, Thomas Gleixner wrote:
> > +/**
> > + for_each_present_cpu(cpu) {
> > + int ret, cpustate = per_cpu(cpuhp_state, cpu);
>
> s/ret,//
Duh, yes.
--
To unsubscribe from this list: send the line
On Mon, Jan 21, 2013 at 07:54:26PM +0900, Hideki EIRAKU wrote:
> This is the Renesas IPMMU driver and IOMMU API implementation.
>
> The IPMMU module supports the MMU function and the PMB function. The
> MMU function provides address translation by pagetable compatible with
> ARMv6. The PMB
On Mon, Jan 21, 2013 at 07:54:25PM +0900, Hideki EIRAKU wrote:
> Hideki EIRAKU (4):
> iommu/shmobile: Add iommu driver for Renesas IPMMU modules
> ARM: mach-shmobile: sh7372: Add IPMMU device
> ARM: mach-shmobile: sh73a0: Add IPMMU device
> ARM: mach-shmobile: r8a7740: Add IPMMU device
On Mon, Jan 28, 2013 at 10:00:08AM +0900, Minchan Kim wrote:
> @@ -663,7 +661,7 @@ static inline void __zs_unmap_object(struct mapping_area
> *area,
>
> flush_cache_vunmap(addr, end);
> unmap_kernel_range_noflush(addr, PAGE_SIZE * 2);
> - local_flush_tlb_kernel_range(addr, end);
On Fri, Feb 01, 2013 at 10:33:04AM +0100, Sedat Dilek wrote:
> Hi Ted,
>
> will those JBD2 fixes in ext4.git#dev [1] get also into mainline kernel(s)?
>
> [ Cut-n-paste out of tig ]
>
> 2013-01-31 13:00 Theodore Ts'o │ o jbd2: track request delay statistics
> 2013-01-30 00:41 Theodore Ts'o
On Fri, Feb 01, 2013 at 02:56:33PM +0100, Joerg Roedel wrote:
> On Mon, Jan 21, 2013 at 07:54:25PM +0900, Hideki EIRAKU wrote:
> > Hideki EIRAKU (4):
> > iommu/shmobile: Add iommu driver for Renesas IPMMU modules
> > ARM: mach-shmobile: sh7372: Add IPMMU device
> > ARM: mach-shmobile:
Hello,
I'd like to revive the topic...
On Tue, 2012-10-16 at 18:23 +0100, Peter Zijlstra wrote:
> On Tue, 2012-10-16 at 12:13 +0200, Stephane Eranian wrote:
> > Hi,
> >
> > There are many situations where we want to correlate events happening at
> > the user level with samples recorded in the
On 02/01/2013 04:57 AM, Ingo Molnar wrote:
>
> * Sasha Levin wrote:
>
>> These headers provide the same API as their pthread mutex counterparts.
>>
>> The design here is to allow to easily switch to liblock lock validation
>> just by adding a "liblock_" to pthread_mutex_*() calls, which means
Hi Felipe, Roger,
On Wed, Jan 30, 2013 at 18:49:17, Mohammed, Afzal wrote:
> On Wed, Jan 30, 2013 at 18:45:04, Balbi, Felipe wrote:
> > On Wed, Jan 30, 2013 at 02:48:50PM +0200, Roger Quadros wrote:
> > > I would appreciate if someone who knows more about beaglebone can help
> > > with
On 02/01/2013 04:21 PM, Mohammed, Afzal wrote:
> Hi Felipe, Roger,
>
> On Wed, Jan 30, 2013 at 18:49:17, Mohammed, Afzal wrote:
>> On Wed, Jan 30, 2013 at 18:45:04, Balbi, Felipe wrote:
>>> On Wed, Jan 30, 2013 at 02:48:50PM +0200, Roger Quadros wrote:
>
I would appreciate if someone who
Hi Roger,
On Fri, Feb 01, 2013 at 19:55:14, Quadros, Roger wrote:
> Thanks Afzal :). You mean the non device tree boot right?
No, dt boot, am335x can only dt boot.
Regards
Afzal
On 02/01/2013 04:27 PM, Mohammed, Afzal wrote:
> Hi Roger,
>
> On Fri, Feb 01, 2013 at 19:55:14, Quadros, Roger wrote:
>
>> Thanks Afzal :). You mean the non device tree boot right?
>
> No, dt boot, am335x can only dt boot.
but DT boot is not supported for OMAP USB Host. How did you get it to
Hi Roger,
On Fri, Feb 01, 2013 at 20:01:38, Quadros, Roger wrote:
> but DT boot is not supported for OMAP USB Host. How did you get it to work?
>
> Are you testing the Host connector or the OTG connector?
If you see latest changes on musb_dsps.c, you will be able to find
out.
As beagle bone
Hello,
On 12/4/2012 3:01 PM, Marek Szyprowski wrote:
mmc_regulator_set_ocr() depends on the ability of regulator to change the
voltage value. When regulator cannot change its voltage output, some code is
skipped to avoid reporting false errors on some boards, which use MMC hosts
with fixed
Hello,
On 12/4/2012 3:01 PM, Marek Szyprowski wrote:
Some regulators don't report any voltage values, so checking supported
voltage range results in disabling all SDHCI_CAN_VDD_* flags and
registration failure. This patch finally provides a correct fix for the
registration of SDHCI driver with
On Fri, Feb 1, 2013 at 2:13 PM, Tao Ma wrote:
> Hi All,
> In our product system, we have several sata disks attached to one
> machine. So when one of the disk fails, the jbd2(yes, we use ext4) will
> hang forever and we will get something in /var/log/messages like below.
> It seems to me
On 31 January 2013 22:10, Rolf Eike Beer wrote:
> H. Peter Anvin wrote:
>> On 01/31/2013 01:42 PM, James Bottomley wrote:
>> > On Thu, 2013-01-31 at 13:29 -0800, H. Peter Anvin wrote:
>> >> On 01/31/2013 12:26 PM, James Bottomley wrote:
>> >>> [adding autofs list and maintainer for their perusal
2013/2/1 Nicolas Pitre :
> On Thu, 31 Jan 2013, Joonsoo Kim wrote:
>
>> A static mapped area is ARM-specific, so it is better not to use
>> generic vmalloc data structure, that is, vmlist and vmlist_lock
>> for managing static mapped area. And it causes some needless overhead and
>> reducing this
On 02/01/2013 04:35 PM, Mohammed, Afzal wrote:
> Hi Roger,
>
> On Fri, Feb 01, 2013 at 20:01:38, Quadros, Roger wrote:
>
>> but DT boot is not supported for OMAP USB Host. How did you get it to work?
>>
>> Are you testing the Host connector or the OTG connector?
>
> If you see latest changes on
On Fri, Feb 01, 2013 at 07:19:07PM +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
901 - 1000 of 1300 matches
Mail list logo
