Thanks for your advise, Michal Nazarewicz.
Having discuss with Joonsoo, I'm adding fallback allocation after
__alloc_from_contiguous().
The fallback allocation works if CMA kernel options is turned on but CMA size
is zero.
- 8<
>From
On Thu, May 15, 2014 at 05:35:01PM +0530, Sekhar Nori wrote:
> + ARM SoC team
>
> On Tuesday 13 May 2014 12:56 PM, Peter Ujfalusi wrote:
> > Get the two interrupt line number at the same time by merging the two
> > instance of if(node){}else{} places.
> > replace the >dev with the already
On Fri, 16 May 2014 13:52:42 +0200, Geert Uytterhoeven
wrote:
> Hi Grant,
>
> On Fri, May 16, 2014 at 12:58 PM, Grant Likely
> wrote:
> > On Thu, 15 May 2014 09:20:24 +0200, Geert Uytterhoeven
> > wrote:
> >> On Thu, May 15, 2014 at 9:12 AM, Pantelis Antoniou
> >> wrote:
> >> >> We also
On Wed, May 14, 2014 at 11:19:22AM +0200, Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> More DT material for AT91. Some fixes that apply on what was merged for 3.15
> but that are not very critical.
> The other patches are feature additions to old or very recent product/board:
> at91sam9261 or
On Mon, 19 May 2014 20:27:32 +0200, Borislav Petkov said:
> From: Borislav Petkov
>
> ... instead of naked numbers.
>
> Stuff in sysrq.c used to set it to 8 which is supposed to mean above
> default level so set it to DEBUG instead as we're terminating/killing
> all tasks and we want to be
On Mon, 19 May 2014 06:31:11 +0200 Julia Lawall wrote:
> From: Julia Lawall
>
> Delete unnecessary local variable whose value is always 0 and that hides
> the fact that the result is always 0.
>
> A simplified version of the semantic patch that fixes this problem is as
> follows:
On Monday, May 19, 2014 8:18:02 PM PDT, Dave Chinner wrote:
On Mon, May 19, 2014 at 05:55:30PM -0700, Daniel Phillips wrote:
On 05/18/2014 04:55 PM, Dave Chinner wrote:
...
I'm not commenting on the c99 comment style, I'm passing comment on
the fact that a filesystem that has commented out
On 05/20/2014 03:07 AM, Rickard Strandqvist wrote:
> There is otherwise a risk of a possible null pointer dereference.
>
> Was largely found by using a static code analysis program called cppcheck.
>
> Signed-off-by: Rickard Strandqvist
> ---
> sound/soc/samsung/dma.c | 10 ++
> 1
On Tue, May 20, 2014 at 10:03:43AM +1000, Stephen Rothwell wrote:
> Is this a request for inclusion of those branches into linux-next
> separately from the scsi tree itself?
James said he wants to include it in the scsi tree, but given how late
we are in the cycle I'd love to see separate
On Tue, May 20, 2014 at 12:04 AM, Nishanth Menon wrote:
> On Mon, May 19, 2014 at 1:08 PM, Inderpal Singh
> wrote:
>> Hi Nishanth,
>>
>> Thanks for the review comments.
>>
>> On Mon, May 19, 2014 at 6:43 PM, Nishanth Menon wrote:
>>> On 05/16/2014 04:09 AM, Inderpal Singh wrote:
At the
On Tue, May 20, 2014 at 12:54:29PM +0900, Tetsuo Handa wrote:
> Dave Chinner wrote:
> > So, XFS should be passing kswapd context to the workqueue allocation
> > context. The patch below does this.
> >
> > Tetsuo-san, when it comes to problems involving XFS, you should
> > really CC
On 19 May 2014 16:24, Tomasz Figa wrote:
> On 19.05.2014 09:10, Rahul Sharma wrote:
>> On 16 May 2014 20:19, Tomasz Figa wrote:
>>> On 16.05.2014 16:30, Rahul Sharma wrote:
On 16 May 2014 16:20, Tomasz Figa wrote:
> On 16.05.2014 12:35, Rahul Sharma wrote:
>> On 16 May 2014 15:12,
On Tue, 2014-05-20 at 07:02 +0200, Fabian Frederick wrote:
> and the winner is ? :)
Either works. You're the patch submitter. Pick one.
But I'm sure you know I'm not pushing the patch upstream... :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Tue, May 20, 2014 at 12:34 AM, Dan Carpenter
wrote:
> On Mon, May 19, 2014 at 09:19:07PM +0530, navin patidar wrote:
>> > You have changed it to return _FAIL instead of true. Perhaps that is ok
>> > but you need to explain it in the changelog.
>> >
>> oops, I'll resend this patch with proper
20.05.2014, 04:00, "Peter Zijlstra" :
> On Mon, May 19, 2014 at 11:31:19PM +0400, Kirill Tkhai wrote:
>
>> @@ -513,9 +513,17 @@ static enum hrtimer_restart dl_task_timer(struct
>> hrtimer *timer)
>> struct
>> sched_dl_entity,
>>
This patchset fixes a broken checksum function and removes a struct
that was being used to ignore bad checksum values.
V2 Changes:
* Change subject to make clear this patchset fixes a bug.
* Explicitly comment that the checksum algorithm is RFC 1071.
* Remove byte swapping code.
* Add
Remove fail_on_bad_eeprom, which was always 0 and thus being used
to ignore incorrect checksumming. This means devices with corrupt
eeprom will now cause the driver to fail.
Since fail_on_bad_eeprom was the last member in use of struct
slic_reg_params, remove that struct altogether.
Rewrite slic_eeprom_cksum() to fix bugs and make readable. This patch
technically has no effect on the user as failed eeprom checksums are
ignored anyway.
The original implementation had the following issues:
1. 2 of the 3 unrolled loops had the following bug:
while ((len -= 32) >= 0)
On Mon, 19 May 2014 16:50:05 -0700
Joe Perches wrote:
> On Mon, 2014-05-19 at 16:40 -0700, Andrew Morton wrote:
> > On Mon, 19 May 2014 16:22:28 -0700 Joe Perches wrote:
> >
> > > On Mon, 2014-05-19 at 16:09 -0700, Andrew Morton wrote:
> > > > On Fri, 16 May 2014 22:38:15 +0200 Fabian
On Mon, 19 May 2014 23:49:22 +0930, David Newall said:
> How does a packet get fragmented in this case? Does it only happen when
> bridging to a device with smaller MTU? That scenario sounds quite
> un-bridge-like. It also sounds like something that can be handled by
> real routing.
Which
Hi Bin,
On 5/19/2014 9:24 PM, Bin Liu wrote:
Hi,
On Mon, May 19, 2014 at 8:39 AM, George Cherian wrote:
BABBLE and RESET share the same interrupt. The interrupt
is considered to be RESET if MUSB is in peripheral mode and
as a BABBLE if MUSB is in HOST mode.
Handle babble condition iff MUSB
[Really adding Mark]
On Mon, May 19, 2014 at 9:25 PM, Olof Johansson wrote:
> [adding Mark]
>
> On Sat, May 17, 2014 at 06:22:16AM +0200, Alexandre Belloni wrote:
>> On 16/05/2014 at 16:26:35 -0700, Olof Johansson wrote :
>> > On Wed, May 07, 2014 at 07:39:35PM +0200, Nicolas Ferre wrote:
>> > >
On Mon, May 19, 2014 at 05:10:32PM +0200, Nicolas Ferre wrote:
> On 17/05/2014 01:31, Olof Johansson :
> > On Fri, May 16, 2014 at 04:26:35PM -0700, Olof Johansson wrote:
> >> On Wed, May 07, 2014 at 07:39:35PM +0200, Nicolas Ferre wrote:
> >>> On 07/05/2014 19:34, Nicolas Ferre :
> Arnd,
For audio to work on Snow board, we need the codec master clock 'mclk'
to be properly configured.
Currently XCLKOUT is configured as 'mclk' for codec chip and it is
required to be clocked at 24MHz for the codec to work properly.
Add appropriate clock handling within Snow sound-card driver to set
[adding Mark]
On Sat, May 17, 2014 at 06:22:16AM +0200, Alexandre Belloni wrote:
> On 16/05/2014 at 16:26:35 -0700, Olof Johansson wrote :
> > On Wed, May 07, 2014 at 07:39:35PM +0200, Nicolas Ferre wrote:
> > > There is a little conflict with at91-3.16-dt that you already pulled in
> > >
On Mon, May 19, 2014 at 6:31 PM, Arnd Bergmann wrote:
> On Friday 16 May 2014 16:03:04 Sunil Kovvuri wrote:
>> When the SR-IOV capable device's driver tries to enable sriov
>> (pci_enable_sriov()) it fails to create/add PCI device for each
>> virtual function reporting "not enough MMIO resources
On 19 May 2014 18:38, Nishanth Menon wrote:
>> + if (new_opp->rate == opp->rate) {
>> + mutex_unlock(_opp_list_lock);
>> + kfree(new_opp);
>> + return 0;
>
> IF we decide on ensuring that the OPP additions are done one time[1] -
Fingers crossed :)
But
Dave Chinner wrote:
> So, XFS should be passing kswapd context to the workqueue allocation
> context. The patch below does this.
>
> Tetsuo-san, when it comes to problems involving XFS, you should
> really CC x...@oss.sgi.com because very few people really know how
> XFS works and even fewer
In era_ctr(), era->md remain NULL until it's set after metadata_open().
On the other hand, era_destroy() assume era->md is non-NULL and it is
called by era_ctr() before initializing the value.
This patch just checks if era->md is non-NULL.
Signed-off-by: Naohiro Aota
---
Hi Dudley,
On Wed, Apr 16, 2014 at 08:35:52AM +, Dudley Du wrote:
> Re-architecture the driver to support function pointers, so it can support
> and integrate new devices later in one driver.
> Including use async thread in device proble to speed up system boot time.
> TEST=test on
Hi Dudley,
On Wed, Apr 16, 2014 at 08:39:34AM +, Dudley Du wrote:
> Rely on EV_SW and SW_LID bits to identify a LID device, and hook
> up our filter to listen for SW_LID events to enable/disable touchpad when
> LID is open/closed.
> TEST=test on Chomebooks.
This is a policy and it does not
On Mon, 19 May 2014 19:28:38 +0900, Yoshihiro YUNOMAE said:
> The header information is changed as follows:
>/;
Has this been tested with popular userspace that reads /dev/kmsg, to make
sure that it actually plays nice with a 5th field being added? Yes, I know
that
On Mon, May 19, 2014 at 11:18 PM, Christoph Hellwig wrote:
> On Mon, May 19, 2014 at 11:05:50PM +0800, Ming Lei wrote:
>> Another simple fix is to disable ipi for flush request, but looks
>> this one should be better.
>
> I think the first thing is to bite the bullet and sort out and document
>
On Wed, May 14, 2014 at 03:11:22PM -0400, Konrad Rzeszutek Wilk wrote:
> Hey Greg
>
> This email is in regards to backporting two patches to stable that
> fall under the 'performance' rule:
>
> bfe11d6de1c416cea4f3f0f35f864162063ce3fa
> fbe363c476afe8ec992d3baf682670a4bd1b6ce6
>
> I've copied
On Mon, May 19, 2014 at 05:55:30PM -0700, Daniel Phillips wrote:
> On 05/18/2014 04:55 PM, Dave Chinner wrote:
> >On Fri, May 16, 2014 at 05:50:59PM -0700, Daniel Phillips wrote:
> >static const struct inode_operations tux_file_iops = {
> >// .permission = ext4_permission,
> >
On Mon, 19 May 2014, li.xi...@freescale.com wrote:
> > > For each vmalloc area, there is one guard page at the end of it.
> > > so the vm->size = PAGE_ALIGN(offset + request size) + guard page size.
> >
> > Nope. There is no guard page for statically created vmalloc areas.
> >
>
> Yes, you
On Tue, May 20, 2014 at 02:29:31AM +, Namhyung Kim wrote:
> Hi Rodrigo,
>
> On Mon, May 19, 2014 at 3:11 PM, Rodrigo Campos wrote:
> > Is there something I can help to have this merged ? As far as I tested, this
> > works fine here. Or is this ok, just waiting on the "perf report: Add -F
>
On 05/20/2014 04:55 AM, Stephen Warren wrote:
On 05/18/2014 08:54 PM, FanWu wrote:
On 05/17/2014 03:53 AM, Stephen Warren wrote:
On 05/16/2014 10:21 AM, Linus Walleij wrote:
On Wed, May 14, 2014 at 4:01 AM, wrote:
From: Fan Wu
The patch added params in disable_setting to differ the two
On Thu, 15 May 2014, Nicolas Pitre wrote:
> On Thu, 15 May 2014, Peter Zijlstra wrote:
>
> > On Wed, May 14, 2014 at 04:57:10PM -0400, Nicolas Pitre wrote:
> > > It is better not to think about compute capacity as being equivalent to
> > > "CPU power". The upcoming "power aware" scheduler may
On 20 May 2014 02:46, Rafael J. Wysocki wrote:
> Do patches [2-5/5] depend on this one BTW?
Yes.
--
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
On 20 May 2014 02:43, Rafael J. Wysocki wrote:
> What about
>
> if (error)
> return error;
>
> and then you'd save an indentation level?
Yes.
> Anyway, I find adding of_node* stuff directly to the driver core this way
> kind of disgusting as there still are platforms
On Mon, May 19, 2014 at 10:40 PM, Tetsuo Handa
wrote:
>
> Since the kernel worker thread needs to escape from the while loop so that
> alloc_page() can allocate memory (and eventually allow xfs_vm_writepage()
> to release memory), I think that we should not block forever. This patch
> introduces
On Tue, 20 May 2014, Rusty Russell wrote:
> Hugh Dickins writes:
> >> On Monday 19 May 2014 05:42 AM, Rusty Russell wrote:
> >> >
> >> > Perhaps we try to generalize from two data points (a slight improvement
> >> > over doing it from 1!), eg:
> >> >
> >> > /* 4 seems good for 4k-page x86, 0
Hi Rodrigo,
On Mon, May 19, 2014 at 3:11 PM, Rodrigo Campos wrote:
> Is there something I can help to have this merged ? As far as I tested, this
> works fine here. Or is this ok, just waiting on the "perf report: Add -F
> option for
> specifying output fields" patchset ?
Thanks for testing!!
2014-05-20 오전 10:28, Michal Nazarewicz 쓴 글:
On Mon, May 19 2014, Gioh Kim wrote:
If CMA option is not selected, __alloc_from_contiguous would not be
called. We don't need to the fallback allocation.
And if CMA option is selected and initialized correctly,
the cma allocation can fail in case
On Tue, 15 Apr 2014, David Herrmann wrote:
> Some basic tests to verify sealing on memfds works as expected and
> guarantees the advertised semantics.
Thanks for providing these.
A few remarks below, and I should note one oddity.
Curious about leaks (probably none, I was merely curious), I
Jiri,
I updated my -v6 branch to fix the breakage - move the hunk to 15/20.
Do you want me to resend or would you review with this thread
directly? Either way would be find to me.
Thanks,
Namhyung
On Mon, May 19, 2014 at 1:54 PM, Namhyung Kim wrote:
> 2014-05-19 (월), 15:12 +0200, Jiri Olsa:
On Tue, 15 Apr 2014, David Herrmann wrote:
> memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor
> that you can pass to mmap(). It can support sealing and avoids any
> connection to user-visible mount-points. Thus, it's not subject to quotas
> on mounted file-systems, but
On Tue, 15 Apr 2014, David Herrmann wrote:
> If two processes share a common memory region, they usually want some
> guarantees to allow safe access. This often includes:
> - one side cannot overwrite data while the other reads it
> - one side cannot shrink the buffer while the other accesses
On Tue, May 20, 2014 at 2:06 AM, Steven Rostedt wrote:
> On Mon, 2014-05-19 at 23:29 +0900, Namhyung Kim wrote:
>> 2014-05-16 (금), 10:02 -0400, Steven Rostedt:
>> > -struct plugin_option {
>> > - struct plugin_option*next;
>> > +struct pevent_plugin_option {
>> > + struct
mces_seen is a Per-CPU variable which should only be accessed by Per-CPU as
possible. So the
clear operation of mces_seen should also be lcoal to Per-CPU rather than
monarch CPU.
Meanwhile, there is also a potential risk that mces_seen will not be be cleared
if a timeout
occors in mce_end for
Hugh Dickins writes:
> On Mon, 19 May 2014, Madhavan Srinivasan wrote:
>> On Monday 19 May 2014 05:42 AM, Rusty Russell wrote:
>> > Hugh Dickins writes:
>> >> On Thu, 15 May 2014, Madhavan Srinivasan wrote:
>> >>>
>> >>> Hi Ingo,
>> >>>
>> >>> Do you have any comments for the latest version of
Dan Carpenter writes:
> We cap "stat.size" at INT_MAX but we don't check for negative values so
> my static checker complains. At this point, you already have control of
> the kernel and if you start passing negative values here then you
> deserve what happens next.
>
> On 64 bit systems the
Randy Dunlap writes:
> On 05/19/2014 01:11 AM, Diego Viola wrote:
>> I mean "e.g.:" is wrong, it should be e.g. or e.g.,
>
> I don't see that in the wikipedia page. Are you basing that on
> "in this usage it is sometimes followed by a comma, depending on style."?
>
> I don't see a problem with
On Tuesday 20 May 2014 04:53 AM, Hugh Dickins wrote:
> On Mon, 19 May 2014, Madhavan Srinivasan wrote:
>> On Monday 19 May 2014 05:42 AM, Rusty Russell wrote:
>>> Hugh Dickins writes:
On Thu, 15 May 2014, Madhavan Srinivasan wrote:
>
> Hi Ingo,
>
> Do you have any comments
ping? It seems to be easy enough to reproduce on -next, I'd be happy to try
debug patches/fixes.
Thanks,
Sasha
On 05/12/2014 02:25 PM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel I've stumbled on the following spew:
>
On Mon, 2014-05-19 at 23:29 +0900, Namhyung Kim wrote:
> Hi Steve,
>
> 2014-05-16 (금), 10:02 -0400, Steven Rostedt:
>
> > From: "Steven Rostedt (Red Hat)"
> >
> > The traceevent plugins allows developers to have their events print out
> > information that is more advanced than what can be
On 2014-05-19 18:28, Ming Lei wrote:
On Mon, May 19, 2014 at 10:14 PM, Jens Axboe wrote:
On 05/19/2014 08:13 AM, Christoph Hellwig wrote:
I recently saw patches to fs/bio.c that were sent to Al instead of Jens.
I think having bio.c in fs/ is rather confusing, so maybe it's time to
include the
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Tuesday, May 20, 2014 6:52 AM
> Subject: Re: [PATCH v3 1/2] ACPI: Cleanup to convert acpi.no_static_ssdt into
> a compile-time configurable.
>
> On Tuesday, May 20, 2014 12:49:04 AM Rafael J. Wysocki wrote:
> > On Monday,
Hi David,
Today's linux-next merge of the sparc-next tree got a conflict in
arch/sparc/include/asm/pgtable_64.h between commit 26cf432551d7
("sparc64: Add basic validations to {pud,pmd}_bad()") from Linus' tree
and commit f05a68653e56 ("sparc: drop use of extern for prototypes in
On Mon, May 19, 2014 at 03:17:30PM +0100, Rupesh Gujare wrote:
> I will be not able to work on ozwpan driver anymore.
> Remove my name & add Tateno as maintainer.
>
> Signed-off-by: Rupesh Gujare
> ---
> MAINTAINERS |2 +-
> drivers/staging/ozwpan/TODO |2 +-
> 2 files
On Tue, 2014-05-20 at 09:43 +0900, Thomas Gleixner wrote:
> In kernel/locking/rtmutex.h:
> >
> > static inline int debug_rt_mutex_detect_deadlock(struct rt_mutex_waiter
> > *waiter,
> > int detect)
> > {
> > return (waiter != NULL);
> > }
On 05/20/2014 01:18 AM, Christoph Hellwig wrote:
> Looks good to me,
>
> Reviewed-by: Christoph Hellwig
>
OK, thanks.
And I shall continue, and should finish allmodconfig for unicore32
within this month (which I already delayed one month more).
Thanks.
--
Chen Gang
Open, share, and
On Mon, May 19 2014, Gioh Kim wrote:
> If CMA option is not selected, __alloc_from_contiguous would not be
> called. We don't need to the fallback allocation.
>
> And if CMA option is selected and initialized correctly,
> the cma allocation can fail in case of no-CMA-memory situation.
> I thinks
>> #ifdef CONFIG_CPU_PM
>> @@ -613,7 +636,7 @@ static void gic_cpu_restore(unsigned int gic_nr)
>> dist_base + GIC_DIST_PRI + i * 4);
>>
>> writel_relaxed(GIC_INT_PRI_THRESHOLD, cpu_base + GIC_CPU_PRIMASK);
>> - writel_relaxed(GIC_CPU_ENABLE,
On Mon, 2014-05-19 at 20:49 -0400, Tejun Heo wrote:
> On Mon, May 19, 2014 at 03:32:22PM -0700, Joe Perches wrote:
> > > > + memset(buf, 0, PAGE_SIZE);
> >
> > memset(buf, 0, count)?
>
> It's always PAGE_SIZE. Outputs longer than that are truncated.
Yeah, I know, but the code and
On Mon, May 19, 2014 at 10:57:08PM +0300, Dan Carpenter wrote:
> On Mon, May 19, 2014 at 09:42:22AM -0500, Romer, Benjamin M wrote:
> > On Sun, 2014-05-18 at 09:49 -0700, Greg KH wrote:
> > > Also, why are these entries moving to debugfs at all? Why are they
> > > needed? Who will use them? Are
On Mon, 2014-05-19 at 17:04 -0700, Eric W. Biederman wrote:
> Seth Forshee writes:
>
> > What I set out for was feature parity between loop devices in a secure
> > container and loop devices on the host. Since some operations currently
> > check for system-wide CAP_SYS_ADMIN, the only way I see
On Sat, May 17, 2014 at 1:52 PM, Or Gerlitz wrote:
> Roland, we're soon on -rc6 and there's no reason for this to miss
> 3.16, could you please comment whether you want it to go through your
> tree or net-next?
I will pick it up.
--
To unsubscribe from this list: send the line "unsubscribe
On Thu, May 08, 2014 at 07:25:53PM +0300, Mathias Nyman wrote:
> Hi Greg
>
> These following xhci patches are for usb-next and hopefully for 3.16
>
> This patcheseries includes a bigger change in xhci command queue code,
> (last four patches), a task that I've been working on for a longer time.
On Thu, May 08, 2014 at 07:25:55PM +0300, Mathias Nyman wrote:
> From: Dan Williams
>
> Add a command line switch for disabling ehci port switchover. Useful
> for working around / debugging xhci incompatibilities where ehci
> operation is available.
>
> Reference:
("bonding: Fix stacked device detection
in arp monitoring").
vlan_dev_priv() is protected by:
#if defined(CONFIG_VLAN_8021Q) || defined(CONFIG_VLAN_8021Q_MODULE)
but the newly added call in vlan_get_encap_level() is not.
I have used the net tree from next-20140519 for today.
--
Cheer
On Fri, May 16, 2014 at 06:32:55PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Here's the pull request for 3.16. It contains mostly bug fixes and cleanup
> apart from one new driver for exynos5 usb3 PHY. Please consider merging them
> to your usb tree.
>
> Let me know if I have to change
On Mon, May 12, 2014 at 06:01:02PM +0300, Mathias Nyman wrote:
> On 05/08/2014 07:21 PM, Dan Williams wrote:
> > On Thu, May 8, 2014 at 9:25 AM, Mathias Nyman
> > wrote:
> >> From: Dan Williams
> >>
> >> Save someone else the debug cycles of figuring out why a driver's
> >> transfer request is
Commit-ID: eb705905b713837d2cc26dfa019df16aeb8813be
Gitweb: http://git.kernel.org/tip/eb705905b713837d2cc26dfa019df16aeb8813be
Author: Davidlohr Bueso
AuthorDate: Mon, 19 May 2014 17:27:57 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 20 May 2014 09:53:11 +0900
rwsem: Fix warnings
Hi Alexandre and Simon,
On Tuesday 20 May 2014 07:39:13 Simon Horman wrote:
> [ CCed Laurent Pinchart ]
>
> The renesas and shmobile portions of this seem reasonable to me
> and I have checked that there do not seem to be any conflicts
> with changes I already have queued up for v3.16 (and
On 05/18/2014 04:55 PM, Dave Chinner wrote:
On Fri, May 16, 2014 at 05:50:59PM -0700, Daniel Phillips wrote:
We would like to offer Tux3 for review for mainline merge. We have
prepared a new repository suitable for pulling:
https://git.kernel.org/cgit/linux/kernel/git/daniel/linux-tux3.git/
On Mon, May 19, 2014 at 03:32:22PM -0700, Joe Perches wrote:
> > > + memset(buf, 0, PAGE_SIZE);
>
> memset(buf, 0, count)?
It's always PAGE_SIZE. Outputs longer than that are truncated.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
2014-05-20 오전 4:59, Michal Nazarewicz 쓴 글:
On Sun, May 18 2014, Joonsoo Kim wrote:
I think that this problem is originated from atomic_pool_init().
If configured coherent_pool size is larger than default cma size,
it can be failed even if this patch is applied.
The coherent_pool size
On Tue, May 20, 2014 at 09:27:54AM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-next full request for v3.16. I add detailed description of this
> pull request on below. Please pull extcon with following updates.
>
> I report you about merge of MAX77836 patchset from MFD git
[cc x...@oss.sgi.com]
On Mon, May 19, 2014 at 11:40:46PM +0900, Tetsuo Handa wrote:
> >From f016db5d7f84d6321132150b13c5888ef67d694f Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Mon, 19 May 2014 23:24:11 +0900
> Subject: [PATCH] mm/vmscan: Do not block forever at shrink_inactive_list().
From: Julia Lawall
Delete unnecessary local variable whose value is always 0 and that hides
the fact that the result is always 0.
A simplified version of the semantic patch that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@r exists@
local idexpression ret;
expression e;
Andrew Morton wrote:
> On Mon, 19 May 2014 16:23:07 -0700 (PDT) Hugh Dickins
> wrote:
>
> > Shouldn't FAULT_AROUND_ORDER and fault_around_order be changed to be
> > the order of the fault-around size in bytes, and fault_around_pages()
> > use 1UL << (fault_around_order - PAGE_SHIFT)
>
> Yes.
On Thu, 15 May 2014, Steven Rostedt wrote:
> On Wed, 14 May 2014 20:03:27 -
> Thomas Gleixner wrote:
>
> > In case the dead lock detector is enabled we follow the lock chain to
> > the end in rt_mutex_adjust_prio_chain, even if we could stop earlier
> > due to the priority/waiter
> Hi,
cc'iong intel-gfx.
>
> I've upgraded kernel on my PC to 3.15-rc5 and I got today freeze
> (recovery possibly only by power off/on) when waking from suspend.
> There is only warning in log but system was completely dead (no keys
> reaction ).
>
> May 14 15:53:15 nb kernel:
cc'ing dri-devel.
> >From d0d57745ba23faf605b0f249b57d283fe1a8ee60 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Mon, 19 May 2014 17:59:03 +0900
> Subject: [PATCH] gpu/drm/ttm: Pass GFP flags in order to avoid deadlock.
>
> Commit 7dc19d5a "drivers: convert shrinkers to new count/scan
cc'ing dri-devel.
> >From e314a1a1583e585d062dfc30c8aad8bf5380510b Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Mon, 19 May 2014 18:43:21 +0900
> Subject: [PATCH] gpu/drm/ttm: Use mutex_lock_killable() for shrinker
> functions.
>
> I can observe that RHEL7 environment stalls with
On Mon, 19 May 2014, Sergei Shtylyov wrote:
> Hello.
>
> On 19-05-2014 8:31, Julia Lawall wrote:
>
> > From: Julia Lawall
>
> > Delete unnecessary local variable whose value is always 0 and that hides
> > the fact that the result is always 0.
>
> > A simplified version of the semantic patch
* Tony Lindgren [140514 14:57]:
> * Sebastian Reichel [140510 09:40]:
> > Add SSI device tree data for OMAP3 and Nokia N900.
>
> Picking this patch into omap-for-v3.16/dt thanks.
Just noticed that this patch seems to somehow break idle
modes on n900, so dropping both dts changes for now.
On Mon, 19 May 2014, Sergei Shtylyov wrote:
> Hello.
>
> On 19-05-2014 8:31, Julia Lawall wrote:
>
> > From: Julia Lawall
>
> > Delete unnecessary local variable whose value is always 0 and that hides
> > the fact that the result is always 0.
>
> > A simplified version of the semantic patch
On Mon, May 19, 2014 at 10:14 PM, Jens Axboe wrote:
> On 05/19/2014 08:13 AM, Christoph Hellwig wrote:
>> I recently saw patches to fs/bio.c that were sent to Al instead of Jens.
>> I think having bio.c in fs/ is rather confusing, so maybe it's time to
>> include the simple git-mv for it in the
Dear Greg,
This is extcon-next full request for v3.16. I add detailed description of this
pull request on below. Please pull extcon with following updates.
I report you about merge of MAX77836 patchset from MFD git repo(Lee Jones).
The MAX77836 patchset in this pull request has the dependency on
> So if given the choice between the 2, I think checking
> !CONFIG_RWSEM_GENERIC_SPINLOCK is better just because we use that to
> decide the implementation/structure layout.
Yeah, I suspect this is more suitable as well. Thanks.
8<-
From: Davidlohr
Rafael J. Wysocki wrote:
>
> On Monday, May 19, 2014 12:51:24 PM Stephen Rothwell wrote:
> >
> > --Sig_/n+GoYBpTr9ERl.sTIEYr/Og
> > Content-Type: text/plain; charset=US-ASCII
> > Content-Transfer-Encoding: quoted-printable
> >
> > Hi Rafael,
> >
> > Today's linux-next merge of the pm tree got
On 05/19/2014 04:10 PM, Borislav Petkov wrote:
>
> The question is, why can't that pstore mumbo jumbo go and do its dance
> in !irq context?
>
> And how useful is the whole deal really, btw? I wanted to use it for
> saving oopses into it, for example, but Tony said its write speed is
> horribly
Seth Forshee writes:
> What I set out for was feature parity between loop devices in a secure
> container and loop devices on the host. Since some operations currently
> check for system-wide CAP_SYS_ADMIN, the only way I see to accomplish
> this is to push knowledge of the user namespace
Hi Christoph,
On Mon, 19 May 2014 07:06:14 -0700 Christoph Hellwig wrote:
>
> I'd like to announce the new scsi patch queue tree, which will pick up
> any scsi core or driver patches promptly to allow easy integration and
> feedback that contributors might be used to from other kernel
Hi Ralf,
Yesterday and today, trying to fetch the mips tree
(git://git.linux-mips.org/pub/scm/ralf/upstream-sfr.git#mips-for-linux-next)
hangs for a long time (I got impatient and just killed the fetch).
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
signature.asc
On Mon, May 19, 2014 at 11:31:19PM +0400, Kirill Tkhai wrote:
> @@ -513,9 +513,17 @@ static enum hrtimer_restart dl_task_timer(struct hrtimer
> *timer)
>struct sched_dl_entity,
>dl_timer);
>
> Subject: Re: [PATCH] regmap: irq: Fix possible ZERO_SIZE_PTR pointer
> dereferencing error.
>
> On Mon, May 19, 2014 at 03:13:45PM +0800, Xiubo Li wrote:
> > Since we cannot make sure the 'chip->num_regs' will always be none zero
> > from the users, and then if 'chip->num_regs' equals to zero
1 - 100 of 1998 matches
Mail list logo
