From: Daniel Tang
Changelog v2:
* Rename ci13xxx to ci_hdrc
* Fixed alignment issues
The USB controller in TI-NSPIRE calculators are based off either Freescale's
USB OTG controller or the USB controller found in the IMX233, both of which
are Chipidea compatible.
This patch adds a device tree
(2013/11/24 5:16), Oleg Nesterov wrote:
> The probe can dump the registers or memory, but it is not possible
> to dump, say, current->pid. This patch adds the pseudo regs table,
> currently it has only two methods to get current/smp_processor_id
> but it can be trivially extended.
Good catch! :)
This patch (commit: 3a72660b07) is only slated for stable 3.12, but
should go to 3.10/11 as well, no?
On Wed, 2013-11-20 at 11:44 +0100, Jesper Nilsson wrote:
> Commit 2caacaa82a51b78fc0c800e206473874094287ed restructured
> the ipc shm to shorten critical region, but introduced a path
> where
On Wed, Nov 13, 2013 at 4:14 PM, Grant Likely wrote:
> On Wed, 13 Nov 2013 09:17:01 +1000, Peter Crosthwaite
> wrote:
>> On Tue, Nov 12, 2013 at 6:50 PM, Grant Likely
>> wrote:
>> > On Tue, 12 Nov 2013 17:49:37 +1000, Peter Crosthwaite
>> > wrote:
>> >> Hi Grant,
>> >>
>> >> On Tue, Nov 12,
Trusted Foundations is a TrustZone-based secure monitor for ARM that
can be invoked using the same SMC-based API on supported platforms.
This patch adds initial basic support for Trusted Foundations using
the ARM firmware API. Current features are limited to the ability to
boot secondary
Support for Trusted Foundations is light and allows the kernel to run on
a wider range of devices, so enable it by default.
Signed-off-by: Alexandre Courbot
Reviewed-by: Tomasz Figa
Reviewed-by: Stephen Warren
---
arch/arm/configs/tegra_defconfig | 1 +
1 file changed, 1 insertion(+)
diff
Not all Tegra devices can set the CPU reset handler in the same way.
In particular, devices using a TrustZone secure monitor cannot set it
up directly and need to ask the firmware to do it.
This patch separates the act of setting the reset handler from its
preparation, so the former can be
Use a firmware operation to set the CPU reset handler and only resort to
doing it ourselves if there is none defined.
This supports the booting of secondary CPUs on devices using a TrustZone
secure monitor.
Signed-off-by: Alexandre Courbot
Reviewed-by: Tomasz Figa
Reviewed-by: Stephen Warren
Add the "tlm" prefix for Trusted Logic Mobility.
Signed-off-by: Alexandre Courbot
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
Add the Device Tree bindings documentation for the Trusted Foundation
secure monitor.
Signed-off-by: Alexandre Courbot
---
.../arm/firmware/tlm,trusted-foundations.txt | 20
1 file changed, 20 insertions(+)
create mode 100644
Register the firmware operations for Trusted Foundations if the device
tree indicates it is active on the device.
Signed-off-by: Alexandre Courbot
Reviewed-by: Tomasz Figa
Reviewed-by: Stephen Warren
---
Documentation/devicetree/bindings/arm/tegra.txt | 5 +
arch/arm/mach-tegra/Kconfig
New rebase that should be ready-to-apply on the latest Tegra tree. The last
remaining blocker is Russell's approval for this series and it is my hope to
obtain it with this version.
There has been quite some debate around this series, notably about the SMC
calling conventions and whether the
Jiri Olsa wrote:
>> The incomplete bit is marked using a TODO; removing two trailing '%'
>> symbols doesn't seem to work. Can someone please tell me how to fix
>> this problem?
>
> aah here it is..
I fixed it and sent another iteration.
--
To unsubscribe from this list: send the line
In
$ perf diff -c ratio
color the Ratio column using percent_color_snprintf().
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Ramkumar Ramachandra
---
tools/perf/builtin-diff.c | 20
1 file changed, 20 insertions(+)
diff --git
Generalize the function so that we can accommodate all three comparison
methods: delta, ratio, and wdiff.
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Ramkumar Ramachandra
---
tools/perf/builtin-diff.c | 47 +--
1 file
Color the numbers in the Delta column either green or red depending on
whether the number is positive or negative.
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Ramkumar Ramachandra
---
tools/perf/builtin-diff.c | 37 -
1 file
In
$ perf diff -c wdiff:M,N
color the numbers in the Weighted Diff column either green or red,
depending on whether the number is positive or negative.
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Ramkumar Ramachandra
---
tools/perf/builtin-diff.c | 22
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Ramkumar Ramachandra
---
tools/perf/builtin-diff.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/perf/builtin-diff.c b/tools/perf/builtin-diff.c
index 3b67ea2..79e0448 100644
--- a/tools/perf/builtin-diff.c
+++
Hi,
This round fixes two problems in the last round:
- In [2/5], the color version includes the 0.01 threshold that was
present in the non-color version (thanks to Jiri).
- In [4/5], the trailing '%' is gone (maked as a TODO in the last
round).
and introduces one new patch for wdiff:
This patch inserts information of bio types in more detail.
So, we can now see REQ_META and REQ_PRIO too.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 4 ++--
include/trace/events/f2fs.h | 22 +-
2 files changed, 19 insertions(+), 7 deletions(-)
diff --git
Hi Rob,
On Sun, Nov 24, 2013 at 8:31 AM, Rob Landley wrote:
>> > Linus, I hope this can be merged during the -rc cycle of 3.13, since the
>> > gpiod_ interface is going to be introduced there. It would not make much
>> > sense for it to come without its documentation.
>>
>> You're right of
On 11/22/2013 08:13 PM, Daniel Lezcano wrote:
>
> Hi Alex,
>
> I tried on my Xeon server (2 x 4 cores) your patchset and got the
> following result:
>
> kernel a5d6e63323fe7799eb0e6 / + patchset
>
> hackbench -T -s 4096 -l 1000 -g 10 -f 40
> 27.604 38.556
Wondering if the
On Sat, 2013-11-23 at 13:01 +0100, Peter Zijlstra wrote:
> > I used to have a patch to schedule() that would always immediately fall
> > through and only actually block on the second call; it illustrated the
> > problem really well, in fact so well the kernels fails to boot most
> > times.
>
> I
On Fri, 2013-11-22 at 22:33 -0800, Darren Hart wrote:
> On Fri, 2013-11-22 at 16:56 -0800, Davidlohr Bueso wrote:
> > All wake_futex() callers already verify that the we are not dealing with
> > a pi futex_q, so we can remove the redundant WARN() check, as this is never
> > triggered anyway.
> >
On Sat, 2013-11-23 at 19:46 -0800, Linus Torvalds wrote:
> On Sat, Nov 23, 2013 at 5:16 AM, Thomas Gleixner wrote:
> >
> > Now the question is why we queue the waiter _AFTER_ reading the user
> > space value. The comment in the code is pretty non sensical:
> >
> >* On the other hand, we
On 11/22/2013 08:13 PM, Daniel Lezcano wrote:
>>
>> The git tree for this patchset at:
>> g...@github.com:alexshi/power-scheduling.git no-load-idx
>> Since Fengguang had included this tree into his kernel testing system.
>> and I haven't get a regression report until now. I suppose it is fine
>>
If CONFIG_F2FS_CHECK_FS is unset, we don't need to add any debugging overhead.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 72718ef..417280a 100644
--- a/fs/f2fs/f2fs.h
+++
Hello Maintainers:
Please help check it when you have time, thanks.
I changed my mail address -- I have to leave original company, so at
present, I need be as a volunteer to Public Open Source (just like
another quite a few volunteers).
Within this month, I still want to let hexagon pass
On Saturday 23 November 2013 11:10 PM, Greg Kroah-Hartman wrote:
> On Sat, Nov 23, 2013 at 10:45:37PM -0500, Santosh Shilimkar wrote:
>> On Saturday 23 November 2013 10:44 PM, Greg Kroah-Hartman wrote:
>>> On Sat, Nov 23, 2013 at 10:37:01PM -0500, Santosh Shilimkar wrote:
@@ -250,8 +249,8 @@
Hi,
2013-11-22 (금), 09:09 +0800, Chao Yu:
> Previously we read sit entries page one by one, this method lost the chance
> of reading contiguous page together. So we read pages as contiguous as
> possible for better mount performance.
>
> change log:
> o merge judgements/use 'Continue' or
On Sat, 23 Nov 2013 20:03:30 -0800 Kent Overstreet wrote:
> It was being open coded in a few places.
>
> Signed-off-by: Kent Overstreet
> Cc: Jens Axboe
> Cc: Joern Engel
> Cc: Prasad Joshi
> Cc: Neil Brown
> Cc: Chris Mason
Acked-by: NeilBrown
for the drivers/md/md.c bits, however...
Hello Maintainers:
Please help check it when you have time, thanks.
I changed my mail address -- I have to leave original company, so at
present, I need be as a volunteer to Public Open Source (just like
another quite a few volunteers).
Within this month, I still want to let hexagon pass
On Sat, Nov 23, 2013 at 10:45:37PM -0500, Santosh Shilimkar wrote:
> On Saturday 23 November 2013 10:44 PM, Greg Kroah-Hartman wrote:
> > On Sat, Nov 23, 2013 at 10:37:01PM -0500, Santosh Shilimkar wrote:
> >> @@ -250,8 +249,8 @@ int __init dma_contiguous_reserve_area(phys_addr_t
> >> size,
Hi,
2013-11-23 (토), 10:53 +0800, Chao Yu:
> Hi,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> > Sent: Friday, November 22, 2013 5:11 PM
> > To: Chao Yu
> > Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> >
It was being open coded in a few places.
Signed-off-by: Kent Overstreet
Cc: Jens Axboe
Cc: Joern Engel
Cc: Prasad Joshi
Cc: Neil Brown
Cc: Chris Mason
---
block/blk-flush.c | 19 +--
drivers/md/md.c| 12 +---
fs/btrfs/check-integrity.c | 32
Otherwise prints would truncate the variables on LPAE machines.
Cc: Marek Szyprowski
Cc: Greg Kroah-Hartman
Signed-off-by: Santosh Shilimkar
---
Dropped accidental change pr_debug to pr_info from last version.
drivers/base/dma-contiguous.c |9 -
1 file changed, 4 insertions(+), 5
On Sun, 24 Nov 2013, Matthew Garrett wrote:
> On Sat, Nov 23, 2013 at 10:40:15PM -0200, Henrique de Moraes Holschuh wrote:
> > On Fri, 22 Nov 2013, Matthew Garrett wrote:
> > > We have userspace that relies on uevents of type
> > > BACKLIGHT_UPDATE_HOTKEY. I don't know that we have userspace that
Hi,
Again, this tracepoint alos can be integrated with write_bios like this.
>From e0360910b24624e40d92eb2e1949914339b83881 Mon Sep 17 00:00:00 2001
From: Chao Yu
Date: Sun, 24 Nov 2013 12:36:42 +0900
Subject: [PATCH] f2fs: adds a tracepoint for f2fs_submit_read_bio
This patch adds a
On Sat, Nov 23, 2013 at 5:16 AM, Thomas Gleixner wrote:
>
> Now the question is why we queue the waiter _AFTER_ reading the user
> space value. The comment in the code is pretty non sensical:
>
>* On the other hand, we insert q and release the hash-bucket only
>* after testing *uaddr.
On Saturday 23 November 2013 10:44 PM, Greg Kroah-Hartman wrote:
> On Sat, Nov 23, 2013 at 10:37:01PM -0500, Santosh Shilimkar wrote:
>> @@ -250,8 +249,8 @@ int __init dma_contiguous_reserve_area(phys_addr_t size,
>> phys_addr_t base,
>> *res_cma = cma;
>> cma_area_count++;
>>
>> -
On Saturday 23 November 2013 10:43 PM, Greg Kroah-Hartman wrote:
> On Sat, Nov 23, 2013 at 10:37:01PM -0500, Santosh Shilimkar wrote:
>> Otherwise prints would truncate the variables on LPAE machines.
>>
>> Cc: Marek Szyprowski
>> Cc: Greg Kroah-Hartman
>> Signed-off-by: Santosh Shilimkar
>>
On Sat, Nov 23, 2013 at 10:37:01PM -0500, Santosh Shilimkar wrote:
> @@ -250,8 +249,8 @@ int __init dma_contiguous_reserve_area(phys_addr_t size,
> phys_addr_t base,
> *res_cma = cma;
> cma_area_count++;
>
> - pr_info("CMA: reserved %ld MiB at %08lx\n", (unsigned long)size /
On Sat, Nov 23, 2013 at 10:37:01PM -0500, Santosh Shilimkar wrote:
> Otherwise prints would truncate the variables on LPAE machines.
>
> Cc: Marek Szyprowski
> Cc: Greg Kroah-Hartman
> Signed-off-by: Santosh Shilimkar
> ---
> drivers/base/dma-contiguous.c |9 -
> 1 file changed, 4
I read this: http://hardware.slashdot.org/comments.pl?sid=3102545=41270883
"to explain: the patents are there to protect people from physical harm due to
the possibility of idiotic companies creating non-interoperable products that
could potentially short-circuit things e.g. a lithium battery.
On 11/18/2013 03:34:20 AM, Linus Walleij wrote:
On Sat, Nov 16, 2013 at 1:34 PM, Alexandre Courbot
wrote:
> The first version received zero feedback, hopefully this one will
get more
> attention. :) Not much changes, just some more proofreading and the
fixes
> and improvements that came
Otherwise prints would truncate the variables on LPAE machines.
Cc: Marek Szyprowski
Cc: Greg Kroah-Hartman
Signed-off-by: Santosh Shilimkar
---
drivers/base/dma-contiguous.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/base/dma-contiguous.c
On Fri, Nov 22, 2013 at 12:25 PM, David Howells wrote:
> Linus Torvalds wrote:
>
>> So for future cases: if there are big independent overhauls of core
>> subsystems, I'd really like to see them kept separate, ok?
>
> Since the trusted and encrypted keys that Mimi and Dmitry deal with are also
>
On Thu, Nov 07, 2013 at 05:02:38PM +0800, Jisheng Zhang wrote:
> This patch fixes conflicting types for 'set_cpu_coherent' and fixes the
> following sparse warnings.
>
> arch/arm/mach-mvebu/system-controller.c:42:38:
> warning: symbol 'armada_370_xp_system_controller' was not declared. Should it
On Thu, Nov 07, 2013 at 04:59:33PM +0800, Jisheng Zhang wrote:
> This symbol is used only in this file. The patch fix the following
> sparse warning:
> warning: symbol 'of_cpu_clk_setup' was not declared. Should it be static?
>
> Signed-off-by: Jisheng Zhang
> ---
> drivers/clk/mvebu/clk-cpu.c
On Fri, Nov 01, 2013 at 02:58:16AM +, Zheng, Lv wrote:
> > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> > Sent: Thursday, October 31, 2013 8:22 PM
> >
> > On Thursday, October 31, 2013 05:08:50 AM Greg Kroah-Hartman wrote:
> > > On Thu, Oct 31, 2013 at 12:39:21PM +0100, Rafael J.
Hi,
We need to avoid redundancy as much as possible.
So, how about this patch?
>From 7b4a4f1628a1a793942c7f675e6afecece64b659 Mon Sep 17 00:00:00 2001
From: Chao Yu
Date: Wed, 20 Nov 2013 16:40:10 +0800
Subject: [PATCH] f2fs: adds a tracepoint for submit_read_page
This patch adds a tracepoint
Hi,
2013-11-22 (금), 12:41 +0900, Changman Lee:
> How about doing mark_page_accessed(page) in ra_nat_pages like
> ra_sit_pages to prevent readahead pages are reclaimed by VM?
Agreed.
I'll modify and merge this.
Thanks,
>
> On 목, 2013-11-21 at 18:35 +0900, Jaegeuk Kim wrote:
> > This patch
On 11/23/2013 07:22 PM, Pavel Machek wrote:
On Sat 2013-11-23 18:01:32, Ric Wheeler wrote:
On 11/23/2013 03:36 PM, Pavel Machek wrote:
On Wed 2013-11-20 08:02:33, Howard Chu wrote:
Theodore Ts'o wrote:
Historically, Intel has been really good about avoiding this, but
since they've moved to
On 11/23/2013 07:25 PM, One Thousand Gnomes wrote:
On Fri, 22 Nov 2013 10:59:25 -0500
Peter Hurley wrote:
Instrument .receive_buf() and read() paths with trace_printk's
to aid in debugging flow control changes.
tty devices have a device, we have a dev_dbg() layer. The old tty trace
predates
On 11/23/2013 07:23 PM, One Thousand Gnomes wrote:
On Fri, 22 Nov 2013 10:59:24 -0500
Peter Hurley wrote:
Only wakeup the _waiting_ reader, polls and/or writer(s).
Signed-off-by: Peter Hurley
---
drivers/tty/n_tty.c | 18 --
1 file changed, 12 insertions(+), 6
On 11/23/2013 07:26 PM, One Thousand Gnomes wrote:
On Fri, 22 Nov 2013 10:59:23 -0500
Peter Hurley wrote:
Distinguish if caller is n_tty_poll() or n_tty_read(), and
set the read/wakeup threshold accordingly.
Signed-off-by: Peter Hurley
Doh ignore previous.. yes that patch is right. I
On Fri, Nov 22, 2013 at 06:04:00PM -0500, Tejun Heo wrote:
>Hello,
>
>On Wed, Nov 20, 2013 at 12:51:21AM -0500, Tejun Heo wrote:
>> The patch is just extremely marginal. Ah well... why not? I'll apply
>> it once -rc1 drops.
>
>So, I was about to apply this patch but decided against it. It
Direct decompression into the page cache. If we fall back
to using an intermediate buffer (because we cannot grab all the
page cache pages) and we get a decompress fail, we forgot to
release the pages.
Reported-by: Roman Peniaev
Signed-off-by: Phillip Lougher
---
fs/squashfs/file_direct.c |
On 22/11/13 07:40, Roman Peniaev wrote:
Hello, Phillip.
one remark below:
+static int squashfs_read_cache(struct page *target_page, u64 block, int
bsize,
+ int pages, struct page **page)
+{
+ struct inode *i = target_page->mapping->host;
+ struct squashfs_cache_entry
> Yes, and I'm arguing that is a bug (as in, < 0.01% people are using
> hdparm correctly).
Generally speaking if you are using hdparm for tuning it means we need to
fix something in the ATA layer so you don't have to !
> I guess it would be safer not to reattach drives after power
> fail...
On Sat, Nov 23, 2013 at 10:40:15PM -0200, Henrique de Moraes Holschuh wrote:
> On Fri, 22 Nov 2013, Matthew Garrett wrote:
> > We have userspace that relies on uevents of type
> > BACKLIGHT_UPDATE_HOTKEY. I don't know that we have userspace that relies
> > on uevents of type
On Sunday, November 24, 2013 12:36:03 AM Rafael J. Wysocki wrote:
> On Saturday, November 23, 2013 03:07:01 PM Greg Kroah-Hartman wrote:
> > On Sun, Nov 24, 2013 at 12:12:59AM +0100, Rafael J. Wysocki wrote:
> > > On Saturday, November 23, 2013 02:53:58 PM Greg Kroah-Hartman wrote:
[...]
> > > >
On Thu, 21 Nov 2013 22:05:56 -0800
"David E. Box" wrote:
> +static int iosf_mbi_probe(struct platform_device *pdev)
> +{
> + struct resource *mem;
> +
> + /* Get and map MBI address space */
> + mem = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + iosf_mbi_data.addr =
On Fri, 22 Nov 2013, Matthew Garrett wrote:
> On Fri, Nov 22, 2013 at 09:36:01AM -0200, Henrique de Moraes Holschuh wrote:
> > On Thu, 21 Nov 2013, Matthew Garrett wrote:
> > > The uevent support was initially added to handle systems where pressing
> > > a hotkey generates an event (good) but the
On Fri, 22 Nov 2013 07:16:25 -0500
Peter Hurley wrote:
> Although the maximum allowable canonical line is specified to
> be 255 bytes (MAX_CANON), the practical limit has actually been
> the size of the line discipline read buffer (N_TTY_BUF_SIZE == 4096).
Looks good. MAX_CANON in SVID and
> 7) Rescan line discipline buffer when changing from non-canonical to canonical
> mode. The real problem with this approach (besides the inefficiency) is that
> this
> solution could break some (admittedly unknown) program that contrived to
> exchange
> data in non-canonical mode but read in
On Fri, 22 Nov 2013 10:59:23 -0500
Peter Hurley wrote:
> Distinguish if caller is n_tty_poll() or n_tty_read(), and
> set the read/wakeup threshold accordingly.
>
> Signed-off-by: Peter Hurley
Doh ignore previous.. yes that patch is right. I should pay attention to
0/7 8)
--
To unsubscribe
On Fri, 22 Nov 2013 10:59:25 -0500
Peter Hurley wrote:
> Instrument .receive_buf() and read() paths with trace_printk's
> to aid in debugging flow control changes.
tty devices have a device, we have a dev_dbg() layer. The old tty trace
predates this but there isn't really any excuse for not
On Fri, 22 Nov 2013 10:59:24 -0500
Peter Hurley wrote:
> Only wakeup the _waiting_ reader, polls and/or writer(s).
>
> Signed-off-by: Peter Hurley
> ---
> drivers/tty/n_tty.c | 18 --
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/tty/n_tty.c
On Sat 2013-11-23 18:01:32, Ric Wheeler wrote:
> On 11/23/2013 03:36 PM, Pavel Machek wrote:
> >On Wed 2013-11-20 08:02:33, Howard Chu wrote:
> >>Theodore Ts'o wrote:
> >>>Historically, Intel has been really good about avoiding this, but
> >>>since they've moved to using 3rd party flash
On Fri, 22 Nov 2013 10:59:23 -0500
Peter Hurley wrote:
> Distinguish if caller is n_tty_poll() or n_tty_read(), and
> set the read/wakeup threshold accordingly.
That looks very wrong to me. The poll() and read() wakeup should always
match. In addition if MIN_CHAR is set without a timeout then
> > And the 520 doesn't claim this feature (look for "enhanced power loss
> > protection" at http://ark.intel.com/products/66248), so that wouldn't
> > explain these results anyway.
>
> Correct i think intel simply ignores CMD_FLUSH on that drive - no idea
> why an they fixed this for their 330,
From: Rafael J. Wysocki
After commit bcdde7e221a8 (sysfs: make __sysfs_remove_dir() recursive)
I'm seeing traces analogous to the one below in Thunderbolt testing:
WARNING: CPU: 3 PID: 76 at /scratch/rafael/work/linux-pm/fs/sysfs/group.c:214
sysfs_remove_group+0x59/0xe0()
sysfs group
23.11.2013, 22:40, "Guenter Roeck" :
> ===
> Building sparc64:allmodconfig ... failed
> --
> Error log:
> arch/sparc/kernel/kgdb_64.c: In function 'kgdb_trap':
> arch/sparc/kernel/kgdb_64.c:162:7: error: implicit declaration of function
> 'exception_enter'
On 11/23/13, 2:44 AM, Jiri Olsa wrote:
so.. I understand you'll make changes anyway
and dont mind to rebase? ;-)
I can rebase.
David
--
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
This adds initial documentation for the pinctrl-msm8x74 driver.
Signed-off-by: Bjorn Andersson
---
.../bindings/pinctrl/qcom,msm8x74-pinctrl.txt | 86 ++
1 file changed, 86 insertions(+)
create mode 100644
This adds a pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm TLMM block.
Signed-off-by: Bjorn Andersson
---
drivers/pinctrl/Kconfig |6 +
drivers/pinctrl/Makefile |1 +
drivers/pinctrl/pinctrl-msm.c | 1118 +
This series adds a pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm TLMM block found in recent Qualcomm SoCs (8x60 and newer).
It designed with both v2 and v3 of the block in mind and comes with initial
definitions for the 8x74 SoCs.
This should be filled in with more data and
Add initial definition of parameters for pinctrl-msm for the msm8x74
platform.
Signed-off-by: Bjorn Andersson
---
drivers/pinctrl/Kconfig | 4 +
drivers/pinctrl/Makefile | 1 +
drivers/pinctrl/pinctrl-msm8x74.c | 641 ++
3 files
Building ARM with NO_BOOTMEM generates below warning. Using min_t
to find the correct alignment avoids the warning.
Cc: Tejun Heo
Cc: Andrew Morton
Signed-off-by: Santosh Shilimkar
---
mm/nobootmem.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/nobootmem.c
On Saturday, November 23, 2013 03:07:01 PM Greg Kroah-Hartman wrote:
> On Sun, Nov 24, 2013 at 12:12:59AM +0100, Rafael J. Wysocki wrote:
> > On Saturday, November 23, 2013 02:53:58 PM Greg Kroah-Hartman wrote:
> > > On Sat, Nov 23, 2013 at 11:56:48PM +0100, Rafael J. Wysocki wrote:
> > > > On
Hello,
On Sat, Nov 23, 2013 at 05:48:35PM -0500, Tejun Heo wrote:
> Please hold on a bit. I have !CONFIG_SYSFS build failure. I think I
> forgot to add dummy interface for a newly added function. I'm fixing
> it right now.
Alright, the end result is the same. 0001 was missing dummy
Introduce kernfs interface to manipulate a directory which takes and
returns sysfs_dirents.
create_dir() is renamed to kernfs_create_dir_ns() and its argumantes
and return value are updated. create_dir() usages are replaced with
kernfs_create_dir_ns() and sysfs_create_subdir() usages are
On Sun, Nov 24, 2013 at 12:12:59AM +0100, Rafael J. Wysocki wrote:
> On Saturday, November 23, 2013 02:53:58 PM Greg Kroah-Hartman wrote:
> > On Sat, Nov 23, 2013 at 11:56:48PM +0100, Rafael J. Wysocki wrote:
> > > On Friday, November 22, 2013 08:43:55 AM Bjorn Helgaas wrote:
> > > > [+cc Rafael,
>From 16a81407cf835109cb0ae7500de859d63c5e46c2 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Sat, 23 Nov 2013 18:01:46 -0500
The way namespace tags are implemented in sysfs is more complicated
than necessary. As each tag is a pointer value and required to be
non-NULL under a namespace enabled
On 11/23/2013 03:36 PM, Pavel Machek wrote:
On Wed 2013-11-20 08:02:33, Howard Chu wrote:
Theodore Ts'o wrote:
Historically, Intel has been really good about avoiding this, but
since they've moved to using 3rd party flash controllers, I now advise
everyone who plans to use any flash storage,
On Saturday, November 23, 2013 02:53:58 PM Greg Kroah-Hartman wrote:
> On Sat, Nov 23, 2013 at 11:56:48PM +0100, Rafael J. Wysocki wrote:
> > On Friday, November 22, 2013 08:43:55 AM Bjorn Helgaas wrote:
> > > [+cc Rafael, James]
> > >
> > > On Tue, Nov 19, 2013 at 11:18 PM, Tejun Heo wrote:
> >
подправьте зрение без операционным рецептом http://goo.gl/ig7wQL
--
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
Please read the FAQ at
On Sat, Nov 23, 2013 at 11:56:48PM +0100, Rafael J. Wysocki wrote:
> On Friday, November 22, 2013 08:43:55 AM Bjorn Helgaas wrote:
> > [+cc Rafael, James]
> >
> > On Tue, Nov 19, 2013 at 11:18 PM, Tejun Heo wrote:
> > > (cc'ing Bjorn)
> > >
> > > Hello,
> > >
> > > On Tue, Nov 19, 2013 at
Hello,
Please hold on a bit. I have !CONFIG_SYSFS build failure. I think I
forgot to add dummy interface for a newly added function. I'm fixing
it right now.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Friday, November 22, 2013 08:43:55 AM Bjorn Helgaas wrote:
> [+cc Rafael, James]
>
> On Tue, Nov 19, 2013 at 11:18 PM, Tejun Heo wrote:
> > (cc'ing Bjorn)
> >
> > Hello,
> >
> > On Tue, Nov 19, 2013 at 03:09:58PM +0200, Mika Westerberg wrote:
> >> Commit bcdde7e221a8 (sysfs: make
On Fri, Nov 22, 2013 at 01:51:28PM +0530, Kamala R wrote:
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index f54e3a1..d90b9ab 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -1564,21 +1564,24 @@ int ip6_route_add(struct fib6_config *cfg)
> goto
sysfs_init_inode_attrs() is a bit clumsy to use requiring the caller
to check whether @sd->s_iattr is already set or not. Rename it to
sysfs_inode_attrs(), update it to check whether @sd->s_iattr is
already initialized before trying to initialize it and return
@sd->s_iattr. This simplifies the
kernfs inherited "security.*" xattr support from sysfs. This patch
extends xattr support to "trusted.*" using simple_xattr_*(). As
trusted xattrs are restricted to CAP_SYS_ADMIN, simple_xattr_*() which
uses kernel memory for storage shouldn't be problematic.
Note that the existing "security.*"
Hello,
This is repost of [L], rebased on top of the refreshed patches.
kernfs inherited "security.*" xattr support from sysfs but for it to
be useable for cgroupfs, it needs to support "trusted.*" too. This
patchset adds "trusted.*" xattr support using simple_xattr*().
Note that the existing
From: Oussama Ghorbel
Date: Fri, 22 Nov 2013 16:23:20 +0100
> Send icmpv6 error with type "destination unreachable" and code
> "address unreachable" when receiving icmpv4 error and sufficient
> data bytes are available
> This patch enhances the compliance of sit tunnel with section 3.4 of
> rfc
From: Vlad Yasevich
Date: Thu, 21 Nov 2013 17:14:01 -0500
> On 11/21/2013 04:56 PM, Chang Xiangzhong wrote:
>> Function sctp_check_transmitted(transport t, ...) would iterate all of
>> transport->transmitted queue and looking for the highest __newly__ acked tsn.
>> The original algorithm would
Introduce kernfs removal interfaces - kernfs_remove() and
kernfs_remove_by_name[_ns]().
These are just renames of sysfs_remove() and sysfs_hash_and_remove().
No functional changes.
v2: Dummy kernfs_remove_by_name_ns() for !CONFIG_SYSFS updated to
return -ENOSYS instead of 0.
Signed-off-by:
Currently the kobject based interface guarantees that a parent
sysfs_dirent is always a directory; however, the planned kernfs
interface will be directly based on sysfs_dirents and the caller may
specify non-directory node as the parent. Add an explicit check in
__sysfs_add_one() so that such
A directory sysfs_dirent points to the associated kobj. A regular or
bin file points to the associated [bin_]attribute. This patch
replaces sysfs_dirent->s_dir.kobj and ->s_attr.[bin_]attr with void *
->priv.
This is to prepare for kernfs interface so that sysfs can specify the
private data in
1 - 100 of 508 matches
Mail list logo
