On 18 August 2012 01:21, Henrik Rydberg wrote:
> Hi Daniel,
>
>> Add the device ID for supporting the Macbook Pro 2012 'MacBookPro10,1'.
>> The bluetooth device presents itself as:
>>
>> T: Bus=02 Lev=04 Prnt=04 Port=02 Cnt=03 Dev#= 8 Spd=12 MxCh= 0
>> D: Ver= 2.00 Cls=ff(vend.) Sub=01
Hi Philip,
The interrupt could be from another source, though Message Signalled
Interrupts are a PCI (and variants) only feature at present. I'm happy
to split the patch and/or make the module param specific to sdhci-pci.
Let's see what the maintainers prefer...Chris?
Dan
On 18 August 2012
On Fri, Aug 17, 2012 at 07:44:37AM -0700, Paul E. McKenney wrote:
> On Fri, Aug 17, 2012 at 10:02:40PM +0800, Fengguang Wu wrote:
> > On Fri, Aug 17, 2012 at 06:43:28AM -0700, Paul E. McKenney wrote:
> > > On Fri, Aug 17, 2012 at 06:06:35PM +0800, Fengguang Wu wrote:
> > > > Greetings,
> > > >
>
On 08/18/2012 12:07 AM, Daniel Forrest wrote:
I was being careful since I wasn't certain about the locking. Does
the test need to be protected by "lock_anon_vma_root"? That's why I
chose the overhead of the possible wasted "anon_vma_chain_alloc".
The function anon_vma_clone is being called
On Fri, Aug 17, 2012 at 11:46:18PM -0400, Rik van Riel wrote:
> On 08/17/2012 08:03 PM, Daniel Forrest wrote:
>
> >Based on your comments, I came up with the following patch. It boots
> >and the anon_vma/anon_vma_chain SLAB usage is stable, but I don't know
> >if I've overlooked something. I'm
> "Mike" == Mike Snitzer writes:
Mike> Could be I've wasted a few hours by rebasing these patches...
Mike> regardless, it would be great if you could share what your plans
Mike> are.
Heh, I worked on syncing my patch queue up to Jens' and James' trees
this afternoon. But I didn't quite
On 08/17/2012 08:03 PM, Daniel Forrest wrote:
Based on your comments, I came up with the following patch. It boots
and the anon_vma/anon_vma_chain SLAB usage is stable, but I don't know
if I've overlooked something. I'm not a kernel hacker.
The patch looks reasonable to me. There is one
On Thu, Jun 21, 2012 at 11:46 PM, Martin K. Petersen
wrote:
>> "Christoph" == Christoph Hellwig writes:
>
>>> There are several additional commands in the pipeline where the 1:1
>>> mapping between DMA size and block range is invalid. I want to get
>>> rid of the 1:1 assumption in general so
The 'attach' function can fail between when the devpriv and
the comedi subdevices are allocated. If it does the 'detach'
will try to access unallocated memory when it goes thru the
subdevices.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
Currently the 'detach' function in this driver walks thru the
boardinfo in order to find the subdevice index for any sdio
subdevices in order to call the subdev_8255_cleanup(). Then
it goes thru all the subdevices to clean the s->private pointer.
All the sdio subdevices are unique in that the
Instead of calculating the number of subdevices in the 'attach'
simply add the number to the boardinfo.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci_dio.c | 39 +---
1 file changed, 18 insertions(+),
Remove all the boardinfo data that is simply '0'.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci_dio.c | 84
1 file changed, 84 deletions(-)
diff --git
Convert the boardinfo initialization to C99 format to make it
less error prone.
The struct diosubd_data information is not converted to C99 format
yet because some of it will be removed.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
Convert this PCI driver to use the comedi PCI auto config attach
mechanism by adding an 'attach_pci' callback function. Since the
driver does not require any external configuration options, and
the legacy 'attach' callback is now optional, remove it.
Signed-off-by: H Hartley Sweeten
Cc: Ian
These macros rely on a local variable having a specific name. Remove
them and use the comedi_board() helper to get the this_board pointer.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci_dio.c | 33 ++--
Remove the DPRINTK function trace messages and associated
PCI_DIO_EXTDEBUG define. These should not be in the final driver.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci_dio.c | 13 -
1 file changed, 13
Only one 'reset' of the card is required in the attach. Remove the
one before setting up the subdevices and leave the one before
exiting the attach function.
The 'valid' variable in the private data is not needed. This variable
is used in the detach to determine if it's ok to call the 'reset'
Convert this PCI driver to use the comedi PCI auto config attach
mechanism by adding an 'attach_pci' callback function. Since the
driver does not require any external configuration options, and
the legacy 'attach' callback is now optional, remove it.
Signed-off-by: H Hartley Sweeten
Cc: Ian
This driver only supports one board type. Remove the boardinfo and
associated code.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1723.c | 139 ---
1 file changed, 42 insertions(+), 97 deletions(-)
The initial state and io_bits for the dio subdevice is determined in
the pci1723_attach() but it's being saved in the wrong subdevice. Move
the code so it gets saved correctly.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
This comedi_lrange is the same as the global range_bipolar10
exported by the comedi core. Use that range instead.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1723.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
The devpriv macro relies on a local variable having a specific name.
Remove it.
The this_board macro in this driver is a bit different in this driver.
In other comedi drivers, this macro returns the dev->board_ptr. In this
driver its simply 'boardtypes' which returns the first boardinfo element.
Remove the DPRINTK function trace messages. These should not be
in the final driver.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1723.c | 5 -
1 file changed, 5 deletions(-)
diff --git
In shrink_page_list, call to page_referenced_file will causes the
acquisition/release of mapping->i_mmap_mutex for each page in the page
list. However, it is very likely that successive pages in the list
share the same mapping and we can reduce the frequency of i_mmap_mutex
acquisition by holding
We gather the pages that need to be unmapped in shrink_page_list. We do
the unmap in a single batch to reduce the frequency of acquisition of
the tree lock protecting the address mapping radix tree. This is
possible as successive pages likely share the same mapping in the
__remove_mapping_batch
Move some of the functions to remove the need for the forward
declarations.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1710.c | 297 +--
1 file changed, 140 insertions(+), 157 deletions(-)
diff
To do page reclamation in shrink_page_list function, there are two
locks taken on a page by page basis. One is the tree lock protecting
the radix tree of the page mapping and the other is the
mapping->i_mmap_mutex protecting the reverse mapping of file maped
pages. I tried to batch the
Remove all the boardinfo data that is set to '0' or 'NULL'.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1710.c | 23 ---
1 file changed, 23 deletions(-)
diff --git
Convert the boardinfo initialization to C99 format to make it
less error prone.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1710.c | 152 +--
1 file changed, 118 insertions(+), 34 deletions(-)
diff
These macros rely on a local variable having a specific name. Remove
them and use the comedi_board() helper to get the this_board pointer.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1710.c | 44
The macros PCI171X_EXTDEBUG and DPRINTK enable a number of function
trace messages. These trace messages should not be in the final
driver. Remove them.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/adv_pci1710.c | 132
Another round of updates to the comedi pci drivers.
* remove function trace messages
* remove devpriv and thisboard type macros
* cleanup the boardinfo
* remove forward declarations
* use attach_pci and remove legacy attach (when possible)
* misc. other changes
H Hartley Sweeten (20):
staging:
On Fri, Aug 17, 2012 at 10:42 PM, Greg Kroah-Hartman
wrote:
> On Fri, Aug 17, 2012 at 10:38:16AM -0400, Alan Stern wrote:
>> On Fri, 17 Aug 2012, Ming Lei wrote:
>>
>> > But, if HOTPLUG is not enabled, should device_add() trigger driver probe
>> > further after kernel init is completed? Or even
On Sat, Aug 18, 2012 at 6:02 AM, Rafael J. Wysocki wrote:
> On Friday, August 17, 2012, Ming Lei wrote:
>> +void dpm_for_each_dev(void *data, void (*fn)(struct device *, void *))
>
> Is this function actually used more than once?
At least now, it is called each time before system sleep.
On 08/17/2012 07:54 PM, David Daney wrote:
From: David Daney
The main update is conversion to device tree. Now the the OCTEON
device tree prerequisites are upstream, we can convert the
pata_octeon_cf driver.
The second change allows the driver to function when the kernel is
built for
On 08/17/2012 09:04 AM, Hiroshi Doyu wrote:
dev_dbg_reatelimited() without DEBUG printed "217078 callbacks
suppressed". This shouldn't print anything without DEBUG.
Signed-off-by: Hiroshi Doyu
Reported-by: Antti Palosaari
---
include/linux/device.h |6 +-
1 files changed, 5
The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)
are available in the git repository at:
git://neil.brown.name/md/ tags/md-3.6-fixes
for you to fetch changes up to e0ee778528bbaad28a5c69d2e219269a3a096607:
md/raid10:
On Thu, Aug 16, 2012 at 02:58:45PM -0400, Rik van Riel wrote:
> Oh dear.
>
> Basically, what happens is that at fork time, a new
> "level" is created for the anon_vma hierarchy. This
> works great for normal forking daemons, since the
> parent process just keeps running, and forking off
>
Ingo,
Please pull the latest tip/perf/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent
Head SHA1: 60916a9382e88fbf5e54fd36a3e658efd7ab7bed
Will Deacon (1):
tracing/syscalls: Fix perf syscall tracing when
From: David Daney
The patch needs to eliminate the definition of OCTEON_IRQ_BOOTDMA so
that the device tree code can map the interrupt, so in order to not
temporarily break things, we do a single patch to both the interrupt
registration code and the pata_octeon_cf driver.
Also rolled in is a
From: David Daney
We need to set the 'endian' bit in this case.
Signed-off-by: David Daney
---
drivers/ata/pata_octeon_cf.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/ata/pata_octeon_cf.c b/drivers/ata/pata_octeon_cf.c
index 652d035..4e1194b 100644
---
From: David Daney
The main update is conversion to device tree. Now the the OCTEON
device tree prerequisites are upstream, we can convert the
pata_octeon_cf driver.
The second change allows the driver to function when the kernel is
built for little-endian operation.
The only real change in
Jesper Juhl wrote:
> In newer glibc's (versions > 2.06) reasonably secure permissions of
> 0600 are used when creating a temporary file with mkstemp(). But for
> older glibc's (versions <= 2.06) 0666 is used which is not secure.
Thanks for your suggestion! I'm afraid I prefer not to make the
On 08/17/2012 05:21 PM, Dan Magenheimer wrote:
>> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
>> Subject: Re: [PATCH 0/4] promote zcache from staging
>>
>> On 08/09/2012 03:20 PM, Dan Magenheimer wrote
>>> I also wonder if you have anything else unusual in your
>>> test setup, such as
On Fri, Aug 17, 2012 at 04:03:15AM +0100, Ben Hutchings wrote:
> 3.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Daniel Vetter
>
> commit 0d8957c8a90bbb5d34fab9a304459448a5131e06 upstream.
>
> We may only start to set up the new
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f30.c | 1247 ++
1 files changed, 1247 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f1a.c | 1025 ++
1 files changed, 1025 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f41.c | 1020 ++
1 files changed, 1020 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f34.c | 917 ++
drivers/input/rmi4/rmi_f34.h | 74
2 files changed, 991
Driver for Synaptics touchscreens using RMI4 protocol.
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_dev.c | 448 ++
1 files
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
Documentation/input/rmi4.txt | 25 ++
Documentation/input/rmidev.txt | 144 +
Documentation/input/rmisysfs.txt | 200
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f01.c | 1331 ++
drivers/input/rmi4/rmi_f01.h | 88 +++
2 files changed, 1419
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_i2c.c | 452 +
drivers/input/rmi4/rmi_spi.c | 911 ++
2
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f21.c | 832 ++
1 files changed, 832 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f19.c | 869 ++
1 files changed, 869 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f09.c | 772 ++
1 files changed, 772 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_fw_update.c | 724
1 files changed, 724 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/rmi4/rmi_f17.c | 713 ++
1 files changed, 713 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
Acked-by: Jean Delvare
---
drivers/input/Kconfig |2 +
drivers/input/Makefile |4 +-
drivers/input/rmi4/Kconfig | 262
This patch implements a driver supporting Synaptics ClearPad and other
touchscreen sensors that use the RMI4 protocol, as defined here:
http://www.synaptics.com/sites/default/files/511-000136-01-Rev-E-RMI4%20Intrfacing%20Guide.pdf
as well as successor documents that haven't made their way
"Lespiau, Damien" writes:
> I can't see anything in the docs about an order requirement for those.
Right, the docs don't say anything, which is a bit disconcerting.
> Not sure why the other way does not make sense. Somehow disabling TX
> before RX makes some sense to me (TX enabled without a
On Fri, Aug 17, 2012 at 08:47:04AM +0200, Marco Stornelli wrote:
> Great. I'll remove the calls for ext3/ext4 when I'll submit the
> second version of the patch.
FYI, I have the following patch my ext4 tree, so I could do more
intensive testing. I'll let folks know if anything goes horribly
On 08/17/2012 03:55 PM, Dave Airlie wrote:
> On Sat, Aug 18, 2012 at 8:54 AM, Dave Airlie wrote:
>> On Sat, Aug 18, 2012 at 8:28 AM, Randy Dunlap wrote:
>>> On 08/17/2012 03:25 PM, Justin M. Forbes wrote:
>>>
for , we have verified cases on inteldrmfb, radeondrmfb, and
cirrusdrmfb.
On Thu, Aug 16, 2012 at 11:10:30AM -1000, Mitch Bradley wrote:
> On 8/16/2012 8:38 AM, Stephen Warren wrote:
> > Device tree bindings shouldn't reference Linux documentation; the
> > bindings are supposed to be OS-agnostic.
> While it is true that bindings should try to be OS-agnostic, there is
On Fri, 17 Aug 2012 18:30:11 -0400 John Drescher wrote:
> For the last few weeks I have been doing some reliability testing on a
> mdraid6 array. One of my test was to physically hot remove a raid
> member disk. This worked flawlessly with gentoo-sources-3.5.0 for the
> 5 or so times I tried it
On Fri, Aug 17, 2012 at 6:30 PM, John Drescher wrote:
> For the last few weeks I have been doing some reliability testing on a
> mdraid6 array. One of my test was to physically hot remove a raid
> member disk. This worked flawlessly with gentoo-sources-3.5.0 for the
> 5 or so times I tried it
On Sat, Aug 18, 2012 at 8:54 AM, Dave Airlie wrote:
> On Sat, Aug 18, 2012 at 8:28 AM, Randy Dunlap wrote:
>> On 08/17/2012 03:25 PM, Justin M. Forbes wrote:
>>
>>> for , we have verified cases on inteldrmfb, radeondrmfb, and
>>> cirrusdrmfb.
>>>
>>> This is the last message displayed before the
On Sat, Aug 18, 2012 at 8:28 AM, Randy Dunlap wrote:
> On 08/17/2012 03:25 PM, Justin M. Forbes wrote:
>
>> for , we have verified cases on inteldrmfb, radeondrmfb, and
>> cirrusdrmfb.
>>
>> This is the last message displayed before the system hangs. This seems
>> to be hitting a large number of
nvpublic
> On Fri, Aug 17, 2012 at 02:16:28AM -0700, Bill Huang wrote:
> [...]
> > diff --git a/drivers/mfd/tps6586x.c b/drivers/mfd/tps6586x.c
> [...]
> > @@ -505,6 +519,11 @@ static int __devinit tps6586x_i2c_probe(struct
> > i2c_client *client,
> > goto err_add_devs;
> > }
> >
On Fri, Aug 17, 2012 at 04:08:07PM -0400, J. Bruce Fields wrote:
> Wait a minute, that assumption's a problem because that calculation
> depends in part on xpt_reserved, which is changed here
>
> In particular, svc_xprt_release() calls svc_reserve(rqstp, 0), which
> subtracts
On 08/16/2012 06:08 PM, Greg KH wrote:
> On a larger note, I _really_ don't want a set of 'delete and then add it
> back' set of patches. That destroys all of the work that people had
> done up until now on the code base.
>
> I understand your need, and want, to start fresh, but you still need
On 08/17/2012 03:25 PM, Justin M. Forbes wrote:
> for , we have verified cases on inteldrmfb, radeondrmfb, and
> cirrusdrmfb.
>
> This is the last message displayed before the system hangs. This seems
> to be hitting a large number of users in Fedora, though certainly not
> everyone. This
For the last few weeks I have been doing some reliability testing on a
mdraid6 array. One of my test was to physically hot remove a raid
member disk. This worked flawlessly with gentoo-sources-3.5.0 for the
5 or so times I tried it with my 12 disk + 1 spare mdraid6 array.
After pulling a disk a
for , we have verified cases on inteldrmfb, radeondrmfb, and
cirrusdrmfb.
This is the last message displayed before the system hangs. This seems
to be hitting a large number of users in Fedora, though certainly not
everyone. This started happening with the 3.5 updates, and is still an
issue.
> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> Subject: Re: [PATCH 0/4] promote zcache from staging
>
> On 08/09/2012 03:20 PM, Dan Magenheimer wrote
> > I also wonder if you have anything else unusual in your
> > test setup, such as a fast swap disk (mine is a partition
> > on the
I was considering extending the kernel command-line option
root=PARTUUID= to also support MBR (NT disk signatures). I was thinking
of a syntax along the lines of:
root=PARTUUID=-PP[/PARTNROFF=%d]
... where is the hex representation of the NT disk signature,
and PP is the hex
[V2 fixes patch submission errors; no code changes]
This patchset moves both the original "demo" zcache (in staging since 2.6.29)
and ramster (in staging since 3.4) to a new stable code base which re-merges
duplicate code and resolves various serious design flaws needed to allow
progress in
On Thu, Aug 16, 2012 at 12:26:02PM +0800, Axel Lin wrote:
> For linear voltage mapping, the n_voltages is (max - min) / step + 1
Applied, thanks.
--
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
Frederic Weisbecker wrote:
> On Thu, Aug 16, 2012 at 02:23:54PM +1000, Michael Neuling wrote:
> > Hi,
> >
> > I've been trying to get hardware breakpoints with perf to work on POWER7
> > but I'm getting the following:
> >
> > % perf record -e mem:0x1000 true
> >
> > Error:
On Thu, Aug 16, 2012 at 08:49:30PM +0530, Shubhrajyoti D wrote:
> Remove the call of platform_set_drvdata(pdev, NULL) as they are not
> needed anymore.
Applied, thanks. These calls were never *needed* people just like to
put them in.
--
To unsubscribe from this list: send the line "unsubscribe
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, August 17, 2012 1:17 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de;
> a...@canonical.com; b...@decadent.org.uk
> Subject: Re: [PATCH V3
On Friday, August 17, 2012, Ming Lei wrote:
> dpm_list and its pm lock provide a good way to iterate all
> devices in system. Except this way, there is no other easy
> way to iterate devices in system.
>
> firmware loader need to cache firmware images for devices
> before system sleep, so
On Thursday 2012-07-26 03:00, Phil Turmel wrote:
>> I used atop to show the transfer speeds to each drive. Here's a
>> screenshot:
>> http://img402.imageshack.us/img402/6484/screenshotfrom201207251.png
>
>[ The output of "lsdrv" [1] might be useful here, along with
>"mdadm -D /dev/md0" and "mdadm
> You could, but why not always just schedule_work()? If we are hosed by
> broken workqueue/scheduler locking, the user isn't going to
> see those files in sysfs either way :)
I'm not concern about failure of sysfs operations.
In panic function call, panic_notifier_chain is kicked. Also users
On 08/17/2012 12:06 AM, mathieu.poir...@linaro.org wrote:
> +static int do_keyreset_event(struct sysrq_state *state,
> + unsigned int code, int value)
> +{
> + int ret;
> + int processed = 0;
> +
> + /* Is the code is of interestest to us */
> +
On Thu, Aug 9, 2012 at 6:01 AM, Glauber Costa wrote:
> Hi,
>
> This is the first part of the kernel memory controller for memcg. It has been
> discussed many times, and I consider this stable enough to be on tree. A
> follow
> up to this series are the patches to also track slab memory. They are
On 08/17/2012 01:02 PM, Laxman Dewangan wrote:
> Tegra20 i2c controller does not support the continue transfer
> which implements the I2C_M_NOSTART functionality of i2c
> protocol mangling.
> Removing the I2C_M_NOSTART functionality for Tegra20.
>
> Signed-off-by: Laxman Dewangan
I tested both
On Fri, Aug 17, 2012 at 2:15 PM, Seiji Aguchi wrote:
>
>> I'm not a fan of creating a periodic timer that wakes up here to check for
>> an event that should be considered very rare.
>>
>> Can this just become scheduled work? Scheduling work itself is a very
>> lightweight process and should be
Mimi Zohar writes:
> On Thu, 2012-08-16 at 15:59 -0400, Josh Boyer wrote:
>> On Thu, Aug 16, 2012 at 3:45 PM, Mimi Zohar wrote:
>> > On Thu, 2012-08-16 at 15:13 -0400, Josh Boyer wrote:
>> >> On Thu, Aug 16, 2012 at 3:08 PM, Mimi Zohar
>> >> wrote:
>> >> >> > +#include "internal.h"
>> >> >> >
On Thursday 2012-07-26 12:10, Michal Marek wrote:
>On 19.7.2012 23:49, Daniel Wisehart wrote:
>> diff --git a/scripts/patch-kernel b/scripts/patch-kernel
>> index d000ea3..a7672eb 100755
>> --- a/scripts/patch-kernel
>> +++ b/scripts/patch-kernel
>> @@ -226,7 +226,7 @@ fi
>>
>> # This all
Pete Clements writes:
> Fyi:
> Get below panic with 3.6-rc2 soon after boot (hand copy of screen).
> [] ? tcp_v4_rcv+0x626/0x740
> [] ? ip_local_deliver_finish+0x6f/0x120
> [] ? ip_rcv+0x2b0/0x2b0
> [] ? ip_rcv_finish+0xe3/0x2d0
> [] ? __netif_receive_skb+03a8/0x4a0
> [] ?
On Fri, Aug 17, 2012 at 09:43:37AM -0700, John Stultz wrote:
> I also have another change pending in -tip that I've marked for
> stable. Once that lands I'm planning on reviewing the current stable
> trees to check that they have all the needed changes.
John, for the record, I have already
> I'm not a fan of creating a periodic timer that wakes up here to check for an
> event that should be considered very rare.
>
> Can this just become scheduled work? Scheduling work itself is a very
> lightweight process and should be relatively safe to do from a
> pstore write.
I agree that
On Fri, Aug 17, 2012 at 02:26:15PM -0400, Paul Gortmaker wrote:
> On 12-08-17 11:22 AM, Herton Ronaldo Krzesinski wrote:
> > On Wed, Aug 15, 2012 at 03:47:58PM -0400, Paul Gortmaker wrote:
> >> From: Mitsuo Hayasaka
> >>
> >>---
> >> This is a commit
Al Viro writes:
> On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
>> On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
>> > > > What's wrong with saying "we don't support idiotify"?
>> > >
>> > > Al, we need some way to restore inotifies after checkpoint.
>> > >
On 08/17/2012 08:45 PM, Joe Perches wrote:
> On Fri, 2012-08-17 at 20:15 +0200, Jiri Slaby wrote:
>> On 08/17/2012 07:39 PM, Joe Perches wrote:
>>> On Fri, 2012-08-17 at 15:42 +0200, Jiri Slaby wrote:
Before calling __ratelimit in __WARN_RATELIMIT, check the condition
first. When this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have observed a strange guest kernel crash in virtualbox and are
currently trying to understand it. Since I have no real 32-bit Intel
platform any more, I cannot verify that this crash would happen on
native 32bit also, so perhaps someone could
On Fri, 17 Aug 2012 22:25:26 +0800 Fengguang Wu
wrote:
> [CC md list]
>
> On Fri, Aug 17, 2012 at 09:40:39AM -0400, Theodore Ts'o wrote:
> > On Fri, Aug 17, 2012 at 02:09:15PM +0800, Fengguang Wu wrote:
> > > Ted,
> > >
> > > I find ext4 write performance dropped by 3.3% on average in the
> >
> This isn't necessary (nor desirable). If the API here is that we get called
> from process context for ->open and ->close(), just use the
> spin_lock_irq and spin_unlock_irq variants for these paths (avoiding the need
> to remove the lock acquire in ->open and ->close.
OK. I will update my
On Fri, Aug 17, 2012 at 10:39:39AM -0400, Steven Rostedt wrote:
> On Fri, 2012-08-17 at 11:04 -0300, Ezequiel Garcia wrote:
> > On Fri, Aug 17, 2012 at 10:55 AM, Steven Rostedt
> > wrote:
> > > On Fri, 2012-08-17 at 08:01 -0300, Ezequiel Garcia wrote:
> > >
> > >> Regarding the 'complete
1 - 100 of 1058 matches
Mail list logo
