On Wed, 14 Aug 2013, Minchan Kim wrote:
> On Tue, Aug 13, 2013 at 04:21:30PM +, Christoph Lameter wrote:
> > On Tue, 13 Aug 2013, Minchan Kim wrote:
> >
> > > VM sometime want to migrate and/or reclaim pages for CMA, memory-hotplug,
> > > THP and so on but at the moment, it could handle only u
On Wed, Aug 14, 2013 at 03:15:39PM +0200, Peter Zijlstra wrote:
> These patches optimize preempt_enable by firstly folding the preempt and
> need_resched tests into one -- this should work for all architectures. And
> secondly by providing per-arch preempt_count implementations; with x86 using
> pe
Hi Christoph,
On Wed, Aug 14, 2013 at 04:36:44PM +, Christoph Lameter wrote:
> On Wed, 14 Aug 2013, Minchan Kim wrote:
>
> > On Tue, Aug 13, 2013 at 04:21:30PM +, Christoph Lameter wrote:
> > > On Tue, 13 Aug 2013, Minchan Kim wrote:
> > >
> > > > VM sometime want to migrate and/or reclai
On Wed, Aug 14, 2013 at 12:30:08PM +0200, Stephane Eranian wrote:
> On Wed, Aug 14, 2013 at 1:34 AM, Andi Kleen wrote:
> > On Tue, Aug 13, 2013 at 01:55:57PM +0200, Stephane Eranian wrote:
> >> This patch adds support for the new PERF_RECORD_MMAP2
> >> record type exposed by the kernel. This is an
On Fri, Aug 2, 2013 at 7:21 AM, Jingoo Han wrote:
> Add CONFIG_PM_SLEEP to suspend/resume functions to fix the build
> warnings when CONFIG_PM_SLEEP is not selected. This is because
> sleep PM callbacks defined by SET_SYSTEM_SLEEP_PM_OPS are only used
> when the CONFIG_PM_SLEEP is enabled.
>
> dr
On Fri, Aug 2, 2013 at 7:20 AM, Jingoo Han wrote:
> Add CONFIG_PM_RUNTIME to runtime_suspend/runtime_resume functions
> to fix the build warnings when CONFIG_PM_RUNTIME is not selected.
> This is because runtime PM callbacks defined by SET_RUNTIME_PM_OPS
> are only used when the CONFIG_PM_RUNTIME
On Wed, Jul 31, 2013 at 4:19 PM, Viresh Kumar wrote:
> CPUFreq core does following at multiple places:
> module_{get|put}(cpufreq_driver->owner)).
>
> This is done to make sure module doesn't get unloaded if it is currently in
> use.
> This will work only if the .owner field of cpufreq driver is
On Wed, 14 Aug 2013 12:22:49 -0400
Joseph Salisbury wrote:
> BugLink: http://bugs.launchpad.net/bugs/1210848
>
> On an ASUSTek G60JX laptop, the intel_ips driver spams the log with a warning
> message: "ME failed to update for more than 1s, likely hung". This ME
> doesn't support the feature,
Thanks Joerg.
> -Original Message-
> From: Joerg Roedel [mailto:j...@8bytes.org]
> Sent: Wednesday, August 14, 2013 9:45 PM
> To: Sethi Varun-B16395
> Cc: io...@lists.linux-foundation.org; linuxppc-...@lists.ozlabs.org;
> linux-kernel@vger.kernel.org; b...@kernel.crashing.org;
> ga...@kern
On 08/13/2013 11:53 PM, J. Bruce Fields wrote:
> On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan Kara wrote:
>> On Sun 11-08-13 11:48:49, Toralf Förster wrote:
>>> so that the server either crashes (if it is a user mode linux image) or at
>>> least its reboot functionality got broken
>>> - if the NF
On Fri, 9 Aug 2013, Konrad Rzeszutek Wilk wrote:
> > + * requested. The new pages are going to be "pinned": it's guaranteed
> > + * that their p2m mapping won't be changed until explicitly "unpinned".
>
> What if you try to balloon them out? What happens then? Does that
> unpin them automatically?
On Fri, 9 Aug 2013, Konrad Rzeszutek Wilk wrote:
> > > +struct xen_get_dma_buf {
> > > +/*
> > > + * [IN] Details of memory extents to be exchanged (GMFN bases).
> > > + * Note that @in.address_bits is ignored and unused.
> >
> > O, why? What if the user wants to be it under 2G?
>
On Tue, Jul 30, 2013 at 12:01 AM, Stephen Warren wrote:
> I was thinking more about people writing the device trees that define
> these states; they need to explicitly make the choice re: overlapping
> states or independent states. We should not plan to obsolete any current
> usage of overlapping
Hi Greg,
Apologies if this question is due to my ignorance of kernel development
practices. Feel free to point me at documentation.
I noticed that you applied this patch to the 3.10, 3.4, and 3.0 trees. On
kernel.org, it looks like 3.2 is also a longterm kernel. Why was this
patch not applie
On Wed, Aug 14, 2013 at 03:48:35PM +0300, Adrian Hunter wrote:
SNIP
> index 81c170f..4c97f36 100644
> --- a/tools/perf/util/evsel.c
> +++ b/tools/perf/util/evsel.c
> @@ -1389,7 +1389,6 @@ int perf_evsel__parse_sample(struct perf_evsel *evsel,
> union perf_event *event,
> }
>
> if (
On Wed, Aug 14, 2013 at 05:16:42PM +0100, Mel Gorman wrote:
> On Thu, Aug 15, 2013 at 12:52:29AM +0900, Minchan Kim wrote:
> > Hi Mel,
> >
> > On Wed, Aug 14, 2013 at 09:57:11AM +0100, Mel Gorman wrote:
> > > On Wed, Aug 14, 2013 at 12:45:41PM +0800, Xishi Qiu wrote:
> > > > A large free page budd
On Wed, Aug 14, 2013 at 03:48:34PM +0300, Adrian Hunter wrote:
> And store the parsed value there. Note that the 'abi' is
> 0 (no registers), 1 (32-bit registers) or 2 (64-bit registers),
> but the registers are anyway copied one-by-one as 64-bit
> values onto the event i.e. see 'perf_output_sampl
On 08/14/2013 10:25 AM, Linus Walleij wrote:
> Print out the affected group name on activation of pin mux
> settings, and warn if you cannot free a pin that should have
> been part of a certain setting.
> diff --git a/drivers/pinctrl/pinmux.c b/drivers/pinctrl/pinmux.c
> @@ -411,9 +415,14 @@ int
Adding the name field helps when printing error messages referring to
specific binfmts
Signed-off-by: Zach Levis
---
fs/binfmt_aout.c|1 +
fs/binfmt_elf.c |5 +
fs/binfmt_elf_fdpic.c |1 +
fs/binfmt_em86.c|1 +
fs/binfmt_flat.c|1 +
fs/bi
Obligatory first-patchset whitespace commit
Signed-off-by: Zach Levis
---
fs/binfmt_aout.c |8
fs/binfmt_elf.c | 38 +++---
fs/binfmt_elf_fdpic.c |8
fs/binfmt_em86.c |9 ++---
fs/binfmt_flat.c | 26 ++
With these changes, when a binfmt loop is encountered,
the ELOOP will propogate back to the 0 depth. At this point the
argv and argc values will be reset to what they were originally and an
attempt is made to continue with the following binfmt handlers.
Example: a qemu is configured to run 64-bit
This v4 is based off Oleg's changes from "exec: more cleanups" and "exec: minor
cleanups + minor fix"
It incorporates Oleg and Andrew's suggestions and takes care of the issue from
Dan's patch "fs/binfmts: double unlock in search_binary_handler()"
New in v4 is how we handle resetting the linux_
On 08/14/2013 10:14 AM, Alan Stern wrote:
> On Wed, 14 Aug 2013, Mark Brown wrote:
>
>> On Wed, Aug 14, 2013 at 10:27:26AM -0400, Alan Stern wrote:
>>> On Wed, 14 Aug 2013, Mark Brown wrote:
>>
I'd expect that we're just looking at hooks around connection and
disconnection here here - if
On 8/14/2013 9:07 AM, Akinobu Mita wrote:
> The definisions of __ffs(), __fls(), and ffs() for tile are almost same
> as asm-generic/bitops-*.h. The only difference is that it is defined
> as __always_inline or inline. So this switches to use those headers.
>
> Signed-off-by: Akinobu Mita
> Cc:
On 08/14/2013 10:27 AM, Linus Walleij wrote:
> On Wed, Aug 14, 2013 at 6:21 PM, Stephen Warren wrote:
>> On 08/14/2013 09:54 AM, Linus Walleij wrote:
>>> On Wed, Aug 14, 2013 at 7:26 AM, Sonic Zhang wrote:
>>>
From: Sonic Zhang
One peripheral may share part of its pins with the 2n
2013/8/15 Dan Carpenter :
> This is supposed to be testing "i < ARRAY_SIZE()" instead of just
> "ARRAY_SIZE()".
>
> Signed-off-by: Dan Carpenter
>
> diff --git a/drivers/regulator/88pm800.c b/drivers/regulator/88pm800.c
> index 58e9b74..3459f60 100644
> --- a/drivers/regulator/88pm800.c
> +++ b/dr
On Wed, Aug 14, 2013 at 6:21 PM, Stephen Warren wrote:
> On 08/14/2013 09:54 AM, Linus Walleij wrote:
>> On Wed, Aug 14, 2013 at 7:26 AM, Sonic Zhang wrote:
>>
>>> From: Sonic Zhang
>>>
>>> One peripheral may share part of its pins with the 2nd
>>> peripheral and the other pins with the 3rd. If
Print out the affected group name on activation of pin mux
settings, and warn if you cannot free a pin that should have
been part of a certain setting.
Cc: Sonic Zhang
Signed-off-by: Linus Walleij
---
drivers/pinctrl/pinmux.c | 35 +--
1 file changed, 29 insertio
BugLink: http://bugs.launchpad.net/bugs/1210848
On an ASUSTek G60JX laptop, the intel_ips driver spams the log with a warning
message: "ME failed to update for more than 1s, likely hung". This ME doesn't
support the feature, so requesting it be blacklisted for now.
Signed-off-by: Joseph Sal
On 08/14/2013 09:54 AM, Linus Walleij wrote:
> On Wed, Aug 14, 2013 at 7:26 AM, Sonic Zhang wrote:
>
>> From: Sonic Zhang
>>
>> One peripheral may share part of its pins with the 2nd
>> peripheral and the other pins with the 3rd. If it requests all pins
>> when part of them has already be reques
Hi André,
On 14/08/13 15:07, André Hentschel wrote:
Hi Jonathan,
Any updates on this?
I was holding out to see the version with ldrd at the top, as discussed
below - I never saw a version with that change? I'd meant to ping you to
see if that was coming, sorry.
[...]
[...]
Now we've on
There are some cases where checkpatch can take
a long time to complete. Reduce the likelihood
of this long run-time by adding a new test for
lines with and without comments and eliminating
checks on lines with only comments.
This reduces the number of "ctx_statement_block"
calls, and also the num
From: Tuukka Tikkanen
The menu governor uses a static function get_typical_interval() to
try to detect a repeating pattern of wakeups. The previous interval
durations are stored as an array of unsigned ints, but the arithmetic
in the function is performed exclusively as 64 bit values, even when
t
From: Tuukka Tikkanen
Field predicted_us value can never exceed expected_us value, but it has
a potentially larger type. As there is no need for additional 32 bits of
zeroes on 32 bit plaforms, change the type of predicted_us to match the
type of expected_us.
Field correction_factor is used to s
From: Tuukka Tikkanen
Struct menu_device member intervals is declared as u32, but the value
stored is (unsigned) int. The type is changed to match the value being
stored.
Signed-off-by: Tuukka Tikkanen
---
drivers/cpuidle/governors/menu.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-
From: Tuukka Tikkanen
The function get_typical_interval() initializes a number of variables
that are immediately after declarations assigned constant values.
In addition, there are multiple assignments on a single line, which
is explicitly forbidden by Documentation/CodingStyle.
This patch remov
From: Tuukka Tikkanen
This series of patches fixes some bugs, style issues and wild use of
variable types in cpuidle menu governor. One of the bugs is a logic
flaw where a detected previously recurring pattern is given priority
over known guaranteed earlier wakeup. The others involve value
overfl
From: Tuukka Tikkanen
This patch prevents cpuidle menu governor from using repeating interval
prediction result if the idle period predicted is longer than the one
allowed by shortest running timer.
Signed-off-by: Tuukka Tikkanen
---
drivers/cpuidle/governors/menu.c |5 -
1 file change
From: Tuukka Tikkanen
This patch rearranges a if-return-elsif-goto-fi-return sequence into
if-return-fi-if-return-fi-goto sequence. The functionality remains the
same. Also, a lengthy comment that did not describe the functionality
in the order it occurs is split into half and top half is moved c
On Wed, Aug 14, 2013 at 10:06:08AM -0600, Shuah Khan wrote:
> Is this what you have in mind or does my original patch set minus
> the amd_event and drivers/iommu/amd_iommu.c change?
>
> Patch 1:
> drivers/iommu/Makefile
> drivers/iommu/iommu-traces.c
> include/trace/events/iommu.h
>
> One patch f
From: Tuukka Tikkanen
get_typical_interval() uses int_sqrt() in calculation of standard
deviation. The formal parameter of int_sqrt() is unsigned long, which
may on some platforms be smaller than the 64 bit unsigned integer used
as the actual parameter. The overflow can occur frequently when actu
From: Tuukka Tikkanen
The menu governor has a number of tunable constants that may be changed
in the source. If certain combination of values are chosen, an overflow
is possible when the correction_factor is being recalculated.
This patch adds a warning regarding this possibility and describes t
Hi Luigi,
On Wed, Aug 14, 2013 at 08:53:31AM -0700, Luigi Semenzato wrote:
> During earlier discussions of zswap there was a plan to make it work
> with zsmalloc as an option instead of zbud. Does zbud work for
AFAIR, it was not an optoin but zsmalloc was must but there were
several objections be
On Thu, Aug 15, 2013 at 12:52:29AM +0900, Minchan Kim wrote:
> Hi Mel,
>
> On Wed, Aug 14, 2013 at 09:57:11AM +0100, Mel Gorman wrote:
> > On Wed, Aug 14, 2013 at 12:45:41PM +0800, Xishi Qiu wrote:
> > > A large free page buddy block will continue many times, so if the page
> > > is free, skip th
On 08/14/2013 09:06 AM, Peter Zijlstra wrote:
> On Wed, Aug 14, 2013 at 05:39:11PM +0200, Mike Galbraith wrote:
>> On Wed, 2013-08-14 at 06:47 -0700, H. Peter Anvin wrote:
>>
>>> On x86, you never want to take the address of a percpu variable if you
>>> can avoid it, as you end up generating code l
On Wed, Aug 14, 2013 at 09:56:11AM +, Sethi Varun-B16395 wrote:
> Please find the .config file attached with this mail.
Fantastic, thanks. The build works fine, I'll include the driver into my
next-branch. I also have two minor clean-up patches on-top, just if you
where wondering.
Jo
This is supposed to be testing "i < ARRAY_SIZE()" instead of just
"ARRAY_SIZE()".
Signed-off-by: Dan Carpenter
diff --git a/drivers/regulator/88pm800.c b/drivers/regulator/88pm800.c
index 58e9b74..3459f60 100644
--- a/drivers/regulator/88pm800.c
+++ b/drivers/regulator/88pm800.c
@@ -302,7 +302,7
On Wed, 14 Aug 2013, Mark Brown wrote:
> On Wed, Aug 14, 2013 at 10:27:26AM -0400, Alan Stern wrote:
> > On Wed, 14 Aug 2013, Mark Brown wrote:
>
> > > I'd expect that we're just looking at hooks around connection and
> > > disconnection here here - if we're looking at much more it seems like we
On 08/13/2013 11:24 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Wednesday 14 August 2013 12:43 AM, Stephen Warren wrote:
>> On 08/12/2013 11:37 PM, Kishon Vijay Abraham I wrote:
>>> The Palmas device contains only a USB VID detector, so added a
>>> compatible type *ti,palmas-usb-vid*. Dint remo
Hi guys,
this is all 3.12 material, please pull.
Thanks!
The following changes since commit 3b2f64d00c46e1e4e9bd0bb9bb12619adac27a4b:
Linux 3.11-rc2 (2013-07-21 12:05:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/edac_for_3.
On 08/13/2013 06:03 PM, Andi Kleen wrote:
On Mon, Aug 12, 2013 at 09:43:43PM -0400, Peter Hurley wrote:
On 08/09/2013 05:11 PM, Andi Kleen wrote:
When I run emacs over ssh terminal (no X) on 3.11-rc3 it often ignores key
strokes. I first thought the system was busy or so, but when
stracing th
On 08/07/2013 08:42 AM, Akinobu Mita wrote:
The return type of ffs() is 'int' on all architectures except cris and
hexagon. This unifies the return type to 'int'.
The problem I'm seeing is that the following line generates a warning
on cris and hexagon because of the mismatch between format '%u
On 08/14/13 05:59, Ivan T. Ivanov wrote:
> +}
> +
> +static const struct of_device_id of_dwc3_matach[] = {
match? Maybe you can make it all one line too { .compatible = "qcom,dwc3" }
> + {
> + .compatible = "qcom,dwc3",
> + },
> + { },
> +};
> +MODULE_DEVICE_TABLE(of, of_d
On Wed, Aug 14, 2013 at 05:39:11PM +0200, Mike Galbraith wrote:
> On Wed, 2013-08-14 at 06:47 -0700, H. Peter Anvin wrote:
>
> > On x86, you never want to take the address of a percpu variable if you
> > can avoid it, as you end up generating code like:
> >
> > movq %fs:0,%rax
> > subl $1
Hi Joerg,
Thanks for the feedback.
On 08/14/2013 08:17 AM, Joerg Roedel wrote:
Hi Shuah,
thanks for doing this. I have a few suggestions for improvements.
On Tue, Jul 30, 2013 at 08:57:09AM -0600, Shuah Khan wrote:
iommu:add_device_to_group
iommu:remove_device_from_group
iommu:attach_device_
> I have no response from Samuel regarding this patch.
> Could you take care of it, I can rebase it again if necessary.
Yes, please rebase onto v3.11-rc5 and resubmit.
Thanks.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Faceboo
On 8/14/2013 2:46 AM, Andrew Morton wrote:
> On Tue, 13 Aug 2013 19:32:37 -0400 Chris Metcalf wrote:
>
>> On 8/13/2013 7:29 PM, Tejun Heo wrote:
>>> Hello,
>>>
>>> On Tue, Aug 13, 2013 at 06:53:32PM -0400, Chris Metcalf wrote:
int lru_add_drain_all(void)
{
- return schedule_on_ea
On Wed, Aug 14, 2013 at 06:47:45AM -0700, H. Peter Anvin wrote:
> I still don't see this using a decrement of the percpu variable
> anywhere. The C compiler doesn't know how to generate those, so if I'm
> not completely wet we will end up relying on sub_preempt_count()...
> which, because it reli
Hi,
when changing the refresh rate of my laptop display with xrandr on 3.11.0-rc5,
like:
xrandr --output LVDS1 --rate 59.9 --mode 1920x1080
The following WARNING is generated:
[ 50.018055] [drm:intel_pipe_config_compare] *ERROR* mismatch in
adjusted_mode.flags (expected 1, found 0)
[ 50.01
On 08/13/2013 11:37 AM, Alexander Holler wrote:
Am 13.08.2013 16:58, schrieb Benjamin Tissoires:
hid_scan_report() implements its own HID report descriptor parsing.
It was
fine until we added the SENSOR_HUB detection. It is going to be even
worse
with the detection of Win 8 certified touchscre
* Waiman Long wrote:
> On 08/14/2013 06:20 AM, Ingo Molnar wrote:
> >* Waiman Long wrote:
> >
> >>
> >>I would like to share with you a rwlock related system crash that I
> >>encountered during my testing with hackbench on an 80-core DL980. The
> >>kernel crash because of a "watchdog detected h
On 08/14/2013 02:19 AM, Alexey Kardashevskiy wrote:
This reverts commit f83331bab149e29fa2c49cf102c0cd8c3f1ce9f9.
As the tests PPC64 (powernv platform) show, IOMMU pages are leaking
when transferring big amount of small packets (<=64 bytes),
"ping -f" and waiting for 15 seconds is the simplest w
On Tue, Aug 13, 2013 at 04:57:30PM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker wrote:
>
> > > > 19 files changed, 534 insertions(+), 326 deletions(-)
> > >
> > > When merged to -tip it causes this build error:
> > >
> > > kernel/time/tick-sched.c:186:3: error: 'have_nohz_full_mask' u
On Wed, Aug 14, 2013 at 7:26 AM, Sonic Zhang wrote:
> From: Sonic Zhang
>
> One peripheral may share part of its pins with the 2nd
> peripheral and the other pins with the 3rd. If it requests all pins
> when part of them has already be requested and owned by the 2nd
> peripheral, this request fa
Hi Mel,
On Wed, Aug 14, 2013 at 09:57:11AM +0100, Mel Gorman wrote:
> On Wed, Aug 14, 2013 at 12:45:41PM +0800, Xishi Qiu wrote:
> > A large free page buddy block will continue many times, so if the page
> > is free, skip the whole page buddy block instead of one page.
> >
> > Signed-off-by: Xis
During earlier discussions of zswap there was a plan to make it work
with zsmalloc as an option instead of zbud. Does zbud work for
compression factors better than 2:1? I have the impression (maybe
wrong) that it does not. In our use of zram (Chrome OS) typical
overall compression ratios are betw
On 08/14/2013 08:39 AM, Mike Galbraith wrote:
>
> ..so could the rq = cpu_rq(cpu) sequence be improved cycle expenditure
> wise by squirreling rq pointer away in a percpu this_rq, and replacing
> cpu_rq(cpu) above with a __this_cpu_read(this_rq) version of this_rq()?
>
Yes.
-hpa
--
To
On Tue, Aug 13, 2013 at 7:04 AM, Sonic Zhang wrote:
> v2-changes:
> - Remove unlinke() directive.
Fine, but now you also have all my other comments to take care of :-)
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to maj
On Wed, Aug 14, 2013 at 10:27:26AM -0400, Alan Stern wrote:
> On Wed, 14 Aug 2013, Mark Brown wrote:
> > I'd expect that we're just looking at hooks around connection and
> > disconnection here here - if we're looking at much more it seems like we
> > must be doing something wrong.
> Connection a
Hi Henrik,
On 13/08/13 21:17, rydb...@euromail.se wrote:
> Hi Benjamin,
>
> thanks for the patches, things are looking a lot better this way.
thanks for the review :)
>
>> hid_scan_report() implements its own HID report descriptor parsing. It was
>> fine until we added the SENSOR_HUB detectio
On Tue, Jul 16, 2013 at 12:55 PM, Sonic Zhang wrote:
> From: Sonic Zhang
>
> Select PINCTRL_ADI2 for bf54x and bf60x by default.
>
> Signed-off-by: Sonic Zhang
(...)
> +++ b/arch/blackfin/mach-bf548/include/mach/portmux.h
(...)
> +static const struct pinctrl_pin_desc adi_pads[] = {
> + P
On Wed, 2013-08-14 at 06:47 -0700, H. Peter Anvin wrote:
> On x86, you never want to take the address of a percpu variable if you
> can avoid it, as you end up generating code like:
>
> movq %fs:0,%rax
> subl $1,(%rax)
Hmmm..
#define cpu_rq(cpu) (&per_cpu(runqueues, (cpu
Hi Lee,
I have no response from Samuel regarding this patch.
Could you take care of it, I can rebase it again if necessary.
Regards
Andrzej
On 07/17/2013 09:45 AM, Andrzej Hajda wrote:
> Hi Samuel,
>
> A while ago I have send rebased patch adding device-tree support for
> max77693 as you asked:
On Tue, Jul 16, 2013 at 12:55 PM, Sonic Zhang wrote:
> From: Sonic Zhang
>
> - Remove non gpio lib code from blackfin architecture.
> - Limit the lagecy blackfin gpio driver to bf5xx processors only.
> - Remove unused definition of the pint power functions.
>
> Signed-off-by: Sonic Zhang
This
> ---
> include/linux/mfd/as3722-reg.h | 495
>
So the way you've split up the patch isn't quite right. It shouldn't
be split by files, rather by functionality.
Quoting from Documentation/SubmittingPatches:
"If your changes produce a lot of deltas, you
Quoting Rui Xiang (rui.xi...@huawei.com):
> On 2013/8/8 9:37, Gao feng wrote:
> > On 08/07/2013 03:55 PM, Eric W. Biederman wrote:
> >>
> >> Since this still has not been addressed. I am going to repeat Andrews
> >> objection again.
> >>
> >> Isn't there a better way to get iptables information ou
On Wed, Aug 14, 2013 at 04:54:56PM +0200, Florian Lobmaier wrote:
> +static bool as3722_readable(struct device *dev, unsigned int reg)
> +{
> + switch (reg) {
> + case AS3722_SD0_VOLTAGE_REG:
Are there any gaps in this register map? If not just checking the range
would be easier (it look
On Wed, Aug 14, 2013 at 04:54:55PM +0200, Florian Lobmaier wrote:
> +static struct regmap_irq_chip as3722_irq_chip = {
> + .name = "as3722",
> + .irqs = as3722_irqs,
> + .num_irqs = ARRAY_SIZE(as3722_irqs),
> + .num_regs = 4,
> + .status_base = AS3722_INTERRUPTSTATUS1_REG,
> +
I'm going to comment on the format of the patches before I do the code
review.
The $SUBJECT line needs to use the same formatting as previous patches
accepted by the subsystem. In the case of MFD they're formatted like this:
mfd: :
This information can be obtained by issuing something like:
On 08/14/2013 06:20 AM, Ingo Molnar wrote:
* Waiman Long wrote:
I would like to share with you a rwlock related system crash that I
encountered during my testing with hackbench on an 80-core DL980. The
kernel crash because of a "watchdog detected hard lockup on cpu 79". The
crashing CPU was r
On Wed, 14 Aug 2013, Rami Rosen wrote:
> Hi,
> BTW, this is not the only NAPI issue here. When looking into cleanup
> of resources in this driver, a call to netif_napi_del() is missing
> (though there is a call to napi_disable(), which is not enough for
> proper cleanup).
Actually, netif_napi_de
On 13/08/13 20:37, Alexander Holler wrote:
> Am 13.08.2013 16:58, schrieb Benjamin Tissoires:
>> hid_scan_report() implements its own HID report descriptor parsing. It
>> was
>> fine until we added the SENSOR_HUB detection. It is going to be even
>> worse
>> with the detection of Win 8 certified to
Hi,
On Wednesday 14 August 2013 04:34 AM, Tomasz Figa wrote:
> On Wednesday 14 of August 2013 00:19:28 Sylwester Nawrocki wrote:
>> W dniu 2013-08-13 14:05, Kishon Vijay Abraham I pisze:
>>> On Tuesday 13 August 2013 05:07 PM, Tomasz Figa wrote:
On Tuesday 13 of August 2013 16:14:44 Kishon Vi
On 08/14/2013 01:03 PM, Sudeep KarkadaNagesha wrote:
> On 14/08/13 11:51, Daniel Lezcano wrote:
>> On 08/14/2013 11:17 AM, Sudeep KarkadaNagesha wrote:
>>> On 14/08/13 10:08, Daniel Lezcano wrote:
On 08/13/2013 07:29 PM, Sudeep KarkadaNagesha wrote:
> From: Sudeep KarkadaNagesha
>
>>>
Signed-off-by: Florian Lobmaier
---
drivers/regulator/Kconfig|7 +
drivers/regulator/Makefile |1 +
drivers/regulator/as3722-regulator.c | 1336 ++
3 files changed, 1344 insertions(+), 0 deletions(-)
create mode 100644 drivers/regula
Signed-off-by: Florian Lobmaier
---
include/linux/mfd/as3722-reg.h | 495
1 files changed, 495 insertions(+), 0 deletions(-)
create mode 100644 include/linux/mfd/as3722-reg.h
diff --git a/include/linux/mfd/as3722-reg.h b/include/linux/mfd/as3722-reg.h
Signed-off-by: Florian Lobmaier
---
include/linux/mfd/as3722-plat.h | 238 +++
1 files changed, 238 insertions(+), 0 deletions(-)
create mode 100644 include/linux/mfd/as3722-plat.h
diff --git a/include/linux/mfd/as3722-plat.h b/include/linux/mfd/as3722-plat
now using git send-email and splitted mfd patch into multiple patches (4).
Suggestions from 23.05.2013 added.
Signed-off-by: Florian Lobmaier
---
drivers/mfd/Kconfig | 15 +
drivers/mfd/Makefile |1 +
drivers/mfd/as3722-core.c | 747 +
Signed-off-by: Florian Lobmaier
---
drivers/mfd/as3722-regmap.c | 417 +++
1 files changed, 417 insertions(+), 0 deletions(-)
create mode 100644 drivers/mfd/as3722-regmap.c
diff --git a/drivers/mfd/as3722-regmap.c b/drivers/mfd/as3722-regmap.c
new file
Hi,
On Wed, 2013-08-14 at 09:20 -0500, Josh Cartwright wrote:
> On Wed, Aug 14, 2013 at 03:59:42PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > These drivers handles control and configuration of the HS
> > and SS USB PHY transceivers. They are part of the driver
> > which m
Occassionally events (e.g., context-switch, sched tracepoints) are losing
the conversion of sample data associated with a thread. For example:
$ perf record -e sched:sched_switch -c 1 -a -- sleep 5
$ perf script
ls 30482 [000] 1379727.583037: sched:sched_switch: prev_comm=ls
prev_pid=30482 .
On 08/13/2013 06:49 PM, Guenter Roeck wrote:
>
>> That is one aspect (hardware standardization)... but it is more to it
>> than that.
>
> I have to deal with lots of embedded / non-PC x86 based systems. Worst one
> I encountered so far was a board where the VGA memory space was re-used
> for an eep
Around Wed 14 Aug 2013 20:07:44 +0530 or thereabout, Viresh Kumar wrote:
> On 14 August 2013 20:05, Hans-Christian Egtvedt wrote:
>> Around Wed 14 Aug 2013 19:01:53 +0530 or thereabout, Viresh Kumar wrote:
>>> Many common initializations of struct policy are moved to core now and hence
>>> this dr
2013/8/12 Richard Genoud :
> Hi,
>
> I've found something peculiar while I was testing v3.11:
> There's a lot of directory missing (actually hiding) in /proc :
>
> /proc/sys/, /proc/fs/, /proc/bus/ etc...
> all the directories that are not PIDs are in "stealth mode":
> they don't appear with an ls
On Tue, 2013-08-13 at 22:23 +0100, Jonathan Cameron wrote:
> On 07/22/13 15:04, Hector Palacios wrote:
> > Some LRADC channels have fixed pre-dividers so they can measure
> > different voltages at full scale. The reference voltage allows to
> > expose a scaling attribute through the IIO sysfs so th
On Tue, Aug 06, 2013 at 12:20:16AM +0200, Sebastian Hesselbarth wrote:
> This fixes the wrong sync generation and sync calculation of TDA998x
> for HS/VS-based sync detection.
>
> Signed-off-by: Sebastian Hesselbarth
The plus point with this is that interlaced modes (1080i) do work with
the TDA9
Hi Luca,
On 30/07/2013 22:21, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho
---
In v3, use IRQ_TYPE_LEVEL_HIGH in the example, as sugg
Hey Andi!
On Mon, Aug 12, 2013 at 01:56:31AM +0200, Andi Kleen wrote:
>
> I really like the idea of using the spare slots in the radix tree
> for something useful. It's amazing we haven't used that before.
>
> I wonder if with some clever encoding even more information could be fit?
What do you
On 08/14/2013 05:44 AM, Peter Maydell wrote:
On 14 August 2013 11:33, Russell King - ARM Linux
wrote:
On Mon, Aug 12, 2013 at 04:04:08PM -0700, Guenter Roeck wrote:
Hacked diff is below. Can I write that up as clean patch and submit it,
or do we need a test on real hardware ?
Well, if we wan
On 14 August 2013 20:05, Hans-Christian Egtvedt wrote:
> Around Wed 14 Aug 2013 19:01:53 +0530 or thereabout, Viresh Kumar wrote:
>> Many common initializations of struct policy are moved to core now and hence
>> this driver doesn't need to do it. This patch removes such code.
>>
>> Most recent of
401 - 500 of 895 matches
Mail list logo
