This patch fixes the following checkpatch.pl warning in as102/as102_drv.c
WARNING: line over 80 characters in the file
Signed-off-by: Monam Agarwal
---
drivers/staging/media/as102/as102_drv.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Mon, Jan 13, 2014 at 11:22:45AM -0800, Dave Hansen wrote:
>
> Changes from v1:
> * put MTRR under "Processor Options"
> * fix circular dependency introduced in the paravirt shuffle
> * dump extended platforms down to the end of the menu
>
> --
>
> The x86 "Processor type and features"
On Tue 14-01-14 14:27:27, Michal Hocko wrote:
> On Mon 13-01-14 17:52:30, Hugh Dickins wrote:
> > On one home machine I can easily reproduce (by rmdir of memcgdir during
> > reclaim) multiple processes stuck looping forever in mem_cgroup_iter():
> > __mem_cgroup_iter_next() keeps selecting the
Hi Kishon,
And happy new year..
On Tue, Jan 07, 2014 at 07:10:36PM +0530, Kishon Vijay Abraham I wrote:
> >>> /**
> >>> - * phy_get() - lookup and obtain a reference to a phy.
> >>> + * phy_get_index() - obtain a phy based on index
> >>
> >> NAK. It still takes a 'char' argument and the name is
Em Tue, Jan 14, 2014 at 02:15:40PM +0100, Jiri Olsa escreveu:
> On Tue, Jan 14, 2014 at 10:09:07AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jan 14, 2014 at 10:41:37AM +0900, Masami Hiramatsu escreveu:
> > > (2014/01/14 3:14), Arnaldo Carvalho de Melo wrote:
> > > > Jiri, this is
On Tue, Jan 14, 2014 at 12:36:06PM +0100, Jean-Francois Moine wrote:
> This patch
> - removes the fields of the platform data which are of no use to the
> non-DT platform callers,
> - uses a new private structure to handle all the sound card information,
> - simplifies the code and make easier a
On 01/14/2014 03:09 PM, Sergey Senozhatsky wrote:
> On (01/14/14 15:02), Jerome Marchand wrote:
>> On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
>>> On (01/14/14 14:43), Jerome Marchand wrote:
>>> [..]
>>
>> That's weird: good/bad_compress are accounted, but it seems to me that
>>
2014-01-13 (월), 15:00 -0300, Arnaldo Carvalho de Melo:
> Em Thu, Jan 09, 2014 at 11:07:59PM +0900, Namhyung Kim escreveu:
> > It failed to build perf on my ubuntu 10.04 box (gcc 4.4.3):
> >
> > CC util/strlist.o
> > cc1: warnings being treated as errors
> > util/strlist.c: In
2014/1/11 boris brezillon :
> On 09/01/2014 22:04, Jean-Jacques Hiblot wrote:
>>
>> Hi Boris,
>>
>> 2014/1/9 boris brezillon :
>>>
>>> Hello JJ,
>>>
>>>
>>> On 09/01/2014 13:31, Jean-Jacques Hiblot wrote:
The EBI/SMC external interface is used to access external peripherals
(NAND
On Tue, Jan 14, 2014 at 12:58:56PM +0100, Wolfram Sang wrote:
> devm_ioremap_resource does sanity checks on the given resource. No need to
> duplicate this in the driver.
>
> Signed-off-by: Wolfram Sang
> ---
>
> Should go via subsystem tree
too late for v3.14, I'll merge this for v3.15.
--
This adds support for the DMA Contiguous Memory Allocator for intel-iommu.
This change enables dma_alloc_coherent() to allocate big contiguous
memory.
It is achieved in the same way as nommu_dma_ops currently does, i.e.
trying to allocate memory by dma_alloc_from_contiguous() and alloc_pages()
is
Hi
On Tue, Jan 14, 2014 at 2:45 PM, Fengguang Wu wrote:
> Hi David,
>
> I'm not sure if this is a good bisect because the errors are noisy,
> however it's good to inform you of this possibility.
>
> First bad commit may be a3483353c ("drm: check for !kdev in
> drm_unplug_minor()")
To be
The DMA Contiguous Memory Allocator support on x86 is disabled when
swiotlb config option is enabled. So DMA CMA is always disabled on
x86_64 because swiotlb is always enabled. This attempts to support
for DMA CMA with enabling swiotlb config option.
The contiguous memory allocator on x86 is
Currently, "cma=" kernel parameter is used to specify the size of CMA,
but we can't specify where it is located. We want to locate CMA below
4GB for devices only supporting 32-bit addressing on 64-bit systems
without iommu.
This enables to specify the placement of CMA by extending "cma=" kernel
On Tue, Jan 14, 2014 at 02:26:27PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/cpufreq/speedstep-lib.c: In function 'speedstep_get_freqs':
> drivers/cpufreq/speedstep-lib.c:467:2: error:
This introduces memblock_alloc_range() which allocates memblock from
the specified range of physical address. I would like to use this
function to specify the location of CMA.
Cc: Marek Szyprowski
Cc: Konrad Rzeszutek Wilk
Cc: David Woodhouse
Cc: Don Dutile
Cc: Thomas Gleixner
Cc: Ingo
> [ Sorry, I am coming down with the flu today so I'm doing dorky things
> like reviewing review comments. I'm not sure how coherent I am. ]
Always welcome.
NB: I did this review in double-quick time, which may account for some
of the weird thought processes (or lack there of).
> > >
Calling dma_alloc_coherent() with __GFP_ZERO must return zeroed memory.
But when the contiguous memory allocator (CMA) is enabled on x86 and
the memory region is allocated by dma_alloc_from_contiguous(), it
doesn't return zeroed memory. Because dma_generic_alloc_coherent()
forgot to fill the
On 01/13/2014 12:14 PM, atom...@redhat.com wrote:
> From: Aaron Tomlin
>
> Enable hung_task_warnings to display every hung
> task warning when set to -1.
>
> Signed-off-by: Aaron Tomlin
Aaron and I talked on IRC, and after some talking these patches
now make sense to me :)
The kernel
This patch set enhances the DMA Contiguous Memory Allocator on x86.
Currently the DMA CMA is only supported with pci-nommu dma_map_ops
and furthermore it can't be enabled on x86_64. But I would like to
allocate big contiguous memory with dma_alloc_coherent() and tell it
to the device that
On 01/13/2014 12:14 PM, atom...@redhat.com wrote:
> From: Aaron Tomlin
>
> Add neg_one to the list of standard constraints.
>
> Signed-off-by: Aaron Tomlin
Acked-by: Rik van Riel
--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On (01/14/14 15:02), Jerome Marchand wrote:
> On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
> > On (01/14/14 14:43), Jerome Marchand wrote:
> > [..]
>
> That's weird: good/bad_compress are accounted, but it seems to me that
> they are to never used in any way. If so, there is
Hi again,
On Tue, Jan 14, 2014 at 07:10:52AM -0600, Felipe Balbi wrote:
> > diff --git a/drivers/hwspinlock/omap_hwspinlock.c
> > b/drivers/hwspinlock/omap_hwspinlock.c
> > index 9f56fb2..194886e 100644
> > --- a/drivers/hwspinlock/omap_hwspinlock.c
> > +++ b/drivers/hwspinlock/omap_hwspinlock.c
On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
> On (01/14/14 14:43), Jerome Marchand wrote:
> [..]
That's weird: good/bad_compress are accounted, but it seems to me that
they are to never used in any way. If so, there is indeed no reason to
keep them.
>
From: Ramkumar Ramachandra
Color the numbers in the Delta column using percent_color_snprintf().
Generalize the coloring function so that we can accommodate all three
comparison methods in future patches: delta, ratio, and wdiff.
Signed-off-by: Ramkumar Ramachandra
Acked-by: Jiri Olsa
Cc:
From: Ramkumar Ramachandra
Make percent_color_snprintf() handle negative values correctly.
Signed-off-by: Ramkumar Ramachandra
Acked-by: Jiri Olsa
Cc: Jiri Olsa
Link:
http://lkml.kernel.org/r/1388388861-7931-2-git-send-email-artag...@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo
---
Em Tue, Jan 14, 2014 at 02:41:01PM +0100, Ingo Molnar escreveu:
> * Arnaldo Carvalho de Melo wrote:
> > Andi Kleen (2):
> > perf stat: Fix --delay option in man page
> > perf record: Add --initial-delay option
> Hm, so we now have two options that do something similar, one named
>
Commit-ID: 60283df7ac26a4fe2d56631ca2946e04725e7eaf
Gitweb: http://git.kernel.org/tip/60283df7ac26a4fe2d56631ca2946e04725e7eaf
Author: Richard Weinberger
AuthorDate: Tue, 14 Jan 2014 08:44:47 +0100
Committer: Ingo Molnar
CommitDate: Tue, 14 Jan 2014 14:05:36 +0100
x86/apic: Read Error
On (01/14/14 14:43), Jerome Marchand wrote:
[..]
> >>
> >> That's weird: good/bad_compress are accounted, but it seems to me that
> >> they are to never used in any way. If so, there is indeed no reason to
> >> keep them.
> >>
> >>
> >>> Account each sub-request
> >>> compression size so we can
On Tue, Jan 14, 2014 at 04:46:34PM +0300, Dan Carpenter wrote:
> [ Sorry, I am coming down with the flu today so I'm doing dorky things
> like reviewing review comments. I'm not sure how coherent I am. ]
>
> On Tue, Jan 14, 2014 at 01:04:09PM +, Lee Jones wrote:
>
> > > +static void
[ Sorry, I am coming down with the flu today so I'm doing dorky things
like reviewing review comments. I'm not sure how coherent I am. ]
On Tue, Jan 14, 2014 at 01:04:09PM +, Lee Jones wrote:
> > +static void rtsx_usb_sg_timed_out(unsigned long data)
> > +{
> > + struct rtsx_ucr *ucr
On Tue, Jan 14, 2014 at 02:23:37PM +0100, Geert Uytterhoeven wrote:
> On Tue, Jan 14, 2014 at 1:52 PM, Mark Brown wrote:
> >On Tue, Jan 14, 2014 at 12:36:51PM +0100, Geert Uytterhoeven wrote:
> > This also pushes the handling of CS_HIGH back out into the driver which
> > doesn't seem like it's
On 01/14/2014 12:10 PM, Sergey Senozhatsky wrote:
> On (01/14/14 11:38), Jerome Marchand wrote:
>> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
>>> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
>>> `show' functions and reduce code duplication.
>>>
>>> 2) Account and report
On Tue, Jan 14, 2014 at 12:58:54PM +0100, Wolfram Sang wrote:
> devm_ioremap_resource does sanity checks on the given resource. No need to
> duplicate this in the driver.
>
> Signed-off-by: Wolfram Sang
> Reviewed-by: Terje Bergstrom
> ---
>
> Should go via subsystem tree
>
>
* Arnaldo Carvalho de Melo wrote:
> Andi Kleen (2):
> perf stat: Fix --delay option in man page
> perf record: Add --initial-delay option
Hm, so we now have two options that do something similar, one named
--delay, the other --initial-delay? That looks rather inconsistent.
On Tue, Jan 14, 2014 at 05:27:46AM -0800, Mike Travis wrote:
>
>
> On 1/14/2014 3:00 AM, Peter Zijlstra wrote:
> > On Mon, Jan 13, 2014 at 10:24:09PM -0600, Mike Travis wrote:
> >> Fix some problems found by the kbuild test robot.
> >>
> >> Signed-off-by: Mike Travis
> >> Reviewed-by: Hedi
On Tue 14-01-14 14:27:27, Michal Hocko wrote:
> On Mon 13-01-14 17:52:30, Hugh Dickins wrote:
> > On one home machine I can easily reproduce (by rmdir of memcgdir during
> > reclaim) multiple processes stuck looping forever in mem_cgroup_iter():
> > __mem_cgroup_iter_next() keeps selecting the
On Tue, Jan 14, 2014 at 02:17:55PM +0100, Geert Uytterhoeven wrote:
> On Tue, Jan 14, 2014 at 1:51 PM, Peter Zijlstra wrote:
> > On Tue, Jan 14, 2014 at 03:53:31PM +1100, Stephen Rothwell wrote:
> >> Today's linux-next merge of the akpm-current tree got a conflict in
> >> kernel/futex.c between
On Tue, Jan 14, 2014 at 12:58:53PM +0100, Wolfram Sang wrote:
> devm_ioremap_resource does sanity checks on the given resource. No need to
> duplicate this in the driver.
>
> Signed-off-by: Wolfram Sang
> ---
>
> Should go via subsystem tree
>
> drivers/amba/tegra-ahb.c | 2 --
> 1 file
Hi Cristoph,
On 8 January 2014 16:03, Christoph Hellwig wrote:
> On Tue, Jan 07, 2014 at 08:37:23PM +0200, Sergey Meirovich wrote:
>> Actually my initial report (14.67Mb/sec 3755.41 Requests/sec) was about ext4
>> However I have tried XFS as well. It was a bit slower than ext4 on all
>>
On Mon 13-01-14 17:54:04, Hugh Dickins wrote:
> It is surprising that the mem_cgroup iterator can return memcgs which
> have not yet been fully initialized. By accident (or trial and error?)
> this appears not to present an actual problem; but it may be better to
> prevent such surprises, by
On 1/14/2014 3:00 AM, Peter Zijlstra wrote:
> On Mon, Jan 13, 2014 at 10:24:09PM -0600, Mike Travis wrote:
>> Fix some problems found by the kbuild test robot.
>>
>> Signed-off-by: Mike Travis
>> Reviewed-by: Hedi Berriche
>
> In general it is best to actually mention the issues the patch
On Mon 13-01-14 17:52:30, Hugh Dickins wrote:
> On one home machine I can easily reproduce (by rmdir of memcgdir during
> reclaim) multiple processes stuck looping forever in mem_cgroup_iter():
> __mem_cgroup_iter_next() keeps selecting the memcg being destroyed, fails
> to tryget it, returns NULL
On Tuesday 14 January 2014, Leif Lindholm wrote:
> On Tue, Jan 14, 2014 at 07:52:32AM +0100, Arnd Bergmann wrote:
> > > > > It uses the generic configuration table scanning to populate ACPI and
> > > > > SMBIOS pointers.
> > > >
> > > > As far as I'm concerned there are no plans to have ACPI
Hi Mark,
On Tue, Jan 14, 2014 at 1:52 PM, Mark Brown wrote:
>On Tue, Jan 14, 2014 at 12:36:51PM +0100, Geert Uytterhoeven wrote:
>
>> The documentation for spi_master.set_cs() says:
>>
>> assert or deassert chip select, true to assert
>>
>> i.e. its "enable" parameter uses assertion-level
On Tue, Jan 14, 2014 at 08:55:50AM +0900, Namhyung Kim wrote:
> Hi Jiri,
>
> Thanks for reminding me. :)
>
> On Thu, 9 Jan 2014 19:06:28 +0100, Jiri Olsa wrote:
> > On Wed, Jan 08, 2014 at 05:46:15PM +0900, Namhyung Kim wrote:
>
> [SNIP]
> >> + /*
> >> + * Check if there's duplicate entries
On Tue, Jan 14, 2014 at 1:51 PM, Peter Zijlstra wrote:
> On Tue, Jan 14, 2014 at 03:53:31PM +1100, Stephen Rothwell wrote:
>> Today's linux-next merge of the akpm-current tree got a conflict in
>> kernel/futex.c between commit a52b89ebb6d4 ("futexes: Increase hash table
>> size for better
On Tuesday, January 14, 2014 at 12:58:55 PM, Wolfram Sang wrote:
> devm_ioremap_resource does sanity checks on the given resource. No need to
> duplicate this in the driver.
>
> Signed-off-by: Wolfram Sang
True that,
Acked-by: Marek Vasut
> ---
>
> Should go via subsystem tree
>
>
On Tue, Jan 14, 2014 at 10:09:07AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 14, 2014 at 10:41:37AM +0900, Masami Hiramatsu escreveu:
> > (2014/01/14 3:14), Arnaldo Carvalho de Melo wrote:
> > > Jiri, this is something else for the give-me-more-ponies list for
> > > tests/make: build it
On Mon, Jan 13, 2014 at 06:19:17PM -0600, Suman Anna wrote:
> This is an updated series mainly addressing Mark Rutland's comments
> about hwlock specifier being always one-cell. The series adds the
> support for #hwlock-cells property and adds a simple default OF
> translate function.
>
> The DTS
On Mon, Jan 13, 2014 at 06:19:24PM -0600, Suman Anna wrote:
> HwSpinlocks are supported on AM33xx, AM43xx and DRA7xx SoC
> device families as well. The IPs are identical to that of
> OMAP4/OMAP5, except for the number of locks.
>
> Add a depends on to the above family of SoCs to enable the
>
On Mon, Jan 13, 2014 at 06:19:23PM -0600, Suman Anna wrote:
> The number of hwspinlocks are determined based on the value read
> from the IP block's SYSSTATUS register. However, the module may
> not be enabled and clocked, and the read may result in a bus error.
>
> This particular issue is seen
Em Tue, Jan 14, 2014 at 10:41:37AM +0900, Masami Hiramatsu escreveu:
> (2014/01/14 3:14), Arnaldo Carvalho de Melo wrote:
> > Jiri, this is something else for the give-me-more-ponies list for
> > tests/make: build it on freshly provisioned systems with multiple mixes
> > of devel packages
Miklos Szeredi wrote:
> On Mon, Jan 13, 2014 at 11:03 PM, Tetsuo Handa
> wrote:
> > Miklos Szeredi wrote:
> >> Cross rename (A, B) is equivalent to plain rename(A, B) + plain rename
> >> (B, A) done as a single atomic operation. If security module allows
> >> both then cross rename is allowed.
> From: Roger Tseng
>
> Realtek USB card reader provides a channel to transfer command or data to
> flash
> memory cards. This driver exports host instances for mmc and memstick
> subsystems
> and handles basic works.
>
> Signed-off-by: Roger Tseng
> ---
> drivers/mfd/Kconfig | 10
Hi Bjorn,
Just two comments.
On Mon, 2014-01-13 at 16:30 -0800, Bjorn Andersson wrote:
> From: "Ivan T. Ivanov"
>
> This bus driver supports the QUP i2c hardware controller in the Qualcomm
> MSM SOCs. The Qualcomm Universal Peripheral Engine (QUP) is a general
> purpose data path engine
On Mon 13-01-14 17:50:49, Hugh Dickins wrote:
> Shorten mem_cgroup_reclaim_iter.last_dead_count from unsigned long to
> int: it's assigned from an int and compared with an int, and adjacent
> to an unsigned int: so there's no point to it being unsigned long,
> which wasted 104 bytes in every
* Borislav Petkov wrote:
> Hi guys,
>
> please pull these microcode loader fixes which addresses early microcode
> loading on AMD. The patches have been ready for a while now and I've
> been running them here for weeks but was waiting for AMD to test them
> too before I send out.
>
> Also, I
On Tue, Jan 14, 2014 at 12:36:51PM +0100, Geert Uytterhoeven wrote:
> {
> - if (spi->mode & SPI_CS_HIGH)
> - enable = !enable;
> -
> - if (spi->cs_gpio >= 0)
> + if (spi->cs_gpio >= 0) {
> + if (spi->mode & SPI_CS_HIGH)
> + enable =
On Tue, Jan 14, 2014 at 03:53:31PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm-current tree got a conflict in
> kernel/futex.c between commit a52b89ebb6d4 ("futexes: Increase hash table
> size for better performance") from the tip tree and commit
On Mon, 13 Jan 2014, Alan Stern wrote:
> On Wed, 8 Jan 2014, Daniel Vetter wrote:
>
>> On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
>> > On Wed, 8 Jan 2014, Daniel Vetter wrote:
>> >
>> > > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
>> > > > On Tue, 7 Jan 2014,
On Tue 14-01-14 11:31:59, Miklos Szeredi wrote:
> On Mon, Jan 13, 2014 at 08:52:27AM +0100, Jan Kara wrote:
> > On Wed 08-01-14 23:10:11, Miklos Szeredi wrote:
>
> > > + if (max_links && new_dir != old_dir) {
> > > error = -EMLINK;
> > > - if (max_links && !target && new_dir !=
From: Mathias Nyman
...
> > The fact that you are having to allocate memory ion an ISR ought also to be
> > ringing alarm bells.
>
> It did.
> Other options are as you said to use a 'software command ring'. Either
> just pre-allocate a full command ring (64 trbs * sizeof(struct
> xhci_command)),
On (01/14/14 13:15), Jerome Marchand wrote:
> On 01/14/2014 11:57 AM, Sergey Senozhatsky wrote:
> >
> > Hello Jerome,
> >
> > On (01/14/14 11:38), Jerome Marchand wrote:
> >> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> >>> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
On 01/14/2014 12:13 PM, Sergey Senozhatsky wrote:
> On (01/14/14 12:02), Jerome Marchand wrote:
>>> static int zram_bvec_rw(struct zram *zram, struct bio_vec *bvec, u32 index,
>>> - int offset, struct bio *bio, int rw)
>>> + int offset, struct bio *bio)
>>> {
The clk_enable() call in the pm_clk_resume() call returns an error
that is not being checked. If clk_enable() fails then we should
not set the state of the clock to PCE_STATUS_ENABLED.
Note, the issue of warning the user if this fails has not been
addressed in this patch as this is not the only
The drivers/base/power/clock_ops.c file is causing warnings from
the clock driver (as shown below) due to failing to do a clk_prepare()
call before enabling a clock. It also fails to check the balance of
prepare/unprepare as __pm_clk_remove() do clk_disable_unprepare() call.
This bug has probably
If clk_enable() fails, then print a message so that the user can see
what is happening instead of silently failing to enable the clock.
Cc: "Rafael J. Wysocki"
Cc: Pavel Machek
Cc: Greg Kroah-Hartman
Cc: linux...@vger.kernel.org
Cc: linux...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
A re-send of the clk_ops.c fixes for handling clocks with the
current renesas development branch. I am not sure if these need
to be applied to any stable kernel branches.
>From v1:
- Fixed comments from Rafael Wysocki on checking of ret.
--
To unsubscribe from this list: send the line
Hi Philipp,
On 01/13/2014 03:03 PM, Philipp Hachtmann wrote:
> Add a new memory state "nomap" to memblock. This can be used to truncate
> the usable memory in the system without forgetting about what is really
> installed.
Sorry, but this solution looks a bit complex (and probably wrong - from
On Tue, 14 Jan 2014 16:23:23 +0800
Dave Young wrote:
> In kdump kernel watchdog could interrupt vmcore capturing because we
> have no way to disable/stop it while crashing happens.
Lots of watchdogs cannot be stopped.
> Add a module parameter stop_before_register so watchdog can be stopped
>
On 01/14/2014 11:57 AM, Sergey Senozhatsky wrote:
>
> Hello Jerome,
>
> On (01/14/14 11:38), Jerome Marchand wrote:
>> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
>>> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
>>> `show' functions and reduce code duplication.
>>>
>>>
On Tue, 2014-01-14 at 15:41 +0800, Ying Xue wrote:
> @@ -2218,10 +2194,6 @@ static int nl80211_set_wiphy(struct sk_buff *skb,
> struct genl_info *info)
> rdev->wiphy.coverage_class = old_coverage_class;
> }
> }
> -
> - bad_res:
> - if (netdev)
> -
Hi,
On Tue, Jan 14, 2014 at 01:03:34PM +0100, John Crispin wrote:
> Hi Wolfgang,
Wolfram, please...
> should we take 1/7 and 6/7 via the mips tree ?
> > Should go via subsystem tree
Yes :)
Thanks,
Wolfram
signature.asc
Description: Digital signature
> Maybe we should unset the low_latency flag as soon as DMA fails? There
> are two flags, one is state->uart_port->flags and the other is
> port->low_latency. I guess we need to unset both.
Well low latency and DMA are pretty much exclusive in the real world so
probably DMA ports shouldn't
Hi Wolfgang,
should we take 1/7 and 6/7 via the mips tree ?
John
On 14/01/2014 12:58, Wolfram Sang wrote:
> devm_ioremap_resource does sanity checks on the given resource. No need to
> duplicate this in the driver.
>
> Signed-off-by: Wolfram Sang
> Acked-by: John Crispin
> ---
>
> Should
On 13/01/14 19:55, Rafael J. Wysocki wrote:
On Saturday, January 11, 2014 01:05:39 PM Ben Dooks wrote:
@@ -262,8 +263,9 @@ int pm_clk_resume(struct device *dev)
list_for_each_entry(ce, >clock_list, node) {
if (ce->status < PCE_STATUS_ERROR) {
-
This patch fixes the following checkpatch.pl issues in
as102/as102_fe.c
WARNING: line over 80 characters
Signed-off-by: Monam Agarwal
---
drivers/staging/media/as102/as102_fe.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/media/as102/as102_fe.c
This patch fixes the following checkpatch.pl issues in
as102/as102_fe.c
WARNING: quoted string split across lines
Signed-off-by: Monam Agarwal
---
drivers/staging/media/as102/as102_fe.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On Sun, 12 Jan 2014 20:33:03 +0700
Linus Torvalds wrote:
> Another week, another RC. And things look fine.
It seems to hate Baytrail/T
My ASUS T100TA has gone from 3.11 'needs video=VGA-1:blah' to get the mode
right but otherwise running nicely and playing 3D games to 3.13-rc8
- crashes and
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang
---
Should go via subsystem tree
drivers/amba/tegra-ahb.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/amba/tegra-ahb.c
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang
---
Should go via subsystem tree
drivers/pci/host/pci-imx6.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/pci/host/pci-imx6.c
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang
---
Should go via subsystem tree
drivers/usb/dwc3/dwc3-omap.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/usb/dwc3/dwc3-omap.c
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang
Acked-by: John Crispin
---
Should go via subsystem tree
arch/mips/lantiq/xway/dma.c | 4
1 file changed, 4 deletions(-)
diff --git
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang
---
Should go via subsystem tree
arch/mips/pci/pci-rt3883.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/mips/pci/pci-rt3883.c
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang
Reviewed-by: Terje Bergstrom
---
Should go via subsystem tree
drivers/gpu/drm/tegra/hdmi.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.
Signed-off-by: Wolfram Sang
---
Should go via subsystem tree
drivers/gpio/gpio-davinci.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/gpio/gpio-davinci.c
On Tue, Jan 14, 2014 at 03:41:01PM +0800, Ying Xue wrote:
The following call chain indicates that bond_do_ioctl() is protected
under rtnl_lock. If we use __dev_get_by_name() instead of
dev_get_by_name() to find interface handler in it, this would
help us avoid to change reference counter of
IMHO the xhci driver is already far too complicated, and this probably just
makes
it even worse.
This is an attempt to make it cleaner and less complicated.
In the end this series removes far more more code than it adds:
5 files changed, 373 insertions(+), 530 deletions(-)
The timers are
Dear Sir.
We got your name and address from Romanian trade bulletin as a
reliable exporters and Manufacture of Furniture and related items
We here are also a big importers and distributors of furnitures and
related products with branches and offices in some of the African
countries for
On Tue, Jan 14, 2014 at 09:41:33AM -0200, Henrique de Moraes Holschuh wrote:
> I just got this assigned to amd64-microcode in Debian, but it is something
> that needs to be worked around by the EFI/BIOS and/or the kernel.
>
> Since we all know just how well it pans out to depend on BIOS/EFI
Hi guys,
please pull these microcode loader fixes which addresses early microcode
loading on AMD. The patches have been ready for a while now and I've
been running them here for weeks but was waiting for AMD to test them
too before I send out.
Also, I think it is finally time for the microcode
On 2014-01-14 03:13, Chase Southwood wrote:
This patch for pcl711.c removes braces causing a checkpatch.pl warning.
It also removes an empty else arm of an if-else statement.
Signed-off-by: Chase Southwood
---
I removed the "else" arm of this statement because it was empty, save for the
On 2014-01-14 03:13, Chase Southwood wrote:
This patch for ni_mio_common.c silences a checkpatch error due to a
trailing statement.
Signed-off-by: Chase Southwood
---
drivers/staging/comedi/drivers/ni_mio_common.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On 2014-01-14 07:23, Dan Carpenter wrote:
On Mon, Jan 13, 2014 at 07:16:14PM -0800, Joe Perches wrote:
On Mon, 2014-01-13 at 21:13 -0600, Chase Southwood wrote:
This patch for ni_mio_common.c silences a checkpatch error due to a
trailing statement.
[]
diff --git
Rasmus Villemoes writes:
Ping...
> Ensure that lcm(a,b) returns the mathematically correct result,
> provided it fits in an unsigned long. The current version returns
> garbage if a*b overflows, even if the final result would fit.
>
> Signed-off-by: Rasmus Villemoes
> ---
> There are of course
On Tue, Jan 14, 2014 at 07:52:32AM +0100, Arnd Bergmann wrote:
> > > > It uses the generic configuration table scanning to populate ACPI and
> > > > SMBIOS pointers.
> > >
> > > As far as I'm concerned there are no plans to have ACPI support on ARM32,
> > > so I wonder what the code to populate
(2013/12/10 23:49), Vivek Goyal wrote:
On Wed, Dec 04, 2013 at 05:10:58PM +0900, HATAYAMA Daisuke wrote:
This patch set is to allow kdump 2nd kernel to wake up multiple CPUs,
a continueing work from:
[PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP
I just got this assigned to amd64-microcode in Debian, but it is something
that needs to be worked around by the EFI/BIOS and/or the kernel.
Since we all know just how well it pans out to depend on BIOS/EFI updates
for *anything*, I'm raising the issue here. IMHO looks like it would be
On Mon, Oct 28, 2013 at 11:04:44AM +0100, Alexander Gordeev wrote:
> Here is an update of few behaviours which caught my eye.
> I have not tested any, so it is up to your judgement ;)
Hi Kent et al.
Can we go ahead with this series?
Thanks!
--
Regards,
Alexander Gordeev
agord...@redhat.com
--
701 - 800 of 1818 matches
Mail list logo
