On 01/11/2015 10:36 PM, Linus Walleij wrote:
> On Fri, Jan 9, 2015 at 4:43 PM, Soren Brinkmann
> wrote:
>
>> Select pinctrl and the Zynq pinctrl driver.
>>
>> Signed-off-by: Soren Brinkmann
>> Tested-by: Andreas Färber
>> ---
>> Changes since RFC v2:
>> - separate mach-zynq changes in their
This patch correct the bad expression while writing the
bit-pattern from software's buffer to hardware registers.
Signed-off-by: Sanjeev Sharma
---
drivers/net/ethernet/freescale/gianfar_ethtool.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 01/11/2015 10:38 PM, Linus Walleij wrote:
> On Fri, Jan 9, 2015 at 4:43 PM, Soren Brinkmann
> wrote:
>
>> Add pinctrl descriptions to the zc702 and zc706 device trees.
>>
>> Signed-off-by: Soren Brinkmann
>> Tested-by: Andreas Färber
>
> Reviewed-by: Linus Walleij
>
> Beautiful and in
On Mon, Jan 12, 2015 at 6:02 AM, Stephen Rothwell wrote:
> After merging the pinctrl tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
Fixed already, hopefully. (Atleast the autobuilders are happy.)
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line
The driver allows using CDCE706 in its default configuration recorded in
EEPROM and adjusting of synthesized clocks by consumers.
Signed-off-by: Max Filippov
---
Changes v1->v2:
- add example usage to devicetree binding doc.
.../devicetree/bindings/clock/ti,cdce706.txt | 42 ++
This patch adds trace for lookup/update/shrink/destroy ops in rb-tree extent
cache.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 9 +++
include/trace/events/f2fs.h | 134
2 files changed, 143 insertions(+)
diff --git a/fs/f2fs/data.c
This patch add and show stat info of total memory footprint for extent tree,node
in debugfs.
Signed-off-by: Chao Yu
---
fs/f2fs/debug.c | 7 +++
fs/f2fs/f2fs.h | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c
index 1f0fb58..0fdfffe
This patch enable rb-tree based extent cache in f2fs.
When we mount with "-o extent_cache", f2fs will try to add recently accessed
page-block mappings into rb-tree based extent cache as much as possible, instead
of original one extent info cache.
By this way, f2fs can support more effective cache
This patch adds a mount option 'extent_cache' in f2fs.
It is try to use a rb-tree based extent cache to cache more mapping information
with less memory if this option is set, otherwise we will use the original one
extent info cache.
Suggested-by: Changman Lee
Signed-off-by: Chao Yu
---
>
> This patch adds the list of supported devfreq-event type as following.
> Each devfreq-event device driver would support the various devfreq-event type
> for devfreq governor at the same time.
> - DEVFREQ_EVENT_TYPE_RAW_DATA
> - DEVFREQ_EVENT_TYPE_UTILIZATION
> -
This patch adds core functions including slab cache init function and
init/lookup/update/shrink/destroy function for rb-tree based extent cache.
Thank Jaegeuk Kim and Changman Lee as they gave much suggestion about detail
design and implementation of extent cache.
Todo:
* add a cached_ei into
Introduce infra macro and data structure for rb-tree based extent cache:
Macros:
* EXT_TREE_VEC_SIZE: indicate vector size for gang lookup in extent tree.
* F2FS_MIN_EXTENT_LEN: indicate minimum length of extent managed in cache.
* EXTENT_CACHE_SHRINK_NUMBER: indicate number of extent in cache
In this patch, we do these jobs:
1. rename {check,update}_extent_cache to f2fs_{lookup,update}_extent_info;
2. introduce universal lookup/update interface of extent cache:
f2fs_{lookup,update}_extent_cache including above two real functions, then
export them to function callers.
So after above
This patch introduces f2fs_map_bh to clean codes of check_extent_cache.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 42 --
1 file changed, 28 insertions(+), 14 deletions(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 935a23b..5a3e489 100644
---
Rename a filed name from 'blk_addr' to 'blk' in struct {f2fs_extent,extent_info}
as annotation of this field descripts its meaning well to us.
By this way, we can avoid long statement in code of following patches.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 13 ++---
Functions to copy the irte data from the old kernel into the kdump kernel.
Signed-off-by: Li, Zhen-Hua
---
drivers/iommu/intel_irq_remapping.c | 62 +
include/linux/intel-iommu.h | 4 +++
2 files changed, 66 insertions(+)
diff --git
Fix the intr-remapping fault.
[1.594890] dmar: DRHD: handling fault status reg 2
[1.594894] dmar: INTR-REMAP: Request device [[41:00.0] fault index 4d
[1.594894] INTR-REMAP:[fault reason 34] Present field in the IRTE entry
is clear
Use old irte in kdump kernel, do not disable and re-enable
On 01/09/2015 11:51 PM, Roger Pau Monné wrote:
> El 06/01/15 a les 14.19, Bob Liu ha escrit:
>> When there is no enough free grants, gnttab_alloc_grant_references()
>> will fail and block request queue will stop.
>> If the system is always lack of grants, blkif_restart_queue_callback() can't
>>
On 01/09/2015 11:51 PM, Roger Pau Monné wrote:
> El 06/01/15 a les 14.19, Bob Liu ha escrit:
>> When there is no enough free grants, gnttab_alloc_grant_references()
>> will fail and block request queue will stop.
>> If the system is always lack of grants, blkif_restart_queue_callback() can't
>>
Move ext_lock out of struct extent_info, then in the following patches we can
use variables with struct extent_info type as a parameter to pass pure data.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 12 ++--
fs/f2fs/f2fs.h | 6 +-
fs/f2fs/inode.c | 7 +++
fs/f2fs/super.c |
When a device driver issues the first dma_map command for a
device, we assign a new and empty page-table, thus removing all
mappings from the old kernel for the device.
Signed-off-by: Li, Zhen-Hua
---
drivers/iommu/intel-iommu.c | 56 ++---
1 file
Add functions to load root entry table from old kernel, and to save updated
root entry table.
Add two member in struct intel_iommu, to store the RTA in old kernel, and
the mapped virt address of it.
We use the old RTA in dump kernel, and when the iommu->root_entry is used as
a cache in kdump
Populate it with support functions to copy iommu translation tables from
from the panicked kernel into the kdump kernel in the event of a crash.
Functions:
malloc new context table and copy old context table to the new one.
malloc new page table and copy old page table to the new one.
Modify the operation of the following functions when called during crash dump:
device_to_domain_id
get_domain_for_dev
init_dmars
intel_iommu_init
Bill Sumner:
Original version.
Zhenhua:
Minor change,
The name of new calling functions.
Do not disable and re-enable
Add structure type domain_values_entry used for kdump;
Add context entry functions needed for kdump.
Bill Sumner:
Original version;
Li, Zhenhua:
Changed the name of new functions, make them consistent with current
context get/set functions.
Signed-off-by: Bill Sumner
Signed-off-by:
Interfaces for when a new domain in the crashdump kernel needs some
values from the panicked kernel's context entries.
Signed-off-by: Bill Sumner
Signed-off-by: Li, Zhen-Hua
---
drivers/iommu/intel-iommu.c | 62 +
1 file changed, 62 insertions(+)
Add some functions to copy the data from old kernel.
These functions are used to copy context tables and page tables.
To avoid calling iounmap between spin_lock_irqsave and spin_unlock_irqrestore,
use a link here, store the pointers , and then use iounmap to free them in
another place.
Li,
This patchset is an update of Bill Sumner's patchset, implements a fix for:
If a kernel boots with intel_iommu=on on a system that supports intel vt-d,
when a panic happens, the kdump kernel will boot with these faults:
dmar: DRHD: handling fault status reg 102
dmar: DMAR:[DMA Read]
Allow specification of the domain-id for the new domain.
This patch only adds the 'did' parameter to iommu_attach_domain()
and modifies all of its callers to specify the default value of -1
which says "no did specified, allocate a new one".
This is no functional change from current behaviour --
Hi Changman,
> -Original Message-
> From: Changman Lee [mailto:cm224@samsung.com]
> Sent: Wednesday, January 07, 2015 7:17 PM
> To: Chao Yu
> Cc: 'Jaegeuk Kim'; linux-f2fs-de...@lists.sourceforge.net;
> linux-kernel@vger.kernel.org
> Subject: Re: [RFC PATCH] f2fs: add extent cache
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Wednesday, January 07, 2015 7:01 AM
> To: Chao Yu
> Cc: 'Changman Lee'; linux-f2fs-de...@lists.sourceforge.net;
> linux-kernel@vger.kernel.org
> Subject: Re: [RFC PATCH] f2fs: add extent cache base
Hi all,
Changes since 20150109:
The usb-gadget-fixes tree gained a conflict against the usb.current tree.
The net-next tree gained a build failure for which I reverted a commit.
The pinctrl tree gained a build failure so I used the version from
next-20150109.
The akpm tree lost a few patches
In general, the data in drm/rockchip GEM objects is never accessed by
the kernel. The objects are either accessed by a GPU, by display
controller DMA, or by mmap'ing them to user space. Thus, these
buffers need not be mapped into kernel address space.
The only exception is the fbdev
At Sun, 11 Jan 2015 22:44:37 +0100,
Hans de Bruin wrote:
>
> On 01/11/2015 04:45 PM, Takashi Iwai wrote:
> > At Sun, 11 Jan 2015 13:21:34 +0100,
> > Hans de Bruin wrote:
> >>
> >> This commit:
> >>
> >> commit 3abb4f4d0e7aaad0d12004b5057f4486a688752b
> >> Author: David Henningsson
> >> Date:
Hi Oleg,
How can I generate a scenario to test:
a) arch_uprobe_xol_was_trapped
b) arch_uprobe_abort_xol
~Pratyush
On Monday 12 January 2015 10:34 AM, Pratyush Anand wrote:
On Friday 09 January 2015 11:29 PM, Oleg Nesterov wrote:
On 12/31, Pratyush Anand wrote:
+int
I sent a new version of this patch in another mail.
Thanks,
Zhonghui
On 2015/1/5 18:48, Arend van Spriel wrote:
> On 01/05/15 03:34, Fu, Zhonghui wrote:
>> Hi Arend,
>>
>> Where to find your patch for this?
>
> Well, we did not submit it. Hence my "Acked-by:" to your patch below.
>
> Regards,
>From 8685c3c2746b4275fc808d9db23c364b2f54b52a Mon Sep 17 00:00:00 2001
From: Zhonghui Fu
Date: Mon, 12 Jan 2015 14:25:46 +0800
Subject: [PATCH] brcmfmac: avoid duplicated suspend/resume operation
WiFi chip has 2 SDIO functions, and PM core will trigger
twice suspend/resume operations for one
On Mon, Jan 12, 2015 at 1:38 AM, Andy Lutomirski wrote:
>> Sequences
>> pushl_cfi %reg
>> CFI_REL_OFFSET reg, 0
>> and
>> popl_cfi %reg
>> CFI_RESTORE reg
>> happen quite often. This patch adds macros which generate them.
>>
>> No assembly changes (verified with
(Fixing Sebastian's email address)
On Sat, Jan 10, 2015 at 8:44 PM, George Bush wrote:
> Hi all
>
> I notice we have hibernation.c in arm/kernel, however, I don't find it in
> arm64.
> Does it mean arm64 do not support hibernation/suspend-to-disk function?
Correct. arm64 is a separate
When a flaky disk is there in a topology then during driver load,
discovery related I/O times out; which results in SCSI error recovery
initiating host reset and then the controller won't see any disk.
In this patch, The driver would return FAILED status to the host reset
initiated due to
Added a support to set cpu affinity mask for each MSIX vector enabled by the
HBA.
So that, running the irqbalancer will balance interrupts among the cpus.
Change_set:
1. Added affinity_hint varable of type cpumask_var_t in adapter_reply_queue
structure. And allocated a memory for this varable
netif_alloc_rx_queues() uses kcalloc() to allocate memory
for "struct netdev_queue *_rx" array.
If we are doing large rx queue allocation kcalloc() might
fail, so this patch does a fallback to vzalloc().
Similar implementation is done for tx queue allocation in
netif_alloc_netdev_queues().
We
Networking under kvm works best if we allocate a per-vCPU RX and TX
queue in a virtual NIC. This requires a per-vCPU queue on the host side.
It is now safe to increase the maximum number of queues.
Preceding patch: 'net: allow large number of rx queues'
made sure this won't cause failures due to
Thank you for comments.
Richard Guy Briggs wrote:
> Steve already mentioned any user-influenced fields need to be escaped,
> so I'd recommend audit_log_untrustedstring() as being much simpler from
> your perspective and much better tested and understood from audit
> maintainer's perspective. At
Networking under KVM works best if we allocate a per-vCPU rx and tx
queue in a virtual NIC. This requires a per-vCPU queue on the host side.
Modern physical NICs have multiqueue support for large number of queues.
To scale vNIC to run multiple queues parallel to maximum number of vCPU's
we need to
Change List in this MPI2 specification,
1. Added SSUTimeout field to MPI2_CONFIG_PAGE_BIOS_1,
and more defines for the BiosOptions field.
Signed-off-by: Sreekanth Reddy
Reviewed-by: Martin K. Petersen
---
drivers/scsi/mpt2sas/mpi/mpi2.h | 5 +++--
drivers/scsi/mpt2sas/mpi/mpi2_cnfg.h
Bump driver version to 19.100.00.00.
Signed-off-by: Sreekanth Reddy
Reviewed-by: Martin K. Petersen
---
drivers/scsi/mpt2sas/mpt2sas_base.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/mpt2sas/mpt2sas_base.h
b/drivers/scsi/mpt2sas/mpt2sas_base.h
index
For any SCSI command, if the driver receives IOC status = SCSI_IOC_TERMINATED
and log info = 0x32010081
then that command will be completed with DID_RESET host status.
The definition of this log info value is "Virtual IO has failed and has to be
retried".
Firmware will provide this log info
Change Set:
1. Extended the upper boundary restriction for the module parameter
max_sgl_entries.
Earlier, the max_sgl_entries was capped at the SCSI_MAX_SG_SEGMENTS kernel
definition.
With this change, the user would be able to set the max_sgl_entries to
any value which is greater than
This patch will log a message when driver receives "Temperature Threshold
exceeded" event from any temperature sensor.
The message will look similar to like
mpt3sas0: Temperature Threshold flags a b c d exceeded for Sensor: x !!!
mpt3sas0: Current Temp In Celsius: y
where a b c d are threshold
Copyright, Trademark & Confidentiality legal statements throughout source code
changed from LSI to Avago.
Signed-off-by: Sreekanth Reddy
Reviewed-by: Martin K. Petersen
---
drivers/scsi/mpt2sas/mpt2sas_base.c | 3 ++-
drivers/scsi/mpt2sas/mpt2sas_base.h | 5 +++--
Below is the changeset from the MPI specification and 2.00.34 header files
1) Defined additional bits in the BiosOptions field of BIOS Page 1 to allow for
finer control of X86 BIOS and UEFI BSD.
2) For the Clean Tool, reserved bit 26 of the Flags field for product specific
use.
Signed-off-by:
Bump mpt2sas driver version to 20.100.00.00.
Signed-off-by: Sreekanth Reddy
Reviewed-by: Martin K. Petersen
---
drivers/scsi/mpt2sas/mpt2sas_base.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/mpt2sas/mpt2sas_base.h
b/drivers/scsi/mpt2sas/mpt2sas_base.h
Please consider this mpt2sas drivers Phase19 and Phase20 patch series.
All these patches are reviewed by Martin K. Petersen.
Some of these features are exists for both mpt2sas & mpt3sas drives,
so some of these patches contains code changes for both mpt2sas & mpt3sas
drivers.
Sreekanth Reddy
From: Kalle Valo
Date: Fri, 09 Jan 2015 18:31:30 +0200
> here are few more fixes to 3.19. Please let me know if there are any
> problems.
Pulled, thanks Kalle.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
VMWare seems not to emulate the PAT MSR correctly: reaeding
MSR_IA32_CR_PAT returns 0 even after writing another value to it.
Detect this bug and don't use the read value if it is 0.
Commit bd809af16e3ab1f8d55b3e2928c47c67e2a865d2 ("x86: Enable PAT to
use cache mode translation tables") triggers
In xen_rebuild_p2m_list() for large areas of invalid or identity
mapped memory the pmd entries on 32 bit systems are initialized
wrong. Correct this error.
Suggested-by: Boris Ostrovsky
Signed-off-by: Juergen Gross
---
arch/x86/xen/p2m.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
In the setup code of the linear mapped p2m list several bugs have
been found, especially for 32 bit dom0. These patches correct the
errors and make 32 bit dom0 bootable again.
Changes since V1:
- split up patch 3 as requested by David Vrabel
- use phys_addr_t instead of u64 as requested by Jan
When allocating a new pmd for the linear mapped p2m list a check is
done for not introducing another pmd when this just happened on
another cpu. In this case the old pte pointer was returned which
points to the p2m_missing or p2m_identity page. The correct value
would be the pointer to the found
When converting a pfn to a physical address be sure to use 64 bit
wide types or convert the physical address to a pfn if possible.
Signed-off-by: Juergen Gross
Tested-by: Boris Ostrovsky
---
arch/x86/xen/setup.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Friday 09 January 2015 11:29 PM, Oleg Nesterov wrote:
On 12/31, Pratyush Anand wrote:
+int arch_uprobe_analyze_insn(struct arch_uprobe *auprobe, struct mm_struct *mm,
+ unsigned long addr)
+{
+ probe_opcode_t insn;
+
+ insn = *(probe_opcode_t *)(>insn[0]);
+
+
With the introduction of the linear mapped p2m list setting memory
areas to "invalid" had to be delayed. When doing the invalidation
make sure no zero sized areas are processed.
Signed-off-by: Juegren Gross
---
arch/x86/xen/setup.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Hi Linus,
After merging the pinctrl tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/pinctrl/pinconf-generic.c: In function 'pinconf_generic_dump_pins':
drivers/pinctrl/pinconf-generic.c:116:19: error: 'struct pinctrl_desc' has no
member named 'num_dt_params'
if
Julian,
On Mon, Jan 12, 2015 at 12:58:05AM +0100, Julian Brost wrote:
> This patch series fixes multiple formatting issues in the documentation for
> the
> Intel MEI, including improperly formatted headlines and issues with spacing
> and
> indentation.
>
> Julian Brost (4):
>
Julian,
On Mon, Jan 12, 2015 at 12:58:09AM +0100, Julian Brost wrote:
[...]
> static struct mei_cl_driver contact_driver = {
> - .id_table = contact_mei_tbl,
> - .name = CONTACT_DRIVER_NAME,
> + .id_table = contact_mei_tbl,
> + .name = CONTACT_DRIVER_NAME,
>
> -
On Friday 09 January 2015 11:15 PM, Oleg Nesterov wrote:
On 01/08, Pratyush Anand wrote:
On Thursday 08 January 2015 10:33 PM, Will Deacon wrote:
I'm assuming that means you don't support compat (AArch32) tasks with this?
Hummm.. Yes, compat not yet supported.
I will come back on this.
On 2015年01月10日 03:04, Lorenzo Pieralisi wrote:
On Sun, Jan 04, 2015 at 10:55:09AM +, Hanjun Guo wrote:
There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
the former signals to the OS that the firmware is PSCI compliant.
The latter selects the appropriate conduit for PSCI calls
On Sun, Jan 11, 2015 at 3:21 AM, Linus Walleij wrote:
> When drivers are compiled in subdirectories the -DDEBUG flag need
> to be passed in the individual Makefiles.
This doesn't look good anymore..
> Reported-by: Mika Westerberg
> Suggested-by: Yingjoe Chen
> Cc: Mika Westerberg
>
Hi Charles,
On 01/09/2015 07:16 PM, Charles Keepax wrote:
On Fri, Jan 09, 2015 at 04:53:40PM +0800, Bo Shen wrote:
As the commit 5fe5b76 (ASoC: dapm: Do not pretend to support
controls for non mixer/mux widgets) remove the fake control.
Then, the wm8904 throw out the following warning at
On Mon, Jan 12, 2015 at 10:20:55AM +0800, Wang Nan wrote:
> From: Namhyung Kim
>
> When build with 'make ARCH=x86' and dwarf unwind is on, there is a
> compiling error:
>
>CC /home/wn/perf/arch/x86/util/unwind-libdw.o
>CC /home/wn/perf/arch/x86/tests/regs_load.o
>
[Just cc'ing Andrew as this patch is in his tree]
On Mon, 12 Jan 2015 11:19:01 +0800 Huang Ying wrote:
>
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 974bb1d5d44f008d7f207437d63d46658ff41dff ("mm: replace
>
This commit adds support for multiple hardware chip selects to spi-orion.
The number of supported chip selects varies based on the SoC and pin
configuration, so it is set using the num-cs device tree binding.
Signed-off-by: Ken Wilson
---
Documentation/devicetree/bindings/spi/spi-orion.txt | 3
Hello,
This patch series adds multiple chip select support for the spi-orion driver.
The first patch moves spi-orion to use the spi setup/set_cs/transfer_one
function pointers, which reduces duplicated code, and simplifies the chip
select support implementation.
The second patch
This commit changes spi-orion to provide setup, set_cs, and transfer_one
functions instead of transfer_one_message. This allows chip select support
for both native and GPIO chip selects to be added.
Signed-off-by: Ken Wilson
---
drivers/spi/spi-orion.c | 73
Hi David,
On Sun, 11 Jan 2015 22:08:29 -0500 (EST) David Miller
wrote:
>
> It's fixed as of 5 minutes ago in the net-next tree, sorry for this.
OK, thanks.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpIty49xzjqt.pgp
Description: OpenPGP digital signature
From: Stephen Rothwell
Date: Mon, 12 Jan 2015 14:05:15 +1100
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig)
> failed like this:
>
> Documentation/networking/timestamping/txtimestamp.c: In function
> '__recv_errmsg_cmsg':
>
Whoops. Changed the title from "2015-Q1" to be "2014-Q4" :)
--
Thanks,
Jike
On 01/09/2015 04:51 PM, Jike Song wrote:
Hi all,
We're pleased to announce a public update to Intel Graphics Virtualization
Technology (Intel GVT-g, formerly known as XenGT). Intel GVT-g is a complete
vGPU
Hi all,
After merging the net-next tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
Documentation/networking/timestamping/txtimestamp.c: In function
'__recv_errmsg_cmsg':
Documentation/networking/timestamping/txtimestamp.c:205:33: error:
dereferencing pointer to
On Thu, Jan 8, 2015 at 11:01 PM, Mike Looijmans wrote:
> Just a ping to inform if you've had had time to look at this?
Its in the queue for review this week. A lot to catch up on after the
holidays. Thanks for the ping.
Regards,
Mike
>
> Mike.
>
> On 12/04/2014 08:26 AM, Mike Looijmans wrote:
From: Christoph Jaeger
Date: Sun, 11 Jan 2015 13:01:16 -0500
> Due to a misplaced parenthesis, the expression
>
> (unlikely(offset) < 0),
>
> which expands to
>
> (__builtin_expect(!!(offset), 0) < 0),
>
> never evaluates to true. Therefore, when sending packets with
>
From: Richard Weinberger
Date: Sun, 11 Jan 2015 22:42:37 +0100
> Joe, I really don't care. This is the least significant
> patch of the series.
> I'll no longer waste my time with that.
If you're not willing to fix stylistic issues now, then nobody should
bother wasting their time on the high
Good day，
Hello.We’re a metal pins manufacturing expert in China. Buyers across the US,
the UK and France favor us. Mode design, casting, polishing and plating done
in-house. We also produce metal crafts and other accessories. No MOQ require
here. Waiting for your mail. I am Jennifer.
Happy
From: Stefan Agner Sent: Friday, January 09, 2015 10:02 PM
> To: da...@davemloft.net
> Cc: shawn@linaro.org; u.kleine-koe...@pengutronix.de; Duan Fugang-
> B38611; mark.rutl...@arm.com; robh...@kernel.org; pawel.m...@arm.com;
> ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; Duan
From: Chunyan Zhang
Date: Thu, 8 Jan 2015 12:01:26 +0800
> This patch-set removed all uses of timeval and used ktime_t instead if
> needed, since 32-bit time types will break in the year 2038.
>
> This patch-set also used the ktime_xxx functions accordingly.
> e.g.
> * Used ktime_get to get
FYI, we noticed the below changes on
commit 38c2adfb00db045a876dd667040abc01b788ad61 ("drm/radeon: Init amdkfd only
if it was compiled")
The original kernel panic caused by radeon init is fixed! Thanks!
testbox/testcase/testparams: vm-vp-quantal-i386/boot/1
68d0cb49f8db5ddc
From: Namhyung Kim
When build with 'make ARCH=x86' and dwarf unwind is on, there is a
compiling error:
CC /home/wn/perf/arch/x86/util/unwind-libdw.o
CC /home/wn/perf/arch/x86/tests/regs_load.o
arch/x86/tests/regs_load.S: Assembler messages:
arch/x86/tests/regs_load.S:65:
Ping,
On Tue, Jan 06, 2015 at 07:20:11AM +0800, Wanpeng Li wrote:
>Ping Juri, Peter, 1/7~6/7 can be reviewed/applied separately since patch 7/7
>is still need more work.
>On Sun, Jan 04, 2015 at 10:31:47AM +0800, Wanpeng Li wrote:
>>v6 -> v7:
>> * rebase
>>
>>I collect recent send out patches to
> -Original Message-
> From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
> Sent: Friday, January 09, 2015 7:11 PM
> To: Wang, Yalin
> Cc: 'Ard Biesheuvel'; 'Will Deacon'; 'linux-kernel@vger.kernel.org';
> 'akinobu.m...@gmail.com'; 'linux...@kvack.org'; 'Joe Perches';
>
> On 01/08/2015 02:04 AM, Peter Pan 潘栋 (peterpandong) wrote:
> >>> This commit adds the devicetree binding document that specifies the
> >>> spi nand devices support.
> >>>
> >>> Signed-off-by: Peter Pan
> >>> ---
> >>> Documentation/devicetree/bindings/mtd/spi-nand.txt | 22
> >>
Correct redundant initialization reported by sparse
Signed-off-by: Rene Kolarik
---
drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c
Hi Thomas,
I am really unable to see where is wrong leading to below warning
complaints. Can you please help me check it?
Add CC netdev maillist.
Thanks,
Ying
Forwarded Message
Subject: [rhashtable] WARNING: CPU: 0 PID: 10 at
kernel/locking/mutex.c:570 mutex_lock_nested()
Hi,
the e-mail address linux-...@linux.intel.com is given as contact address
in multiple files in the Linux kernel [1]. Earlier today I cc'd a patch
to this address [2] which got rejected since I'm not a list member.
Subscribing to it doesn't seem to be possible either.
Therefore this address
On Sun, Jan 11, 2015 at 3:07 PM, Denys Vlasenko wrote:
> Sequences
> pushl_cfi %reg
> CFI_REL_OFFSET reg, 0
> and
> popl_cfi %reg
> CFI_RESTORE reg
> happen quite often. This patch adds macros which generate them.
>
> No assembly changes (verified with objdump -dr
On Sun, Jan 11, 2015 at 2:58 PM, Kirill A. Shutemov
wrote:
> On Thu, Dec 18, 2014 at 09:51:27AM -0800, Darren Hart wrote:
>> thinkpad-acpi using software mute simplifies the driver and the user
>> experience
>> significantly.
>
> Except when it doesn't.
>
> I'm probably in minority, but I don't
On Fri, Nov 14, 2014 at 08:38:25PM +0100, Pali Rohár wrote:
> This patch adds sanity checks and reject trackstick packets from ALPS devices
> which do not have trackstick present (those without ALPS_DUALPOINT flag).
>
> Make sure that driver does not process some bogus packets as trackstick data
On Fri, Nov 14, 2014 at 08:38:24PM +0100, Pali Rohár wrote:
> This patch fix name, product and version of dev2 input device based on format
> used in function psmouse_switch_protocol() in file psmouse-base.c.
>
> Signed-off-by: Pali Rohár
Applied, thank you.
> ---
> drivers/input/mouse/alps.c
On Mon, 2014-12-15 at 14:25 +, Luis Henriques wrote:
> 3.16.7-ckt3 -stable review patch. If anyone has any objections, please let
> me know.
>
> --
>
> From: Steven Capper
>
> commit ded9477984690d026e46dd75e8157392cea3f13f upstream.
>
> For LPAE, we have the following
On Mon, 2014-12-15 at 14:25 +, Luis Henriques wrote:
> 3.16.7-ckt3 -stable review patch. If anyone has any objections, please let
> me know.
>
> --
>
> From: Steven Capper
>
> commit f2950706871c4b6e8c0f0d7c3f62d35930b8de63 upstream.
>
> Long descriptors on ARM are 64
Hi Felipe,
Today's linux-next merge of the usb-gadget-fixes tree got a conflict in
drivers/usb/phy/phy.c between commit 9c9d82492b73 ("usb: phy: Fix
deferred probing") from the usb.current tree and commit c818a94c77a9
("usb: phy: Restore deferred probing path") from the usb-gadget-fixes
tree.
On Sat, Jan 10, 2015 at 10:53 PM, Arnd Bergmann wrote:
> On Saturday 10 January 2015 22:40:22 Linus Walleij wrote:
>> > static int v3_read_config(struct pci_bus *bus, unsigned int devfn, int
>> > where,
>> > int size, u32 *val)
>> > {
>> > - addr =
1 - 100 of 760 matches
Mail list logo
