On Wed, 30 Dec 2015 22:10:44 +0800
Qu Wenruo wrote:
> Understood now.
Good.
> I totally understand that implement ... to polish your
> skill.
That has got to be the most hilarious way I believe I have seen someone
delegate a task. But it was effective.
Only one problem. I do not run BTRFS on m
On Tue, Dec 29, 2015 at 9:17 PM, Yao Yuan wrote:
> Hi Rob,
>
> Thanks for your review.
> So you mean that I should add the commit message for why I add this new
> compatible?
Please don't top post on the lists.
No, the binding doc should explain what are valid combinations of
compatible strings
This introduces the preprocessor symbol KIMAGE_VADDR which will serve as
the symbolic virtual base of the kernel region, i.e., the kernel's virtual
offset will be KIMAGE_VADDR + TEXT_OFFSET. For now, we define it as being
equal to PAGE_OFFSET, but in the future, it will be moved below it once
we mo
This moves the module area to right before the vmalloc area, and
moves the kernel image to the base of the vmalloc area. This is
an intermediate step towards implementing kASLR, where the kernel
image can be located anywhere in the vmalloc area.
Signed-off-by: Ard Biesheuvel
---
arch/arm64/inclu
Since the early fixmap page tables are populated using pages that are
part of the static footprint of the kernel, they are covered by the
initial kernel mapping, and we can refer to them without using __va/__pa
translations, which are tied to the linear mapping.
Instead, let's introduce __phys_to_
KVM on arm64 uses a fixed offset between the linear mapping at EL1 and
the HYP mapping at EL2. Before we can move the kernel virtual mapping
out of the linear mapping, we have to make sure that references to kernel
symbols that are accessed via the HYP mapping are translated to their
linear equival
Since arm64 does not use a decompressor that supplies an execution
environment where it is feasible to some extent to provide a source of
randomness, the arm64 KASLR kernel depends on the bootloader to supply
some random bits in register x1 upon kernel entry.
On UEFI systems, we can use the EFI_RN
This adds support for runtime relocation of the kernel Image, by
building it as a PIE (ET_DYN) executable and applying the dynamic
relocations in the early boot code.
Signed-off-by: Ard Biesheuvel
---
Documentation/arm64/booting.txt | 3 +-
arch/arm64/Kconfig | 13
arch/arm64/
On 12/19/2015 1:37 PM, Andy Shevchenko wrote:
> On Thu, Dec 17, 2015 at 7:01 PM, Sinan Kaya wrote:
>> In order to create a relationship model between the channels and the
>> management object, we are adding support for object hierarchy to the
>> drivers. This patch simplifies the userspace applica
This relaxes the kernel Image placement requirements, so that it
may be placed at any 2 MB aligned offset in physical memory.
This is accomplished by ignoring PHYS_OFFSET when installing
memblocks, and accounting for the apparent virtual offset of
the kernel Image. As a result, virtual address ref
Unfortunately, the current way of using the linker to emit build time
constants into the Image header will no longer work once we switch to
the use of PIE executables. The reason is that such constants are emitted
into the binary using R_AARCH64_ABS64 relocations, which we will resolve
at runtime,
Before introducing new statically allocated page tables and increasing
their alignment in subsequent patches, update the reservation logic
so that only pages that are in actual use end up as reserved with
memblock.
Signed-off-by: Ard Biesheuvel
---
arch/arm64/mm/init.c | 5 -
1 file changed,
Before implementing KASLR for arm64 by building a self-relocating PIE
executable, we have to ensure that values we use before the relocation
routine is executed are not subject to dynamic relocation themselves.
This applies not only to virtual addresses, but also to values that are
supplied by the
This adds support for emitting PLTs at module load time for relative
branches that are out of range. This is a prerequisite for KASLR,
which may place the kernel and the modules anywhere in the vmalloc
area, making it likely that branch target offsets exceed the maximum
range of +/- 128 MB.
Signed
Instead of using absolute addresses for both the exception location and
the fixup, use offsets relative to the exception table entry values. This
is a prerequisite for KASLR, since absolute exception table entries are
subject to dynamic relocation, which is incompatible with the sorting of
the exce
This series implements KASLR for arm64, by building the kernel as a PIE
executable that can relocate itself at runtime, and moving it to a random
offset in the vmalloc area. This v2 also implements physical randomization,
i.e., it allows the kernel to deal with being loaded at any physical offset
(
By default, early_init_dt_add_memory_arch() ignores memory below
the base of the kernel image since it won't be addressable via the
linear mapping. However, this is not appropriate anymore once we
decouple the kernel text mapping from the linear mapping, so archs
may want to drop the low limit enti
Jacob Siverskog writes:
> On Tue, Dec 29, 2015 at 9:08 PM, David Miller wrote:
>> From: Rainer Weikusat
>> Date: Tue, 29 Dec 2015 19:42:36 +
>>
>>> Jacob Siverskog writes:
This should fix a NULL pointer dereference I encountered (dump
below). Since __skb_unlink is called while wal
> This is an API consolidation only. The use of kmalloc + memset to 0
> is equivalent to kzalloc.
>
> Signed-off-by: Nicholas Mc Guire
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
> This is an API consolidation only. Bool initializations should
> use true and false thus bool tests don't need an explicit comparison.
>
> Signed-off-by: Nicholas Mc Guire
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe l
On 12/30/15 9:34 AM, Chao Yu wrote:
> Hi Jaegeuk,
>
>> -Original Message-
>> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
>> Sent: Wednesday, December 30, 2015 8:05 AM
>> To: Chao Yu
>> Cc: linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH 2/2] f2
This patch escapes a regex that uses left brace.
Using checkpatch.pl with Perl 5.22.0 generates the warning: "Unescaped
left brace in regex is deprecated, passed through in regex;"
Comment from regcomp.c in Perl source: "Currently we don't warn when the
lbrace is at the start of a construct. This
2015-12-16 8:21 GMT-03:00 Geyslan G. Bem :
> 2015-12-15 21:13 GMT-03:00 Joe Perches :
>> On Tue, 2015-12-15 at 20:58 -0300, Geyslan G. Bem wrote:
>>> 2015-12-10 8:24 GMT-03:00 Geyslan G. Bem :
>>> > Suggested-by: Peter Senna Tschudin
>>> > Reported-by: Geyslan G. Bem
>>> >
>>>
>>> Joe, do you app
Since kzalloc can be failed in memory pressure,
it needs to be handled, otherwise NULL dereference could be happened
Signed-off-by: Insu Yun
---
drivers/net/wireless/mwifiex/sdio.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/net/wireless/mwifiex/sdio.c
b/drivers/net
On Wed, Dec 30, 2015 at 06:15:23AM -0500, Sanidhya Solanki wrote:
> Only one problem. I do not run BTRFS on my systems nor do I have a
> RAID setup, due to possessing a limited number of free drives. So, while
> I may be able to code for it, I will not be able to test it. I will need
> the communit
Since devm_kzalloc can be failed, it needs to be checked
if not, NULL dereference could be happened.
Signed-off-by: Insu Yun
---
drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
b/drivers/gpu/drm/i915/int
On Wed, Dec 30, 2015 at 10:10:44PM +0800, Qu Wenruo wrote:
> Now I am on the same side of David.
> Which means a runtime interface to change them. (along with mkfs option)
>
> If provide some configurable features, then it should be able to be
> tuned at both right time and mkfs time.
> Or, just
On Wed, Dec 30, 2015 at 09:35:21AM +0100, Paul Kocialkowski wrote:
> In my opinion, it would be more elegant to adapt the core regulator
> framework to first enable the GPIO and then call the regulator enable
> ops callback instead of handling the GPIO in the driver.
Why would we want to actively
On Wed, Dec 23, 2015 at 11:05:15AM +0530, Raja Mani wrote:
> Add device tree binding documentation details for wifi block present
> in Qualcomm IPQ4019 SoC into qcom,ath10k.txt.
>
> Signed-off-by: Raja Mani
> ---
> .../bindings/net/wireless/qcom,ath10k.txt | 87
> --
> asm-generic/barrier.h defines a nop() macro.
> To be able to use this header on ia64, we shouldn't
> call local functions/variables nop().
>
> There's one instance where this breaks on ia64:
> rename the function to iosapic_nop to avoid the conflict.
Acked-by: Tony Luck
--
To unsubscribe from
> On ia64 smp_rmb, smp_wmb, read_barrier_depends, smp_read_barrier_depends
> and smp_store_mb() match the asm-generic variants exactly. Drop the
> local definitions and pull in asm-generic/barrier.h instead.
>
> This is in preparation to refactoring this code area.
Acked-by: Tony Luck
--
To unsu
HI Bjorn,
On Thu, Dec 24, 2015 at 2:03 PM, Bjorn Andersson wrote:
> Make the addr parameter const in SET_IEEE80211_PERM_ADDR() to save
> clients from having to cast away a const qualifier.
>
> Signed-off-by: Bjorn Andersson
> ---
> include/net/mac80211.h | 2 +-
> 1 file changed, 1 insertion(+)
[I repeat myself just in case my last message disappeared. It would be
a shame if 4.4 was also regressed because of a missing response.]
I wrote:
> Russell King wrote:
> > On Thu, Dec 10, 2015 at 03:29:37PM +, Peter Rosin wrote:
> > > Russell King wrote:
> > > > On Thu, Dec 03, 2015 at 09:37:
I wrote:
> [I repeat myself just in case my last message disappeared. It would be
> a shame if 4.4 was also regressed because of a missing response.]
Crap, I should have checked one more time before hitting send. The patch
is already in there! Sorry for the confusion.
Cheers,
Peter
--
To unsubsc
On 12/16/2015 10:29 AM, Rob Herring wrote:
On Mon, Dec 14, 2015 at 5:19 PM, Andrew F. Davis wrote:
On 12/14/2015 04:36 PM, Rob Herring wrote:
On Mon, Dec 14, 2015 at 10:41 AM, Andrew F. Davis wrote:
On 12/11/2015 03:48 PM, Linus Walleij wrote:
On Fri, Dec 11, 2015 at 8:46 PM, Andrew F.
On Wed, Dec 30, 2015 at 10:57:35PM +0800, Geliang Tang wrote:
> Use to_platform_device() instead of open-coding it.
Please don't send new patches in reply to the middle of other serieses,
it gets confusing working out what the currently propose series is.
Send new patches as new patches.
signatu
On Wed, Dec 30, 2015 at 8:47 AM, Souptick Joarder wrote:
>
> HI Bjorn,
>
> On Thu, Dec 24, 2015 at 2:03 PM, Bjorn Andersson wrote:
> > Make the addr parameter const in SET_IEEE80211_PERM_ADDR() to save
> > clients from having to cast away a const qualifier.
> >
> > Signed-off-by: Bjorn Andersson
On 12/22/2015 03:51 AM, Linus Walleij wrote:
On Tue, Dec 15, 2015 at 12:19 AM, Andrew F. Davis wrote:
[Rob]
I agree the generic version is fine (or find who made the first part
;)). What "pisosr" is is not very obvious though. Having 74165 in the
compatible would make it somewhat more obvious
Unfortunately, when we have an Intuos Draw connected using a USB
connection, wacom's IRQ handler will be called while the lock for the
usbhid driver is held by hid_ctrl. This means when we try to schedule a
new proximity event in wacom_intuos_schedule_prox_event() by calling
hid_hw_request(), we'll
On Thu, Dec 24, 2015 at 08:02:39AM +0100, Andrzej Hajda wrote:
> Field usrcnt is unsigned so it cannot be lesser than zero.
> The patch fixes the check, moves it to the beginning of the function
> and changes return value to -EIO in case of usercnt error.
Please don't send new patches in reply to
On Wed, Dec 30, 2015 at 01:28:36AM -0500, Sanidhya Solanki wrote:
> The patch adds the xor function after the P stripe
> has failed, without bad data or the Q stripe.
That's just the comment copied, the changelog does not explain why it's
ok to do just the run_xor there. It does not seem trivial t
On Tue, Dec 22, 2015 at 04:11:47PM +0100, Linus Walleij wrote:
> On Tue, Dec 22, 2015 at 2:46 PM, Daniel Kurtz wrote:
> > Move pinctrl initialization earlier in boot so that real devices can find
> > their pctldev without probe deferring.
> (...)
> > -module_init(mtk_pinctrl_init);
> > +arch_init
On 12/22/2015 11:37 AM, Jonathan Cameron wrote:
On 14/12/15 22:35, Andrew F. Davis wrote:
Add driver for the TI AFE4404 heart rate monitor and pulse oximeter.
This device detects reflected LED light fluctuations and presents an ADC
value to the user space for further signal processing.
Datashee
On Wed, 23 Dec 2015, Jiang Liu wrote:
> static void clear_irq_vector(int irq, struct apic_chip_data *data)
> {
> - struct irq_desc *desc;
> + struct irq_desc *desc = irq_to_desc(irq);
> int cpu, vector = data->cfg.vector;
>
> BUG_ON(!vector);
> @@ -236,10 +235,6 @@ static vo
On Wed, Dec 23, 2015 at 09:41:54PM +0100, Arnd Bergmann wrote:
> On Wednesday 23 December 2015, Catalin Marinas wrote:
> > > That means we have to set ARCH_PACK_STATFS64 in the arm64 header files
> > > though, and propagate the OABI alignment to arm64/ilp32 as well, rather
> > > than using the 88-b
Commit-ID: 1fd9a71076ccbcf731cf02408122600a6f2b5d17
Gitweb: http://git.kernel.org/tip/1fd9a71076ccbcf731cf02408122600a6f2b5d17
Author: Geliang Tang
AuthorDate: Wed, 30 Dec 2015 22:16:37 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 30 Dec 2015 18:29:02 +0100
irqchip/zevio: Use irq_
On 12/22/2015 11:59 AM, Jonathan Cameron wrote:
On 14/12/15 22:36, Andrew F. Davis wrote:
Add driver for the TI AFE4403 heart rate monitor and pulse oximeter.
This device detects reflected LED light fluctuations and presents an ADC
value to the user space for further signal processing.
Data she
Hi,
On 12/30/2015 07:15 PM, Nicholas Krause wrote:
> This fixes error handling in the function iwl_pcie_enqueue_hcmd
> by checking if all calls to the function wl_pcie_txq_build_tfd
> have failed by returning a error code and if so jump to the goto
> label out from the cleaning up of acquired res
On Wed, Dec 30, 2015 at 03:03:33PM +0800, Aaron Ma wrote:
> On Wed, Dec 30, 2015 at 7:42 AM, Paul E. McKenney
> wrote:
> > On Tue, Dec 29, 2015 at 05:34:38PM +0800, Aaron Ma wrote:
> >> Add paul...@linux.vnet.ibm.com
> >>
> >> On Tue, Dec 29, 2015 at 5:32 PM, Aaron Ma wrote:
> >> > Hi, Paul:
> >>
On 12/23/2015 05:29 PM, Linus Walleij wrote:
On Tue, Dec 15, 2015 at 9:10 PM, Andrew F. Davis wrote:
Add driver for TI TPIC2810 8-Bit LED Driver with I2C Interface.
The TPIC2810 has 8 open-drain outputs that can but used to drive
LEDs and other low-side switched resistive loads.
Signed-off-b
On 30/12/15 11:18, James Liao wrote:
Hi Daniel,
On Wed, 2015-12-30 at 17:01 +0800, Daniel Kurtz wrote:
On Wed, Dec 30, 2015 at 2:41 PM, James Liao wrote:
From: Shunli Wang
Add scpsys driver for MT2701 and MT7623.
Signed-off-by: Shunli Wang
Signed-off-by: James Liao
---
drivers/soc/m
I find it a little bit irritating when I receive a patch directly
addressed to me to review, but I don't see the "00/34" cover letter.
I want to see what this series is about, and what the motiviation
for this change is.
I'm also highly frustrated, in general, with mix-and-match CC: lists
for pa
On Fri, Dec 18, 2015 at 04:59:38PM +0800, lixi...@cmss.chinamobile.com wrote:
> > I think we'll need to continue supporting non power of two strides so
> > an unconditional conversion to shifts might be an issue - some weird DSP
> > probably does that.
> Yes, agreed.
> IMO this won't happen to
On 12/29/2015 08:00 PM, Eric Wheeler wrote:
Hi Jens and Kent,
This affects many users, so please take a look when you have a moment:
There is a growing bcache user community with a well-tested patchset that
is necessary for production bcache use. The diffstat is small and we all
want someone t
On 22/12/15 08:51, Henry Chen wrote:
Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout,
because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It
just return error when issue happened, so the state machine will stay on
FSM_VLDCLR state when data send bac
Hi Chao,
On Wed, Dec 30, 2015 at 02:47:29PM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Wednesday, December 30, 2015 9:14 AM
> > To: Chao Yu
> > Cc: linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kerne
On 18/12/15 15:17, Daniel Lezcano wrote:
From: Alexey Klimov
1) Change pr_warn()s to pr_err()s. These messages are actually errors and not
warnings.
2) Add missing \n.
3) Error message for kzalloc() failure is removed per suggestion by Joe Perches.
There is generic stack_dump() for al
On 18/12/15 15:17, Daniel Lezcano wrote:
Increase the compilation test coverage by adding the COMPILE_TEST option.
Signed-off-by: Daniel Lezcano
---
Acked-by: Matthias Brugger
drivers/clocksource/Kconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/cl
Hi Linus,
Basically three amazing fixes in this pull request, split into 4
patches. Believe me, they should go into 4.4. Two of them fix a
regression, the third and last fixes an easy-to-trigger bug.
- Fix a bad irq enable through null_blk, for queue_mode=1 and using
timer completions. Add a bl
Felipe,
On Tue, 29 Dec 2015, Felipe Balbi wrote:
> Anyway, the interesting part is that PRUSS has 64 events (on current
> incarnations at least) and PRUSS has 10 physical IRQ lines to the ARM
> land. Each of these 64 events can be routed to any of these 10 IRQ
> lines. This might not be very usefu
Commit-ID: dd7a5ab495019d424c2b0747892eb2e38a052ba5
Gitweb: http://git.kernel.org/tip/dd7a5ab495019d424c2b0747892eb2e38a052ba5
Author: Daniel J Blueman
AuthorDate: Thu, 31 Dec 2015 02:06:47 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 30 Dec 2015 19:19:03 +0100
x86/numachip: Fix N
On 2015-12-30 03:39, ebied...@xmission.com wrote:
Pablo Neira Ayuso writes:
On Mon, Dec 28, 2015 at 09:05:03PM +0100, Sander Eikelenboom wrote:
Hi,
Running a 4.4.0-rc6 kernel i encountered the warning below.
Cc'ing Eric Biederman.
@Sander, could you provide a way to reproduce this?
I am
On Wed, Dec 30, 2015 at 10:35 PM, Bjorn Andersson wrote:
> On Wed, Dec 30, 2015 at 8:47 AM, Souptick Joarder
> wrote:
>>
>> HI Bjorn,
>>
>> On Thu, Dec 24, 2015 at 2:03 PM, Bjorn Andersson wrote:
>> > Make the addr parameter const in SET_IEEE80211_PERM_ADDR() to save
>> > clients from having to
Signed-off-by: Andrew F. Davis
---
MAINTAINERS | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 44666b1..046d001 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7605,10 +7605,8 @@ NOKIA N900 POWER SUPPLY DRIVERS
M: Pali Rohár
S:
Le mercredi 30 décembre 2015 à 16:33 +, Mark Brown a écrit :
> On Wed, Dec 30, 2015 at 09:35:21AM +0100, Paul Kocialkowski wrote:
>
> > In my opinion, it would be more elegant to adapt the core regulator
> > framework to first enable the GPIO and then call the regulator enable
> > ops callback
The MMCFG PCI accessors weren't being setup for NumacConnect2
correctly due to over-early assignment; this would create the
potential for the wrong PCI domain to be accessed.
Fix this by using the correct arch-specific PCI init function.
Signed-off-by: Daniel J Blueman
Acked-by: Steffen Persvold
Hi Thomas,
Thomas Gleixner writes:
> On Tue, 29 Dec 2015, Felipe Balbi wrote:
>> Anyway, the interesting part is that PRUSS has 64 events (on current
>> incarnations at least) and PRUSS has 10 physical IRQ lines to the ARM
>> land. Each of these 64 events can be routed to any of these 10 IRQ
>>
On Wed, 23 Dec 2015, Jiang Liu wrote:
> @@ -167,11 +170,13 @@ next:
>
> if (test_bit(vector, used_vectors))
> goto next;
> -
> for_each_cpu_and(new_cpu, vector_cpumask, cpu_online_mask) {
> if (!IS_ERR_OR_NULL(per_cpu(vector_
Patch 1:
The main improvement is the refactor of the state machine MIDI parser.
It is better to read and handles states properly, even weird ones.
Patch 3:
Fix a race condition.
Patches 3-4:
Miscelaneous fixes.
Felipe F. Tonello (4):
usb: gadget: f_midi: refactor state machine
usb: g
This refactor results in a cleaner state machine code and as a result fixed a
bug when packaging a MIDI-USB packet right after a non-conformant MIDI byte
stream.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 204 ++-
1 file changed,
Since f_midi_transmit is called by both ALSA and USB frameworks, it can
potentially cause a race condition between both calls. This is bad because the
way f_midi_transmit is implemented can't handle concurrent calls. This is due
to the fact that the usb request fifo looks for the next element and o
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/drivers/usb/gadget/function/f_midi.c
index bbff20697f76..b7d3f5a10bf0 100644
--- a/drivers/usb/gadget/function/f_midi.c
+++ b/driv
This ensures that at any point on the function if a goto to setup_fail is
made, it will unlock the mutex.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/driver
On 12/30/2015 8:28 AM, Andy Shevchenko wrote:
> Yep, I meant not to use an additional variable.
>
>> > BTW, I suggest you spend some time around checkpatch for contributions. I
>> > could
>> > have caught most of the issues you are generally concerned before
>> > submitting a patch.
> Is it a qu
Hi,
This patch series aims at providing a common logic to check for bitflips
in erased pages.
Currently each driver is implementing its own logic to check for bitflips
in erased pages. Not only this create code duplication, but most of these
implementations are incorrect.
Here are a few aspects t
The error code returned by the ecc.correct() are not consistent over the
all implementations.
Document the expected behavior in include/linux/mtd/nand.h and fix
offending implementations.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/atmel_nand.c | 2 +-
drivers/mtd/nand/bf5xx_nand.c
The default NAND read functions are relying on the underlying controller
driver to correct bitflips, but some of those controllers cannot properly
fix bitflips in erased pages.
Check for bitflips in erased pages in default core functions if the driver
delegated the this check by setting the NAND_EC
The diskonchip drivers is manually checking for 'erased pages' while
correcting ECC bytes.
This logic can now done by the core infrastructure, and can thus be removed
from this drivers.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/diskonchip.c | 37 ++---
1
The jz4740 drivers is manually checking for 'erased pages' while
correcting ECC bytes.
This logic can now done by the core infrastructure, and can thus be removed
from this drivers.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/jz4740_nand.c | 18 --
1 file changed, 18 dele
Reposting without XXX in subject: vger does not like them :(
This is really trying to cleanup some virt code, as suggested by Peter, who
said
> You could of course go fix that instead of mutilating things into
> sort-of functional state.
This work is needed for virtio, so it's probably easiest to
The davinci drivers is manually checking for 'erased pages' while
correcting ECC bytes.
This logic can now done by the core infrastructure, and can thus be removed
from this drivers.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/davinci_nand.c | 9 +
1 file changed, 1 insertion(+),
On !SMP, most architectures define their
barriers as compiler barriers.
On SMP, most need an actual barrier.
Make it possible to remove the code duplication for
!SMP by defining a low-level __smp_XXX barriers
which do not depend on the value of SMP, then
use them from asm-generic conditionally.
B
Since Real Time Clock (RTC) configuration options were first enabled in the
arm64 defconfig (commit 2d39ad6 "arm64: defconfig: update defconfig for
3.18"), QEMU's device tree based virt machine has grown to include a PL031
RTC. Update the defconfig accordingly.
Signed-off-by: Christopher Covington
This defines __smp_XXX barriers for powerpc
for use by virtualization.
smp_XXX barriers are removed as they are
defined correctly by asm-generic/barriers.h
This reduces the amount of arch-specific boiler-plate code.
Signed-off-by: Michael S. Tsirkin
---
arch/powerpc/include/asm/barrier.h | 24
The diskonchip drivers is manually checking for 'erased pages' while
correcting ECC bytes.
This logic can now done by the core infrastructure, and can thus be removed
from this drivers.
Signed-off-by: Boris Brezillon
---
Changes since v4:
- add missing NAND_ECC_GENERIC_ERASED_CHECK flag
drivers
Hello,
On Wed, Dec 30, 2015 at 09:34:40AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Wednesday, December 30, 2015 8:05 AM
> > To: Chao Yu
> > Cc: linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel.
The jz4740 drivers is manually checking for 'erased pages' while
correcting ECC bytes.
This logic can now done by the core infrastructure, and can thus be removed
from this drivers.
Signed-off-by: Boris Brezillon
---
Changes since v4:
- add missing NAND_ECC_GENERIC_ERASED_CHECK flag
drivers/mtd
On Wed, Dec 30, 2015 at 11:35:20PM +0800, Chao Yu wrote:
> On 12/30/15 9:34 AM, Chao Yu wrote:
> > Hi Jaegeuk,
> >
> >> -Original Message-
> >> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> >> Sent: Wednesday, December 30, 2015 8:05 AM
> >> To: Chao Yu
> >> Cc: linux-f2fs-de...@lists.sou
Felipe,
On Wed, 30 Dec 2015, Felipe Balbi wrote:
> Thomas Gleixner writes:
> > - Is there a "mapping" block between PRUSS and the host interrupt
> > controller
> >or is this "mapping" block part of PRUSS?
>
> The description in TRM is a bit "poor", but from what I can gather, the
> mapping
On Wed, Dec 30, 2015 at 9:17 PM, Sinan Kaya wrote:
> On 12/30/2015 8:28 AM, Andy Shevchenko wrote:
>> Yep, I meant not to use an additional variable.
>>
>>> > BTW, I suggest you spend some time around checkpatch for contributions. I
>>> > could
>>> > have caught most of the issues you are general
On Wed, Dec 30, 2015 at 12:56:03PM -0500, David Miller wrote:
>
> I find it a little bit irritating when I receive a patch directly
> addressed to me to review, but I don't see the "00/34" cover letter.
>
> I want to see what this series is about, and what the motiviation
> for this change is.
>
On Wed, Dec 30, 2015 at 10:30 AM, Souptick Joarder wrote:
> On Wed, Dec 30, 2015 at 10:35 PM, Bjorn Andersson wrote:
>> On Wed, Dec 30, 2015 at 8:47 AM, Souptick Joarder
>> wrote:
>>>
>>> HI Bjorn,
>>>
>>> On Thu, Dec 24, 2015 at 2:03 PM, Bjorn Andersson wrote:
>>> > Make the addr parameter co
Hi,
Thomas Gleixner writes:
> Felipe,
>
> On Wed, 30 Dec 2015, Felipe Balbi wrote:
>> Thomas Gleixner writes:
>> > - Is there a "mapping" block between PRUSS and the host interrupt
>> > controller
>> >or is this "mapping" block part of PRUSS?
>>
>> The description in TRM is a bit "poor",
At the moment, xchg on sh only supports 4 and 1 byte values, so using it
from smp_store_mb means attempts to store a 2 byte value using this
macro fail.
And happens to be exactly what virtio drivers want to do.
Check size and fall back to a slower, but safe, WRITE_ONCE+smp_mb.
Signed-off-by: Mic
On Wed, Dec 30, 2015 at 02:44:21PM +0100, Arnd Bergmann wrote:
> On Wednesday 30 December 2015 15:24:47 Michael S. Tsirkin wrote:
> > asm-generic variant of smp_store_mb() calls mb() which is stronger
> > than implied by both the name and the documentation.
> >
> > smp_store_mb is only used by cor
On Wed, Dec 30, 2015 at 12:02 AM, Bob Liu wrote:
> Hi Ross,
>
> On 12/24/2015 03:39 AM, Ross Zwisler wrote:
>> Add support for tracking dirty DAX entries in the struct address_space
>> radix tree. This tree is already used for dirty page writeback, and it
>> already supports the use of exceptiona
Hello,
The following program leads to a leak of two sock objects:
// autogenerated by syzkaller (http://github.com/google/syzkaller)
#include
#include
#include
#include
#include
int fd;
void *thr(void *arg)
{
memcpy((void*)0x2000bbbe,
"\x0a\x00\x33\xdc\x14\x4d\x5b\xd1\x00\x00\x00\x
From: "Michael S. Tsirkin"
Date: Wed, 30 Dec 2015 14:58:19 +0200
> -. Patch 1 documents the __smp APIs, and explains why they are
>useful for virt
If virt is doing things like interacting with descriptors that are
shared with a (potentially SMP) host, why don't we just annotate those
specifi
From: "Michael S. Tsirkin"
Date: Wed, 30 Dec 2015 21:55:33 +0200
> The problem I had in the past is that vger rejects email with
> too many CC addresses.
I can't think of a patch set where a > 1024 character CC: list is
legitimate anyways, even if all interested parties are included.
> I'll loo
On Wed, Dec 30, 2015 at 09:42:27PM +0100, Dmitry Vyukov wrote:
> Hello,
>
> The following program leads to a leak of two sock objects:
Damn, Dmitry ;-)
If no one takes care of it by then, I'll look into it next week, thanks.
Marcelo
--
To unsubscribe from this list: send the line "unsubscribe
1 - 100 of 334 matches
Mail list logo
