On 1/4/14, 8:05 AM, Frederic Weisbecker wrote:
On Fri, Jan 03, 2014 at 03:45:36PM -0700, David Ahern wrote:
On 1/3/14, 3:07 PM, Frederic Weisbecker wrote:
I'm not sure I understand why we need that. Why doesn't it work by simply
flushing
events prior to the earliest timestamp among every CPUs
On Tuesday 07 January 2014, Feng Kan wrote:
> @@ -73,8 +73,7 @@ static int xgene_reboot_probe(struct platform_device *pdev)
> return -ENODEV;
> }
>
> - if (of_property_read_u32(pdev->dev.of_node, "mask", &ctx->mask))
> - ctx->mask = 0x;
> +
On 1/8/14, 8:20 AM, Arnaldo Carvalho de Melo wrote:
Em Mon, Dec 30, 2013 at 10:26:41AM -0500, Dongsheng Yang escreveu:
>Ramkumar reported that perf list --raw-dump was broken by 44d742e.
>Fix by making raw-dump a proper argument.
>
>Signed-off-by: David Ahern
Are you sure David Signed-off-by' t
On 01/08/14 13:11, Laszlo Papp wrote:
> On Wed, Jan 8, 2014 at 6:54 PM, Randy Dunlap wrote:
>> On 01/08/2014 08:31 AM, Laszlo Papp wrote:
>>>
>>> Hi,
>>>
>>> which spelling is preferred for the documentation when sending patches?
>>>
>>> I see the UK'ish "initialise" as well as the US'ish "initial
On Tuesday 07 January 2014, Feng Kan wrote:
> Enable the X-Gene reboot driver to use either the ACPI or the DTS
> resource using the platform driver method.
>
> Signed-off-by: Feng Kan
> ---
> drivers/power/reset/xgene-reboot.c | 33 -
> 1 files changed, 28 inse
* Thierry Reding [140108 11:32]:
> On Wed, Jan 08, 2014 at 08:40:41AM -0800, Tony Lindgren wrote:
> >
> > There's nothing wrong with the interrupt related code paths, we're just
> > trying to call the functions at a wrong time when thing are not yet
> > initialized.
>
> The patch won't get rid o
On 01/08/2014 10:37 PM, Pekka Enberg wrote:
On Wed, Jan 8, 2014 at 11:05 PM, Helge Deller wrote:
On 01/07/2014 02:41 AM, Joonsoo Kim wrote:
On Mon, Jan 06, 2014 at 12:54:22PM -0500, Mikulas Patocka wrote:
Hi
On Mon, 6 Jan 2014, Joonsoo Kim wrote:
Hello,
I'm surprised that this VM_BUG_ON()
> PM8921 and PM8058 are PMICs found paired with MSM8960 and MSM8660
> devices respectively. They contain subdevices such as keypads,
> RTCs, regulators, clocks, etc.
>
> Cc:
> Signed-off-by: Stephen Boyd
> ---
> .../devicetree/bindings/mfd/qcom,pm8xxx.txt| 63
> ++
>
On Tuesday 24 December 2013, Stephen Boyd wrote:
> This is a rework of patches sent a months back by Rohit[1].
> The goal of these patches is to add support for SMP and (basic)
> hotplug on MSM based SoCs. To get there, we add support for a
> generic way to hook in SMP/hotplug support code based on
On Wed, Jan 8, 2014 at 11:05 PM, Helge Deller wrote:
> On 01/07/2014 02:41 AM, Joonsoo Kim wrote:
>>
>> On Mon, Jan 06, 2014 at 12:54:22PM -0500, Mikulas Patocka wrote:
>>>
>>> Hi
>>>
>>> On Mon, 6 Jan 2014, Joonsoo Kim wrote:
>>>
Hello,
I'm surprised that this VM_BUG_ON() has not b
On Wed, 08 Jan 2014, Stephen Boyd wrote:
> Convert this driver to use irqdomains so that the PMIC's child
> devices can be converted to devicetree.
>
> Signed-off-by: Stephen Boyd
> ---
> drivers/mfd/pm8921-core.c | 198
> +++---
> include/linux/mfd/pm8x
On Monday 30 December 2013 15:52:51 Sebastian Reichel wrote:
> > > > +MODULE_DESCRIPTION("Bluetooth h4 driver with nokia
> > > > extensions"); +MODULE_LICENSE("GPL");
> > > > +MODULE_AUTHOR("Ville Tervo");
> > > > +MODULE_FIRMWARE(FW_NAME_TI1271_PRELE);
> > > > +MODULE_FIRMWARE(FW_NAME_TI1271_LE);
Nicolas,
On Wed, Jan 8, 2014 at 1:08 PM, Nicolas Pitre wrote:
> On Wed, 8 Jan 2014, Doug Anderson wrote:
>
>> Hi,
>>
>> On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
>> > No, we're saying to put the work-around in the boot loader, not the kernel.
>>
>> Unfortunately the resume path of
I just realized when answering Ma's mail that this doesn't cause the
desired effect after Paul's flow control improvement: starting the queue
doesn't drop the packets which cannot fit the ring. Which in fact might
be not good. We are adding the skb to vif->rx_queue even when
xenvif_rx_ring_slot
Russell,
On Wed, Jan 8, 2014 at 1:02 PM, Russell King - ARM Linux
wrote:
> On Wed, Jan 08, 2014 at 11:43:29AM -0800, Doug Anderson wrote:
>> Olof came up with the idea that you could update the RW firmware
>> (affects initial boot) and then cache away the value and restore it in
>> the kernel aft
On Wednesday 08 January 2014, Boris BREZILLON wrote:
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/sunxi-nand.txt
> @@ -0,0 +1,71 @@
> +Allwinner NAND Flash Controller (NFC)
> +
> +Required properties:
> +- compatible : "allwinner,sun4i-nfc".
> +- reg : shall contain registers locat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Borislav Petkov wrote:
> On Wed, Jan 08, 2014 at 09:42:40AM -0800, H. Peter Anvin wrote:
>> Adding Borislav.
>>
>> Boris, do you happen to know of any erratum on AMD E-350 which
>> may be in play here?
>
> Interesting. Well, nothing looks even remote
On 01/08/2014 10:33 AM, Christoph Hellwig wrote:
> __smp_call_function_single already avoids multiple IPIs by internally
> queing up the items, and now also is available for non-SMP builds as
> a trivially correct stub, so there is no need to wrap it. If the
> additional lock roundtrip cause probl
Nicolas,
On Wed, Jan 8, 2014 at 12:58 PM, Nicolas Pitre wrote:
> On Wed, 8 Jan 2014, Doug Anderson wrote:
>
>> On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
>> wrote:
>> > We've been through these arguments many times, you're not the first to
>> > raise it, and we've decided upon the
From: "David E. Box"
Current Intel SOC cores use a MailBox Interface (MBI) to provide access to
configuration registers on devices (called units) connected to the system
fabric. This is a support driver that implements access to this interface on
those platforms that can enumerate the device usin
just checking on the status of this patch. Am I sending it to the wrong
place? Did it get lost in the post-holiday e-mail purges?
The bug is annoying if you're trying to use perf on ARM systems.
Vince
On Mon, 30 Dec 2013, Vince Weaver wrote:
>
> "perf list" listing of hardware events doe
I'm working on getting the hardware performance counters working on a
Raspberry-Pi (BCM2835/ARM1176).
The counters are there, but the overflow interrupt is not hooked up so the
init code disables perf_event.
The following patch enables perf_event and it works fine for simple
"perf stat" typ
On Wed, Jan 08, 2014 at 01:18:46PM -0800, Muthu Kumar wrote:
> On Wed, Jan 8, 2014 at 1:14 PM, Kent Overstreet wrote:
> > On Wed, Jan 08, 2014 at 09:11:49PM +, Chris Mason wrote:
> >> On Wed, 2014-01-08 at 13:01 -0800, Muthu Kumar wrote:
> >> > On Wed, Jan 8, 2014 at 12:51 PM, Chris Mason wro
On 01/08/2014 02:13 PM, Chris Mason wrote:
> On Tue, 2014-01-07 at 12:15 -0800, Muthu Kumar wrote:
>> Thanks Fengguang. Final patch with added comment. BTW, fengguang
>> mentioned that git-am has trouble with the inline patch and "quilt
>> import" worked fine for him...
>>
>>
>> In btr
On Thu, Jan 02, 2014 at 05:14:11PM +0800, Chen Fan wrote:
> fix the 'vcpi' typos when apic_debug is enabled.
>
> Signed-off-by: Chen Fan
> ---
> arch/x86/kvm/lapic.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied, thanks.
--
To unsubscribe from this list: send the line "
On Wed, Jan 8, 2014 at 1:14 PM, Kent Overstreet wrote:
> On Wed, Jan 08, 2014 at 09:11:49PM +, Chris Mason wrote:
>> On Wed, 2014-01-08 at 13:01 -0800, Muthu Kumar wrote:
>> > On Wed, Jan 8, 2014 at 12:51 PM, Chris Mason wrote:
>> > > On Wed, 2014-01-08 at 12:40 -0800, Muthu Kumar wrote:
>> >
Jens, here's the updated bcache pull, rebased and retested on top of
your latest for-3.14/drivers branch. Only other change was a one liner
in the "bcache/md: Use raid stripe size" patch to update
blk_stack_limits(), as pointed out by Mike Snitzer.
The following changes since commit 54a387cb9e600
On Wed, Jan 08, 2014 at 12:37:03PM -0600, Rob Herring wrote:
> > Patch to parse this compatible string to follow if this binding is
> > acceptable.
>
> One minor comment below, otherwise:
>
> Acked-by: Rob Herring
K, I'll send a series hopefully in a few weeks after some travel.
> > + If th
On Tue, 2014-01-07 at 12:15 -0800, Muthu Kumar wrote:
> Thanks Fengguang. Final patch with added comment. BTW, fengguang
> mentioned that git-am has trouble with the inline patch and "quilt
> import" worked fine for him...
>
>
> In btrfs_end_bio(), we increment bi_remaining if is_orig
On Wed, 8 Jan 2014, Doug Anderson wrote:
> On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
> wrote:
> > We've been through these arguments many times, you're not the first to
> > raise it, and we've decided upon the policy. We want as _few_ work-
> > arounds in the kernel as possible,
On Wed, Jan 08, 2014 at 09:11:49PM +, Chris Mason wrote:
> On Wed, 2014-01-08 at 13:01 -0800, Muthu Kumar wrote:
> > On Wed, Jan 8, 2014 at 12:51 PM, Chris Mason wrote:
> > > On Wed, 2014-01-08 at 12:40 -0800, Muthu Kumar wrote:
> > >> On Wed, Jan 8, 2014 at 12:16 PM, Chris Mason wrote:
> > >
ATTN: Dear,
I am Dr. Musa Hamed Executive Director of the Bank of Africa
Plc B.O.A,Cotonou Benin Rep. I have a very lucrative Business proposal
worth of 21,500,000.00 USD.
An Iraqi named Hamadi Hashem a business man made a fixed deposit of
21,500,000.00 USD . Upon maturity several notices was sen
On Wed, 2014-01-08 at 13:01 -0800, Muthu Kumar wrote:
> On Wed, Jan 8, 2014 at 12:51 PM, Chris Mason wrote:
> > On Wed, 2014-01-08 at 12:40 -0800, Muthu Kumar wrote:
> >> On Wed, Jan 8, 2014 at 12:16 PM, Chris Mason wrote:
> >> > On Wed, 2014-01-08 at 11:54 -0800, Muthu Kumar wrote:
> >> >> Chris
On Wed, Jan 8, 2014 at 6:54 PM, Randy Dunlap wrote:
> On 01/08/2014 08:31 AM, Laszlo Papp wrote:
>>
>> Hi,
>>
>> which spelling is preferred for the documentation when sending patches?
>>
>> I see the UK'ish "initialise" as well as the US'ish "initialization"
>> within the same close to each other
On Wed, Jan 8, 2014 at 9:02 PM, Laszlo Papp wrote:
> On Wed, Jan 8, 2014 at 7:07 PM, Mark Brown wrote:
>> On Wed, Jan 08, 2014 at 06:59:57PM +, Laszlo Papp wrote:
>>> On Wed, Jan 8, 2014 at 6:07 PM, Mark Brown wrote:
>>> > On Wed, Jan 08, 2014 at 05:22:18PM +, Laszlo Papp wrote:
>>
>>> >
On Wed, 8 Jan 2014, Doug Anderson wrote:
> Hi,
>
> On Wed, Jan 8, 2014 at 11:20 AM, Russell King - ARM Linux
> > No, we're saying to put the work-around in the boot loader, not the kernel.
>
> Unfortunately the resume path of the firmware runs from Read Only
> firmware code (yes, it sucks), so
On 01/07/2014 02:41 AM, Joonsoo Kim wrote:
On Mon, Jan 06, 2014 at 12:54:22PM -0500, Mikulas Patocka wrote:
Hi
On Mon, 6 Jan 2014, Joonsoo Kim wrote:
Hello,
I'm surprised that this VM_BUG_ON() has not been triggered until now. It was
introduced in 2007 by commit (b5fab14). Maybe there is no
On Wed, Jan 8, 2014 at 7:07 PM, Mark Brown wrote:
> On Wed, Jan 08, 2014 at 06:59:57PM +, Laszlo Papp wrote:
>> On Wed, Jan 8, 2014 at 6:07 PM, Mark Brown wrote:
>> > On Wed, Jan 08, 2014 at 05:22:18PM +, Laszlo Papp wrote:
>
>> >> - * (eg, a clear on read interrupt status reg
On Wednesday 08 January 2014 21:24:08 Thierry Reding wrote:
>
> The problem with devres, or any other solution for that matter, is that
> for the cases where we'd need something like this (that is, statically
> allocated devices in board setup code) we don't have a fully initialized
> struct devic
On Wed, Jan 08, 2014 at 11:43:29AM -0800, Doug Anderson wrote:
> Olof came up with the idea that you could update the RW firmware
> (affects initial boot) and then cache away the value and restore it in
> the kernel after resume. That would still require a kernel patch but
> perhaps a less objecti
On Wed, Jan 8, 2014 at 12:51 PM, Chris Mason wrote:
> On Wed, 2014-01-08 at 12:40 -0800, Muthu Kumar wrote:
>> On Wed, Jan 8, 2014 at 12:16 PM, Chris Mason wrote:
>> > On Wed, 2014-01-08 at 11:54 -0800, Muthu Kumar wrote:
>> >> Chris,
>> >>
>> >> [8.336061] WARNING: CPU: 0 PID: 0 at fs/bio.c:
Any pointers? Still present in 3.13-rc7.
On Wed, Dec 4, 2013 at 1:22 PM, Roger Quadros wrote:
> +Kishon
>
> On 12/03/2013 11:33 PM, Belisko Marek wrote:
>> Hi,
>>
>> current 3.13-rcX break usb support on gta04 board (similar to
>> beagleboard) when booting via board file.
>>
>> In console we can
On Wed, Jan 08, 2014 at 07:26:07PM +, Sudeep Holla wrote:
> +#if __LINUX_ARM_ARCH__ < 7 /* pre ARMv7 */
> +
> +#define MAX_CACHE_LEVEL 1 /* Only 1 level supported */
> +#define CTR_CTYPE_SHIFT 24
> +#define CTR_CTYPE_MASK (1 << CTR_CTYPE_SHIFT)
> +
I recompiled the kernel using the said config and it works. But, if
you have any other suggestion it would be great.
Regards,
john
On Wed, Jan 8, 2014 at 12:45 PM, John Tobias wrote:
> Hi Fabio,
>
> How about select HAVE_IMX_ANATOP if SOC_IMX6Q || SOC_IMX6SL
>
> Regards,
>
> john
>
> On Wed, Ja
On Wed 08-01-14 19:30:38, Sergey Meirovich wrote:
> On 8 January 2014 17:26, Christoph Hellwig wrote:
> >
> > On my laptop SSD I get the following results (sometimes up to 200MB/s,
> > sometimes down to 100MB/s, always in the 40k to 50k IOps range):
> >
> > time elapsed (sec.):5
> > bandwidth
On Wed, 2014-01-08 at 12:40 -0800, Muthu Kumar wrote:
> On Wed, Jan 8, 2014 at 12:16 PM, Chris Mason wrote:
> > On Wed, 2014-01-08 at 11:54 -0800, Muthu Kumar wrote:
> >> Chris,
> >>
> >> [8.336061] WARNING: CPU: 0 PID: 0 at fs/bio.c:1778
> >> bio_endio+0xbe/0x100()
> >> [8.336062] bio_en
Hi Fabio,
How about select HAVE_IMX_ANATOP if SOC_IMX6Q || SOC_IMX6SL
Regards,
john
On Wed, Jan 8, 2014 at 12:33 PM, Fabio Estevam wrote:
> On Wed, Jan 8, 2014 at 6:03 PM, Alexander Shiyan wrote:
>
>> Maybe better:
>> select HAVE_IMX_ANATOP if ARCH_MULTI_V6_V7
>
> mx31, mx35, mx51 and mx53 do
On Tue, Jan 7, 2014 at 1:00 AM, Jiang Liu wrote:
> Intel DMA/interrupt remapping drivers scan available PCI/memory devices
> at startup and cache discovered hardware topologies. They don't update
> cached information if PCI/memory hotplug event happens at runtime, then
> the stale information may
Hi,
I can very well believe that bogus triggering of this spewing message
is now fixed by your patch (thanks!), but:
I get the very same message here on OpenWrt's 3.10.24
(verified to be properly containing your patch!),
when playing usb-audio on TL-WDR3600 MIPS via MPD mp3 streaming, *and then*:
From: Nicholas Bellinger
This patch adds support for DIF read/write verify emulation
for TARGET_DIF_TYPE1_PROT + TARGET_DIF_TYPE3_PROT operation.
This includes sbc_dif_verify_write() + sbc_dif_verify_read()
calls accessable by backend drivers to perform DIF verify
for SGL based data and protecti
On Wed, Jan 8, 2014 at 12:16 PM, Chris Mason wrote:
> On Wed, 2014-01-08 at 11:54 -0800, Muthu Kumar wrote:
>> Chris,
>>
>> [8.336061] WARNING: CPU: 0 PID: 0 at fs/bio.c:1778 bio_endio+0xbe/0x100()
>> [8.336062] bio_endio: bio for (unknown) without endio
>>
>> This is my recent change to a
From: Nicholas Bellinger
This patch adds support for DIF related CHECK_CONDITION ASC/ASCQ
exception cases into transport_send_check_condition_and_sense().
This includes:
LOGICAL BLOCK GUARD CHECK FAILED
LOGICAL BLOCK APPLICATION TAG CHECK FAILED
LOGICAL BLOCK REFERENCE TAG CHECK FAILED
t
Hello!
This patch:
commit c5c23260594c5701af66ef754916775ba6a46bbc
Author: Herbert Xu
Date: Fri Apr 13 02:37:42 2012 +
bridge: Add multicast_querier toggle and disable queries by default
Sending general queries was implemented as an optimisation to speed
up convergence on sta
From: Nicholas Bellinger
This patch updates spc_emulate_inquiry_std() to set the
PROTECT bit when DIF emulation is enabled by the backend
device.
Cc: Martin K. Petersen
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Sagi Grimberg
Cc: Or Gerlitz
Signed-off-by: Nicholas Bellinger
---
drivers
From: Nicholas Bellinger
This patch adds sbc_check_prot() for performing various DIF
related CDB sanity checks, along with setting SCF_PROT once
sanity checks have passed.
Also, add calls in sbc_parse_cdb() for READ_[10,12,16] +
WRITE_[10,12,16] to perform DIF sanity checking.
Cc: Martin K. Pet
From: Nicholas Bellinger
This patch updates spc_modesense_control() to set the Application
Tag Owner (ATO) bit when when DIF emulation is enabled by the
backend device.
Cc: Martin K. Petersen
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Sagi Grimberg
Cc: Or Gerlitz
Signed-off-by: Nicholas
From: Nicholas Bellinger
This patch updates sbc_emulate_readcapacity_16() to set
P_TYPE and PROT_EN bits when DIF emulation is enabled by
the backend device.
Cc: Martin K. Petersen
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Sagi Grimberg
Cc: Or Gerlitz
Signed-off-by: Nicholas Bellinger
From: Nicholas Bellinger
This patch adds support for exposing DIF protection device
attributes via configfs. This includes:
pi_prot_type: Protection Type (0, 1, 3 currently support)
pi_prot_version: Protection Version (DIF v1 currently supported)
pi_guard_type: Guard Type (1=DIF CRC, 2
From: Nicholas Bellinger
This patch refactors rd_build_device_space() + rd_release_device_space()
into rd_allocate_sgl_table() + rd_release_device_space() so that they
may be used seperatly for setup + release of protection information
scatterlists.
Also add explicit memset of pages within rd_al
From: Nicholas Bellinger
This patch updates tcm_loop_driver_probe() to set protection
information using scsi_host_set_prot() and scsi_host_set_guard(),
which currently enabled all modes of DIF/DIX protection, minus
DIF TYPE0.
Also, update tcm_loop_submission_work() to pass struct scsi_cmnd
relat
From: Nicholas Bellinger
This patch adds support for DIF protection into rd_execute_rw() code
for WRITE/READ I/O using sbc_dif_verify_[write,read]() logic.
It also adds rd_get_prot_table() for locating protection SGLs
assoicated with the ramdisk backend device.
Cc: Martin K. Petersen
Cc: Chris
From: Nicholas Bellinger
This patch updates spc_emulate_evpd_86() (extended INQUIRY) to
report GRD_CHK (Guard Check) and REF_CHK (Reference Check) bits
when DIF emulation is enabled by the backend device.
Cc: Martin K. Petersen
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Sagi Grimberg
Cc:
From: Nicholas Bellinger
This patch adds rd_build_prot_space() + rd_release_prot_space() logic
to setup + release protection information scatterlists.
It also adds rd_init_prot() + rd_free_prot() se_subsystem_api
callbacks used by target core code for setup + release of
protection information.
From: Nicholas Bellinger
This patch adds DIF related definitions to target_core_base.h
that includes enums for target_prot_op + target_prot_type +
target_prot_version + target_guard_type + target_pi_error.
Also included is struct se_dif_v1_tuple, along with changes
to struct se_cmd, struct se_de
From: Nicholas Bellinger
This patch adds support to target_submit_cmd_map_sgls() for
accepting 'sgl_prot' + 'sgl_prot_count' parameters for
DIF protection information.
Note the passed parameters are stored at se_cmd->t_prot_sg
and se_cmd->t_prot_nents respectively.
Also, update tcm_loop and vho
From: Nicholas Bellinger
Hi MKP & SCSI folks,
This series contains initial support for target mode DIF Type1+Type3
emulation within target core, RAMDISK_MCP device backend, and tcm_loop
fabric driver.
DIF emulation is enabled via a new 'pi_prot_type' device attribute
within configfs, which is s
On Wed, Jan 8, 2014 at 6:03 PM, Alexander Shiyan wrote:
> Maybe better:
> select HAVE_IMX_ANATOP if ARCH_MULTI_V6_V7
mx31, mx35, mx51 and mx53 do not have this ANATOP block.
Regards,
Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
Em Wed, 08 Jan 2014 21:01:38 +0100
Frank Schäfer escreveu:
> Am 07.01.2014 18:59, schrieb Tejun Heo:
> > Hello,
> >
> > cc'ing Mauro and quoting whole body for him.
> >
> > So, ummm, the sysfs rule was that any group below a device should be
> > removed before the device itself is removed; howeve
On Wed, 8 Jan 2014 08:56:28 -0800, Greg Kroah-Hartman wrote:
> On Wed, Jan 08, 2014 at 04:40:58PM +0100, Jean Delvare wrote:
> > Hi Greg, hi all,
> >
> > A memory leak has been reported to me:
> > http://marc.info/?l=linux-i2c&m=138779165123331&w=2
> >
> > The leak is in i801_probe, caused by an
From: Alexander Usyskin
Fix syntax errors in comments and debug strings
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c| 4 ++--
drivers/misc/mei/client.c| 22 +++---
drivers/misc/mei/debugfs.c | 4 ++--
drivers/misc/mei/
On Wed, 2014-01-08 at 21:15 +0100, Ondrej Zary wrote:
> The driver works fine with narrow boards. Please don't break working drivers
> because of some stupid warning.
My patch changed a buildtime warning for both narrow and wide boards in
a runtime error on wide boards only. That wouldn't break t
On Wed, Jan 08, 2014 at 07:26:06PM +, Sudeep Holla wrote:
> From: Sudeep Holla
> +#define define_one_ro(_name) \
> +static struct cache_attr _name = \
> + __ATTR(_name, 0444, show_##_name, NULL)
In the future, we do have __ATTR_RO(), which should be used instead.
You should never use __AT
On Wed, Jan 08, 2014 at 07:26:06PM +, Sudeep Holla wrote:
> From: Sudeep Holla
>
> This patch adds initial support for providing processor cache information
> to userspace through sysfs interface. This is based on x86 implementation
> and hence the interface is intended to be fully compatible
On Wed, Jan 08, 2014 at 09:09:17PM +0100, Arnd Bergmann wrote:
> On Wednesday 08 January 2014 20:59:10 Thierry Reding wrote:
> > On Wed, Jan 08, 2014 at 05:25:17PM +0100, Arnd Bergmann wrote:
> > > On Wednesday 08 January 2014, Thierry Reding wrote:
> > > > On Wed, Jan 08, 2014 at 04:11:08PM +0100,
On Wed, Jan 08, 2014 at 07:26:06PM +, Sudeep Holla wrote:
> From: Sudeep Holla
>
> This patch adds initial support for providing processor cache information
> to userspace through sysfs interface. This is based on x86 implementation
> and hence the interface is intended to be fully compatible
thanks for the info. Will fix it.
On Wed, Jan 8, 2014 at 12:03 PM, Alexander Shiyan wrote:
> Hello.
>
> Среда, 8 января 2014, 11:56 -08:00 от John Tobias :
>> Moved ARCH_HAS_CPUFREQ, HAVE_IMX_ANATOP and PM_OPP on ARCH_MXC so that
>> the user can enable the cpufreq support for iMX6Q and/or iMX6SL
On Wed, Jan 08, 2014 at 09:01:38PM +0100, Frank Schäfer wrote:
> Am 07.01.2014 18:59, schrieb Tejun Heo:
> > Hello,
> >
> > cc'ing Mauro and quoting whole body for him.
> >
> > So, ummm, the sysfs rule was that any group below a device should be
> > removed before the device itself is removed; howe
Florian Westphal wrote:
> Eric Dumazet wrote:
> > > The confirmed bit should always be set here.
> >
> > So why are you testing it ?
>
> To detect ct object recycling when tuple is identical.
>
> This is my understanding of how we can end up with two
> cpus thinking they have exclusive ownersh
Hi Kumar,
Do you have any comments on this patch?--
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.tux.org/lkml/
On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
> On Wed, 8 Jan 2014, Daniel Vetter wrote:
>
> > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
> > > On Tue, 7 Jan 2014, Daniel Vetter wrote:
> > >
> > > > I really want users to report these issues, and excessive WARNs see
On Wed, Jan 08, 2014 at 04:56:45PM +0800, fal...@meizu.com wrote:
> From: Wu Zhangjin
>
> During embedded linux system booting, before decompressing the kernel image,
> the bootloader(E.g. Uboot) loads the compressed kernel image and ramdisk into
> two contiguous memory space, these two memory sp
Eric Dumazet wrote:
> > The confirmed bit should always be set here.
>
> So why are you testing it ?
To detect ct object recycling when tuple is identical.
This is my understanding of how we can end up with two
cpus thinking they have exclusive ownership of the same ct:
A cpu0: starts lookup:
On Tue, 2013-01-29 at 11:20 +0100, Paul Bolle wrote:
> On Mon, 2012-11-05 at 11:58 +0100, Paul Bolle wrote:
> > Building advansys.o triggers this warning:
> > drivers/scsi/advansys.c:71:2: warning: #warning this driver is still
> > not properly converted to the DMA API [-Wcpp]
> >
> > This wa
On Wed, Jan 08, 2014 at 11:50:35AM -0700, Stephen Warren wrote:
> On 01/08/2014 06:39 AM, Thierry Reding wrote:
> > On Mon, Jan 06, 2014 at 01:40:51PM -0700, Stephen Warren wrote:
> >> On 12/24/2013 06:32 AM, Peter De Schrijver wrote:
> > [...]
> >>> diff --git a/arch/arm/boot/dts/tegra20.dtsi
> >
On Wednesday 08 January 2014 21:05:14 Paul Bolle wrote:
> On Tue, 2013-01-29 at 11:20 +0100, Paul Bolle wrote:
> > On Mon, 2012-11-05 at 11:58 +0100, Paul Bolle wrote:
> > > Building advansys.o triggers this warning:
> > > drivers/scsi/advansys.c:71:2: warning: #warning this driver is
> > > sti
On Wed, 2014-01-08 at 11:54 -0800, Muthu Kumar wrote:
> Chris,
>
> [8.336061] WARNING: CPU: 0 PID: 0 at fs/bio.c:1778 bio_endio+0xbe/0x100()
> [8.336062] bio_endio: bio for (unknown) without endio
>
> This is my recent change to avoid memory leak in bio_endio. But I
> think the problem is
On Wednesday 08 January 2014 20:59:10 Thierry Reding wrote:
> On Wed, Jan 08, 2014 at 05:25:17PM +0100, Arnd Bergmann wrote:
> > On Wednesday 08 January 2014, Thierry Reding wrote:
> > > On Wed, Jan 08, 2014 at 04:11:08PM +0100, Arnd Bergmann wrote:
> > The more I think about the iommu case, the mo
On 01/08/2014 02:51 PM, Andi Kleen wrote:
Sasha Levin writes:
Fuzzing a recent kernel with a large configuration hits the static
allocation limits and disables lockdep.
Doesn't that use a lot more memory? I thought lockdep preallocates.
Doubling may be too aggressive.
The patch adds abou
On Wed, Jan 08, 2014 at 11:50:35AM -0700, Stephen Warren wrote:
> On 01/08/2014 06:39 AM, Thierry Reding wrote:
> > On Mon, Jan 06, 2014 at 01:40:51PM -0700, Stephen Warren wrote:
> >> On 12/24/2013 06:32 AM, Peter De Schrijver wrote:
> > [...]
> >>> diff --git a/arch/arm/boot/dts/tegra20.dtsi
> >
Hello.
Среда, 8 января 2014, 11:56 -08:00 от John Tobias :
> Moved ARCH_HAS_CPUFREQ, HAVE_IMX_ANATOP and PM_OPP on ARCH_MXC so that
> the user can enable the cpufreq support for iMX6Q and/or iMX6SL.
>
> Signed-off-by: John Tobias
> ---
> arch/arm/mach-imx/Kconfig | 13 ++---
> 1 file c
On 13/12/25, AKASHI Takahiro wrote:
> audit_syscall_exit() saves a result of regs_return_value() in intermediate
> "int" variable and passes it to __audit_syscall_exit(), which expects its
> second argument as a "long" value.
> This will result in truncating the value returned by a system call and
On Wed, Jan 08, 2014 at 05:25:17PM +0100, Arnd Bergmann wrote:
> On Wednesday 08 January 2014, Thierry Reding wrote:
> > On Wed, Jan 08, 2014 at 04:11:08PM +0100, Arnd Bergmann wrote:
> > > On Wednesday 08 January 2014 15:55:27 Thierry Reding wrote:
> > > > It stands to reason that if they push bac
Hi Doug,
> The existing watchdog timeout worked OK but didn't deal with
> rounding in an ideal way when dividing out all of its clocks.
>
> Specifically if you had a timeout of 32 seconds and an input clock of
> , you'd end up setting a timeout of 31.9998 seconds and
> reporting a timeout
Am 07.01.2014 18:59, schrieb Tejun Heo:
> Hello,
>
> cc'ing Mauro and quoting whole body for him.
>
> So, ummm, the sysfs rule was that any group below a device should be
> removed before the device itself is removed; however, nothing really
> checked whether this actually was the case. We didn't
Hi John,
On Wed, Jan 8, 2014 at 5:56 PM, John Tobias wrote:
> Moved ARCH_HAS_CPUFREQ, HAVE_IMX_ANATOP and PM_OPP on ARCH_MXC so that
> the user can enable the cpufreq support for iMX6Q and/or iMX6SL.
>
> Signed-off-by: John Tobias
> ---
> arch/arm/mach-imx/Kconfig | 13 ++---
> 1 file c
Moved ARCH_HAS_CPUFREQ, HAVE_IMX_ANATOP and PM_OPP on ARCH_MXC so that
the user can enable the cpufreq support for iMX6Q and/or iMX6SL.
Signed-off-by: John Tobias
---
arch/arm/mach-imx/Kconfig | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/arch/arm/mach-imx/Kco
Hi Doug,
> On modern SoCs the watchdog timer is parented on a clock that doesn't
> change every time we have a cpufreq change. That means we don't need
> to constantly adjust the watchdog timer, so avoid registering for and
> dealing with cpufreq transitions unless we've actually got
> CONFIG_ARM
Chris,
[8.336061] WARNING: CPU: 0 PID: 0 at fs/bio.c:1778 bio_endio+0xbe/0x100()
[8.336062] bio_endio: bio for (unknown) without endio
This is my recent change to avoid memory leak in bio_endio. But I
think the problem is higher up, most likely bio_endio is called twice
on the same bio (w
On Wed, Jan 8, 2014 at 8:35 AM, Joerg Roedel wrote:
> On Wed, Jan 08, 2014 at 08:23:49AM -0500, Rob Clark wrote:
>> On Tue, Jan 7, 2014 at 5:53 PM, Joerg Roedel wrote:
>> > On Tue, Jan 07, 2014 at 11:47:26PM +0100, Joerg Roedel wrote:
>> >> The DRM driver for MSM depends on symbols from the MSM
>
There are about a dozen places in the x86 EFI code which loop through
the EFI memory map descriptors. All of these places use essentially
the same for-loop code. This patch adds a for_each_efi_memory_desc()
helper to clean up all of the duplicate code and make it available
for other architectures t
201 - 300 of 772 matches
Mail list logo
