On Mon, Apr 14, 2014 at 06:27:10PM +0900, Masahiro Yamada wrote:
> W=... provides extra gcc checks.
>
> Having such code in scripts/Makefile.build results in the same flags
> being added to KBUILD_CFLAGS multiple times becuase
> scripts/Makefile.build is invoked every time Kbuild descends into
> t
On Wed, Apr 16, 2014 at 12:06:03PM +0100, Lee Jones wrote:
> s/regmap/Regmap
It's consistently written regmap in all the documentation and so on :)
> addmap{0,1} doesn't quite sit right with me.
> REVISIT: Ah, it's address-map, rather than add map. Okay, not as bad
> as I first thought, but sti
On Wed, Apr 16, 2014 at 4:23 PM, delicious quinoa
wrote:
> On Thu, Apr 3, 2014 at 3:40 PM, delicious quinoa
> wrote:
>> On Fri, Mar 28, 2014 at 1:27 PM, delicious quinoa
>> wrote:
>>> On Tue, Mar 18, 2014 at 4:55 PM, Pantelis Antoniou
>>> wrote:
The following patchset introduces Device Tre
Mark,
On Wed, Apr 16, 2014 at 1:51 PM, Mark Brown wrote:
> On Wed, Apr 16, 2014 at 11:25:24AM -0700, Doug Anderson wrote:
>> An issue was discovered with tps65090 where sometimes the FETs
>> wouldn't actually turn on when requested (they would report
>> overcurrent). The most problematic FET was
On Wed, 16 Apr 2014 17:13:18 -0400 Johannes Weiner wrote:
> Per-memcg swappiness and oom killing can currently not be tweaked on a
> memcg that is part of a hierarchy, but not the root of that hierarchy.
> Users have complained that they can't configure this when they turned
> on hierarchy mode.
On Wed, Apr 16, 2014 at 4:44 PM, Paul E. McKenney
wrote:
> Good catch, queued for 3.16! I missed it because of my habit of building
> the torture tests directly into the kernel rather than loading them
> as modules. So thank you both for the patch and for your testing efforts!
>
You are welcome
On Monday, April 14, 2014 10:54 PM, Chase Southwood wrote:
> devpriv->iobase is currently being used to hold the iobase address used to
> read/write the board's registers. The same address is stored in the
> comedi_device dev->iobase. We use that instead. The eventual goal is to
> decrease the d
Add the device tree binding support for the v1.3.0 version of the QCOM BAM DMA
driver.
Signed-off-by: Andy Gross
---
.../devicetree/bindings/dma/qcom_bam_dma.txt |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt
On Tue, 15 Apr 2014, Imre Deak wrote:
> On Tue, 2014-04-15 at 21:43 +0200, Daniel Vetter wrote:
>> On Mon, Apr 14, 2014 at 11:56:03AM -0700, Steven Noonan wrote:
>> > On Mon, Apr 14, 2014 at 11:35:05AM -0700, Keith Packard wrote:
>> > > Steven Noonan writes:
>> > >
>> > > > Was using my machine
This set of patches adds support for the v1.3.0 version of the QCOM BAM
dmaengine driver. The older version of the BAM is present in the MSM8x64,
APQ8064, and IPQ8064 processors.
Due to register address space changes between versions, all of the register
accesses have to be calculated using diffe
This patch adds support for the v1.3.0 version of the BAM dma ip block. This
patch adds register access abstraction to deal with the changes to the register
map between the two versions. Blocks of registers moved around within the
address space, and multipliers used for calculating the pipe regis
On Wed, Apr 16, 2014 at 04:46:01PM -0400, Pranith Kumar wrote:
> remove an unused duplicate definition of torture_param
>
> Signed-off-by: Pranith Kumar
This one confused me at first because I could only find one torture_param().
I applied the patch anyway, and it built without errors. I looked
On Wed, Apr 16, 2014 at 05:34:26PM -0400, Pranith Kumar wrote:
> On Wed, Apr 16, 2014 at 4:44 PM, Paul E. McKenney
> wrote:
> > Good catch, queued for 3.16! I missed it because of my habit of building
> > the torture tests directly into the kernel rather than loading them
> > as modules. So than
On Tuesday, April 15, 2014 11:58 PM, Chase Southwood wrote:
> We can remove this function from the boardinfo and move the code from
> hwdrv_apci1564.c into addi_apci_1564.c since it is the only reset function
> used by the driver. The function was also messy and failed to reset a few
> registers, t
On Wed, Apr 16, 2014 at 02:34:47PM -0700, Doug Anderson wrote:
> On Wed, Apr 16, 2014 at 1:51 PM, Mark Brown wrote:
> > Please don't send new patches as replies in the middle of threads, it
> > makes it confusing trying to work out which versions of things should be
> > applied.
> I'm a little c
Hello,
On Wed, Apr 09, 2014 at 09:21:08AM -0600, Shuah Khan wrote:
> +#define TOKEN_DEVRES_FREE0
> +#define TOKEN_DEVRES_BUSY1
> +
> +struct token_devres {
> + int status;
> + charid[];
> +};
Please just do "bool busy" and drop the constants.
> +struct tkn_match {
> +
On Wed, Apr 16, 2014 at 2:46 PM, Jani Nikula
wrote:
> On Tue, 15 Apr 2014, Imre Deak wrote:
>> On Tue, 2014-04-15 at 21:43 +0200, Daniel Vetter wrote:
>>> On Mon, Apr 14, 2014 at 11:56:03AM -0700, Steven Noonan wrote:
>>> > On Mon, Apr 14, 2014 at 11:35:05AM -0700, Keith Packard wrote:
>>> > > St
ebied...@xmission.com (Eric W. Biederman) writes:
> There are a lot of ways we could approach this, and I sat down and wrote
> the simplest variant I could think of, so hopefully there are not silly
> bugs that get overlooked.
>
> The code move all cleanup from mntput that would do filesystem I/O
On Wed, Apr 16, 2014 at 02:17:08PM -0700, H. Peter Anvin wrote:
> On 04/16/2014 12:03 PM, Marcelo Tosatti wrote:
> >> @@ -3550,9 +3550,9 @@ static void reset_rsvds_bits_mask(struct kvm_vcpu
> >> *vcpu,
> >>break;
> >>case PT64_ROOT_LEVEL:
> >>context->rsvd_bits_mask[0][
On Mon, Mar 24, 2014 at 6:28 AM, Catalin Marinas
wrote:
> On Fri, Mar 21, 2014 at 09:08:46PM +, Rob Herring wrote:
>> From: Rob Herring
>>
>> Add earlycon support for the pl011 serial port. This allows enabling
>> the pl011 for console when early_params are processed. This is based
>> on the
On Sun, 13 Apr 2014 22:09:17 +0200 Fabian Frederick wrote:
> Fixing coccinelle warning
Please always quote the full error message or warning text when fixing
such things.
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -2376,7 +2376,7 @@ next_lv:
> if (lv)
>
On 2014-04-16 20:32, Zhang Rui wrote:
On Sun, 2014-04-13 at 02:05 +0200, Manuel Krause wrote:
On 2014-04-11 00:51, Manuel Krause wrote:
On 2014-04-07 13:45, Rafael J. Wysocki wrote:
On Monday, April 07, 2014 01:17:51 AM Manuel Krause wrote:
On 2014-04-06 04:43, Guenter Roeck wrote:
On 04/05/
Sound whispers,
WARNING: CPU: 3 PID: 900 at lib/dma-debug.c:593
debug_dma_assert_idle+0x159/0x1d0()
snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped
cacheline [cln=0x03014000]
CPU: 3 PID: 900 Comm: chronyd Not tainted 3.15.0-0.rc1.git1.1.fc21.i686 #1
Call Trace:
[] dum
On 04/17/2014 12:50 AM, Tejun Heo wrote:
> Hello, Lai.
>
> On Thu, Apr 17, 2014 at 12:21:21AM +0800, Lai Jiangshan wrote:
>> OK. It is better to use get_pwq(). I will also change the above comments to:
>>
>> The base ref and the possible ref from rerscuer(stopped) are never
>> dropped on per-cpu
On Wed, Apr 16, 2014 at 02:31:38PM -0600, Bjorn Helgaas wrote:
> On Wed, Apr 16, 2014 at 09:04:04PM +0200, Borislav Petkov wrote:
> > On Thu, Mar 20, 2014 at 02:48:30PM -0600, Bjorn Helgaas wrote:
> > > Right. Even if we had this long-term solution, we'd still have
> > > Stephane's current pro
>> --- a/drivers/fmc/fmc-chardev.c
>> +++ b/drivers/fmc/fmc-chardev.c
>> @@ -141,8 +141,8 @@ static int fc_probe(struct fmc_device *fmc)
>> fc->misc.fops = &fc_fops;
>> fc->misc.name = kstrdup(dev_name(&fmc->dev), GFP_KERNEL);
>>
>> -spin_lock(&fc_lock);
>> ret = misc_register(
Am 16.04.2014 22:00, schrieb Michael Kerrisk (man-pages):
> [CC += Jeremy Allison]
>
> On Wed, Apr 16, 2014 at 8:57 PM, Jeff Layton wrote:
>> Sorry to spam so many lists, but I think this needs widespread
>> distribution and consensus.
>>
>> File-private locks have been merged into Linux for v3.1
On Sun, 13 Apr 2014 20:05:34 +0200 Manfred Spraul
wrote:
> Hi Andrew,
>
> On 04/02/2014 12:08 AM, Andrew Morton wrote:
> > Well, I'm assuming 64GB==infinity. It *was* infinity in the RHEL5
> > timeframe, but infinity has since become larger so pickanumber.
>
> I think infinity is the right s
On Wed, 2014-04-16 at 15:15 -0700, Andrew Morton wrote:
> On Sun, 13 Apr 2014 22:09:17 +0200 Fabian Frederick wrote:
> > Fixing coccinelle warning
[]
> > @@ -2376,7 +2376,7 @@ next_lv:
[]
> > - if (record_cnt == 0 && ordered == false) {
> > + if (record_cnt == 0
From: mr...@linux.ee
Date: Thu, 17 Apr 2014 01:22:17 +0300 (EEST)
>> > Just for the archives, I got one of these again with 3.14:
>>
>> Meelis and Aaro, thanks again for all of your reports.
>>
>> After pouring over a lot of the data and auditing some code I'm
>> suspecting it's a problem with t
> > Just for the archives, I got one of these again with 3.14:
>
> Meelis and Aaro, thanks again for all of your reports.
>
> After pouring over a lot of the data and auditing some code I'm
> suspecting it's a problem with transparent huge pages.
>
> One thing you two can do to help me further c
On Wed, Apr 16, 2014 at 09:06:24AM -0700, Eric Dumazet wrote:
> From: Eric Dumazet
>
> Calling rcu_bh_qs() after every softirq action is not really needed.
>
> What RCU needs is at least one rcu_bh_qs() per softirq round to note a
> quiescent state was passed for rcu_bh
>
> Note for Paul and my
On Wed, Apr 16, 2014 at 06:31:22PM -0400, Dave Jones wrote:
> On Wed, Apr 16, 2014 at 02:31:38PM -0600, Bjorn Helgaas wrote:
> > On Wed, Apr 16, 2014 at 09:04:04PM +0200, Borislav Petkov wrote:
> > > On Thu, Mar 20, 2014 at 02:48:30PM -0600, Bjorn Helgaas wrote:
> > > > Right. Even if we had th
Mark,
On Wed, Apr 16, 2014 at 2:54 PM, Mark Brown wrote:
> On Wed, Apr 16, 2014 at 02:34:47PM -0700, Doug Anderson wrote:
>> On Wed, Apr 16, 2014 at 1:51 PM, Mark Brown wrote:
>
>> > Please don't send new patches as replies in the middle of threads, it
>> > makes it confusing trying to work out
On Sat, 5 Apr 2014, Greg KH wrote:
> On Mon, Mar 31, 2014 at 01:18:34PM +0200, Thomas Gleixner wrote:
> > On Thu, 27 Mar 2014, Vince Weaver wrote:
> > > On Wed, 26 Mar 2014, Thomas Gleixner wrote:
> > > > Ok. So we know now what we are looking for.
> > > >
> > > > [1.579996] Serial: 8250/16550
On Wed, Apr 16, 2014 at 2:03 AM, Tomi Valkeinen wrote:
>
> The drivers/video/Kconfig change in this pull request will conflict with the
> fbdev reorder series, which is not yet in your tree. If that's an issue, I can
> resend this without the Kconfig change.
I was actually hoping/expecting you to
On Thu, Mar 27, 2014 at 12:30:34PM +0100, Paolo Bonzini wrote:
> About 25% of the time spent in emulation of invalid guest state
> is wasted in checking whether emulation is required for the next
> instruction. However, this almost never changes except when a
> segment register (or TR or LDTR) cha
On Fri, 11 Apr 2014 13:42:32 -0700 Dave Hansen wrote:
>
> I recently added a patch to let folks pass a "reason" string
> dump_page() which gets dumped out along with the page's data.
> This essentially saves the bug-reader a trip in to the source
> to figure out why we BUG_ON()'d.
>
> The new V
On Wed, Apr 16, 2014 at 1:31 PM, Bjorn Helgaas wrote:
> On Wed, Apr 16, 2014 at 09:04:04PM +0200, Borislav Petkov wrote:
>> On Thu, Mar 20, 2014 at 02:48:30PM -0600, Bjorn Helgaas wrote:
>> > Right. Even if we had this long-term solution, we'd still have
>> > Stephane's current problem, because t
VDDIO_SDMMC3 is the VQMMC (I/O) supply, not the VMMC (core) supply,
for the SD slot on Venice2.
Signed-off-by: Andrew Bresticker
---
Changes from v1:
- removed vqmmc supply for eMMC
---
arch/arm/boot/dts/tegra124-venice2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ar
Tegra SDHCI controllers, by default, report a base clock frequency
of 208Mhz in SDHCI_CAPABILTIES which may or may not be equal to the
actual base clock frequency. This is because the clock rate is
configured by the clock controller, which is external to the SD/MMC
controller. Since the SD/MMC co
Program TEGRA_SDHCI_VENDOR_MISC_CTRL so that UHS modes aren't advertised
in SDHCI_CAPABILITIES_1. While the Tegra SDHCI controller does support
these modes, they require Tegra-specific tuning and calibration routines
which the driver does not support yet.
Signed-off-by: Andrew Bresticker
---
No
On Wed, Apr 16, 2014 at 5:14 PM, Paul E. McKenney
wrote:
>
> This fails for me. The problem is that the defined macro makes everything
> static, and rcutorture_runnable is used in kernel/sysctl.c. :-/
>
> In theory, it would be possible to make torture_param() take "static"
> as a parameter, but
On Wed, Apr 16, 2014 at 5:08 PM, Stephane Eranian wrote:
> On Wed, Apr 16, 2014 at 1:31 PM, Bjorn Helgaas wrote:
>> On Wed, Apr 16, 2014 at 09:04:04PM +0200, Borislav Petkov wrote:
>>> On Thu, Mar 20, 2014 at 02:48:30PM -0600, Bjorn Helgaas wrote:
>>> > Right. Even if we had this long-term solut
These five patches bring tps65090 up to speed with what's currently
in the Chromium OS kernel 3.8 tree and running on the Samsung ARM
Chromebook. Changes were tested atop the current linux tree
(v3.15-rc1). FET retries were tested on a machine with a known flaky
tps65090. Since display isn't wor
The tps65090 regulator allows you to specify how long you want it to
wait before detecting an overcurrent condition. Allow specifying that
through the device tree (or through platform data).
Signed-off-by: Doug Anderson
Signed-off-by: Simon Glass
Signed-off-by: Michael Spang
Signed-off-by: Sea
On the ARM Chromebook tps65090 has two masters: the AP (the main
processor running linux) and the EC (the embedded controller). The AP
is allowed to mess with FETs but the EC is in charge of charge control.
The tps65090 interupt line is routed to both the AP and the EC, which
can cause quite a he
We offer the right solution to your financial needs.
We stand apart from other lenders because we believe in customer service,
and we stay with you until you get the results you want. In general we
offer home loans,car loans,hotel loans,commercial loans, business loans,
e.t.c, Contact us via E-MAIL
Laba diena,
Tas ir GT Bank plc, likumīgu un aizņemties naudu, lai akreditētu
company.We aizdevumiem ar zemu procentu likmi 2.1%. Mēs aizņemties naudu, lai
cilvēkiem, kuriem ir nepieciešama finansiāla palīdzība. Vai jums ir slikta
kredītu vai jums ir nepieciešama nauda, lai samaks
An issue was discovered with tps65090 where sometimes the FETs
wouldn't actually turn on when requested (they would report
overcurrent). The most problematic FET was the one used for the LCD
backlight on the Samsung ARM Chromebook (FET1). Problems were
especially prevalent when the device was plu
The following patches fix a couple of issues which prevented Venice2
boards from booting via eMMC and SD card reliably. Note that this
includes disabling UHS support since SDR50 and above require a
Tegra-specific tuning procedure which is not supported yet (and still
seems to have issues even in d
If we weren't given an interrupt we shouldn't tell child devices (like
the tps65090 charger) that they have an interrupt. This is needed so
that we can support polling mode in the tps65090 charger driver.
See also (charger: tps65090: Allow charger module to be used when no
irq).
Signed-off-by: D
Nearly all of the registers in tps65090 combine control bits and
status bits. Turn off caching of all registers except the select few
that can be cached.
In order to avoid adding more duplicate #defines, we also move some
register offset definitions to the mfd driver (and resolve
inconsistent nam
Randy,
On Wed, Apr 16, 2014 at 1:33 PM, Randy Dunlap wrote:
> On 04/16/2014 11:25 AM, Doug Anderson wrote:
>> diff --git a/drivers/regulator/tps65090-regulator.c
>> b/drivers/regulator/tps65090-regulator.c
>> index 2e92ef6..ca13a1a 100644
>> --- a/drivers/regulator/tps65090-regulator.c
>> +++ b/
On 04/16/2014 05:08 PM, Andrew Bresticker wrote:
> VDDIO_SDMMC3 is the VQMMC (I/O) supply, not the VMMC (core) supply,
> for the SD slot on Venice2.
I've applied this (one patch) to Tegra's for-3.16/dt branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body o
On Wed, 2014-04-16 at 15:46 -0700, Andrew Morton wrote:
> On Sun, 13 Apr 2014 20:05:34 +0200 Manfred Spraul
> wrote:
>
> > Hi Andrew,
> >
> > On 04/02/2014 12:08 AM, Andrew Morton wrote:
> > > Well, I'm assuming 64GB==infinity. It *was* infinity in the RHEL5
> > > timeframe, but infinity has s
On Wed, Apr 16, 2014 at 07:10:41PM -0400, Pranith Kumar wrote:
> On Wed, Apr 16, 2014 at 5:14 PM, Paul E. McKenney
> wrote:
> >
> > This fails for me. The problem is that the defined macro makes everything
> > static, and rcutorture_runnable is used in kernel/sysctl.c. :-/
> >
> > In theory, it
Hi Doug,
On 16 April 2014 15:25, Doug Anderson wrote:
> Simon,
>
> On Wed, Apr 16, 2014 at 1:50 PM, Simon Glass wrote:
>>> +#define MAX_CTRL_READ_TRIES5
>>> +#define MAX_FET_ENABLE_TRIES 1000
>>
>> Gosh that is a lot of tries - should we maybe give up sooner?
>
> That's actually a squash o
On Wed, 16 Apr 2014 10:47:02 -0400 Jeff Layton
wrote:
> On Wed, 16 Apr 2014 14:03:36 +1000
> NeilBrown wrote:
>
> > If an incoming NFS request is coming from the local host, then
> > nfsd will need to perform some special handling. So detect that
> > possibility and make the source visible in
Hi,
Ok. I will update the comment in the code and patch description.
Thanks for review.
Regards,
Daeseok Youn.
2014-04-17 2:38 GMT+09:00 Tejun Heo :
> Hello,
>
> On Wed, Apr 16, 2014 at 02:33:27PM +0900, Daeseok Youn wrote:
>>
>> Replace blocks of code which checks whether pwq is defalut with
>
If it occurs an error, we should call f2fs_unlock_op.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/inline.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/fs/f2fs/inline.c b/fs/f2fs/inline.c
index 383db1f..3258c7c 100644
--- a/fs/f2fs/inline.c
+++ b/fs/f2fs/inline.c
Before the rescuer is picked to running, the works of the @pwq
may be processed by some other workers, and destroy_workqueue()
may called at the same time. This may result a nasty situation
that rescuer may exit with non-empty mayday list.
It is no harm currently, destroy_workqueue() can safely to
There is a race condition between rescuer_thread() and
pwq_unbound_release_workfn().
The works of the @pwq may be processed by some other workers,
and @pwq is scheduled to release(due to its wq's attr is changed)
before the rescuer starts to process. In this case
pwq_unbound_release_workfn() will
On Wednesday, April 16, 2014 4:34 PM, Chase Southwood wrote:
>
> Move apci1564_reset() from hwdrv_apci1564.c to addi_apci_1564.c. The
> function was very messy and failed to reset a couple registers, these
> issues were fixed on the move.
The commit message needs updated. You are no longer moving
Hi,
2014-04-16 (수), 13:11 +0400, Andrey Tsyvarev:
> Hi,
>
> With this patch mounting of the image continues to fail (with similar
> BUG_ON).
> But when image is formatted again (and steps mentioned in the previous
> message are performed),
> mounting of it is now succeed.
>
> Is this is a true
Hello,
Dmitry Torokhov, le Sat 12 Apr 2014 18:25:57 -0700, a écrit :
> On Fri, Apr 11, 2014 at 08:12:02AM +0200, Samuel Thibault wrote:
> > I'm sorry this went out with a few mistakes.
> >
> > Samuel Thibault, le Wed 09 Apr 2014 01:33:06 +0200, a écrit :
> > > Dmitry Torokhov, le Tue 08 Apr 2014
On Wednesday, April 16, 2014 at 02:37:13 PM, Austin Boyle wrote:
> This patch generalises the calculation of block protect bits based on the
> number of sectors and implements the _is_locked function.
>
> Existing calculation of block protect bits only works for devices with 64
> sectors or more.
On Tue, Apr 15, 2014 at 11:18:26AM +0200, Vlastimil Babka wrote:
> The compaction freepage scanner implementation in isolate_freepages() starts
> by taking the current cc->free_pfn value as the first pfn. In a for loop, it
> scans from this first pfn to the end of the pageblock, and then subtracts
On 04/17/2014 03:51 AM, Tejun Heo wrote:
> Hello,
>
> On Tue, Mar 25, 2014 at 05:56:04PM +0800, Lai Jiangshan wrote:
>> freezing is nothing related to pools, but POOL_FREEZING adds a connection,
>> and causes freeze_workqueues_begin() and thaw_workqueues() complicated.
>>
>> Since freezing is work
Hi Mel, Andrew,
On Wed, 16 Apr 2014 20:21:35 +0100 Mel Gorman wrote:
>
> On Wed, Apr 16, 2014 at 03:19:56PM +1000, Stephen Rothwell wrote:
> >
> > After merging the akpm-current tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > In file included from mm/vmsca
On Wed, Apr 16, 2014 at 10:42:17PM +0200, Yves Deweerdt wrote:
>
> __user should be kept when casting to struct binder_version *
>
>
Mathieu sent this one earlier.
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2014-April/048614.html
His is perfect, except that he missed the
Here are some minor cleanups for dmtimer code in preparation for moving it out
to drivers.
There is OMAP1 specific dmtimer code earlier, that are handled in mach-omap1
directly now. Other than this, few functions and code has been refactored to
reduce redundancy and some minor cleanups.
OMAP1 h
Hello,
2014-04-16 21:38 GMT+09:00 Jean-Christophe PLAGNIOL-VILLARD
:
>
> On Apr 16, 2014, at 5:40 PM, Daeseok Youn wrote:
>
>>
>> The spec->modedb can be NULL by fb_create_modedb().
>>
>> And also smatch says:
>> drivers/video/fbdev/core/fbmon.c:975 fb_edid_to_monspecs() error:
>> potential null
"load_start" implies start, so it makes sense to set the ST bit in
__omap_dm_timer_load_start instead of callers.
Signed-off-by: Joel Fernandes
---
arch/arm/mach-omap2/timer.c |6 +++---
arch/arm/plat-omap/dmtimer.c |1 -
arch/arm/plat-omap/include/plat/dmtimer
While at it, also delete the old definition of the function in dmtimer.c code.
This completes the separation and removal of OMAP1 header dependency in dmtimer
code and removes references to MOD_CONF_CTRL registers in dmtimer.
Signed-off-by: Joel Fernandes
---
arch/arm/mach-omap1/include/mach/har
On Wednesday, April 16, 2014 4:53 PM, Chase Southwood wrote:
>>On Wednesday, April 16, 2014 6:36 PM, Hartley Sweeten
>> wrote:
>>>On Wednesday, April 16, 2014 4:34 PM, Chase Southwood wrote:
>>>Move apci1564_reset() from hwdrv_apci1564.c to addi_apci_1564.c. The
>>>function was very messy and fai
There is a platform specific hook just for OMAP1 to set its clk parent. Remove
this hook and have OMAP1 set its parent in omap1_dm_timer_init. If OMAP1 is
ever migrated to clock framework, the correct way to do this would be through
clk_set_parent like other platforms.
Signed-off-by: Joel Fernan
The subsequent devm_ioremap_resource will catch it and print an error, let it
be checked there.
Signed-off-by: Joel Fernandes
---
arch/arm/plat-omap/dmtimer.c |4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat-omap/dmtimer.c
index 7e806f9..1fd3
Inorder to move non-DM timer specific code that modifies the "idlect"
mask on OMAP1, from dmtimer code, to OMAP1 specific timer initialization code,
we introduce a new function that can possibly be reused for other purposes in
the future. The function just checks if a timer is running based on the
Once clock-parents or default-parent support for DT clocks is available,
we should use it to set clock parent and turn clk_set_parent into a NOOP.
Signed-off-by: Joel Fernandes
---
arch/arm/plat-omap/dmtimer.c |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/plat-omap/dmtimer.
A common pattern in dmtimer code is to read the control reg, set and reset
certain bits, and write it back. We abstract this pattern and introduce a
new function to do so.
Signed-off-by: Joel Fernandes
---
arch/arm/plat-omap/dmtimer.c | 63 --
1 file cha
Simplify the check for a timer availability in atleast 4 places by providing a
function to do the same.
Signed-off-by: Joel Fernandes
---
arch/arm/plat-omap/dmtimer.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/arch/arm/plat-omap/dmtimer.c b/a
Hi Vlastimil,
Below just nitpicks.
On Tue, Apr 15, 2014 at 11:18:27AM +0200, Vlastimil Babka wrote:
> isolate_freepages() is currently somewhat hard to follow thanks to many
> different pfn variables. Especially misleading is the name 'high_pfn' which
> looks like it is related to the 'low_pfn' v
OMAP1 doesn't support clock framework, add a comment where needed
and correct a FIXME.
Signed-off-by: Joel Fernandes
---
arch/arm/plat-omap/dmtimer.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat-omap/dmtimer.c
index ecd3f
pr_debug() parameters are reverse order of format string
Signed-off-by: Frank Rowand
---
drivers/base/dd.c |4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)
Index: b/drivers/base/dd.c
===
--- a/driv
On 04/15/2014 11:41 AM, Saravana Kannan wrote:
> Ah, I misunderstood your previous email. I thought you Nack-ed my patch
> and decided to send your own patch to replace mine. Ok, I'll fix up mine
> and send it out.
MyungJoo/Kyungmin,
I sent out an updated patch. Can you please take a look?
Thank
On Wed, 16 Apr 2014, Johannes Weiner wrote:
> Subject: [patch] mm: filemap: update find_get_pages_tag() to deal with shadow
> entries
>
> Dave Jones reports the following crash when find_get_pages_tag() runs
> into an exceptional entry:
>
> kernel BUG at mm/filemap.c:1347!
> RIP: 0010:[] []
>
On Wed, Apr 16, 2014 at 04:56:00PM -0600, Bjorn Helgaas wrote:
> > I'm seeing the exact same message on my thinkpad t430s.
> > When I try your patch, modesetting no longer works. When it tries
> > to change to the framebuffer I get a black screen and lockup.
> > If I boot with nomodeset it lo
On Wed, 16 Apr 2014 10:42:07 -0400 Jeff Layton wrote:
> On Wed, 16 Apr 2014 14:03:35 +1000
> NeilBrown wrote:
>
> > Comments, criticisms, etc most welcome.
> >
> > Thanks,
> > NeilBrown
> >
>
> I've only given this a once-over, but the basic concept seems a bit
> flawed. IIUC, the basic ide
On Wed, Apr 16, 2014 at 03:21:04PM -0600, Jason Gunthorpe wrote:
> On Wed, Apr 16, 2014 at 06:05:45PM +0100, Liviu Dudau wrote:
>
> > I have found out that we cannot pasd the config ranges from the DT into the
> > pci_host_bridge structure as the PCI framework doesn't have a resource type
> > for
On Wed, Apr 16, 2014 at 4:42 PM, Kirill A. Shutemov
wrote:
> On Wed, Apr 16, 2014 at 07:52:29AM +0800, Bob Liu wrote:
>> > *ptl = pmd_lock(mm, pmd);
>> > - if (pmd_none(*pmd))
>> > + if (!pmd_present(*pmd))
>> > goto unlock;
>>
>> But I didn't get the idea why p
Hi Kirill,
On Mon, Apr 14, 2014 at 05:42:18PM +0300, Kirill A. Shutemov wrote:
> I've spent few day trying to understand rmap code. And now I think my
> patch is wrong.
>
> I actually don't see where walk order requirement comes from. It seems all
> operations (insert, remove, foreach) on anon_vm
On Wednesday, April 16, 2014 13:16:33 Jeremy Allison wrote:
> On Wed, Apr 16, 2014 at 10:00:46PM +0200, Michael Kerrisk (man-pages) wrote:
> > [CC += Jeremy Allison]
> >
> > On Wed, Apr 16, 2014 at 8:57 PM, Jeff Layton wrote:
> > > Sorry to spam so many lists, but I think this needs widespread
>
(2014/04/16 18:36), Peter Zijlstra wrote:
> On Wed, Apr 16, 2014 at 03:33:06PM +0900, Hidetoshi Seto wrote:
>> So we need 2 operations:
>> a) remove regression
>
> What regression; there's never been talk about a regression, just a bug
> found. AFAICT this 'regression' is ever since we introduce
On Wed, 2014-04-16 at 17:12 -0700, Frank Rowand wrote:
> pr_debug() parameters are reverse order of format string
Another way to do this might be to change all the
printks/pr_debugs to dev_
Something like:
---
drivers/base/dd.c | 35 +--
1 file changed, 17 inserti
On Wed, 16 Apr 2014 19:00:51 +1000 Dave Chinner wrote:
> On Wed, Apr 16, 2014 at 04:49:41PM +1000, NeilBrown wrote:
> > On Wed, 16 Apr 2014 16:25:20 +1000 Dave Chinner wrote:
> >
> > > On Wed, Apr 16, 2014 at 02:03:37PM +1000, NeilBrown wrote:
> > > > __d_alloc can be called with i_mutex held,
To Seung-Woo.
On 04/16/2014 07:44 PM, Seung-Woo Kim wrote:
> Hi,
>
> On 2014년 04월 16일 19:27, Sangjung Woo wrote:
>> Use the resource-managed extcon device register function (i.e.
>> devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon
>> device
>> is attached with this functio
On Wed, 16 Apr 2014 16:17:26 +1000 NeilBrown wrote:
> On Wed, 16 Apr 2014 15:37:56 +1000 Dave Chinner wrote:
>
> > On Wed, Apr 16, 2014 at 02:03:36PM +1000, NeilBrown wrote:
> > > - /*
> > > - * Given that we do not allow direct reclaim to call us, we should
> > > - * never be called while i
On 4/16/2014 5:48 PM, Joe Perches wrote:
> On Wed, 2014-04-16 at 17:12 -0700, Frank Rowand wrote:
>> pr_debug() parameters are reverse order of format string
>
> Another way to do this might be to change all the
> printks/pr_debugs to dev_
Yes, but if that is done, one may as well do all of drive
Hi,
But would not ability to trigger BUG_ON by mounting a crafted image
considered as an issue having security implications?
Regards,
Alexey
On 16.04.2014 16:35, Jaegeuk Kim wrote:
> Hi,
>
> 2014-04-16 (수), 13:11 +0400, Andrey Tsyvarev:
>> Hi,
>>
>> With this patch mounting of the image continu
601 - 700 of 772 matches
Mail list logo
