Hi
This implements anon_inodes_new() to create anonymous inodes. Patch #1
describes the changes to anon_inodes.c and why DRM could make great use of this.
Patch #2 converts DRM core to use anon_inodes_new() instead of delayed
dev_mapping initialization (but kept simple, TTM can be converted
On Wed, Jul 10, 2013 at 4:12 PM, Paul Taysom wrote:
> The following commit introduced a 10x regression for
> syncing inodes in ext4 with relatime enabled where just
> the atime had been modified.
>
> commit 4ea425b63a3dfeb7707fc7cc7161c11a51e871ed
> Author: Jan Kara
> Date: Tue Jul
On 07/10/2013 03:22 PM, Theodore Ts'o wrote:
>
> I agree this is an important thing to do, but I'm hesitant about
> having someone formally annointed as "the successor". Information in
> the MAINTAINERS file can get stale, and removing someone who may not
> have as much time, and so has become a
On 07/11/2013 04:42 AM, David Miller wrote:
> From: Chen Gang
> Date: Sat, 22 Jun 2013 13:26:09 +0800
>
>> >
>> > For the related next strcpy(), the destination length is less than 512,
>> > but the source maximize length may be 'OPROMMAXPARAM' (4096) which is
>> > more than 512.
>> >
>> > One
Hi Shuah,
thanks for your reply.
> >> +#ifdef CONFIG_PM_SLEEP
> >> + .driver = {
> >> + .pm = _tis_pm,
> >> + },
> >> +#endif
> >>
> >> };
> >
> > I don't think the #if CONFIG_PM_SLEEP is required here.
In this case, the SIMPLE_DEV_PM_OPS macro handles the case internally - i.e.
Vi tilbyr legitime lån som personlige og forretningsmessige lån uten sikkerhet
(bare identification) med maksimum
garanti, på 3% rente, fra $ 5000 til $ 90,000,000 i 1 år til 40 år
nedbetalingstid overalt i verden
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
] SMP
2 [4.678953] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.10.0-next-20130710 #57
3 [4.678959] Hardware name: Intel Corp. Mohan Peak/Server, BIOS
EDVLCRB1.86B.0017.R00.1305271414 05/27/2013
4 [4.678963] task: 88017aa8 ti: 88017aa6c000 task.ti:
88017aa6c000
On Wednesday 10 July 2013, Wolfram Sang wrote:
> Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
> we can rely on device core for setting the default pins. Compile tested only.
>
> Acked-by: Linus Walleij (personally at LCE13)
> Signed-off-by: Wolfram Sang
On (07/01/13 12:42), Michael Wang wrote:
> On 06/26/2013 05:15 AM, Sergey Senozhatsky wrote:
> [snip]
> >
> > [ 60.277848] Chain exists of:
> > (&(_cdbs->work)->work) --> _cdbs->timer_mutex --> cpu_hotplug.lock
> >
> > [ 60.277864] Possible unsafe locking scenario:
> >
> > [ 60.277869]
The following commit introduced a 10x regression for
syncing inodes in ext4 with relatime enabled where just
the atime had been modified.
commit 4ea425b63a3dfeb7707fc7cc7161c11a51e871ed
Author: Jan Kara
Date: Tue Jul 3 16:45:34 2012 +0200
vfs: Avoid unnecessary WB_SYNC_NONE
On Wednesday 10 July 2013, Alan Stern wrote:
> This isn't right. There are USB host controllers that use PIO, not
> DMA. The HAS_DMA dependency should go with the controller driver, not
> the USB core.
>
> On the other hand, the USB core does call various routines like
> dma_unmap_single. It
On Wed, Jul 10, 2013 at 03:57:30PM -0700, Greg Kroah-Hartman wrote:
> On Wed, Jul 10, 2013 at 03:48:56PM -0700, Guenter Roeck wrote:
> > On Wed, Jul 10, 2013 at 01:05:10PM -0700, Greg Kroah-Hartman wrote:
> > > To make it easier for driver subsystems to work with attribute groups,
> > > create the
On 07/10/2013 04:43 PM, Peter Hüwe wrote:
> Hi,
>
> thanks for your patch
>> static struct pnp_device_id tpm_pnp_tbl[] = {
>> {"PNP0C31", 0}, /* TPM */
>> {"ATM1200", 0}, /* Atmel */
>> @@ -835,9 +834,12 @@ static struct pnp_driver tis_pnp_driver = {
>> .name =
On Wed, Jul 10, 2013 at 01:05:13PM -0700, Greg Kroah-Hartman wrote:
> groups should be able to support binary attributes, just like it
> supports "normal" attributes. This lets us only handle one type of
> structure, groups, throughout the driver core and subsystems, making
> binary attributes a
On 07/10/2013 12:29 PM, Gerlando Falauto wrote:
Hi Sebastian, Jonas,
first of all thank you for your HUGE efforts in this area.
On 07/08/2013 12:05 AM, Jonas Gorski wrote:
On Sun, 7 Jul 2013 23:43:41 +0200
Jonas Gorski wrote:
On Sun, 7 Jul 2013 22:33:51 +0200
Sebastian Hesselbarth wrote:
[+cc linux-pci]
On Wed, Jul 10, 2013 at 10:21:32PM +, Wyborny, Carolyn wrote:
> > -Original Message-
> > From: Bjorn Helgaas [mailto:bhelg...@google.com]
> [..]
>
> > Pavel's ThinkPad X60 has two NICs: Intel 82573L and Intel PRO/Wireless
> > 3945ABG. I'm pretty sure the problem he's
On Wed, Jul 10, 2013 at 03:48:56PM -0700, Guenter Roeck wrote:
> On Wed, Jul 10, 2013 at 01:05:10PM -0700, Greg Kroah-Hartman wrote:
> > To make it easier for driver subsystems to work with attribute groups,
> > create the ATTRIBUTE_GROUPS macro to remove some of the repetitive
> > typing for the
Fix build warning of unused variable:
drivers/video/vga16fb.c:1268:26: warning: unused variable ‘dev’
[-Wunused-variable]
Signed-off-by: Luis Henriques
---
drivers/video/vga16fb.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/video/vga16fb.c b/drivers/video/vga16fb.c
index
On 07/03/2013 01:34 AM, Joonsoo Kim wrote:
> - if (page)
> + do {
> + page = buffered_rmqueue(preferred_zone, zone, order,
> + gfp_mask, migratetype);
> + if (!page)
> +
On Wed, Jul 10, 2013 at 01:05:10PM -0700, Greg Kroah-Hartman wrote:
> To make it easier for driver subsystems to work with attribute groups,
> create the ATTRIBUTE_GROUPS macro to remove some of the repetitive
> typing for the most common use for attribute groups.
>
> Signed-off-by: Greg
Hi,
thanks for your patch
> static struct pnp_device_id tpm_pnp_tbl[] = {
> {"PNP0C31", 0}, /* TPM */
> {"ATM1200", 0}, /* Atmel */
> @@ -835,9 +834,12 @@ static struct pnp_driver tis_pnp_driver = {
> .name = "tpm_tis",
> .id_table = tpm_pnp_tbl,
>
On Wed, 10 Jul 2013, H. Peter Anvin wrote:
> > If any CPU instruction execution would collide with the patching,
> > it'd be trapped by the int3 breakpoint and redirected to the provided
> > "handler" (which would typically mean just skipping over the patched
> > region, acting as "nop" has been
He must be too, umm, busy to update his own bouncing
email address too.
Signed-off-by: Joe Perches
---
poke - prod...
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index e51d018..3c81917 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
On Wednesday, July 10, 2013 02:11:05 AM Rafael J. Wysocki wrote:
> On Tuesday, July 09, 2013 01:32:42 PM Toshi Kani wrote:
> > On Mon, 2013-07-08 at 02:10 +0200, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> > > An ACPI_NOTIFY_BUS_CHECK notification means that we should scan the
On Wed, Jul 10, 2013 at 03:23:37PM -0700, Greg Kroah-Hartman wrote:
> On Wed, Jul 10, 2013 at 03:04:41PM -0700, Guenter Roeck wrote:
> > On Wed, Jul 10, 2013 at 01:05:08PM -0700, Greg Kroah-Hartman wrote:
> > > Hi all,
> > >
> > > Guenter and Oliver have been pointing out a few limitations of the
Hi Toralf,
On 07/11/2013 02:20 AM, Toralf Förster wrote:
> I tested the patch several times on top of a66b2e5 - the origin issue is
> fixed but - erratically another issue now appears : all 4 cores are runs
> after wakeup at 2.6 GHz.
> The temporary hot fix is to switch between governor
On 07/10/2013 04:25 PM, Jiri Kosina wrote:
> Hi,
>
> this is a resurrection of a few years old idea to have jump labels use
> synchronization based on int3 breakpoint rather than relying on
> stop_machine() with all the consequences.
>
> ftrace has been doing exactly this kind of patching for
On Wed, Jul 10, 2013 at 03:18:12PM -0700, Guenter Roeck wrote:
> On Wed, Jul 10, 2013 at 03:05:31PM -0700, Greg Kroah-Hartman wrote:
> >
> > We should be using groups, not attribute lists, for classes to allow
> > subdirectories, and soon, binary files. Groups are just more flexible
> > overall,
On Wed, Jul 10, 2013 at 03:04:41PM -0700, Guenter Roeck wrote:
> On Wed, Jul 10, 2013 at 01:05:08PM -0700, Greg Kroah-Hartman wrote:
> > Hi all,
> >
> > Guenter and Oliver have been pointing out a few limitations of the
> > driver core's ability to create files properly (i.e. in a way that
> >
(Reminder: please cc the relevant mailing lists when proposing a topic
for the kernel summit.)
On Wed, Jul 10, 2013 at 04:45:51PM -0400, Steven Rostedt wrote:
> Recently we lost a major Open Source developer to a tragic accident.
> Seth Vidal wasn't a kernel developer, but his death reminds us of
> -Original Message-
> From: Bjorn Helgaas [mailto:bhelg...@google.com]
[..]
> Holy cow, you guys have a lot of folks listed in MAINTAINERS for Intel
> drivers :)
> This is an ASPM question, if that helps narrow down the folks interested.
Well, we try to have everyone involved, I guess.
We should be using groups, not attribute lists, for classes to allow
subdirectories, and soon, binary files. Groups are just more flexible
overall, so add them.
The dev_attrs list will go away after all in-kernel users are converted
to use dev_groups.
Signed-off-by: Greg Kroah-Hartman
---
v2:
On Wed, Jul 10, 2013 at 03:05:31PM -0700, Greg Kroah-Hartman wrote:
>
> We should be using groups, not attribute lists, for classes to allow
> subdirectories, and soon, binary files. Groups are just more flexible
> overall, so add them.
>
> The dev_attrs list will go away after all in-kernel
Comm: swapper/0 Not tainted
3.10.0-next-20130710 #57
3 [4.678959] Hardware name: Intel Corp. Mohan Peak/Server, BIOS
EDVLCRB1.86B.0017.R00.1305271414 05/27/2013
On Wed, Jul 10, 2013 at 02:56:36PM -0700, H. Peter Anvin wrote:
> No, the idea is that the affected CPU will simply execute int3 -> iret
> ad nauseam until the first byte is repatched, at that point execution
> will resume normally.
Ok, that sounds simple enough. I just hope we don't unearth some
On Thu, Jun 27, 2013 at 11:08 PM, Hanumant Singh
wrote:
> Add a new device tree enabled pinctrl driver for
> Qualcomm MSM SoC's. This driver provides an extensible
> framework to interface all MSM's that use a TLMM pinmux,
> with the pinctrl subsytem.
>
> This driver is split into two parts: the
We should be using groups, not attribute lists, for classes to allow
subdirectories, and soon, binary files. Groups are just more flexible
overall, so add them.
The dev_attrs list will go away after all in-kernel users are converted
to use dev_groups.
Signed-off-by: Greg Kroah-Hartman
---
On Wed, Jul 10, 2013 at 01:05:08PM -0700, Greg Kroah-Hartman wrote:
> Hi all,
>
> Guenter and Oliver have been pointing out a few limitations of the
> driver core's ability to create files properly (i.e. in a way that
> doesn't race with userspace.) The driver core allows this, but it
> doesn't
On Tue, Jul 9, 2013 at 1:55 AM, Yijing Wang wrote:
> Introduce PCIe Ext Capability Device Serial Number support,
> so we can use the unique device serial number to identify
> the physical device. During system suspend, if the PCIe
> device was removed and inserted a new same device, after
>
On 07/10/2013 02:48 PM, Borislav Petkov wrote:
> On Wed, Jul 10, 2013 at 02:36:41PM -0700, H. Peter Anvin wrote:
>> I'm wondering if it would be easier/more general to just return to the
>> instruction. The "more general" bit would allow this to be used for
>> other things, like alternatives, and
On Wed, Jul 10, 2013 at 11:39:50AM -0400, Vince Weaver wrote:
> On Wed, 10 Jul 2013, Dave Jones wrote:
>
> > Something is really fucked up in the kernel side of perf.
> > I get this right after booting..
> >
> > [ 114.516619] perf samples too long (4262 > 2500), lowering
> >
On 07/11/2013 01:45 AM, Geert Uytterhoeven wrote:
When builtin (CONFIG_USB_FOTG210_UDC=y):
LD drivers/usb/gadget/built-in.o
WARNING: drivers/usb/gadget/built-in.o(.data+0xbf8): Section mismatch in
reference from the variable fotg210_driver to the function
On Wed, Jul 10, 2013 at 10:08:50PM +0800, Haojian Zhuang wrote:
> On Wed, Jul 10, 2013 at 8:24 PM, Jason Cooper wrote:
> > On Wed, Jul 10, 2013 at 04:19:46PM +0800, Haojian Zhuang wrote:
> >> On Tue, Jul 9, 2013 at 8:49 PM, Jason Cooper wrote:
> >> > Neil,
> >> >
> >> > On Tue, Jul 09, 2013 at
On Wed, Jul 10, 2013 at 03:50:10PM -0500, Matt Sealey wrote:
> On Tue, Jul 9, 2013 at 7:49 AM, Jason Cooper wrote:
> > Neil,
> >
> > I agree with the need to change, however, this has been in the binding
> > documentation since v3.5. I wish we had caught this when we decided
> > against using
On Wed, Jul 10, 2013 at 02:36:41PM -0700, H. Peter Anvin wrote:
> I'm wondering if it would be easier/more general to just return to the
> instruction. The "more general" bit would allow this to be used for
> other things, like alternatives, and perhaps eventually dynamic call
> patching.
Well,
On Wed, 2013-07-10 at 23:31 +0200, Jiri Kosina wrote:
> Introduce a method for run-time instrucntion patching on a live SMP kernel
> based on int3 breakpoint, completely avoiding the need for stop_machine().
Yet more trivia:
instruction typo
> The way this is achieved:
>
> - add a
When builtin (CONFIG_USB_FOTG210_UDC=y):
LD drivers/usb/gadget/built-in.o
WARNING: drivers/usb/gadget/built-in.o(.data+0xbf8): Section mismatch in
reference from the variable fotg210_driver to the function
.init.text:fotg210_udc_probe()
The variable fotg210_driver references
the function
On 07/10/2013 02:31 PM, Jiri Kosina wrote:
>
> If any CPU instruction execution would collide with the patching,
> it'd be trapped by the int3 breakpoint and redirected to the provided
> "handler" (which would typically mean just skipping over the patched
> region, acting as "nop" has been there,
On 07/09/2013 03:11 PM, Neil Horman wrote:
Recently we added an early quirk to detect 5500/5520 chipsets with early
revisions that had problems with irq draining with interrupt remapping enabled:
commit 03bbcb2e7e292838bb0244f5a7816d194c911d62
Author: Neil Horman
Date: Tue Apr 16 16:38:32
On Wed, 10 Jul 2013, Geert Uytterhoeven wrote:
> If NO_DMA=y:
>
> drivers/built-in.o: In function `usb_hcd_unmap_urb_setup_for_dma':
> drivers/usb/core/hcd.c:1361: undefined reference to `dma_unmap_single'
> ,,,
>
> Commit d9ea21a779278da06d0cbe989594bf542ed213d7 ("usb: host: make
>
Introduce a method for run-time instrucntion patching on a live SMP kernel
based on int3 breakpoint, completely avoiding the need for stop_machine().
The way this is achieved:
- add a int3 trap to the address that will be patched
- sync cores
- update all but the first
Hello,
On 05/01/2013 07:33 PM, H. Peter Anvin wrote:
> On 05/01/2013 10:01 AM, Jonas Heinrich wrote:
>> Hello, I tried the newest kernel, 3.9 today but the bug is still
>> present. Applying the attached patch solves the bug for me.
>>
>> Best regards, Jonas Heinrich
>
> Okay... WTF is going on
If NO_DMA=y:
drivers/built-in.o: In function `usb_hcd_unmap_urb_setup_for_dma':
drivers/usb/core/hcd.c:1361: undefined reference to `dma_unmap_single'
drivers/built-in.o: In function `usb_hcd_unmap_urb_for_dma':
drivers/usb/core/hcd.c:1393: undefined reference to `dma_unmap_sg'
From: Marc Kleine-Budde
Date: Wed, 10 Jul 2013 23:02:57 +0200
> On 07/10/2013 05:57 PM, Wolfram Sang wrote:
>> Since commit ab78029 (drivers/pinctrl: grab default handles from device
>> core),
>> we can rely on device core for setting the default pins. Compile tested only.
>>
>> Acked-by:
If NO_DMA=y:
drivers/built-in.o: In function `rt2x00queue_unmap_skb':
drivers/net/wireless/rt2x00/rt2x00queue.c:129: undefined reference to
`dma_unmap_single'
drivers/net/wireless/rt2x00/rt2x00queue.c:133: undefined reference to
`dma_unmap_single'
drivers/built-in.o: In function
If NO_DMA=y:
drivers/built-in.o: In function `ath10k_skb_unmap':
drivers/net/wireless/ath/ath10k/core.h:98: undefined reference to
`dma_unmap_single'
drivers/built-in.o: In function `ath10k_skb_map':
drivers/net/wireless/ath/ath10k/core.h:83: undefined reference to
`dma_map_single'
If NO_DMA=y:
drivers/built-in.o: In function `sh_eth_free_dma_buffer':
drivers/net/ethernet/renesas/sh_eth.c:1103: undefined reference to
`dma_free_coherent'
drivers/net/ethernet/renesas/sh_eth.c:1110: undefined reference to
`dma_free_coherent'
drivers/built-in.o: In function
On 07/10/2013 05:57 PM, Wolfram Sang wrote:
> Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
> we can rely on device core for setting the default pins. Compile tested only.
>
> Acked-by: Linus Walleij (personally at LCE13)
> Signed-off-by: Wolfram Sang
Acked-by:
Four bug fixes:
1) Enable snoop tags properly on Sparc32/LEON, from Andreas Larsson
2) strcpy() length check fix from Chen Gang.
3) Forgotten unregister_netdev() in sunvnet driver, from Dave Kleikamp.
4) Fix broken assembler offsets used in vm_area_struct accesses on
sparc32, from Olivier
[+cc previous cc list from lkml]
On Wed, Jul 10, 2013 at 11:25 AM, hyphop wrote:
> hello
> i have same problem. low write speed after system sleep
>
> kernel 3.9.9
>
> i can see it HDD SATA & USB disks to
>
> i try to make another test
>
> before sleep i make file /tmp/test ( /tmp mounted as
On Thu, Jul 04, 2013 at 03:49:02AM -0400, Dave Jones wrote:
> I don't use the auto config, because I end up filling up /boot
> unless I go through and clean them out by hand every time I install
> a new one (which I do probably a dozen or so times a day).
> Is there some easy way to prune old
I tested the patch several times on top of a66b2e5 - the origin issue is
fixed but - erratically another issue now appears : all 4 cores are runs
after wakeup at 2.6 GHz.
The temporary hot fix is to switch between governor performance and
ondemand for all 4 cores.
On 06/30/2013 08:52 PM,
On Tue, Jul 9, 2013 at 7:49 AM, Jason Cooper wrote:
> Neil,
>
> I agree with the need to change, however, this has been in the binding
> documentation since v3.5. I wish we had caught this when we decided
> against using stock ticker symbols (not all stock markets use
> alphabetical abbreviated
Michal, All,
On 2013-07-08 19:35 +0200, Yann E. MORIN spake thusly:
> On 2013-07-08 13:19 +0200, Jean Delvare spake thusly:
> > Le Monday 24 June 2013 à 20:11 +0200, Yann E. MORIN a écrit :
> > > From: "Yann E. MORIN"
> [--SNIP--]
> > > Since the search can be a regexp, it is possible that more
Stephen Warren writes:
> On 07/10/2013 08:36 AM, Eric W. Biederman wrote:
>> Simon Horman writes:
>>
>>> From: Stephen Warren
>>>
>>> Prior to commit 3ab8352 "kexec jump", if machine_kexec() returned,
>>> sys_reboot() would return -EINVAL. This patch restores this behaviour
>>> for the
On Thu, Jun 27, 2013 at 4:45 PM, Tony Lindgren wrote:
> The off mode bits can be enabled continuously, the mux hardware
> automatically sets them. So sounds like you don't need any
> separate "idle" "sleep" and "off" states, the following should
> do:
>
> "default" (or "static") static pins that
From: Chen Gang
Date: Sat, 22 Jun 2013 13:26:09 +0800
>
> For the related next strcpy(), the destination length is less than 512,
> but the source maximize length may be 'OPROMMAXPARAM' (4096) which is
> more than 512.
>
> One work flow may:
> openprom_sunos_ioctl() -> if (cmd ==
From: Sasha Levitskiy
Input: Propagate hardware event timestamp to evdev.
Convey hardware generated timestamp associated with the current event packet.
The use of these event codes by hardware drivers is optional.
Used to reduce jitter and improve velocity tracking in ABS_MT and other timing
On Thu, Jun 27, 2013 at 4:01 PM, Grygorii Strashko
wrote:
> I think, In the future the OMAP pinctrl configurations would be manged in
> more flexible way then now (thanks to "pinctrl PM helpers" and you;))
> - "Idle" state will be splitted to "Idle"/"sleep"
> - "default" state will be splitted
Hi Jason,
On Tue, Jul 09, 2013 at 05:42:29PM +, Rich, Jason wrote:
> Greetings,
> I've recently encountered an issue where multiple hosts are failing to boot
> up about 1/5 of the time. So far I have confirmed this
> issue on three seperate host machines. The issue presents itself after
>
On Tue, Jul 9, 2013 at 9:00 PM, Yijing Wang wrote:
> Hi Bjorn,
>Thanks for your review and comments!
>
>>> We can use PCIe Device Serial Number to identify the device if
>>> device support DSN.
>>
>> I think I like the idea of this, especially because the Microsoft PCI
>> Hardware Compliance
Make jump labels use text_poke_bp() for text patching instead of
text_poke_smp(), avoiding the need for stop_machine().
Signed-off-by: Jiri Kosina
---
arch/x86/kernel/jump_label.c | 16 ++--
1 files changed, 14 insertions(+), 2 deletions(-)
diff --git
Introduce a method for run-time instrucntion patching on a live SMP kernel
based on int3 breakpoint, completely avoiding the need for stop_machine().
The way this is achieved:
- add a int3 trap to the address that will be patched
- sync cores
- update all but the first
Hi,
this is a resurrection of a few years old idea to have jump labels use
synchronization based on int3 breakpoint rather than relying on
stop_machine() with all the consequences.
ftrace has been doing exactly this kind of patching for year since
08d636b6 ("ftrace/x86: Have arch x86_64 use
On 07/10/13 22:05, Greg Kroah-Hartman wrote:
Hi all,
Hey Greg,
Guenter and Oliver have been pointing out a few limitations of the
driver core's ability to create files properly (i.e. in a way that
doesn't race with userspace.) The driver core allows this, but it
doesn't export that ability
>> Signed-off-by: Naveen N. Rao
>
> Acked-by: Borislav Petkov
Applied-by: Tony Luck :-)
Naveen: Thanks for having this idea, implementing it, and sticking
with it through the review process.
Once 3.11-rc1 is out I'll ask Ingo to pull this series to the tip tree
... and then on to 3.12
-Tony
This makes it easier to create static binary attributes, which is needed
in a number of drivers, instead of "open coding" them.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/sysfs.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/linux/sysfs.h b/include/linux/sysfs.h
Make it easier to create attributes without having to always audit the
mode settings.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/device.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/linux/device.h b/include/linux/device.h
index bcf8c0d..1d546a0 100644
---
A number of parts of the kernel created their own version of this, might
as well have the sysfs core provide it instead.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/sysfs.h | 2 ++
kernel/events/core.c | 2 --
mm/backing-dev.c | 2 --
3 files changed, 2 insertions(+), 4
From: Guenter Roeck
From: Guenter Roeck
device_create_groups lets callers create devices as well as associated
sysfs attributes with a single call. This avoids race conditions seen
if sysfs attributes on new devices are created later.
[fixed up comment block placement and add checks for
Hi all,
Guenter and Oliver have been pointing out a few limitations of the
driver core's ability to create files properly (i.e. in a way that
doesn't race with userspace.) The driver core allows this, but it
doesn't export that ability to drivers very easily, and for binary
files, not at all.
Dear RT Folks,
I'm pleased to announce the 3.2.48-rt69 stable release.
This release is just an update to the new stable 3.2.48 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Dear RT Folks,
I'm pleased to announce the 3.0.85-rt113 stable release.
This release is just an update to the new stable 3.0.85 version
and no RT specific changes have been made.
You can get this release via the git tree at:
groups should be able to support binary attributes, just like it
supports "normal" attributes. This lets us only handle one type of
structure, groups, throughout the driver core and subsystems, making
binary attributes a "full fledged" part of the driver model, and not
something just "tacked on".
To make it easier for driver subsystems to work with attribute groups,
create the ATTRIBUTE_GROUPS macro to remove some of the repetitive
typing for the most common use for attribute groups.
Signed-off-by: Greg Kroah-Hartman
---
include/linux/sysfs.h | 9 +
1 file changed, 9
Dear RT Folks,
I'm pleased to announce the 3.4.52-rt67 stable release.
This release is just an update to the new stable 3.4.52 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Dear RT Folks,
I'm pleased to announce the 3.6.11.6-rt38 stable release.
This release is just an update to the new stable 3.6.11.6 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Wed, Jul 10, 2013 at 08:28:15PM +0200, Markus Trippelsdorf wrote:
> Well, there's also no hand-holding when lzop is missing for LZO. And
> the error message is clear enough. No?
Actually, we should error out more gracefully than that. Maybe check for
the presence of the executable first and if
On Wednesday, July 10, 2013 02:33:04 PM Stephen Smalley wrote:
> On 06/05/2013 05:15 PM, Waiman Long wrote:
> > Currently, the ebitmap_node structure has a fixed size of 32 bytes. On
> > a 32-bit system, the overhead is 8 bytes, leaving 24 bytes for being
> > used as bitmaps. The overhead ratio is
[+cc Jeff, Jesse, et al, e1000-devel]
Holy cow, you guys have a lot of folks listed in MAINTAINERS for Intel
drivers :) This is an ASPM question, if that helps narrow down the
folks interested.
On Wed, Jul 10, 2013 at 7:29 AM, Pavel Machek wrote:
> Hi!
>
>> >> But:
>> >> 1) it should not list
Dear Wolfram Sang,
> Since commit ab78029 (drivers/pinctrl: grab default handles from device
> core), we can rely on device core for setting the default pins. Compile
> tested only.
>
> Acked-by: Linus Walleij (personally at LCE13)
> Signed-off-by: Wolfram Sang
Something like that is already
I've been doing a bad job at managing the drivers/clocksource directory,
so Daniel has been helping with review and patch queuing for the clocksource
and clockevent drivers, so add him formally to the MAINTAINERS list.
Cc: Daniel Lezcano
Cc: Thomas Gleixner
Cc: Joe Perches
Cc: Arnd Bergmann
I've been doing a bad job at managing the drivers/clocksource directory,
so Daniel has been helping with review and patch queuing for the clocksource
and clockevent drivers, so add him formally to the MAINTAINERS list.
Cc: Daniel Lezcano
Cc: Thomas Gleixner
Cc: Joe Perches
Cc: Arnd Bergmann
Hi Linus,
Nothing overly exciting here - a couple of new drivers that don't do a
great deal, along with some miscellaneous fixes and a couple of small
feature enablement patches.
The following changes since commit d2b4a646717153a1a180b64d4a8464054dbd700e:
Merge branch 'for-linus' of
From: Robert Richter
Fix having verbose build with V=0, e.g:
make V=0 -C tools/ perf
Signed-off-by: Robert Richter
Link: http://lkml.kernel.org/r/20130503134953.GU8356@rric.localhost
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/Documentation/Makefile | 2 +-
Hi,
I was wondering if there is a reason the modules under the samples
directory only build if you use the command make uImage modules?
I have created a patch so that they compile if you enable CONFIG_SAMPLES
and then build the kernel separately, i.e.
make uImage
make modules
This two step
On 07/08/2013 07:02 AM, Christian Ruppert wrote:
...
> OK, a small drawing of our hardware should make this clear, let's take
> an imaginary example of one port with 10 pins, one i2c interface, one
> spi interface and one GPIO bank:
>
> | mux N-1|
> ++
>
From: Adrian Hunter
The final sample format bit used to be PERF_SAMPLE_STACK_USER which
neglected to do a final increment of the array pointer. The result is
that the following parsing might start at the wrong place.
Signed-off-by: Adrian Hunter
Cc: David Ahern
Cc: Frederic Weisbecker
Cc:
From: Robert Richter
The OUTPUT directory is wrongly determind leading to:
make[3]: *** No rule to make target `.../.build/perf/PERF-VERSION-FILE'. Stop.
Fixing this by using the generic approach in script/Makefile.include.
Signed-off-by: Robert Richter
Link:
From: "Kirill A. Shutemov"
Addresses of allocated memory areas saved to '*src' and '*dst', so we
need to check them for NULL, not 'src' and 'dst'.
Signed-off-by: Kirill A. Shutemov
Acked-by: Hitoshi Mitake
Cc: Hitoshi Mitake
Cc: Ingo Molnar
Cc: Paul Mackerras
Cc: Peter Zijlstra
Link:
101 - 200 of 1208 matches
Mail list logo
