On 09.08.2013 13:44, ext Mark Brown wrote:
> On Fri, Aug 09, 2013 at 12:09:11PM +0200, Ionut Nicu wrote:
>> As opposed to the other regmap cache implementations,
>> regcache_flat didn't use the cache_present bitmap for
>> figuring out whether a register was cached or not, nor
>> did it mark a
On 08/09, Frederic Weisbecker wrote:
>
> On Thu, Aug 08, 2013 at 08:15:21PM +0200, Oleg Nesterov wrote:
> > But probably we should move "attr.bp_len == HW_BREAKPOINT_LEN_1" check
> > from arch_build_bp_info() to its caller, arch_validate_hwbkpt_settings().
> >
> > Because:
> >
> > > But this
On Fri, Aug 9, 2013 at 12:15 PM, Tom Cooksey wrote:
>
>> > Turning to DRM/KMS, it seems the supported formats of a plane can be
>> > queried using drm_mode_get_plane. However, there doesn't seem to be a
>> > way to query the supported formats of a crtc? If display HW only
>> > supports scanning
Am 09.08.2013 19:02, schrieb David Herrmann:
I hope that explains how all this works. I can look over your patch on
Sunday if still necessary.
Thanks a lot for the explanation. Actually I don't have a problem but
Andrew Morton asked me some questions I can't answer without looking in
to you and will get this change out of this
>>> commit.
>>
>> The two commits look like this now attached too in case you want
>> to test:
>
> I'd be happy to test, but those changes cause build failures on top of
> next-20130809. Which other patches do I need to a
On 08/09/2013 10:46 AM, Alexander Gordeev wrote:
> On Fri, Aug 09, 2013 at 09:52:19AM -0600, Jens Axboe wrote:
>> On 08/09/2013 09:07 AM, Alexander Gordeev wrote:
>>> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
>>> index dcbc2a4..b131a48 100644
>>> --- a/block/blk-mq-tag.c
>>> +++
Hi Alexander
On Fri, Aug 9, 2013 at 6:33 PM, Alexander Holler wrote:
> Am 09.08.2013 18:21, schrieb Alexander Holler:
>
>> I've now also verified if hid-sensor-hub receives an event with
>> sensor_hub_raw_event() in the error-path (hid_device_io_stop() called
>> and probe() failed), and this
Hallo.
Sie sind auf der Suche nach Finanzierung, um Ihre Aktivitäten, die
Durchführung eines Projekts oder aus anderen Gründen wieder zu beleben.
Ich gewährt Darlehen von 3000 bis hin zu 4.000.000 mit einer Rate von 3
%.
Für weitere Informationen kontaktieren Sie mich:
On 08/08/13 23:15, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130808:
>
> *crickets*
>
>
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
Adding support for handling ECC error decoding for new F15 models.
On newer models, support has been included for upto 4 DCT's, however,
only DCT0 and DCT3 are currently configured. (Refer BKDG Section 2.10)
Routing DRAM Requests algorithm is different for F15h M30h.
It is cleaner to use a brand
On 8/9/2013 8:18 AM, Borislav Petkov wrote:
}
@@ -205,8 +209,9 @@ static int amd64_set_scrub_rate(struct mem_ctl_info *mci, u32 bw)
if (boot_cpu_data.x86 == 0xf)
min_scrubrate = 0x0;
- /* F15h Erratum #505 */
- if (boot_cpu_data.x86 == 0x15)
+
At Fri, 9 Aug 2013 17:39:47 +0100,
Mark Brown wrote:
>
> On Fri, Aug 09, 2013 at 03:52:04PM +0200, Takashi Iwai wrote:
>
> > Above all, the multiple indices don't work anyway with the snd_jack
> > stuff in the current form. The index was introduced only for kjack,
> > and for HD-audio, snd_jack
Fabio,
Thanks for your review.
On Fri, Aug 9, 2013 at 9:41 AM, Fabio Estevam wrote:
> On Fri, Aug 9, 2013 at 1:33 PM, Doug Anderson wrote:
>
>> +#else
>> +#define dw_mci_exynos_suspend NULL
>> +#define dw_mci_exynos_resume NULL
>> +#define dw_mci_exynos_resume_noirq NULL
On Fri, Aug 09, 2013 at 09:52:19AM -0600, Jens Axboe wrote:
> On 08/09/2013 09:07 AM, Alexander Gordeev wrote:
> > diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
> > index dcbc2a4..b131a48 100644
> > --- a/block/blk-mq-tag.c
> > +++ b/block/blk-mq-tag.c
> > @@ -468,10 +468,9 @@ struct
On Thu, Aug 08, 2013 at 08:15:21PM +0200, Oleg Nesterov wrote:
> On 08/08, Frederic Weisbecker wrote:
> >
> > I'm all for fixing this. May be we can start by backporting a patch that
> > ignores the value of gen_len for instruction breakpoints in x86?
>
> Or perhaps we can start with the
On 08/09/13 07:59, Jason Cooper wrote:
> Randy,
>
> On Thu, Aug 08, 2013 at 01:03:04PM -0700, Randy Dunlap wrote:
>> On 08/08/13 00:08, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20130807:
>>>
>>
>> on i386 and x86_64:
>> when CONFIG_PCI_MSI is not enabled:
>>
>> There are many of
On 07/30/2013 08:57 AM, Shuah Khan wrote:
> Add tracing feature to iommu to report various iommu events. Classes
> iommu_group, iommu_device, iommu_map_unmap, and iommu_amd_event are defined.
>
> iommu_group class events can be enabled to trigger when devices get added
> to and removed from an
On Fri, Aug 9, 2013 at 1:33 PM, Doug Anderson wrote:
> +#else
> +#define dw_mci_exynos_suspend NULL
> +#define dw_mci_exynos_resume NULL
> +#define dw_mci_exynos_resume_noirq NULL
> +#endif /* CONFIG_PM_SLEEP */
You could avoid this else block if you use 'static
On Sat, Aug 10, 2013 at 12:25:58AM +0800, Axel Lin wrote:
> -MODULE_AUTHOR("S Twiss ");
> +MODULE_AUTHOR("Steve Twiss ");
It's perfectly reasonable for someone to want to be referred to by their
initial, or their full spelled out name, or a nickname, or...
signature.asc
Description: Digital
Hi Linus,
The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:
Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.11-4
for you to fetch changes up to
On Fri, Aug 09, 2013 at 03:52:04PM +0200, Takashi Iwai wrote:
> Above all, the multiple indices don't work anyway with the snd_jack
> stuff in the current form. The index was introduced only for kjack,
> and for HD-audio, snd_jack is provided just for a compatibility
> reason, thus it doesn't
The dw_mmc driver keeps a cache of the current slot->clock in order to
avoid doing a whole lot of work every time set_ios() is called.
However, after suspend/resume the register values are bogus so we need
to ensure that the cached value is invalidated.
Specifically I saw problems with the SD
If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
looping around forever. This has been seen to happen on exynos5420
silicon despite the fact that we haven't enabled any wakeup events due
to a silicon errata. It is safe to do on all exynos variants.
Signed-off-by: Doug
The TMOUT register is initted to 0x at probe time but isn't
initted after suspend/resume. Add an init of this value.
No problems were observed without this (it will also get initted in
__dw_mci_start_request if there is data to send), but it makes the
register dump before and after
On 08/09/2013 12:10 AM, Wei Ni wrote:
> On 08/09/2013 01:37 AM, Stephen Warren wrote:
>> On 08/08/2013 12:56 AM, Wei Ni wrote:
>>> Add OF document for lm90 in Documentation/devicetree/.
>>
>>> diff --git a/Documentation/devicetree/bindings/hwmon/lm90.txt
>>>
Pantelis Antoniou writes:
> Hi
> On Aug 9, 2013, at 6:16 PM, Kevin Hilman wrote:
>
>> Pantelis Antoniou writes:
>>
>>> Hi Kevin,
>>>
>>> On Aug 7, 2013, at 9:45 PM, Kevin Hilman wrote:
>>>
[fixing address for Benoit]
Pantelis Antoniou writes:
> omap_device relies
Am 09.08.2013 18:21, schrieb Alexander Holler:
I've now also verified if hid-sensor-hub receives an event with
sensor_hub_raw_event() in the error-path (hid_device_io_stop() called
and probe() failed), and this still *does* happen. That event (input
report) doesn't come through hid-sensor-hub to
This series of patches addresses some suspend/resume problems with
dw_mmc on exynos platforms, espeically exynos5420. Since
suspend/resume is not fully working on ToT Linux (v3.11-rc4) on
exynos5250-snow, this series was tested against the current ToT
ChromeOS 3.8 tree. I have confirmed basic
After suspend/resume all of the dw_mmc registers are reset to
defaults. We restore most of them, but specifically don't setup the
clock registers after resume unless we've got a powered card. Things
still work because the core will eventually call set_ios() and we'll
set things up.
There
Hello,
On Thu, Aug 08, 2013 at 06:16:12PM +0800, Tang Chen wrote:
> In previous parts' patches, we have obtained SRAT earlier enough, right after
> memblock is ready. So this patch-set does the following things:
Can you please set up a git branch with all patches?
Thanks.
--
tejun
--
To
Hello, Chris.
On Fri, Aug 09, 2013 at 12:12:43PM -0400, Chris Metcalf wrote:
> I could certainly make schedule_on_cpu_mask() do sanity checking,
> perhaps via a WARN_ON_ONCE() if offline cpus were specified, and
> otherwise just have it create a local struct cpumask that it and's
> with
On Fri, Aug 09, 2013 at 04:40:32PM +0100, Kumar Gala wrote:
> The binding spec wasn't clear that the order of the phandles in the
> usb-phy array has meaning. Clarify this point in the binding that
> it should be .
>
> Signed-off-by: Kumar Gala
> ---
>
On 08/09, Oleg Nesterov wrote:
>
> Steven, Jovi, what should we do with that patch? It seems that it
> was forgotten.
>
> I can take these patches into my ubprobes branch
I meant that patch from Jovi, sorry for confusion.
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe
The modalias is set by the MODULE_DEVICE_TABLE, thus remove redundant
MODULE_ALIAS. Also Fix trivial typo for the author name.
Signed-off-by: Axel Lin
---
drivers/regulator/da9210-regulator.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Sorry, I didn't read this series yet. Not that I think this needs my
help, but I'll try to do this a later...
On 08/09, Masami Hiramatsu wrote:
>
> I just concern using kmalloc() in the event handler.
GFP_KERNEL should be fine for uprobe handler.
However, iirc this conflicts with the patches
On Thu, Aug 8, 2013 at 9:46 AM, David Howells wrote:
> Nico Williams wrote:
>
>> b) how to create tmpfs locations in which to store credentials (which
>> can be unbounded in size, so storing them in the kernel is silly;
>
> Ummm... tmpfs stores them in the kernel too - though it can page them
Fix is already merged:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=adfb8e51332153016857194b85309150ac560286
> -Original Message-
> From: Andi Kleen [mailto:a...@firstfloor.org]
> Sent: Friday, August 09, 2013 11:58 AM
> To: linux-kernel@vger.kernel.org
> Cc:
Am 09.08.2013 13:12, schrieb Jiri Kosina:
On Fri, 9 Aug 2013, Alexander Holler wrote:
=
[ INFO: inconsistent lock state ]
3.10.5-dockstar-00038-g03242d1-dirty #408 Not tainted
-
inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W}
On Fri, Jul 26, 2013 at 04:19:23PM -0700, Paul E. McKenney wrote:
> diff --git a/kernel/rcutree_plugin.h b/kernel/rcutree_plugin.h
> index 3edae39..ff84bed 100644
> --- a/kernel/rcutree_plugin.h
> +++ b/kernel/rcutree_plugin.h
> @@ -28,7 +28,7 @@
> #include
> #include
> #include
> -#include
commits look like this now attached too in case you want
> to test:
I'd be happy to test, but those changes cause build failures on top of
next-20130809. Which other patches do I need to apply first?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
On Fri, 9 Aug 2013, Rasmus Villemoes wrote:
> This semantic patch replaces "return {0,1};" with "return
> {false,true};" in functions returning bool. There doesn't seem to be
> any false positives, but some whitespace mangling is happening, for
> example:
When you change the argument to
This semantic patch replaces "return {0,1};" with "return
{false,true};" in functions returning bool. There doesn't seem to be
any false positives, but some whitespace mangling is happening, for
example:
diff -u -p a/block/blk-throttle.c b/block/blk-throttle.c
--- a/block/blk-throttle.c
+++
Hello, Mark.
On Fri, Aug 9, 2013 at 12:12 PM, Mark Langsdorf
wrote:
> I'll update the description when I resubmit it to give you more detail on
> the impact.
Yes, please give me some hints on to which branch the patches are
targeted and whether stable should be cc'd. I can't really tell just
On 8/9/2013 11:02 AM, Tejun Heo wrote:
> Hello, Chris.
>
> On Wed, Aug 07, 2013 at 04:49:44PM -0400, Chris Metcalf wrote:
>> This primitive allows scheduling work to run on a particular set of
>> cpus described by a "struct cpumask". This can be useful, for example,
>> if you have a per-cpu
On Fri, 2013-08-09 at 11:35 -0400, Vivek Goyal wrote:
> Also what about all the other patches you had for secureboot where you
> closed down all the paths where root could write to kernel memory. So
> if you want to protect sig_enforce boolean, then you need to close down
> all these paths
On 08/09/2013 11:10 AM, Tejun Heo wrote:
On Wed, Aug 07, 2013 at 10:52:36AM -0500, Mark Langsdorf wrote:
The Calxeda sata_highbank driver has been adding its descriptions to the
ahci driver. Separate them properly.
Signed-off-by: Mark Langsdorf
Acked-by: Rob Herring
Will wait for the
On Fri, Aug 09, 2013 at 12:10:15PM -0400, Tejun Heo wrote:
> Will wait for the update. I suppose this doesn't need to go in to
> for-3.11-fixes? I'd really appreciate what impact each patch has.
^
descriptions of
--
tejun
On Wed, Aug 07, 2013 at 10:52:36AM -0500, Mark Langsdorf wrote:
> The Calxeda sata_highbank driver has been adding its descriptions to the
> ahci driver. Separate them properly.
>
> Signed-off-by: Mark Langsdorf
> Acked-by: Rob Herring
Will wait for the update. I suppose this doesn't need to
Hi,
On Fri, 2013-08-09 at 16:23 +0300, Felipe Balbi wrote:
> Hi,
>
> On Tue, Aug 06, 2013 at 02:53:11PM +0300, Ivan T. Ivanov wrote:
> > diff --git a/drivers/usb/dwc3/dwc3-msm.c b/drivers/usb/dwc3/dwc3-msm.c
> > new file mode 100644
> > index 000..e509abc
> > --- /dev/null
> > +++
On Wed, Aug 07, 2013 at 10:52:35AM -0500, Mark Langsdorf wrote:
> From: Rob Herring
>
> Signed-off-by: Rob Herring
> Signed-off-by: Mark Langsdorf
Applied to libata/for-3.12.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Wed, Aug 07, 2013 at 10:52:34AM -0500, Mark Langsdorf wrote:
> The ACTIVITY and ERROR signals were reversed in the original commit.
> Fix that so that hard drive activity does not show up on the error
> light, and attempts to indicate that the hard drive is failing do
> not show up as hard
From: Andi Kleen
Add support for padding the variable length tables in kallsyms.
This adds a new --pad=XXX option to kallsyms to specify the table lengths,
and another option --pad-file=X to write the table lengths to a file.
Then when a table is shorter than the padding add the necessary
From: Andi Kleen
Remove the ELF relocations from the kallsyms_address[] table.
Instead we just store offsets to _text and relocate that while
accessing the kallsyms table. This is done with a new
kallsyms_offsets[] table. With these changes .tmp_kallsyms*.o
becomes relocation free.
This allows
This is my attempt to avoid extra link steps for kallsyms.
Originally for LTO (where it gives dramatic build time improvements),
but it also gives a nice build speedup on a standard build (-10s on my laptop)
Even with this we still link two times (one more for modpost), but this
may be
From: Andi Kleen
kallsyms currenly links the kernel upto three times
(in addition to another one for modpost checks)
Linking can be a quite slow operation, especially when
the kernel has a lot of debug information (lots of IO),
or Link Time Optimization is used.
Final linking is also a non
This is what I observe:
On the first connect, the musb starts with DEVCTL.Session set. On
disconnect, musb_core calls try_idle. That functions removes the Session
bit signalize that the session is over (something that only in OTG is
required). A new device, that is plugged, is no longer
On Fri, Aug 09, 2013 at 11:32:42AM +0100, Srinivas KANDAGATLA wrote:
> On 08/08/13 18:11, Sören Brinkmann wrote:
> > Hi Daniel,
> >
> > On Thu, Aug 01, 2013 at 07:48:04PM +0200, Daniel Lezcano wrote:
> >> On 08/01/2013 07:43 PM, Sören Brinkmann wrote:
> >>> On Thu, Aug 01, 2013 at 07:29:12PM
On Fri, Aug 09, 2013 at 03:36:16PM +0200, Rafael J. Wysocki wrote:
> > No, it doesn't. And this patch-set can be merged first.
>
> OK, so if nobody objects, I can take patches [1,3-4/4], but I don't think I'm
> the right maintainer to handle [2/4].
Given the dependencies, we'll probably need
From: Andi Kleen
This fixes my 32bit build which failed with:
drivers/built-in.o: In function
`si_calculate_leakage_for_v_and_t_formula':
/home/ak/lsrc/git/linux-2.6/drivers/gpu/drm/radeon/si_dpm.c:1770:
undefined reference to `__divdi3'
Cc: airl...@linux.ie
Cc: alexander.deuc...@amd.com
On 08/09/2013 09:07 AM, Alexander Gordeev wrote:
> On Fri, Aug 09, 2013 at 08:24:38AM -0600, Jens Axboe wrote:
>> On 08/09/2013 02:23 AM, Alexander Gordeev wrote:
>>> + ap->qc_tags = blk_mq_init_tags(ATA_MAX_QUEUE, 1, NUMA_NO_NODE);
>>> + if (!ap->qc_tags) {
>>> + kfree(ap);
>>> +
Hi,
On Thu, Aug 8, 2013 at 8:18 PM, Seungwon Jeon wrote:
> On Fri, August 09, 2013, Chris Ball wrote:
>> On Fri, Aug 09 2013, Olof Johansson wrote:
>> > On Thu, Aug 8, 2013 at 5:16 PM, Doug Anderson wrote:
>> >
>> >> I guess my overall question is: if there are no actual implementations
>> >>
On Fri, Aug 09, 2013 at 11:36:06AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Aug 05, 2013 at 05:30:53PM +0100, Stefano Stabellini wrote:
> > XENMEM_exchange can't be used by autotranslate guests because of two
> > severe limitations:
> >
> > - it does not copy back the mfns into the out field
A typo was introduced when merging the "security-fixes" branch which made the
comparison an assignment.
Signed-off-by: Tobias Mueller
---
In the previous version I forgot the Signed-off-by header
---
arch/arm/kernel/process.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
n Mon, Aug 05, 2013 at 05:30:55PM +0100, Stefano Stabellini wrote:
> Support autotranslate guests in swiotlb-xen by keeping track of the
> phys-to-bus and bus-to-phys mappings of the swiotlb buffer
> (xen_io_tlb_start-xen_io_tlb_end).
>
> Use a simple direct access on a pre-allocated array for
On Fri, Jul 26, 2013 at 04:19:21PM -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> This commit adds control variables and states for full-system idle.
> The system will progress through the states in numerical order when
> the system is fully idle (other than the timekeeping CPU),
Seungwon,
On Fri, Aug 9, 2013 at 6:35 AM, Seungwon Jeon wrote:
> On Wed, August 07, 2013, Doug Anderson wrote:
>> After suspend/resume all of the dw_mmc registers are reset to
>> defaults. We restore most of them, but specifically don't setup the
>> clock registers after resume unless we've got
On Aug 9, 2013, at 10:47 AM, Laxman Dewangan wrote:
> Renaming the charging property names to have more meaningful:
>
> Renaming property "ti,back-battery-charge-enable" to
> "ti,backup-battery-chargeable"
> to tells OS that attahced battery is chargeable and OS can do charging.
>
> Renaming
The binding spec wasn't clear that the order of the phandles in the
usb-phy array has meaning. Clarify this point in the binding that
it should be .
Signed-off-by: Kumar Gala
---
Documentation/devicetree/bindings/usb/dwc3.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
On Mon, Aug 05, 2013 at 05:30:56PM +0100, Stefano Stabellini wrote:
> Xen on arm and arm64 needs SWIOTLB_XEN: when running on Xen we need to
> program the hardware with mfns rather than pfns for dma addresses.
> Remove SWIOTLB_XEN dependency on X86 and PCI and make XEN select
> SWIOTLB_XEN on arm
On Friday 09 August 2013 09:07 PM, Kumar Gala wrote:
On Aug 9, 2013, at 10:47 AM, Laxman Dewangan wrote:
Renaming the charging property names to have more meaningful:
Renaming property "ti,back-battery-charge-enable" to
"ti,backup-battery-chargeable"
to tells OS that attahced battery is
On 08/09/2013 08:32 AM, James Bottomley wrote:
> On Fri, 2013-08-09 at 08:23 -0700, H. Peter Anvin wrote:
>> I would like to change the defaults for CONFIG_EFI and CONFIG_EFI_STUB
>> to y. There is little reason to omit this since EFI now is a
>> significant percentage of all systems.
>
> You
On Fri, Jul 26, 2013 at 04:19:20PM -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> This commit adds the code that updates the rcu_dyntick structure's
> new fields to track the per-CPU idle state based on interrupts and
> transitions into and out of the idle loop (NMIs are ignored
On Mon, Aug 05, 2013 at 05:30:50PM +0100, Stefano Stabellini wrote:
> Initially set dma_ops to arm_dma_ops.
Looks OK to me.
>
>
> Signed-off-by: Stefano Stabellini
> CC: will.dea...@arm.com
> CC: li...@arm.linux.org.uk
>
>
> Changes in v3:
> - keep using arm_dma_ops in dmabounce.
> ---
>
On Aug 9, 2013, at 10:47 AM, Laxman Dewangan wrote:
> Renaming the charging property names to have more meaningful:
>
> Renaming property "ti,back-battery-charge-enable" to
> "ti,backup-battery-chargeable"
> to tells OS that attahced battery is chargeable and OS can do charging.
>
> Renaming
And sorry for off-topic email, but I can't resist.
Can't we finally kill block_all_signals() and ->notifier ? This
is very, very wrong and doesn't work anyway.
I tried to ask many, many times. Starting from 2007 at least.
And every time the discussion "hangs". I am quoting the last
email I sent
On Mon, Aug 05, 2013 at 05:30:53PM +0100, Stefano Stabellini wrote:
> XENMEM_exchange can't be used by autotranslate guests because of two
> severe limitations:
>
> - it does not copy back the mfns into the out field for autotranslate
> guests;
>
> - it does not guarantee that the hypervisor
On Fri, Aug 09, 2013 at 03:07:13PM +, Matthew Garrett wrote:
> On Fri, 2013-08-09 at 07:02 -0400, Vivek Goyal wrote:
> > On Fri, Aug 09, 2013 at 03:36:37AM -0400, Matthew Garrett wrote:
> > > kexec permits the loading and execution of arbitrary code in ring 0, which
> > > is something that
This patch adds DMI system IDs for the new Kontron modules COMe-bHL6 and
COMe-cTH6 to the Kontron PLD driver.
Signed-off-by: Michael Brunner
---
drivers/mfd/kempld-core.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/mfd/kempld-core.c
On Fri, 2013-08-09 at 13:52 +0800, Tang Chen wrote:
> On 08/09/2013 12:47 AM, Toshi Kani wrote:
> > add_memory() and remove_memory() can only handle a memory range aligned
> > with section. There are problems when an unaligned range is added and
> > then deleted as follows:
> >
> > -
Renaming the charging property names to have more meaningful:
Renaming property "ti,back-battery-charge-enable" to
"ti,backup-battery-chargeable"
to tells OS that attahced battery is chargeable and OS can do charging.
Renaming property "ti,back-battery-charge-low-current" to
This patch fixes the bit masking within the GPIO driver. The masking is
basically done twice which causes the wrong GPIOs to be addressed.
Signed-off-by: Michael Brunner
---
drivers/gpio/gpio-kempld.c | 24 +---
1 file changed, 9 insertions(+), 15 deletions(-)
diff --git
This patch changes the driver name to be consistent with the name that
is registered as cell name in the MFD driver. Otherwise the driver won't
load.
Signed-off-by: Michael Brunner
---
drivers/gpio/gpio-kempld.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi
On Aug 9, 2013, at 6:16 PM, Kevin Hilman wrote:
> Pantelis Antoniou writes:
>
>> Hi Kevin,
>>
>> On Aug 7, 2013, at 9:45 PM, Kevin Hilman wrote:
>>
>>> [fixing address for Benoit]
>>>
>>> Pantelis Antoniou writes:
>>>
omap_device relies on the platform notifier callbacks managing
On Fri, Aug 09, 2013 at 03:07:13PM +, Matthew Garrett wrote:
> On Fri, 2013-08-09 at 07:02 -0400, Vivek Goyal wrote:
> > On Fri, Aug 09, 2013 at 03:36:37AM -0400, Matthew Garrett wrote:
> > > kexec permits the loading and execution of arbitrary code in ring 0, which
> > > is something that
On Fri, 2013-08-09 at 08:23 -0700, H. Peter Anvin wrote:
> I would like to change the defaults for CONFIG_EFI and CONFIG_EFI_STUB
> to y. There is little reason to omit this since EFI now is a
> significant percentage of all systems.
You didn't actually attach the patch, but I presume this is
On Mon, Aug 05, 2013 at 05:30:49PM +0100, Stefano Stabellini wrote:
> IOMMU_HELPER is needed because SWIOTLB calls iommu_is_span_boundary,
> provided by lib/iommu_helper.c.
>
> Signed-off-by: Stefano Stabellini
And Reviewed-by: Konrad Rzeszutek Wilk
Thanks.
> CC: will.dea...@arm.com
> CC:
device_close()->recalc_sigpending() is not needed, sigprocmask()
takes care of TIF_SIGPENDING correctly.
And without ->siglock it is racy and wrong, it can wrongly clear
TIF_SIGPENDING and miss a signal.
But even with this patch device_close() is still buggy:
1. sigprocmask() should not
On Sun, Aug 04, 2013 at 03:39:41PM +0100, Stefano Stabellini wrote:
> GNTTABOP_unmap_grant_ref unmaps a grant and replaces it with a 0
> mapping instead of reinstating the original mapping.
> Doing so separately would be racy.
>
> To unmap a grant and reinstate the original mapping atomically we
On 08/08/2013 03:13 PM, Ben Hutchings wrote:
I don't think this documentation is currently very useful. See further
comments inline:
On Fri, 2013-07-19 at 17:43 -0500, Sherry Hurwitz wrote:
File: README
File: microcode_amd.bin.README
File: microcode_amd_fam15h.bin.README
Signed-off-by:
On Fri, Aug 09, 2013 at 03:07:13PM +, Matthew Garrett wrote:
> On Fri, 2013-08-09 at 07:02 -0400, Vivek Goyal wrote:
> > On Fri, Aug 09, 2013 at 03:36:37AM -0400, Matthew Garrett wrote:
> > > kexec permits the loading and execution of arbitrary code in ring 0, which
> > > is something that
On 08/08, Oleg Nesterov wrote:
>
> And of course, there could be another bug. I just did
> "grep recalc_sigpending" and immediately found at least one buggy
> user, fs/dlm/user.c which calls it lockless.
and the usage of sigprocmask() is wrong, see 1/1.
In fact there are more users which play
I would like to change the defaults for CONFIG_EFI and CONFIG_EFI_STUB
to y. There is little reason to omit this since EFI now is a
significant percentage of all systems.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Seungwon and Jaehoon,
On Fri, Aug 9, 2013 at 6:32 AM, Seungwon Jeon wrote:
> On Wed, August 07, 2013, Doug Anderson wrote:
>> The dw_mmc driver keeps a cache of the current slot->clock in order to
>> avoid doing a whole lot of work every time set_ios() is called.
>> However, after suspend/resume
On Thu, Aug 01, 2013 at 11:10:15AM +0100, David Vrabel wrote:
> On 31/07/13 16:00, Roger Pau Monne wrote:
> > There's no need to keep the foreign access in a grant if it is not
> > persistently mapped by the backend. This allows us to free grants that
> > are not mapped by the backend, thus
On Fri, 9 Aug 2013, Richard Genoud wrote:
> > diff --git a/drivers/clocksource/time-armada-370-xp.c
> > b/drivers/clocksource/time-armada-370-xp.c
> > index 847cab6..8149b7b 100644
> > --- a/drivers/clocksource/time-armada-370-xp.c
> > +++ b/drivers/clocksource/time-armada-370-xp.c
> > @@
Hi,
On Fri, 2013-08-09 at 16:32 +0300, Felipe Balbi wrote:
> On Fri, Aug 09, 2013 at 12:53:47PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > DWC3 glue layer is hardware layer around Synopsys DesignWare
> > USB3 core. Its purpose is to supply Synopsys IP with required
> >
Pantelis Antoniou writes:
> Hi Kevin,
>
> On Aug 7, 2013, at 9:45 PM, Kevin Hilman wrote:
>
>> [fixing address for Benoit]
>>
>> Pantelis Antoniou writes:
>>
>>> omap_device relies on the platform notifier callbacks managing resources
>>> behind the scenes. The resources were not properly
On Fri, Aug 09, 2013 at 08:24:38AM -0600, Jens Axboe wrote:
> On 08/09/2013 02:23 AM, Alexander Gordeev wrote:
> > + ap->qc_tags = blk_mq_init_tags(ATA_MAX_QUEUE, 1, NUMA_NO_NODE);
> > + if (!ap->qc_tags) {
> > + kfree(ap);
> > + return NULL;
> > + }
>
> This should be
Seungwon,
On Fri, Aug 9, 2013 at 6:33 AM, Seungwon Jeon wrote:
> On Wed, August 07, 2013, Doug Anderson wrote:
>> If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
>> looping around forever. This has been seen to happen on exynos5420
>> silicon despite the fact that we
Hi Jan,
On Wed, Aug 7, 2013 at 6:58 PM, Jan Engelhardt wrote:
>
> It occurred to an openSUSE user that our mkinitrd would throw a
> warning when used with kmod:
>
> libkmod: conf_files_list: unsupported file mode /dev/null: 0x21b6
>
> Grepping for the error message revealed that there might be
201 - 300 of 1132 matches
Mail list logo
