On Thu, Jan 10, 2013 at 06:26:55PM +, Arnd Bergmann wrote:
> On Thursday 10 January 2013, Thierry Reding wrote:
> > I don't understand how this would help. The encoding is like this:
> >
> > [27:24] extended register number
> > [23:16] bus number
> > [15:11] device
On Thu, Jan 10, 2013 at 11:20:07AM -0700, Jason Gunthorpe wrote:
> On Thu, Jan 10, 2013 at 11:25:44AM +0100, Thierry Reding wrote:
> > On Thu, Jan 10, 2013 at 09:17:19AM +, Arnd Bergmann wrote:
> > > On Thursday 10 January 2013, Thierry Reding wrote:
> > > > On Wed, Jan 09, 2013 at 04:17:58PM
On Thu, 2013-01-10 at 13:02 +0100, Linus Walleij wrote:
> On Thu, Jan 10, 2013 at 11:57 AM, Russell King - ARM Linux
> wrote:
> > On Thu, Jan 03, 2013 at 10:47:20AM +1300, Tony Prisk wrote:
>
> >> +static int vt8500_gpio_remove(struct platform_device *pdev)
> >> +{
> >> + int i;
> >> +
On Thu, 2013-01-10 at 11:49 +0100, Linus Walleij wrote:
> On Sun, Dec 30, 2012 at 9:29 PM, Tony Prisk wrote:
>
> > The vendor does not provide numbering for gpio pins. Vendor source
> > exports dedicated gpio pins first, followed by multifunction pins.
> > As this is what end users expect, this
The following patch introduces in-place modification of Smack rules.
Until now Smack supported only overwriting of existing rules.
To change permitted access for a given subject and object, user had
to read list of rules to get current accesses, modify it and write
modified rule back to kernel.
Rule modifications are enabled via /smack/change-rule. Format is as follows:
"Subject Object rwaxt rwaxt"
First two strings are subject and object labels up to 255 characters.
Third string contains permissions to enable.
Fourth string contains permissions to disable.
All unmentioned permissions
Hi Rusty,
On Thu, Jan 10, 2013 at 11:30 AM, Rusty Russell wrote:
...
>I now have some lightly-tested code (via a userspace harness).
Great - thank you for looking into this. I will start integrating this
with my patches
when you send out a proper patch.
...
> diff --git
On Thu, Jan 10, 2013 at 10:06:24AM -0800, Kukjin Kim wrote:
> You know, we have several options to avoid it. When you take this series in
> your tree, you can provide topic branch for me. Or this series should be
> separated for arch/arm/ and drivers/ for both trees, then only drivers/iommu
>
The edma_slave_config() implementation depends on the
direction field such that it will not properly configure
a slave channel when called without direction set.
This fixes the implementation so that the slave config
is copied as is and prep_slave_sg() handles the
direction dependent handling.
* Felipe Balbi [130110 04:49]:
> On Thu, Jan 10, 2013 at 03:46:55PM +0530, kishon wrote:
> > On Thursday 10 January 2013 03:34 PM, Benoit Cousson wrote:
> > >
> > >Rob and I did not agree to use that temp hack in the case of DT, so you
> > >were supposed to repost with a proper driver for the SCM
Kukjin Kim wrote:
>
> 'Joerg Roedel' wrote:
> >
> > On Mon, Dec 31, 2012 at 10:18:46AM -0800, Kukjin Kim wrote:
> > > Cho KyongHo wrote:
> >
> > > > Diffstats:
> > > > arch/arm/boot/dts/exynos5250-smdk5250.dts |2 +-
> > > > arch/arm/boot/dts/exynos5250.dtsi | 27 +-
> > > >
Hi,
On Mon, Jan 07, 2013 at 07:11:58PM +0100, Laurent Pinchart wrote:
> > + l2index = (iova >> 12) & 0xff;
> > + spin_lock(_domain->map_lock);
> > + ret = l2alloc(sh_domain, l1index);
>
> l2alloc calls dma_pool_alloc(GFP_KERNEL), that not safe in a non-sleepable
>
On Thu, 2013-01-10 at 10:21 +, Arnd Bergmann wrote:
> On Thursday 10 January 2013, Tony Prisk wrote:
> > On Wed, 2013-01-09 at 21:27 +, Arnd Bergmann wrote:
> > >
> > > > Should patches in pull-requests have Ack'd lines already?
> >
> > This is what I thought - and the reason I haven't
On Thu, Jan 10, 2013 at 6:12 AM, Rafael J. Wysocki wrote:
> Hi,
>
> On Thursday, January 10, 2013 11:28:36 AM Stephen Rothwell wrote:
>> Hi Rafael,
>>
>> Today's linux-next merge of the pm tree got a conflict in
>> drivers/acpi/pci_root.c between commit 3c449ed00759 ("PCI/ACPI: Reserve
>>
On Thursday 10 January 2013, Thierry Reding wrote:
> I don't understand how this would help. The encoding is like this:
>
> [27:24] extended register number
> [23:16] bus number
> [15:11] device number
> [10: 8] function number
> [ 7: 0] register number
>
The exynos code claimed the write protect with devm_gpio_request() but
never did anything with it. That meant that anyone using a write
protect GPIO would effectively be write protected all the time.
The handling for wp-gpios belongs in the main dw_mmc driver and has
been moved there.
The "disable-wp" property is used to specify that a given SD card slot
doesn't have a concept of write protect. This eliminates the need for
special case code for SD slots that should never be write protected
(like a micro SD slot or a dev board).
The dw_mmc driver is special in needing to
The next change will remove the code from the dw_mmc-exynos that added
the DW_MCI_QUIRK_NO_WRITE_PROTECT. Keep existing functionality of
having no write protect pin on smdk5250 by adding the disable-wp
property.
Signed-off-by: Doug Anderson
Acked-by: Seungwon Jeon
---
Changes in v3:
- New for
On some SoCs (like exynos5250) you need to use an external GPIO for
write protect. Add support for wp-gpios to the core dw_mmc driver
since it could be useful across multiple SoCs.
With this change I am able to make use of the write protect for the
external SD slot on exynos5250-snow.
> Acked-by: Tony Luck
>
> [Also Ack for part2 the touches efivars.c]
>
Thanks :)
> -Tony
>
> [Or are you asking me to apply these rather than just Ack them??]
Please apply these to your tree.
Seiji
> -Original Message-
> From: Tony Luck [mailto:tony.l...@gmail.com]
> Sent:
On Thu, Dec 20, 2012 at 7:12 AM, Seiji Aguchi wrote:
> + if (pstore_cannot_block_path(reason)) {
> + is_locked = spin_trylock_irqsave(>buf_lock, flags);
> + if (!is_locked) {
> + pr_err("pstore dump routine blocked in %s path, may
> corrupt
On Thu, Jan 10, 2013 at 11:25:44AM +0100, Thierry Reding wrote:
> On Thu, Jan 10, 2013 at 09:17:19AM +, Arnd Bergmann wrote:
> > On Thursday 10 January 2013, Thierry Reding wrote:
> > > On Wed, Jan 09, 2013 at 04:17:58PM -0700, Jason Gunthorpe wrote:
> > > > On Wed, Jan 09, 2013 at 04:12:31PM
On Thu, Jan 10, 2013 at 09:27:28AM -0800, Colin Cross wrote:
> On Thu, Jan 10, 2013 at 6:02 AM, Don Zickus wrote:
> > On Wed, Jan 09, 2013 at 05:57:39PM -0800, Colin Cross wrote:
> >> Emulate NMIs on systems where they are not available by using timer
> >> interrupts on other cpus. Each cpu will
> > More of my paranoia for array access here. :)
>
> I've added this at the top of pkc7_digest():
>
> if (pkcs7->sig.pkey_hash_algo > PKEY_HASH__LAST ||
> pkey_hash_algo_name[pkcs7->sig.pkey_hash_algo])
There should be a '!' here.
> return -ENOPKG;
David
--
To
On 01/11/2013 01:30 AM, Marcelo Tosatti wrote:
> On Tue, Jan 08, 2013 at 02:38:36PM +0800, Xiao Guangrong wrote:
>> The current reexecute_instruction can not well detect the failed instruction
>> emulation. It allows guest to retry all the instructions except it accesses
>> on error pfn
>>
>> For
'Joerg Roedel' wrote:
>
> On Mon, Dec 31, 2012 at 10:18:46AM -0800, Kukjin Kim wrote:
> > Cho KyongHo wrote:
>
> > > Diffstats:
> > > arch/arm/boot/dts/exynos5250-smdk5250.dts |2 +-
> > > arch/arm/boot/dts/exynos5250.dtsi | 27 +-
> > > arch/arm/mach-exynos/Kconfig
On 01/11/2013 01:26 AM, Marcelo Tosatti wrote:
> On Tue, Jan 08, 2013 at 02:38:36PM +0800, Xiao Guangrong wrote:
>> The current reexecute_instruction can not well detect the failed instruction
>> emulation. It allows guest to retry all the instructions except it accesses
>> on error pfn
>>
>> For
On Wed, Jan 9, 2013 at 1:33 PM, Greg Kroah-Hartman
wrote:
> Note, there are still a lot of patches submitted for inclusion in the
> stable releases that I have not gotten to yet. I wanted to get this
> release out now, instead of delaying for a week or so while I dig
> through all of the pending
On Wed, Jan 9, 2013 at 1:34 PM, Greg Kroah-Hartman
wrote:
> Note, there are still a lot of patches submitted for inclusion in the
> stable releases that I have not gotten to yet. I wanted to get this
> release out now, instead of delaying for a week or so while I dig
> through all of the pending
Hello,
I have a user with uid=1000 that runs a process, let's say with pid 42.
If I do a readlink on /proc/42/exe from another process run by that
same user,
it reads the link correctly.
If root calls readlink on that same link, it works correctly.
The problem is that I have another process
On Wed, Jan 9, 2013 at 1:34 PM, Greg Kroah-Hartman
wrote:
> Note, there are still a lot of patches submitted for inclusion in the
> stable releases that I have not gotten to yet. I wanted to get this
> release out now, instead of delaying for a week or so while I dig
> through all of the pending
Hi Peter,
On Thu, Jan 10, 2013 at 02:36:05PM +0100, Peter Ujfalusi wrote:
> Convert the probe to use devm_*. At the same time reorder the calls
> so we will register the input device as the last step when the driver
> is loaded.
If you are doing this please also use devm_input_allocate_device()
On Tue, Jan 08, 2013 at 07:42:38PM +0900, Takuya Yoshikawa wrote:
> Changelog v1->v2:
> The condition in patch 1 was changed like this:
> npages && (mem->flags & KVM_MEM_LOG_DIRTY_PAGES)
>
> This patch set makes kvm_mmu_slot_remove_write_access() rmap based and
> adds conditional
Hi Laxman,
On Thu, Jan 10, 2013 at 12:01:23PM +0530, Laxman Dewangan wrote:
> Hi Dmitry,
>
> On Monday 07 January 2013 10:22 PM, Stephen Warren wrote:
> >On 01/06/2013 04:14 AM, Laxman Dewangan wrote:
> >>This patch series:
> >> - fix build warning,
> >> - use devm_* for allocation,
> >> -
* Rik van Riel [2013-01-08 17:32:52]:
> Moving the wait loop for congested loops to its own function allows
> us to add things to that wait loop, without growing the size of the
> kernel text appreciably.
>
> Signed-off-by: Rik van Riel
> Reviewed-by: Steven Rostedt
> Reviewed-by: Michel
(Sorry Mel, you're getting this twice because I forgot CC's last time)
On 01/10/2013 03:36 AM, Mel Gorman wrote:
Any particular reason you did not use scripts/gfp-translate?
Because I didn't look hard enough & didn't see it :(
Script is dumb as rocks, requires access to the source code and
* Rafael Aquini [2013-01-10 00:27:23]:
> On Wed, Jan 09, 2013 at 06:20:35PM +0530, Raghavendra K T wrote:
> > I ran kernbench on 32 core (mx3850) machine with 3.8-rc2 base.
> > x base_3.8rc2
> > + rik_backoff
> > N Min MaxMedian AvgStddev
> > x
On Thu, Jan 10, 2013 at 03:30:36PM -0200, Marcelo Tosatti wrote:
> On Tue, Jan 08, 2013 at 02:38:36PM +0800, Xiao Guangrong wrote:
> > The current reexecute_instruction can not well detect the failed instruction
> > emulation. It allows guest to retry all the instructions except it accesses
> > on
[Issue]
Currently, irq vector handlers for tracing are just
copied non-trace handlers by simply inserting tracepoints.
It is difficult to manage the codes.
[Solution]
This patch shares common codes between non-trace and trace handlers
as follows to make them manageable and readable.
[Purpose of this patch]
As Vaibhav explained in the thread below, tracepoints for irq vectors
are useful.
http://www.spinics.net/lists/mm-commits/msg85707.html
The current interrupt traces from irq_handler_entry and irq_handler_exit
provide when an interrupt is handled. They provide good data
On 01/09/2013 02:07 PM, Yves DUF wrote:
Hello Mister Mattock.
I hope this email will not bother you. It's about the eGalax
Touchscreen driver you modify more or less recently.
I try to use it on a archos 9 tablet PC, with tricks from that link and others:
Change log
v6 -> v7
- Divide into two patches to make a code review easier.
Summery of each patch is as follows.
- Patch 1/2
- Add an irq_vector tracing infrastructure.
- Create idt_table for tracing. It is refactored to avoid duplicating
existing logic.
-
On Tue, Jan 08, 2013 at 02:38:36PM +0800, Xiao Guangrong wrote:
> The current reexecute_instruction can not well detect the failed instruction
> emulation. It allows guest to retry all the instructions except it accesses
> on error pfn
>
> For example, some cases are nested-write-protect - if the
On Tue, Jan 08, 2013 at 02:38:36PM +0800, Xiao Guangrong wrote:
> The current reexecute_instruction can not well detect the failed instruction
> emulation. It allows guest to retry all the instructions except it accesses
> on error pfn
>
> For example, some cases are nested-write-protect - if the
On 01/10/2013 05:29 PM, Florian Westphal wrote:
> Alan Cox wrote:
>> > On Thu, 10 Jan 2013 15:46:26 +0100
>> > Florian Westphal wrote:
>>> > > Frank Lichtenheld discovered that openpty() doesn't work anymore when
>>> > > /dev/pts is not present.
>>> > >
>>> > > We bisected this down to
>>> > >
On Thu, Jan 10, 2013 at 6:02 AM, Don Zickus wrote:
> On Wed, Jan 09, 2013 at 05:57:39PM -0800, Colin Cross wrote:
>> Emulate NMIs on systems where they are not available by using timer
>> interrupts on other cpus. Each cpu will use its softlockup hrtimer
>> to check that the next cpu is
On 10/01/13 15:02, Adrian Byszuk wrote:
> On 10/01/13 12:35, Borislav Petkov wrote:
>> On Thu, Jan 10, 2013 at 11:59:48AM +0100, Adrian Byszuk wrote:
>>> I think I won't get the answer this way. Bisecting between
>>> 3.7 and 3.8-rc2 (from linus tree) led me to commit
>>>
On Mon, Dec 31, 2012 at 10:18:46AM -0800, Kukjin Kim wrote:
> Cho KyongHo wrote:
> > Diffstats:
> > arch/arm/boot/dts/exynos5250-smdk5250.dts |2 +-
> > arch/arm/boot/dts/exynos5250.dtsi | 27 +-
> > arch/arm/mach-exynos/Kconfig |5 -
> >
On Sat, Jan 05, 2013 at 08:37:46AM +, Alex Shi wrote:
> If the wake/exec task is small enough, utils < 12.5%, it will
> has the chance to be packed into a cpu which is busy but still has space to
> handle it.
>
> Signed-off-by: Alex Shi
> ---
> kernel/sched/fair.c | 51
On 01/10/2013 09:31 AM, James Hogan wrote:
> Add oprofile support for metag.
>
> Signed-off-by: James Hogan
> Cc: Robert Richter
> Cc: oprofile-l...@lists.sf.net
> ---
> arch/metag/Kconfig|1 +
> arch/metag/Makefile |2 +
>
Copy the modified timex data back to the user also with positive return
values. This fixes reading of the CLOCK_REALTIME timex data when the
clock is in a non-zero state.
Signed-off-by: Miroslav Lichvar
---
kernel/posix-timers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, Jan 10, 2013 at 9:01 AM, Vivek Goyal wrote:
> On Thu, Jan 10, 2013 at 08:53:18AM -0800, Yinghai Lu wrote:
>> On Thu, Jan 10, 2013 at 6:26 AM, Vivek Goyal wrote:
>> >
>> > This happens only in case of kdump and not kexec. In case of kdump
>> > we want second kernel to use only selected
On Mon, Jan 07, 2013 at 06:51:52PM +1100, Alexey Kardashevskiy wrote:
> The iommu_init() initializes IOMMU internal structures and data
> required for the IOMMU API as iommu_group_alloc().
> It is registered as a subsys_initcall now.
>
> One of the IOMMU users is going to be a PCI subsystem on
Hello.
On 01/10/2013 07:51 PM, Roger Quadros wrote:
> We use "vcc" as the supply name for the PHY's power supply.
> The power supply will be enabled during .init() and disabled
> during .shutdown()
> Signed-off-by: Roger Quadros
> ---
> drivers/usb/otg/nop-usb-xceiv.c | 18
On Thu, Jan 10, 2013 at 4:19 AM, Borislav Petkov wrote:
> This is not how SOB chaining works:
>
> SOB: Author
> SOB: Handler - this is you, who has added it to the patchset
> SOB: Committer - maintainer
>
> You need to read Documentation/SubmittingPatches if there's still things
> unclear.
On 13-01-10 09:43 AM, Ben Hutchings wrote:
> On Tue, 2013-01-08 at 18:35 -0500, Paul Gortmaker wrote:
>> From: Jan Kara
>>
>>---
>> This is a commit scheduled for the next v2.6.34 longterm release.
>>
On Thu, Jan 10, 2013 at 08:53:18AM -0800, Yinghai Lu wrote:
> On Thu, Jan 10, 2013 at 6:26 AM, Vivek Goyal wrote:
> >
> > This happens only in case of kdump and not kexec. In case of kdump
> > we want second kernel to use only selected memory areas.
> >
> > In fact this is one improvement area.
On Thu, 2013-01-10 at 16:48 +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2012-12-13 at 11:58 +, Arnd Bergmann wrote:
> > On Wednesday 12 December 2012, Joe Perches wrote:
> > > Use the new vsprintf extension to avoid any possible
> > > message interleaving.
> > >
> > > Convert the #ifdef
On Thu, Jan 10, 2013 at 05:18:40PM +0100, Frederic Weisbecker wrote:
> 2013/1/10 Russell King - ARM Linux :
> > On Thu, Jan 10, 2013 at 09:02:15AM -0500, Don Zickus wrote:
> >> On Wed, Jan 09, 2013 at 05:57:39PM -0800, Colin Cross wrote:
> >> > Emulate NMIs on systems where they are not available
On Wed 09-01-13 15:26:43, Namjae Jeon wrote:
> 2012/12/13, Namjae Jeon :
> > 2012/10/19, Namjae Jeon :
> >> 2012/10/19, Jan Kara :
> >>> Hello,
> >>>
> >>> On Wed 10-10-12 00:10:01, Namjae Jeon wrote:
> From: Namjae Jeon
>
> This patch implements extent caching.
> Instead of
On Thu, 10 Jan 2013 11:42:41 -0500
Mathieu Desnoyers wrote:
> * Stephen Hemminger (shemmin...@vyatta.com) wrote:
> > On Wed, 9 Jan 2013 13:46:17 -0500
> > Mathieu Desnoyers wrote:
> >
> > > liburcu is a LGPLv2.1 userspace RCU (read-copy-update) library. This
> > > data synchronization library
On 01/10/2013 07:30 AM, James Hogan wrote:
> +pte_t *huge_pte_alloc(struct mm_struct *mm,
> + unsigned long addr, unsigned long sz)
> +{
> + pgd_t *pgd;
> + pud_t *pud;
> + pmd_t *pmd;
> + pte_t *pte;
> +
> + pgd = pgd_offset(mm, addr);
> + pud =
This API allows PHY users to get the usb_phy data structure
from a device handle.
Signed-off-by: Roger Quadros
---
drivers/usb/otg/otg.c | 36
include/linux/usb/phy.h |6 ++
2 files changed, 42 insertions(+), 0 deletions(-)
diff --git
PHY reset GPIO handling will be done in the PHY driver
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 47 ---
1 files changed, 0 insertions(+), 47 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c b/drivers/mfd/omap-usb-host.c
index
Reset GPIO handling for the PHY must be done in the PHY
driver. We use the PHY helpers instead to reset the PHY.
Signed-off-by: Roger Quadros
---
drivers/usb/host/ehci-omap.c | 70 ++
1 files changed, 10 insertions(+), 60 deletions(-)
diff --git
If the PHY has a clock associated to it then manage the clock.
We just enable the clock in .init() and disable it in .shutdown().
Add clk_rate parameter in platform data and configure the
clock rate during probe if supplied.
Signed-off-by: Roger Quadros
---
drivers/usb/otg/nop-usb-xceiv.c |
PHY regulator handling must be done in the PHY driver
Signed-off-by: Roger Quadros
---
drivers/usb/host/ehci-omap.c | 31 +--
1 files changed, 1 insertions(+), 30 deletions(-)
diff --git a/drivers/usb/host/ehci-omap.c b/drivers/usb/host/ehci-omap.c
index
Let's have a single platform data structure for the OMAP's High-Speed
USB host subsystem instead of having 3 separate ones i.e. one for
board data, one for USB Host (UHH) module and one for USB-TLL module.
This makes the code much simpler and avoids creating multiple copies of
platform data.
EHCI driver would need to know the number of ports available
on the platform. We set the nports parameter of platform_data
based on IP version if it was not already provided.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
We use "vcc" as the supply name for the PHY's power supply.
The power supply will be enabled during .init() and disabled
during .shutdown()
Signed-off-by: Roger Quadros
---
drivers/usb/otg/nop-usb-xceiv.c | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git
On Thu, Jan 10, 2013 at 6:26 AM, Vivek Goyal wrote:
>
> This happens only in case of kdump and not kexec. In case of kdump
> we want second kernel to use only selected memory areas.
>
> In fact this is one improvement area. Instead of using memmap= entries
> in kdump case, we should probably
If the OMAP's Host controller is in PHY mode then we instantiate
a platform device for the PHY (one for each port in PHY mode) and
hold a reference to it so that we can use the usb_phy API, e.g.
while suspend/resume.
The platform data for the PHY must be supplied in the newly added
.phy_config
We model the HUB_RESET GPIO as a fixed regulator device. This regulator
is then used as "reset" supply for the USB PHY device and is managed
by the PHY driver.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/board-omap4panda.c | 48 ++--
1 files changed, 33
These platform data bits are no longer used so remove them.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/board-omap4panda.c |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
b/arch/arm/mach-omap2/board-omap4panda.c
Provide platform data for the USB host's PHY.
Also get rid of managing PHY clock. This will now be done by the phy driver.
For that to work we create a clock alias that links the PHY clock name to the
PHY device name.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/board-omap4panda.c |
We model the HUB_POWER GPIO as a fixed regulator device. This regulator
is then used as "vcc" supply for the USB PHY device and is managed
by the PHY driver.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/board-omap4panda.c | 38 +++
1 files changed, 33
We expect the RESET line to be modeled as a regulator with supply
name "reset". The regulator should be modeled such that enabling
the regulator brings the PHY device out of RESET and disabling the
regulator holds the device in RESET.
They PHY will be held in RESET in .shutdown() and brought out
The OMAP's High Speed Host controller can interface to ULPI/UTMI
PHY's transparently i.e. whithout requiring the device drivers to
access the PHY [1]. However, the OS must ensure that the PHY has
the necessary resources (power/clock/reset) enabled before it is used.
Till now, the omap-ehci driver
Linus,
I just hit this bug with the lastest kernel. A change that came in this
merge window broke the writing to the trace_options file. It causes
garbage to be read during the compare of option names, and breaks
setting options via the trace_options file, although options can still
be set via
* Stephen Hemminger (shemmin...@vyatta.com) wrote:
> On Wed, 9 Jan 2013 13:46:17 -0500
> Mathieu Desnoyers wrote:
>
> > liburcu is a LGPLv2.1 userspace RCU (read-copy-update) library. This
> > data synchronization library provides read-side access which scales
> > linearly with the number of
On Fri, 2013-01-11 at 00:14 +0900, Tetsuo Handa wrote:
> The reason I think is that people turn off LSMs because they are using LSMs
> without understanding "what the current configuration is" and/or "how to
> change
> configuration". People do not spend (or cannot afford spending) resources for
On Thu, 10 Jan 2013 15:07:42 +0100, Laurent Navet wrote:
> avoid these checkpatch.pl issues :
> - ERROR: "foo * bar" should be "foo *bar"
> - ERROR: switch and case should be at the same indent
> - ERROR: "(foo*)" should be "(foo *)"
> - ERROR: do not use assignment in if condition
> - ERROR:
On Wed, 9 Jan 2013 13:46:17 -0500
Mathieu Desnoyers wrote:
> liburcu is a LGPLv2.1 userspace RCU (read-copy-update) library. This
> data synchronization library provides read-side access which scales
> linearly with the number of cores. It does so by allowing multiples
> copies of a given data
Alan Cox wrote:
> On Thu, 10 Jan 2013 15:46:26 +0100
> Florian Westphal wrote:
> > Frank Lichtenheld discovered that openpty() doesn't work anymore when
> > /dev/pts is not present.
> >
> > We bisected this down to
> >
> > commit bbb63c514a3464342967237a51a21ea8f61ab951
> > Author: Wanlong Gao
On Thu, Jan 10, 2013 at 4:38 AM, Borislav Petkov wrote:
> [ deliberately breaking the thread because it got too long]
>
> On Sat, Dec 22, 2012 at 09:35:47PM +0100, Borislav Petkov wrote:
>> Hi Alex,
>>
>> got the sickest bug on 3.8-rc1, see below. The GPU locks up somewhere
>> down
2013/1/10 Russell King - ARM Linux :
> On Thu, Jan 10, 2013 at 09:02:15AM -0500, Don Zickus wrote:
>> On Wed, Jan 09, 2013 at 05:57:39PM -0800, Colin Cross wrote:
>> > Emulate NMIs on systems where they are not available by using timer
>> > interrupts on other cpus. Each cpu will use its
Hello.
On 01/10/2013 06:35 PM, Maxime Ripard wrote:
> Commit 09f6ffde introduced a dependency on USB_EHCI_HCD for the chipidea
Please also specify the summary of that commit in parens (or however you
like).
> USB host driver, that in turns depends on USB_ARCH_HAS_EHCI.
> If this symbol is
Hi Steven,
On 10/01/13 15:59, Steven Rostedt wrote:
> On Thu, 2013-01-10 at 15:31 +, James Hogan wrote:
>> +#include
>> +#include
>> +#include
>> +#include
>
> duplicate
Thanks, I'll fix.
> The rest looks good.
Thanks for reviewing
Cheers
James
--
To unsubscribe from this list:
Kees Cook wrote:
> This is a quick review of the devel-pekeys tree...
Thanks!
> +static int public_key_verify_signature_2(const struct key *key,
>
> Maybe name this "key_verify_signature" instead of using the trailing _2?
I would prefer that it begin with "public_key_" as that reflects the
On 01/10/13 07:26, Michal Nazarewicz wrote:
> On Thu, Jan 10 2013, Minchan Kim wrote:
>> getc returns "int" so EOF could be -1 but storing getc's return
>> value to char directly makes the vaule to 255 so below condition
>> is always false.
>
> Technically, this is implementation defined and I
Hi, few comments/questions below.
On 01/10/2013 04:31 PM, James Hogan wrote:
> --- /dev/null
> +++ b/drivers/tty/metag_da.c
> @@ -0,0 +1,696 @@
...
> +struct dashtty_port {
> + struct tty_port port;
> + spinlock_t rx_lock;
> + void*rx_buf;
>
On Thu, 2013-01-10 at 10:59 -0500, Steven Rostedt wrote:
> The rest looks good.
>
> Acked-by: Steven Rostedt
Change that to:
Reviewed-by: Steven Rostedt
Thanks,
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, 2013-01-10 at 15:31 +, James Hogan wrote:
> --- /dev/null
> +++ b/arch/metag/kernel/ftrace.c
> @@ -0,0 +1,127 @@
> +/*
> + * Copyright (C) 2008 Imagination Technologies Ltd.
> + * Licensed under the GPL
> + *
> + * Dynamic ftrace support.
> + */
> +
> +#include
> +#include
>
On Thu, 2013-01-10 at 16:32 +0100, Paul Bolle wrote:
> I haven't investigated in depth what happened, so this can even be something
> dumb
> on my side during build.
Not during build but definitely dumb and on my side. (Please don't ask.)
Apologies for the noise.
Paul Bolle
--
To unsubscribe
Make asm-generic/io.h check CONFIG_VIRT_TO_BUS before defining
virt_to_bus() and bus_to_virt(), otherwise it's easy to accidentally
have a silently failing incorrect direct mapped definition rather then
no definition at all.
Signed-off-by: James Hogan
Acked-by: Arnd Bergmann
---
Some 32 bit architectures require 64 bit values to be aligned (for
example Meta which has 64 bit read/write instructions). These require 8
byte alignment of event data too, so use
!CONFIG_HAVE_64BIT_ALIGNED_ACCESS instead of !CONFIG_64BIT ||
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS to decide
The commit "binfmt_elf: cleanups"
(f670d0ecda73b7438eec9ed108680bc5f5362ad8) removed an ifndef elf_map but
this breaks compilation for metag which does define elf_map.
This adds the ifndef back in as it was before, but does not affect the
other cleanups made by that patch.
Signed-off-by: James
Add the header describing addresses, fields, and bits
of various core memory mapped registers in the low non-MMU region.
Signed-off-by: James Hogan
---
arch/metag/include/asm/metag_mem.h | 1106
1 files changed, 1106 insertions(+), 0 deletions(-)
create
Add a couple of header files containing core architecture constants.
The first () contains some constants relating to the
instruction set, such as values to give to the CACHEW and CACHER
instructions.
The second () contains constants for the core register
units directly accessible to various
Add boot code for metag. Due to the multi-threaded nature of Meta it is
not uncommon for an RTOS or bare metal application to be started on
other hardware threads by the bootloader. Since there is a single MMU
switch which affects all threads, the MMU is traditionally configured by
the bootloader
301 - 400 of 1352 matches
Mail list logo
