Remove uuid from the debug messages in bus-fixup.c
as this is already part of the device name.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus-fixup.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/misc/mei/bus-fixup.c b/drivers/misc/mei/bus-fixup.c
Hi Laurent,
On 11/09/2015 09:50 PM, Laurent Pinchart wrote:
> Hi Peter,
>
> Thank you for the patch.
>
> What happened to this patch series ? It looks like
> dma_request_slave_channel_compat_reason() isn't in mainline, so I can't apply
> this patch.
>
> I'll mark this patch as deferred in pat
From: Alexander Usyskin
The MEI FW can receive only one flow control for read.
Currently the driver only checks if a flow control credit was already
sent and read is pending in the rd_pending queue, but it also has to
check if flow control credit already queued in the write control queue
to prev
Use tracing events also for reading and writing pci configuration space
/tracing/events/mei/mei_pci_reg_{read,write}
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hw-me.c | 10 --
drivers/misc/mei/hw-txe.c| 10 --
drivers/misc/mei/mei-trace.c | 2 ++
drivers/misc/mei
Le 10/11/2015 01:29, Michael Ellerman a écrit :
> On Sat, 2015-11-07 at 12:35 +0100, Laurent Vivier wrote:
>> Le 07/11/2015 00:24, Scott Wood a écrit :
>>> On Fri, 2015-11-06 at 23:22 +0100, Laurent Vivier wrote:
Le 06/11/2015 22:09, Scott Wood a écrit :
> On Thu, 2015-11-05 at 12:47 +01
On 11/4/2015 10:59 PM, Mark Brown wrote:
On Mon, Nov 02, 2015 at 02:24:35PM +0900, Milo Kim wrote:
This looks mostly good, just a few fairly small things:
+lm363x_regulator_of_get_init_data(struct device *dev,
+ struct lm363x_regulator *lm363x_regulator, int id)
+{
+
On 11/09/2015 08:19 PM, Andreas Dannenberg wrote:
> Fixes the associations between the tx_mask and rx_mask and the associated
> playback / capture streams during setting of the TDM slot. With this
> patch in place it is now possible for example to only populate tx_mask
> (leaving rx_mask as 0) for
On Mon, Nov 09, 2015 at 03:30:53PM -0500, Tejun Heo wrote:
...
> Hmm can't we simply merge among !SLAB_ACCOUNT and SLAB_ACCOUNT
> kmem_caches within themselves? I don't think we'd be losing anything
> by restricting merge at that level. For anything to be tagged
> SLAB_ACCOUNT, it has to have
On Fri, Nov 06, 2015 at 04:21:10PM +, Will Deacon wrote:
> On Sat, Nov 07, 2015 at 12:11:16AM +0800, yalin wang wrote:
> > i just enable it on ARM64,
> > and it can work,
> > i don’t see some special requirement to enable this config .
>
> Right, so why does HAVE_LATENCYTOP_SUPPORT exist?
If
Hi Jacek,
On 11/4/2015 1:15 AM, Jacek Anaszewski wrote:
Hi Milo,
Thanks for the patch. Please find my comments in the code.
diff --git a/Documentation/ABI/testing/sysfs-class-led-lm3633
b/Documentation/ABI/testing/sysfs-class-led-lm3633
new file mode 100644
index 000..c1d8759
--- /dev/nu
On Mon, Nov 09, 2015 at 07:21:48PM -0800, Frank Rowand wrote:
> In the current Linus tree, new build warning.
>
> When CONFIG_DEBUG_LOCK_ALLOC is not enabled,
>
> drivers/regulator/core.c: In function 'regulator_lock_supply':
> drivers/regulator/core.c:142:6: warning: unused variable 'i'
> [
there maybe more than one i2s module inside chip, and these i2s modules
have different channels features.
for example: there are 3 i2s in rk3066, one support 8 channels playback
and 2 channels capture, but the others only support 2 channels playback
and 2 channels capture.
in order to compatible
add playback and capture properties to compatible various chips.
Signed-off-by: Sugar Zhang
---
arch/arm/boot/dts/rk3066a.dtsi | 6 ++
arch/arm/boot/dts/rk3188.dtsi | 2 ++
arch/arm/boot/dts/rk3288.dtsi | 2 ++
3 files changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/rk3066a.dtsi
there maybe more than one i2s module inside chip, and these i2s modules
have different channels features.
for example: there are 3 i2s in rk3066, one support 8 channels playback
and 2 channels capture, but the others only support 2 channels playback
and 2 channels capture.
in order to compatible
rockchip,playback-channels: max playback channels, 8 channels default.
Signed-off-by: Sugar Zhang
---
Documentation/devicetree/bindings/sound/rockchip-i2s.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/rockchip-i2s.txt
b/Documentation/devicetre
22M/24M clocks are only required for I2S, so move the control to
I2S DAI ops.
Signed-off-by: Koro Chen
---
sound/soc/mediatek/mtk-afe-pcm.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/sound/soc/mediatek/mtk-afe-pcm.c b/sound/soc/mediatek/mtk-afe-pcm.c
inde
Hi, Olof,
> On Mon, Nov 9, 2015 at 6:53 PM, Alison Wang wrote:
> > v7 LPAE multi-platform defconfig is based on v7 multi-platform
> > defconfig and adds LPAE support.
> >
> > The platforms based on Cortex-A7/A12/A15/A17, PJ4B, Krait are also
> > enabled in this defconfig. But Cortex-A5/A8/A9, Sc
Hi,
The problem is that the call to might_sleep might sleep and the return value of
wait_event_timeout does not account for the time slept in there.
The might_sleep includes a call to __schedule if CONFIG_PREEMPT_VOLUNTARY is
defined.
A problematic scenario can be like the following:
- A driv
On 11/09/2015 05:32 PM, John Garry wrote:
> This is the driver patchset for the HiSilicon SAS driver. The driver
> is a platform driver.
>
> The driver will support multiple revisions of HW. Currently only "v1"
> HW is supported.
>
> The driver uses libsas framework within the SCSI framework.
>
On Mon, Nov 09, 2015 at 04:16:16PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 9, 2015 at 2:21 AM, Alexandre Courbot wrote:
> > On Fri, Nov 6, 2015 at 12:55 AM, LABBE Corentin
> > wrote:
> >> of_match_device could return NULL, and so cause a NULL pointer
> >> dereference later at line 132:
> >> p
On 9 November 2015 at 22:08, Kees Cook wrote:
> On Sat, Nov 7, 2015 at 11:55 PM, Ard Biesheuvel
> wrote:
>> On 8 November 2015 at 07:58, Kees Cook wrote:
>>> On Fri, Nov 6, 2015 at 11:39 PM, Ard Biesheuvel
>>> wrote:
On 7 November 2015 at 08:09, Ingo Molnar wrote:
>
> * Matt Flemi
Hi Jacek,
On 11/4/2015 1:15 AM, Jacek Anaszewski wrote:
+ - led-max-microamp: Max current setting. Type is .
>+ Unit is microampere. Range is from 5000 to 3.
Could you specify also a step?
Yep, step is 1000. Thanks for catching this.
I'll update the binding in the n
Dear Client,
Have a good day!
Glad to learn you're on the market of Acupuncture Pen products
We are the manufacture at family use electronic health devices since 2000.
Have ISO13485:2003 Medical,FDA approved and Europe CE certification.
We keep good quality and reliable cooperation for global val
Andrew,
is this simple addition something you could still send on to Linus
for this merge window? I would make my life easier to have it in
so I could start using it in patches for various trees in the next
merge window.
Thanks,
Christoph
On Fri, Oct 23, 2015 at 06:33:27PM +0300, Daniel
On 11/09/2015 09:16 PM, Laurent Pinchart wrote:
> Hi Andrzej,
>
> Thank you for the patch.
>
> On Thursday 24 September 2015 16:00:12 Andrzej Hajda wrote:
>> The function can return negative value.
>>
>> The problem has been detected using proposed semantic patch
>> scripts/coccinelle/tests/assign_
Around Mon 09 Nov 2015 11:21:17 -0800 or thereabout, Yang Shi wrote:
> FRAME_POINTER is set by default if ARCH_WANT_FRAME_POINTERS and DEBUG_KERNEL
> are selcted, this is the standard way to include FRAME_POINTER used by all
> of other architectures.
>
> And, set DEBUG_KERNEL=y in defconfigs othe
Commit-ID: b71b437eedaed985062492565d9d421d975ae845
Gitweb: http://git.kernel.org/tip/b71b437eedaed985062492565d9d421d975ae845
Author: Peter Zijlstra
AuthorDate: Mon, 2 Nov 2015 10:50:51 +0100
Committer: Ingo Molnar
CommitDate: Mon, 9 Nov 2015 16:13:11 +0100
perf: Fix inherited events
Commit-ID: 2fd59077755c44dbbd9b2fa89cf988235a3a6a2b
Gitweb: http://git.kernel.org/tip/2fd59077755c44dbbd9b2fa89cf988235a3a6a2b
Author: Paul E. McKenney
AuthorDate: Wed, 4 Nov 2015 05:48:38 -0800
Committer: Ingo Molnar
CommitDate: Mon, 9 Nov 2015 16:13:11 +0100
perf: Disable IRQs across
Commit-ID: 25b3e5a3344e1f700c1efec5b6f0199f04707fb1
Gitweb: http://git.kernel.org/tip/25b3e5a3344e1f700c1efec5b6f0199f04707fb1
Author: Rik van Riel
AuthorDate: Thu, 5 Nov 2015 15:56:22 -0500
Committer: Ingo Molnar
CommitDate: Mon, 9 Nov 2015 16:13:27 +0100
sched/numa: Fix math underflo
On Mon, Nov 09, 2015 at 01:20:12PM -0800, Kees Cook wrote:
> Just to remind everyone: while we certainly want to clean these up in
> the code where possible, we still want to make the constification
> plugin part of the regular builds. We want to provide a
> secure-by-default build, even when vendo
Hello! So, what should we do with this?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On
> Behalf Of Pavel
> Fedin
> Sent: Monday, November 02, 2015 10:
On 11/10/2015 04:19 AM, Michael S. Tsirkin wrote:
> On Mon, Nov 09, 2015 at 12:35:45PM +0800, Jason Wang wrote:
>> >
>> >
>> > On 11/09/2015 01:11 AM, Michael S. Tsirkin wrote:
>>> > > On Tue, Sep 15, 2015 at 02:41:53PM +0800, Jason Wang wrote:
> >> Hi:
> >>
> >> This series fixe
Make it possible to use the bulk API with optional supplies, by allowing
the consumer to marking supplies as optional in the regulator_bulk_data.
Signed-off-by: Bjorn Andersson
---
drivers/regulator/core.c | 6 --
drivers/regulator/devres.c | 7 +--
include/linux/regula
On Mon, 2015-11-09 at 18:18 -0800, Andy Lutomirski wrote:
>
> Which leaves the special case of Xen, where even preexisting devices
> don't bypass the IOMMU. Can we keep this specific to powerpc and
> sparc? On x86, this problem is basically nonexistent, since the IOMMU
> is properly self-describ
&chip->dev.kobj,
> > + "ppi");
> > + if (rc && rc != -ENOENT) {
> > + tpm_chip_unregister(chip);
> > + return rc;
>
t's going wrong.
> >>
> >> Thanks for following up. I'll be glad to test any patches if you have
> >> anything you'd like me to test.
> >
> > You need "clockevents/drivers/mtk: Fix spurious interrupt leading to
> > crash" (https://l
&chip->dev.kobj,
> + "ppi");
> + if (rc && rc != -ENOENT) {
> + tpm_chip_unregister(chip);
> + return
On 11/9/2015 2:15 AM, Hannes Reinecke wrote:
On 11/09/2015 02:57 AM, Sinan Kaya wrote:
The mpt2sas and mpt3sas drivers are spinning forever in
their IRQ handlers if there are a lot of jobs queued up
by the PCIe card. This handler is causing spikes for
the rest of the system and sluggish behavi
On 2015/11/10 4:09, Arnd Bergmann wrote:
> On Monday 09 November 2015 17:10:43 Lorenzo Pieralisi wrote:
>> On Mon, Nov 09, 2015 at 03:07:38PM +0100, Tomasz Nowicki wrote:
>>> On 06.11.2015 14:22, Jiang Liu wrote:
On 2015/11/6 20:40, Tomasz Nowicki wrote:
> On 06.11.2015 12:46, Jiang Liu wr
On Mon, Nov 9, 2015 at 9:28 PM, Benjamin Herrenschmidt
wrote:
> On Mon, 2015-11-09 at 18:18 -0800, Andy Lutomirski wrote:
>>
>> /* Qumranet donated their vendor ID for devices 0x1000 thru 0x10FF.
>> */
>> static const struct pci_device_id virtio_pci_id_table[] = {
>> { PCI_DEVICE(0x1af4, P
On Mon, Nov 9, 2015 at 9:26 PM, Benjamin Herrenschmidt
wrote:
> On Mon, 2015-11-09 at 18:18 -0800, Andy Lutomirski wrote:
>>
>> Which leaves the special case of Xen, where even preexisting devices
>> don't bypass the IOMMU. Can we keep this specific to powerpc and
>> sparc? On x86, this problem
ti-qspi controller provides mmap port to read data from SPI flashes.
mmap port is enabled in QSPI_SPI_SWITCH_REG. ctrl module register may
also need to be accessed for some SoCs. The QSPI_SPI_SETUP_REGx needs to
be populated with flash specific information like read opcode, read
mode(quad, dual, no
Add qspi memory mapped region entries for AM43xx based SoCs. Also,
update the binding documents for the controller to document this change.
Signed-off-by: Vignesh R
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/spi/ti_qspi.txt | 5 +++--
arch/arm/boot/dts/am4372.dtsi
Add qspi memory mapped region entries for DRA7xx based SoCs. Also,
update the binding documents for the controller to document this change.
Signed-off-by: Vignesh R
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/spi/ti_qspi.txt | 14 ++
arch/arm/boot/dts/dra7.dtsi
In addition to providing direct access to SPI bus, some spi controller
hardwares (like ti-qspi) provide special memory mapped port
to accesses SPI flash devices in order to increase read performance.
This means the controller can automatically send the SPI signals
required to read data from the SPI
Changes since v2:
Remove mmap_lock_mutex.
Optimize enable/disable of mmap mode.
Changes since v1:
Introduce API in SPI core that MTD flash driver can call for mmap read
instead of directly calling spi-master driver callback. This API makes
sure that SPI core msg queue is locked during mmap transf
Certain spi controllers may support memory mapped interface to read from
m25p80 type flash devices. This interface provides better read
performance than regular SPI interface.
Call spi_mtd_mmap_read() interface, if supported, to make use of
memory-mapped interface.
Signed-off-by: Vignesh R
---
d
On Mon, 2015-11-09 at 18:18 -0800, Andy Lutomirski wrote:
>
> /* Qumranet donated their vendor ID for devices 0x1000 thru 0x10FF.
> */
> static const struct pci_device_id virtio_pci_id_table[] = {
> { PCI_DEVICE(0x1af4, PCI_ANY_ID) },
> { 0 }
> };
>
> Can we match on that range?
Wanpeng Li writes:
> On 11/10/15 9:47 AM, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://github.com/0day-ci/linux
>> Wanpeng-Li/KVM-x86-Reset-RFLAGS-state-following-processor-init-reset/20151103-194355
>> commit 0c32e5dd82fd0e63fd9e6aecf5a4bffbdf2ab207 ("KVM: x86:
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Jan-Kara/ext4-Fix-races-between-page-faults-and-hole-punching/20151105-002716
commit dfbd72d0d6f10086064b918419fb2094ff9fbdb6 ("ext4: Fix races between page
faults and hole punching")
odpovezte mi na nize uvedenou e-mailovou adresu pro vysvetlení výroku.
E-mail: chn.j...@gmail.com
--
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
Create a new ioctl to expose the block layer's newfound ability to
issue either a zeroing discard, a WRITE SAME with a zero page, or a
regular write with the zero page. This BLKZEROOUT2 ioctl takes
{start, length, flags} as parameters. So far, the only flag available
is to enable the zeroing disc
Hi,
I have tested rcar_thermal funstion on stable linux v4.3.
It is good with this patchs.
Tested-by: Nguyen Viet Dung
Best regards
Nguyen Viet Dung
On 2015年11月10日 11:11, Kuninori Morimoto wrote:
Hi Zhang, Eduardo
Cc: Dung, Hiep
rcar_thermal doesn't work after unbind/re-bind today.
These pa
Hi,
On 10/12/2015 01:33 AM, Brian Norris wrote:
Hi Boris,
On Fri, Oct 02, 2015 at 08:27:38AM +0200, Boris Brezillon wrote:
Brian, Archit,
On Thu, 1 Oct 2015 19:44:34 -0700
Brian Norris wrote:
On Wed, Aug 19, 2015 at 10:19:02AM +0530, Archit Taneja wrote:
Some controllers can access the fa
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit db1003a719d75cebe5843a7906c02c29bec9922c ("x86/numachip: Cleanup
Numachip support")
Elapsed time: 210
BUG: kernel early-boot hang
Linux version 4.3.0-rc2-1-gdb1003a #1
Comma
dma_to_phys() is not guaranteed to be available on all platforms and
should not be used outside of arch/. Replace it with what it is expected
to do in our case: simply cast the DMA handle to a physical address.
Reported-by: Stephen Rothwell
Signed-off-by: Alexandre Courbot
---
drivers/gpu/drm/n
__rmem_check_for_overlap() is called very early in boot, and on some
powerpc systems it's not safe to call WARN that early in boot.
If the overlap check fails the system will oops instead of printing a
warning. Furthermore because it's so early in boot the console is not up
and the user doesn't se
Remove the wrapper function ll_finish_md_op_data() and replace all
its calls with the standard function kfree() that it wraps. Also,
prototype of the function is removed as it is no longer of any use.
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
Substitute standard function kfree() in place of the function
ll_finish_md_op_data().
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
drivers/staging/lustre/lustre/llite/llite_close.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
Sinan Kaya wrote:
OK. I did an internal code review before posting the patch. Nobody
complained about iterator types. I am trying to find what goes as a good
practice vs. what is personal style.
I normally check for inappropriate usage of sized integers in my
reviews, but I admit I'm inconsis
Replace the calls of the function ll_finish_md_op_data() with the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
drivers/staging/lustre/lustre/llite/llite_nfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
Substitute the standard function kfree() for the function
ll_finish_md_op_data().
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
drivers/staging/lustre/lustre/llite/symlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dri
On 11/9/2015 1:25 PM, Rob Herring wrote:
On Sun, Nov 08, 2015 at 09:17:20PM -0500, Sinan Kaya wrote:
On 11/8/2015 12:08 AM, Timur Tabi wrote:
On 11/8/2015 12:08 AM, Timur Tabi wrote:
Sinan Kaya wrote:
+val = val & ~(MAX_BUS_REQ_LEN_MASK << MAX_BUS_WR_REQ_BIT_POS);
+val = val | (mgmt
On Mon, 2015-11-09 at 22:41 -0600, Rob Herring wrote:
> On Mon, Nov 9, 2015 at 10:29 PM, Michael Ellerman wrote:
> > On Tue, 2015-09-15 at 18:30 -0700, Mitchel Humpherys wrote:
> > > Any overlap in the reserved memory regions (those specified in the
> > > reserved-memory DT node) is a bug. These
Change the calls of the function ll_finish_md_op_data() to the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
drivers/staging/lustre/lustre/llite/xattr_cache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
rm/nouveau/nvkm/subdev/instmem/gk20a.c:143:2: error: implicit
>> declaration of function 'dma_to_phys' [-Werror=implicit-function-declaration]
>>
>> Caused by commit
>>
>> 69c4938249fb ("drm/nouveau/instmem/gk20a: use direct CPU access")
>&g
Replace the calls of the function ll_finish_md_op_data() with the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
drivers/staging/lustre/lustre/llite/namei.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletion
On 11/9/2015 4:26 AM, Andy Shevchenko wrote:
On Mon, Nov 9, 2015 at 5:07 AM, Sinan Kaya wrote:
On 11/8/2015 3:09 PM, Andy Shevchenko wrote:
On Sun, Nov 8, 2015 at 6:52 AM, Sinan Kaya wrote:
This patch adds supporting utility functions
for selftest. The intention is to share the self
te
On Mon, Nov 09, 2015 at 05:01:18PM -0600, Chris J Arges wrote:
> On 11/09/2015 02:56 PM, Josh Poimboeuf wrote:
> > I'd recommend splitting this up into two separate patches:
> >
> > 1. introduce old_sympos
> > 2. change the sysfs interface
> >
> > On Mon, Nov 09, 2015 at 10:16:05AM -0600, Chris J
Replace the calls of the function ll_finish_md_op_data() with the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
drivers/staging/lustre/lustre/llite/file.c | 24
1 file changed, 12 insertions(+)
Sinan Kaya wrote:
The code says it is using these macros for small integers only which
can't overflow. I was trying to get rid of compiler warning and it seems
to have disappeared.
I would double-check the assembly code, if I were you. I don't like it
when warnings just go away like that.
Replace the calls of the function ll_finish_md_op_data() with the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
Changes in v2:
Fix commit message and merge a patch
drivers/staging/lustre/lustre/llite/dir.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletion
On 11/9/2015 10:26 PM, Timur Tabi wrote:
Sinan Kaya wrote:
I created this patch back in March with an older version of the compiler
and older kernel (3.19). I'm no longer able to reproduce this with this
compiler and linux-next.
Thread model: posix
gcc version 4.8.3 20140401 (prerelease) (cr
This patchset removes an unnecessary wrapper function, its prototype and
replaces all its calls in different files with the standard function
that it wraps.
After applying this patch, code becomes cleaner.
Changes in v2:
Fix commit message and merge a patch
Shivani Bhardwaj (8):
Staging
Hi Dan,
On Mon, 9 Nov 2015 18:42:31 -0800 Dan Williams wrote:
>
> On Mon, Nov 9, 2015 at 5:24 PM, Stephen Rothwell
> wrote:
> >
> > Is that new stuff in the nvdimm tree really meant for v4.4? If not,
> > please remove it until -rc1 has been released.
>
> Done. I was indeed squeezing things
On 11/9/2015 8:48 AM, Timur Tabi wrote:
Sinan Kaya wrote:
And why kmalloc anyway? Why not leave it on the stack?
char src[] = "hello world";
?
I need to call dma_map_single on this address to convert it to a DMA
address. That's why.
And you can't do that with an object that's on t
This patchset removes livepatch's need for architecture-specific relocation
code by leveraging existing code in the module loader to perform
arch-dependent work. Specifically, instead of duplicating code and
re-implementing what the apply_relocate_add() function in the module loader
already does in
Intialize the list of relocation sections in the sample
klp_object (even if the list will be empty in this case).
Also mark module as a livepatch module so that the module
loader can appropriately initialize it.
Signed-off-by: Jessica Yu
---
samples/livepatch/livepatch-sample.c | 2 ++
1 file ch
Architecture-specific relocation code no longer needed, since symbol
resolution and relocation work will be offloaded to module loader.
Signed-off-by: Jessica Yu
---
arch/x86/kernel/Makefile| 1 -
arch/x86/kernel/livepatch.c | 91 -
2 files change
In livepatch modules, preserve section, symbol, string information from
the load_info struct in the module loader. This information is used to
patch modules that are not loaded in memory yet; specifically it is used
to resolve remaining symbols and write relocations when the target
module loads.
S
Add livepatch elf reloc section flag, livepatch symbol bind
and section index
Signed-off-by: Jessica Yu
---
include/uapi/linux/elf.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/uapi/linux/elf.h b/include/uapi/linux/elf.h
index 71e1d0e..967ce1b 100644
--- a/include/uapi/linux/e
On Thu, Oct 29, 2015 at 04:42:37PM +0100, Markus Pargmann wrote:
> del_timer_sync(&nbd->timeout_timer);
> +
> +out:
> + spin_unlock_irq(&nbd->sock_lock);
... and in its callback we have this:
> @@ -148,17 +155,15 @@ static void nbd_xmit_timeout(unsigned long arg)
>
> nbd->discon
Reuse module loader code to write relocations, thereby eliminating the
need for architecture specific code in livepatch. Namely, we reuse
apply_relocate_add() in the module loader to write relocs instead of
duplicating functionality in livepatch's klp_write_module_reloc(). To
apply relocation secti
On 11/9/2015 1:19 PM, Rob Herring wrote:
On Sat, Nov 07, 2015 at 11:53:00PM -0500, Sinan Kaya wrote:
This patch adds support for hidma engine. The driver
consists of two logical blocks. The DMA engine interface
and the low-level interface. The hardware only supports
memcpy/memset and this driv
On Mon, Nov 9, 2015 at 10:29 PM, Michael Ellerman wrote:
> On Tue, 2015-09-15 at 18:30 -0700, Mitchel Humpherys wrote:
>
>> Any overlap in the reserved memory regions (those specified in the
>> reserved-memory DT node) is a bug. These bugs might go undetected as
>> long as the contested region is
On Tue, 2015-09-15 at 18:30 -0700, Mitchel Humpherys wrote:
> Any overlap in the reserved memory regions (those specified in the
> reserved-memory DT node) is a bug. These bugs might go undetected as
> long as the contested region isn't used simultaneously by multiple
> software agents, which mak
On Tue, Nov 10, 2015 at 12:27:34PM +1030, Rusty Russell wrote:
> Josh Poimboeuf writes:
> > On Mon, Nov 09, 2015 at 02:53:57PM +1030, Rusty Russell wrote:
> >
> >> @@ -1858,74 +1849,75 @@ static void mod_sysfs_teardown(struct module *mod)
> >> /*
> >> * LKM RO/NX protection: protect module's te
On Wed, Oct 14, 2015 at 02:41:57PM +0200, Lukasz Pawelczyk wrote:
> int (*getprocattr)(struct task_struct *p, char *name, char **value);
> - int (*setprocattr)(struct task_struct *p, char *name, void *value,
> - size_t size);
> + int (*setprocattr)(struct t
Made visorbus_main.c checkpatch warning-free by fixing the comment style
issues.
Signed-off-by: Gavin O'Leary
---
drivers/staging/unisys/visorbus/visorbus_main.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/unisys/visorbus/visorbus_main.c
On Mon, Nov 09, 2015 at 03:47:20PM -0700, Jason Gunthorpe wrote:
> On Sun, Nov 08, 2015 at 09:51:07AM +0200, Jarkko Sakkinen wrote:
> > + if (rc && rc != -ENOENT) {
> > + tpm_chip_unregister(chip);
> > + return rc;
> > + }
> > + }
>
> This
Linus,
Thanks for your review!
On Mon, Nov 9, 2015 at 2:21 AM, Linus Walleij wrote:
> On Fri, Nov 6, 2015 at 12:41 AM, Moritz Fischer
> wrote:
>
>> The USRP E3XX series requires pinctrl to configure the idle state
>> FPGA image for minimizing power consumption.
>> This is required since differe
Hi,
On Mon, Nov 09, 2015 at 03:23:03PM -0600, Andrew F. Davis wrote:
> Check if I2C core has been built as a module when BATTERY_BQ27XXX
> is built-in. If so disable I2C functionality.
>
> Fixes: 6bd03ce3c12a ("power: bq27xxx_battery: Remove unneeded dependency in
> Kconfig")
> Reported-by: Arnd
Hi John,
On 2015/11/10 0:32, John Garry wrote:
> This patch also includes relevant memory/pool
> free'ing and sas/scsi host removal
>
> Signed-off-by: John Garry
> ---
> drivers/scsi/hisi_sas/hisi_sas_main.c | 71
> ++-
> 1 file changed, 70 insertions(+), 1 dele
On 11/09/2015 08:33 PM, Al Viro wrote:
On Fri, Nov 06, 2015 at 05:52:08PM +0530, Vishnu Pratap Singh wrote:
Have you even tried to trigger the failure exits you've added? The
more you've successfully set up, the _less_ your cleanup code ends
up undoing; that simply can't be right.
That aside,
Hi Alison,
On Mon, Nov 9, 2015 at 6:53 PM, Alison Wang wrote:
> v7 LPAE multi-platform defconfig is based on v7 multi-platform
> defconfig and adds LPAE support.
>
> The platforms based on Cortex-A7/A12/A15/A17, PJ4B, Krait are
> also enabled in this defconfig. But Cortex-A5/A8/A9, Scorpion
> and
Hi Linus,
Here are our branches from arm-soc for v4.4.
Nothing too crazy this time around, we've documented each branch as usual.
Yet again the DT branch is by far the biggest, and it's not a trend we mind
to continue. This is the first time we're mixing arm64/arm contents in that
branch as well
A handful of fixes that came in and didn't seem warranted to go in through
the 4.3-rc cycle.
- MAINTAINERS updates for one of the Broadcom platforms and lpc18xx
- A couple of non-critical Davinci bugfixes
- A fix to reset irq affinity for TI platforms (silences a warning at reboot)
Conflicts:
Defconfig updates are kept separate from other branches mostly to avoid
conflicts between the different categories (driver branch enabling something
that has context conflict with SoC options, etc).
A lot of this again is scattered across the various hardware platforms.
multi_v7_defconfig, our "ge
Again we have a sizable (but not huge) cleanup branch with a net delta of about
-3k lines.
Main contents here is:
- A bunch of development/cleanup of a few PXA boards
- Removal of bockw platforms on shmobile, since the platform has now gone
completely multiplatform. Whee!
- move of the 32kHz ti
As we've enabled multiplatform kernels on ARM, and greatly done away with
the contents under arch/arm/mach-*, there's still need for SoC-related
drivers to go somewhere.
Many of them go in through other driver trees, but we still have
drivers/soc to hold some of the "doesn't fit anywhere" lowlevel
1 - 100 of 900 matches
Mail list logo
