2014-07-18 17:46 GMT+03:00 Benoit Taine :
> On 18/07/2014 17:38, Andrey Utkin wrote:
>> Is there script for automated checkpatch.pl && get_maintainers.pl &&
>> git send-email for range of commits? I see none. Would it be welcome
>> to submit such one to kernel tree?
> You can use `splitpatch` to
On Saturday 19 July 2014 00:15:35 Chanwoo Choi wrote:
> On Fri, Jul 18, 2014 at 8:14 PM, Arnd Bergmann wrote:
> > On Friday 18 July 2014 19:00:48 Chanwoo Choi wrote:
> >> On 07/18/2014 06:47 PM, Arnd Bergmann wrote:
> >> >
> >> > Further, why is it called "sclk_adc" rather than just "sclk"?
> >>
On Mon, Jul 14, 2014 at 9:18 PM, Seth Forshee
wrote:
> fuse_copy_finish() assumes that mapaddr in fuse_copy_state refers
> to a valid mapping if currbuf is non-NULL, but this isn't always
> true when moving pages for splice I/O. This results in an
> unbalanced call to kunmap_atomic() and thus an
On 07/17/2014 08:46 PM, Masanari Iida wrote:
> Because of file location changes by commit 5ed4ac73e5975,
> make xmldocs failed because of missing files.
> Fix file paths in gadget.tmpl file.
>
> Signed-off-by: Masanari Iida
Hi,
There was a patch for this on the USB mailing list yesterday
from
Acked-by: Lennox Wu
2014-07-14 23:08 GMT+08:00 Sam Ravnborg :
> Remove redundant assignments.
>
> Signed-off-by: Sam Ravnborg
> Cc: Chen Liqin
> Cc: Lennox Wu
> ---
> arch/score/include/uapi/asm/Kbuild | 32
> 1 file changed, 32 deletions(-)
>
> diff --git
On Fri, 18 Jul 2014, Rafael J. Wysocki wrote:
> > > the problem really seems to be that drivers are not
> > > aggressive enough with starting PM transitions (using runtime PM) when
> > > they
> > > see no activity. Thus it seems that when the lid is closed, it'll be good
> > > to switch the
keystone PCI controller is based on v3.65 designware hardware. This
version differs from newer versions of the hardware in few functional
areas discussed below that makes it necessary to change dw_pcie_host_init()
to support v3.65 based PCI controller.
1. No support for ATU port. So any ATU
keystone PCIe controller is based on v3.65 version of the
designware h/w. Main differences are
1. No ATU support
2. Legacy and MSI irq functions are implemented in
application register space
3. MSI interrupts are multiplexed over 8 IRQ lines to the Host
This patch series add PCIe controller driver for keystone SoCs. This is
based on v4 of the series posted to the mailing list. Keystone PCI controller
is based on version 3.65 of the DW hardware. This driver uses the DW core
functions to implement the PCI controller driver for keystone.
Testing:
v3.65 version of the designware h/w, requires application space
registers to be configured to access the remote EP config space.
To support this, add rd[wr]_other_conf API in the pcie_host_opts
Signed-off-by: Murali Karicheri
Reviewed-by: Pratyush Anand
Acked-by: Mohit Kumar
Acked-by: Jingoo
Update the MAINTAINERS file for the keystone PCIe driver
Signed-off-by: Murali Karicheri
CC: Santosh Shilimkar
CC: Russell King
CC: Grant Likely
CC: Rob Herring
CC: Mohit Kumar
CC: Jingoo Han
CC: Bjorn Helgaas
CC: Pratyush Anand
CC: Richard Zhu
CC: Kishon Vijay Abraham I
CC: Marek
Keystone PCI controller is based on v3.65 version of the DW
PCI h/w that implements MSI controller registers in application
space compared to the newer version. This requires updates to
the DW core API to support the PCI controller driver based on
this old DW hardware. Add msi_irq_set()/clear()
/dev/mdesc on Linux does not support reading arbitrary number
of bytes and seeking while /dev/mdesc on Solaris does. This
causes tools that work on Solaris to break on Linux. This patch
adds these two capabilities to /dev/mdesc.
Signed-off-by: Khalid Aziz
---
v3:
- Whitespace cleanup
On Fri, Jul 18, 2014 at 8:14 PM, Arnd Bergmann wrote:
> On Friday 18 July 2014 19:00:48 Chanwoo Choi wrote:
>> On 07/18/2014 06:47 PM, Arnd Bergmann wrote:
>> >
>> > Further, why is it called "sclk_adc" rather than just "sclk"?
>>
>> The sclk means 'special clock' in Exynos TRM. Exynos SoC has
Linus,
The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to
On Fri, Jul 18, 2014 at 4:45 PM, Johannes Weiner wrote:
> I assumed the source page would always be new, according to this part
> in fuse_try_move_page():
>
> /*
> * This is a new and locked page, it shouldn't be mapped or
> * have any special flags on it
> */
On Fri, Jul 18, 2014 at 12:51:06AM +, Elliott, Robert (Server Storage)
wrote:
> SYNCHRONIZE CACHE (16) should be favored over SYNCHRONIZE
> CACHE (10) unless SYNCHRONIZE CACHE (10) is not supported.
I gues you mean (16) for the last occurance? What's the benefit of
using SYNCHRONIZE CACHE
On Thu, Jul 17, 2014 at 11:53:33PM +, KY Srinivasan wrote:
> I still see this problem. There was talk of fixing it elsewhere.
Well, what we have right not is entirely broken, given that the
block layer doesn't initialize ->timeout on TYPE_FS requeuests.
We either need to revert that initial
On Thu, Jul 17, 2014 at 05:29:36PM +0200, Michal Hocko wrote:
> On Mon 07-07-14 14:55:58, Johannes Weiner wrote:
> > Pages are now uncharged at release time, and all sources of batched
> > uncharges operate on lists of pages. Directly use those lists, and
> > get rid of the per-task batching
On Fri, Jul 18, 2014 at 12:28:54PM +0200, Hans de Goede wrote:
> Hi,
>
> On 07/18/2014 09:16 AM, Mikko Perttunen wrote:
> > So here's v5: this time, as suggested, I handle the sata clock myself and
> > let ahci_platform handle it too, leading it to be prepared+enabled twice.
> > This works
On Fri, Jul 18, 2014 at 07:57:13AM -0700, Joe Perches wrote:
> I think your viewpoint is a bit tainted as you're the
> same guy that wrote "fuck readability".
>
> https://lkml.org/lkml/2013/11/19/116
It seems you still haven't understood what I actually meant.
If you'd tried to understand what
Joakim Tjernlund/Transmode wrote on 2014/07/18 15:49:17:
>
> Richard Weinberger wrote on 2014/07/18
14:58:30:
> >
> > On Thu, Jul 17, 2014 at 1:18 PM, Joakim Tjernlund
> > wrote:
> > > Trying to real /proc//exe I noticed I could not read links not
> > > belonging to my user such as:
> > >
On 07/18/2014 12:55 AM, Wang Nan wrote:
> + if (!zone_is_empty(movable_zone))
> + if (zone_spans_pfn(movable_zone, start_pfn) ||
> + (zone_end_pfn(movable_zone) <= start_pfn))
> + zone = movable_zone;
> +
It's nice that you hit so
On Fri, Jul 18, 2014 at 12:58:31PM +0100, Anup Patel wrote:
> On 18 July 2014 16:37, Catalin Marinas wrote:
> > From 133656f8378dbb838ad5f12ea29aa9303d7ca922 Mon Sep 17 00:00:00 2001
> > From: Catalin Marinas
> > Date: Fri, 18 Jul 2014 11:54:37 +0100
> > Subject: [PATCH] arm64: Create non-empty
On Fri, 2014-07-18 at 16:49 +0200, Borislav Petkov wrote:
> On Fri, Jul 18, 2014 at 07:35:26AM -0700, Joe Perches wrote:
> > Using the one-liner above also makes it harder to
> > automate checkpatch neatening and avoid using Lindent:
>
> automated checkpatch?? More idiocy... we want less, in case
On Fri, Jul 18, 2014 at 07:43:57AM -0700, Guenter Roeck wrote:
> Thinking about it, Linux itself can be abused as well. We should
> take it away to prevent that abuse from happening.
Whatever floats your boat, dude.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting
> Is there script for automated checkpatch.pl && get_maintainers.pl &&
> git send-email for range of commits? I see none. Would it be welcome
> to submit such one to kernel tree?
Spurious checkpatch.pl changes increasing number of git-blame
"false positives" are more than enough.
Alexey
--
On Fri, Jul 18, 2014 at 03:53:05PM +0900, Minchan Kim wrote:
> MADV_FREE needs pmd_dirty and pmd_mkclean for detecting recent
> overwrite of the contents since MADV_FREE syscall is called for
> THP page.
>
> This patch adds pmd_dirty and pmd_mkclean for THP page MADV_FREE
> support.
>
> Cc:
On 18/07/2014 17:38, Andrey Utkin wrote:
> Is there script for automated checkpatch.pl && get_maintainers.pl &&
> git send-email for range of commits? I see none. Would it be welcome
> to submit such one to kernel tree?
You can use `splitpatch` to split a patch into multiple mails with the
On Fri, Jul 18, 2014 at 03:53:04PM +0900, Minchan Kim wrote:
> MADV_FREE needs pmd_dirty and pmd_mkclean for detecting recent
> overwrite of the contents since MADV_FREE syscall is called for
> THP page.
>
> This patch adds pmd_dirty and pmd_mkclean for THP page MADV_FREE
> support.
>
> Cc:
On Fri, Jul 18, 2014 at 04:16:48PM +0200, Peter Zijlstra wrote:
> On Fri, Jul 18, 2014 at 08:01:26AM -0500, Bruno Wolff III wrote:
> > build_sched_domain: cpu: 0 level: SMT cpu_map: 0-3 tl->mask: 0,2
> > [0.254433] build_sched_domain: cpu: 0 level: MC cpu_map: 0-3 tl->mask: 0
> > [
On Fri, Jul 18, 2014 at 07:35:26AM -0700, Joe Perches wrote:
> Using the one-liner above also makes it harder to
> automate checkpatch neatening and avoid using Lindent:
automated checkpatch?? More idiocy... we want less, in case you've
forgotten.
Let me state it again:
The thing is called
Hi Michal,
[cc'ing Miklos for fuse's use of replace_page_cache()]
On Fri, Jul 18, 2014 at 09:12:46AM +0200, Michal Hocko wrote:
> On Tue 15-07-14 14:19:35, Michal Hocko wrote:
> > [...]
> > > +/**
> > > + * mem_cgroup_migrate - migrate a charge to another page
> > > + * @oldpage: currently
On Fri, 18 Jul 2014, Nick Krause wrote:
> I am assuming this is a stupid question but since I am new I will ask it
> anyway.
> Can the usb_bus structure be Null? If can I will send it a patch removing
> the
> fix mes on lines 854 and 878 of hcd.c .
Line numbers in a source file usually
The omap1's debug-macro.S is similar to the generic 8250 code. Compared to
the 8520 code the omap1 macro automatically determines what UART to use
based on breadcrumbs left by the bootloader and automatically copes with
the eccentric register layout on OMAP7XX.
This patch drops both these
On 07/18/2014 07:27 AM, Borislav Petkov wrote:
On Fri, Jul 18, 2014 at 07:21:14AM -0700, Christoph Hellwig wrote:
Or he could just use the existing -f flag.
If you mean the -f flag to checkpatch, he's removing them both.
Two different 'he'.
I really don't understand why you're trying to
On Fri, Jul 18, 2014 at 03:31:57PM +0100, Mark Rutland wrote:
SNIP
> > > I'm not sure what the best way of handling this is. We need to clean up
> > > the children when the last possible user of the event is gone, but it
> > > looks to me like we'd need to have a separate child_refcount or
> > >
Hi,
On Fri, Jul 18, 2014 at 08:11:15AM +0100, Lee Jones wrote:
> > > diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> > > index eb69eb9..171ca52 100644
> > > --- a/drivers/usb/dwc3/core.c
> > > +++ b/drivers/usb/dwc3/core.c
> > > @@ -47,6 +47,14 @@
> > >
> > > /*
> > >
On Fri, 18 Jul 2014, Amit Virdi wrote:
> On 7/17/2014 8:25 PM, Alan Stern wrote:
> > I can't say this is actually wrong, but have you ever encountered a
> > situation where this would be needed? How often does anyone need to do
> > a multi-packet transfer over an interrupt endpoint?
>
>
Is there script for automated checkpatch.pl && get_maintainers.pl &&
git send-email for range of commits? I see none. Would it be welcome
to submit such one to kernel tree?
--
Andrey Utkin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Enable ARMCLK down feature on Exynos3250 SoC. The frequency of
ARMCLK will be reduced upon entering idle mode (WFI or WFE).
The feature behaves like very fast cpufreq ondemand governor.
The patch uses simillar settings as Exynos5250 (clk-exynos5250.c),
except it disables clock up feature.
Enable ARMCLK down feature on all Exynos4 SoCs. The frequency of
ARMCLK will be reduced upon entering idle mode (WFI or WFE).
The feature behaves like very fast cpufreq ondemand governor. In idle
mode this reduces energy consumption on full frequency chosen by
cpufreq governor by approximately:
On Fri, 2014-07-18 at 16:24 +0200, Borislav Petkov wrote:
> On Fri, Jul 18, 2014 at 04:17:42PM +0200, Lars-Peter Clausen wrote:
> > --file is a in my opinion useful option and at least I use it on a
> > regular basis.
[]
> diff -urN /dev/null $file | ./scripts/checkpatch.pl -
Using the one-liner
On Fri, 18 Jul 2014, Tomas Henzl wrote:
> > + if (src_sector + nr_sects < src_sector ||
> > + dst_sector + nr_sects < dst_sector)
> > + return -EINVAL;
>
> Hi Mikulas,
> this^ is meant as an overflow test or what is the reason?
> Thanks, Tomas
Yes. It is a test for overflow.
> Date: Fri, 18 Jul 2014 13:57:15 +0530
> Subject: [Question] Why should we check irq_fpu_usable before accessing using
> ASENI instructions.
> From: guru2...@gmail.com
> To: linux-x86...@vger.kernel.org
>
> Hello,
> I am new to assembly language programming.
> In Kernel we check
On Thu, 17 Jul 2014, Steve Calfee wrote:
> Hi Alan,
>
> It has been a few years since I was doing this, but here is my
> understanding. If a device descriptor says x bytes should be reserved
> (1 to 3072), the host will allocate that much bandwidth. If the sender
> sends some number of bytes
Signed-off-by: Cyrille Pitchen
---
drivers/net/ethernet/cadence/macb.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/ethernet/cadence/macb.c
b/drivers/net/ethernet/cadence/macb.c
index 6acd6e2..08105dc 100644
--- a/drivers/net/ethernet/cadence/macb.c
+++
this new compatibility string prevents macb/gem driver from using the
scatter-gather and gso features on sama5d3x boards.
Signed-off-by: Cyrille Pitchen
---
arch/arm/boot/dts/sama5d3_gmac.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, Jul 18, 2014 at 03:03:43PM +0100, Peter Zijlstra wrote:
> On Fri, Jul 18, 2014 at 01:32:39PM +0100, Mark Rutland wrote:
> > Hi all,
> >
> > Sheetal reported a weird issue on arm where events which have been
> > closed seem to stay around and compete for HW counters if an application
> >
Hi,
On 07/18/2014 02:30 PM, Antoine Ténart wrote:
> The ahci_platform driver is a generic driver using the libahci_platform
> functions. Add a generic compatible to avoid having an endless list of
> compatibles with no differences for the same driver.
>
> Signed-off-by: Antoine Ténart
> ---
>
On Fri, Jul 18, 2014 at 07:21:14AM -0700, Christoph Hellwig wrote:
> Or he could just use the existing -f flag.
If you mean the -f flag to checkpatch, he's removing them both.
> I really don't understand why you're trying to educate people by
> taking their toy away. They'll find another one in
The Colibri VF61 is a module which needs a carrier board to actually
run. Different carrier board have different hardware support, hence
we should reflect this in the device tree files. This patch adds the
Colibri Evaluation Board, which supports almost all peripherals
defined in the Colibri
Hi,
this series of patches adds new hardware features to macb driver. These
features can be enabled/disabled at runtime using ethtool. Depending on
hardware and design configuration, some are enabled by default whereas other
are disabled.
For instance, checksum offload features are enabled by
On 10/07/2014 21:59, Boris BREZILLON :
> Hello,
>
> This patch removes a board specific hook for sama5d3xek boards from the
> sama5d3 generic DT board file.
>
> This hook (which register a phy fixup configuring board specific delays
> in the ksz9021 ethernet phy) is now replaced by the
On Fri, Jul 18, 2014 at 04:17:42PM +0200, Lars-Peter Clausen wrote:
> --file is a in my opinion useful option and at least I use it on a
> regular basis.
Use
diff -urN /dev/null $file | ./scripts/checkpatch.pl -
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is
On Fri, Jul 18, 2014 at 06:56:12AM -0700, Guenter Roeck wrote:
> Yes, that came up before. Or I can revert the patch locally, or keep
> an old version of checkpatch around. You make me suffer
Come on, you suffer from a one-liner?! Script it or whatever. Puh-lease!
The thing is inviting lazy
On Thu, 17 Jul 2014, Pranith Kumar wrote:
> > then we have on x86 a increment operation with locked semantics racing
> > with an unlocked one on the same cacheline.
> OK, I will add this as a warning in the documentation. Thanks!
Note that I have not been able to get beyond a bad feeling. Looked
The scatter-gather feature will allow to enable the Generic Segmentation
Offload.
Generic Segmentation Offload can be enabled/disabled using ethtool -K DEVNAME
gso on|off.
e.g:
ethtool -K eth0 gso off
When enabled, the driver may be provided with socket buffers splitted into many
fragments.
On Fri, Jul 18, 2014 at 03:46:29PM +0200, Richard Weinberger wrote:
> As capable kernel hacker you can still use a command like:
> diff -urN /dev/null $file | ./scripts/checkpatch.pl -
Or he could just use the existing -f flag. I really don't understand
why you're trying to educate people by
Signed-off-by: Cyrille Pitchen
---
drivers/net/ethernet/cadence/macb.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/net/ethernet/cadence/macb.c
b/drivers/net/ethernet/cadence/macb.c
index 06e9934..9bdcd1b 100644
---
From: Nicolas Ferre
This addition will also allow to configure DMA burst length.
Signed-off-by: Nicolas Ferre
Acked-by: Cyrille Pitchen
---
drivers/net/ethernet/cadence/macb.c | 72 +++--
drivers/net/ethernet/cadence/macb.h | 19 --
2 files changed, 71
On 10/07/2014 21:59, Boris BREZILLON :
> Add ethernet-phy nodes and specify phy interrupt (connected to pin PB25)
> and board specific timing configs.
>
> Atmel has two different HW designs for its CPU modules: the first one
> (produced by Embest) is connecting PHYAD[0-2] pins to pull up
Signed-off-by: Cyrille Pitchen
---
drivers/net/ethernet/cadence/macb.c | 29 -
drivers/net/ethernet/cadence/macb.h | 2 ++
2 files changed, 30 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/cadence/macb.c
b/drivers/net/ethernet/cadence/macb.c
index
On Fri, 18 Jul 2014, poma wrote:
> I guess someone working over the summertime. :)
Cache names should not contain blanks. I guess the
WARN_ON(strchr(name, ' ')); /* It confuses parsers */
was triggered?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Fri, Jul 18, 2014 at 3:22 AM, Markos Chandras
wrote:
> Hi Kees,
>
> On 07/17/2014 11:29 PM, Kees Cook wrote:
>> Hi,
>>
>> I recently fixed a bug in seccomp on ARM that I think may be present
>> in the MIPS implementation too. In arch/mips/kernel/ptrace.c
>> syscall_trace_enter, the syscall
On Fri, Jul 18, 2014 at 05:21:04PM +0400, Vladimir Davydov wrote:
> Slab warns, because the name of the cache being created contains spaces.
> The "bad" cache is created by scsi_get_host_cmd_pool. Its name
> (pool->cmd_name) is initialized by scsi_alloc_host_cmd_pool as follows:
>
>
On 07/17/2014 05:34 PM, Richard Weinberger wrote:
[...]
In order to deal with that bad habit let's remove the --file option
and bring checkpatch.pl back to its original purpose.
I don't think this is a good solution the problem and I'm not sure how
successful it will actually be at fixing the
On 18/07/14 15:01, Bruno Wolff III wrote:
On Fri, Jul 18, 2014 at 12:16:33 +0200,
Peter Zijlstra wrote:
So it looks like the actual domain tree is broken, and not what we
assumed it was.
Could I bother you to run with the below instead? It should also print
out the sched domain masks so we
On Fri, Jul 18, 2014 at 08:01:26AM -0500, Bruno Wolff III wrote:
> build_sched_domain: cpu: 0 level: SMT cpu_map: 0-3 tl->mask: 0,2
> [0.254433] build_sched_domain: cpu: 0 level: MC cpu_map: 0-3 tl->mask: 0
> [0.254516] build_sched_domain: cpu: 0 level: DIE cpu_map: 0-3 tl->mask:
> 0-3
>
Two global variables, "syslog_prev" and "console_prev", maintain a
copy of the flags value used in the log record most recently
formatted for syslog or the console, respectively.
Initially there is no previous formatted log record, and these
variables simply have an initial value 0. And
Each log record has a "flags" field. The flags keep track of, for
instance, whether the record was saved in its entirety (as opposed
to being one of multiple records that should be merged as a single
unit). A log record's flags field alone is not currently sufficient
to know how the record
It is possible for the log to be filled too quickly for the consoles
to be able to keep up. This is detected in console_unlock(), and
when it occurs, a message is printed on the console. When reviewing
some nearby code, Petr Mládek suggested it might be nicer if this
message were placed on a
In devkmsg_read(), a variable "cont" holds a character that's used
to indicate whether a given log line is a "continuation", that is,
whether a log record should be merged with the one before or after
it. If a record should be merged with its successor (but not its
predecessor) that character is
Two log record flags--LOG_CONT and LOG_NEWLINE--are mutually
exclusive. That is, one or the other is always set, but they are
never both set at the same time in a log record flags field. What
follows is a great deal of explanation that aims to prove this
assertion.
Having that knowledge allows
If a log record has LOG_PREFIX set, its predecessor record should be
terminated if it was marked LOG_CONT.
In devkmsg_read(), this condition was being ignored, which would
lead to such records showing up combined when reading /dev/kmsg.
Fix this oversight.
We should similarly insert a newline in
This patch fixes a problem similar to what was addressed in the
previous patch.
All paths that read and format log records (for consoles, and for
reading via syslog and /dev/kmsg) go through msg_print_text(). That
function starts with some logic to determine whether the given log
record when
This patch corrects a few more typographical errors in "printk.c".
Signed-off-by: Alex Elder
Reviewed-by: Petr Mládek
---
kernel/printk/printk.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index abb129c..71d82ef
On Wed, Jul 09, 2014 at 11:46:56PM +0100, Olof Johansson wrote:
> On Wed, Jul 2, 2014 at 11:03 AM, Laura Abbott wrote:
> > For architectures without coherent DMA, memory for DMA may
> > need to be remapped with coherent attributes. Factor out
> > the the remapping code from arm and put it in a
>
Arnd, Olof, Kevin,
This is the latest regressions that we found while testing the at91sam9n12 and
at91sam9x5 platforms following our move to CCF.
I created a pull-request this time because I have 3 patches: there should be
no conflict anyway. This tag does not contain the fix that Olof had taken
Export symbols from the PPMU driver needed to build the exynos bus
driver as a module.
Cc: MyungJoo Ham
Cc: Kyungmin Park
Cc: Kukjin Kim
Cc: Bartlomiej Zolnierkiewicz
Signed-off-by: Punit Agrawal
---
drivers/devfreq/Kconfig |2 +-
drivers/devfreq/exynos/exynos_ppmu.c |3
Hi,
There's no reason why the exynos PPMU can't be built as a module
except you need -
- The first patch exports the functions that are needed to build
devfreq drivers as modules.
- The second patch then converts the exynos PPMU devfreq driver to be
built as a module.
Compile tested only.
From: Ørjan Eide
These functions are indended for use by drivers and should be available
also when the driver is built as a module.
Cc: MyungJoo Ham
Cc: Kyungmin Park
Signed-off-by: Ørjan Eide
---
drivers/devfreq/devfreq.c |3 +++
1 file changed, 3 insertions(+)
diff --git
On Fri, Jul 18, 2014 at 01:59:06PM +0100, Jonathan Davies wrote:
> The current implementation of idle_cpu only considers tasks that might be in
> the
> CPU's runqueue. If there's nothing in the specified CPU's runqueue, it will
> return 1. But if the CPU is doing work in the softirq context, it
On Thu, Jul 17, 2014 at 11:05:12PM -0400, Nick Krause wrote:
> On Thu, Jul 17, 2014 at 1:38 PM, Nick Krause wrote:
> > On Thu, Jul 17, 2014 at 3:52 AM, Sam Ravnborg wrote:
> >> On Wed, Jul 16, 2014 at 10:25:30PM -0400, Nick Krause wrote:
> >>> I am hitting three Fix mes in this file and am
On Fri, Jul 18, 2014 at 11:31:30AM +0200, Lothar Waßmann wrote:
> There is no need to throw the baby out with the bath due to a bad
> failure analysis. The commit:
> 7adb5c876e9c usb: musb: Fix panic upon musb_am335x module removal
> came to a wrong conclusion about the cause of the crash it was
>
On Thu, Jul 17, 2014 at 03:18:31PM +0200, Andreas Werner wrote:
> Added driver to support the 14F021P00 BMC Watchdog.
> The BMC is a Board Management Controller including watchdog functionality.
>
> This driver use the I2C interface to the BMC using the menf21bmc MFD Core
> driver.
>
>
On Fri, Jul 18, 2014 at 01:32:39PM +0100, Mark Rutland wrote:
> Hi all,
>
> Sheetal reported a weird issue on arm where events which have been
> closed seem to stay around and compete for HW counters if an application
> has forked between the events being opened and them being closed.
>
> I've
On 07/18/2014 06:45 AM, Petr Mládek wrote:
> On Thu 2014-07-17 09:09:10, Alex Elder wrote:
>> If a log record has LOG_PREFIX set, its predecessor record should be
>> terminated if it was marked LOG_CONT. In devkmsg_read(), this
>> condition was being ignored, which would lead to such records
>>
From: Jeff Mahoney
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 22e7478ddbcb670e33fab72d0bbe7c394c3a2c84 upstream.
Prior to commit 0e4f6a791b1e (Fix reiserfs_file_release()), reiserfs
truncates serialized on i_mutex. They mostly still do,
Hi Linus,
Please pull hwmon fixes for Linux 3.16-rc6 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus
Thanks,
Guenter
--
The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab:
Linux 3.16-rc5 (2014-07-13
From: Jan Kara
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit c5c7b8ddfbf8cb3b2291e515a34ab1b8982f5a2d upstream.
Error recovery in ext4_alloc_branch() calls ext4_forget() even for
buffer corresponding to indirect block it did not allocate.
(cc'ing Hans who's now maintaining libahci-platform.)
On Fri, Jul 18, 2014 at 02:29:59PM +0200, Antoine Ténart wrote:
> Tejun, Kishon, Sebastian,
>
> I looked into the AHCI framework to see how to map PHYs and ports
> information. I see two ways of doing this:
> - We can attach the
From: Michal Nazarewicz
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit dc78327c0ea7da5186d8cbc1647bd6088c5c9fa5 upstream.
With a kernel configured with ARM64_64K_PAGES && !TRANSPARENT_HUGEPAGE,
the following is triggered at early boot:
From: Yann Droneaud
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit a8237b32a3faab155a5dc8f886452147ce73da3e upstream.
The i386 ABI disagrees with most other ABIs regarding alignment of
data type larger than 4 bytes: on most ABIs a padding
Hi,
On Fri, Jul 18, 2014 at 11:31:29AM +0200, Lothar Waßmann wrote:
> This patch makes it possible to use the musb driver with HW that
> requires external regulators or clocks.
can you provide an example of such HW ? Are you not using the internal
PHYs ?
> Signed-off-by: Lothar Waßmann
> ---
>
On Fri, Jul 18, 2014 at 03:46:29PM +0200, Richard Weinberger wrote:
> Am 18.07.2014 15:37, schrieb Guenter Roeck:
> > On 07/18/2014 01:23 AM, Borislav Petkov wrote:
> >> On Fri, Jul 18, 2014 at 12:29:37AM -0700, Guenter Roeck wrote:
> >>> First, 'abuse' is a relative term. It describes a use you
>
On Fri, Jul 18, 2014 at 01:05:46PM +0200, Vitaly Kuznetsov wrote:
> Konrad Rzeszutek Wilk writes:
>
> > On Tue, Jul 15, 2014 at 05:43:17PM +0200, Vitaly Kuznetsov wrote:
> >> Konrad Rzeszutek Wilk writes:
> >>
> >> > On Tue, Jul 15, 2014 at 03:40:37PM +0200, Vitaly Kuznetsov wrote:
> >> >>
From: Peter Hurley
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit ef8b9ddcb45fa3b1e11acd72be2398001e807d14 upstream.
If IGNBRK is set without either BRKINT or PARMRK set, some uart
drivers send a 0x00 byte for BREAK without the TTYBREAK
From: "Steven Rostedt (Red Hat)"
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 099ed151675cd1d2dbeae1dac697975f6a68716d upstream.
Disabling reading and writing to the trace file should not be able to
disable all function tracing callbacks.
On Wed, Jul 02, 2014 at 07:03:36PM +0100, Laura Abbott wrote:
> +void *dma_common_pages_remap(struct page **pages, size_t size,
> + unsigned long vm_flags, pgprot_t prot,
> + const void *caller)
> +{
> + struct vm_struct *area;
> +
> + area =
401 - 500 of 2038 matches
Mail list logo
