On Fri, 22 Feb 2013 17:01:48 -0500
Peter Hurley wrote:
> On Fri, 2013-02-22 at 12:59 -0800, Joe Perches wrote:
> > Add the ClearPage/SetPage/TestClearPage/TestSetPage
> > variants to the not reported Page CamelCase variables.
> >
> > Signed-off-by: Joe Perches
> > ---
> >
On Fri, 2013-02-22 at 17:01 -0500, Peter Hurley wrote:
> I didn't bother to mention it before, but since your addressing mm
> CamelCase exceptions, perhaps
>
> _
> xx_XXX_xxx
> XXX_xxx
>
> could be exceptions as well?
Maybe the check should only be for "[A-Z][a-z]|[a-z][A-Z]"
to
On Fri, 2013-02-22 at 14:05 -0800, Andrew Morton wrote:
> On Fri, 22 Feb 2013 17:01:48 -0500
> Peter Hurley wrote:
>
> > On Fri, 2013-02-22 at 12:59 -0800, Joe Perches wrote:
> > > Add the ClearPage/SetPage/TestClearPage/TestSetPage
> > > variants to the not reported Page CamelCase variables.
>
On Fri, Feb 22, 2013 at 10:51:58PM +0100, Fabio Baltieri wrote:
> On Fri, Feb 22, 2013 at 03:59:54AM -0500, Dave Jones wrote:
> > On Thu, Feb 21, 2013 at 10:40:10AM -0800, Greg KH wrote:
> >
> > It looks like every port on my laptop is powered down, as I can't
> > even charge devices with
This is very similar to a patch that Daniel and I sent earlier this month.
http://www.spinics.net/lists/linux-input/msg24666.html
The major difference is that your wait_for_chg does a polling read of
chg, while the one we worked on leaves the irq enabled and waits on
completion.
On Fri, Feb 22,
On Fri, 2013-02-22 at 14:21 -0800, Joe Perches wrote:
> On Fri, 2013-02-22 at 17:01 -0500, Peter Hurley wrote:
> > I didn't bother to mention it before, but since your addressing mm
> > CamelCase exceptions, perhaps
> >
> > _
> > xx_XXX_xxx
> > XXX_xxx
> >
> > could be exceptions
Ping. Any update for this black screen problem?
Chris
On Wed, Feb 20, 2013 at 1:04 PM, Chris Li wrote:
> Here is the dmesg with "drm.debug=0xe" at
> 80187431762989ebade986468d3c548287a12689
>
> That is the 3.6 kernel, exactly one commit before the ACPI commit
> which triggering the black
> -Original Message-
> From: Zach Brown [mailto:z...@redhat.com]
> Sent: Friday, February 22, 2013 1:22 PM
> To: Ric Wheeler
> Cc: Paolo Bonzini; Myklebust, Trond; Linux FS Devel; linux-
> ker...@vger.kernel.org; Chris L. Mason; Christoph Hellwig; Alexander Viro;
> Martin K. Petersen;
On Fri, Feb 22, 2013 at 3:21 PM, Joe Perches wrote:
> On Fri, 2013-02-22 at 17:01 -0500, Peter Hurley wrote:
>> I didn't bother to mention it before, but since your addressing mm
>> CamelCase exceptions, perhaps
>>
>> _
>> xx_XXX_xxx
>> XXX_xxx
>>
>> could be exceptions as well?
>
>
On Thu, Feb 21, 2013 at 11:13:27PM -0500, Waiman Long wrote:
> On 02/21/2013 07:13 PM, Andi Kleen wrote:
> >Dave Chinner writes:
> >
> >>On Tue, Feb 19, 2013 at 01:50:55PM -0500, Waiman Long wrote:
> >>>It was found that the Oracle database software issues a lot of call
> >>>to the seq_path()
On 02/22/2013 02:55 PM, Rhyland Klein wrote:
> On 2/22/2013 2:49 PM, Stephen Warren wrote:
>> On 02/21/2013 04:11 PM, Rhyland Klein wrote:
>>> With the growing support for dt, it make sense to try to make use of
>>> dt features to make the general code cleaner. This patch is an
>>> attempt to
dOn Fri, 2013-02-22 at 15:57 -0700, Shuah Khan wrote:
> What are the guidelines on camelcase warnings on patches. A recent one
> I ran into is on a variable in a structure and fixing it would require
> changing the original variable.
The same as all other checkpatch warnings.
Ignore the ones you
On Fri, 22 Feb 2013 15:57:16 -0700
Shuah Khan wrote:
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 747bcd7..e08e9f6 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -2929,8 +2929,8 @@ sub process {
> > while ($line =~
We've moved away from using platform data in our project because it's
clunky, and because we implemented the config loading that's similar
to what you submitted elsewhere in this series.
Furthermore, for our ARM projects specifically, we are using flattened
device trees to describe our board and
Hi,
We spent a couple of days cornering what appears to be an issue with the
Intel 520 SSD drives in Lenovo x230 laptops. It was first showing up
on a clean Debian installation, while installing a guest operating
system into a VM. Looking around on forums, there appears to be some
people having
2013/2/23 Christoph Lameter :
> On Fri, 22 Feb 2013, Glauber Costa wrote:
>
>> On 02/22/2013 09:01 PM, Christoph Lameter wrote:
>> > Argh. This one was the final version:
>> >
>> > https://patchwork.kernel.org/patch/2009521/
>> >
>>
>> It seems it would work. It is all the same to me.
>> Which one
Hi Nick,
Thanks for this patch. Comments inline.
On Fri, Feb 22, 2013 at 9:57 AM, Nick Dyer wrote:
> From: Iiro Valkonen
>
> The delay before the chip can be accessed after reset varies between different
> chips in maXTouch family. Waiting for 200ms and then monitoring the CHG (chip
> is ready
On 22.02.2013 22:51, Jan Kara wrote:
On Wed 20-02-13 13:40:03, Marcus Sundman wrote:
On 20.02.2013 10:42, Marcus Sundman wrote:
On 05.12.2012 17:32, Jan Kara wrote:
I see. Maybe you could have something like
while true; do echo w >/proc/sysrq-trigger; sleep 10; done
running in the
On Fri, Feb 22, 2013 at 1:48 PM, Konrad Rzeszutek Wilk
wrote:
> Hey Rafael,
>
> Per git bisect it looks like that patch:
> ACPI: Separate adding ACPI device objects from probing ACPI drivers
> blows up when running under Xen PV guests:
>
> (please notice that ACPI is turned off with normal Xen PV
On Fri, Feb 22, 2013 at 4:30 AM, Rafael J. Wysocki wrote:
> On Friday, February 22, 2013 09:22:15 AM Thomas Gleixner wrote:
>> On Fri, 22 Feb 2013, Rafael J. Wysocki wrote:
>> > On Friday, February 22, 2013 02:40:58 AM Rafael J. Wysocki wrote:
>> > > It looks like the hest_tab memory mapping is
On 2/22/2013 10:27 AM, Will Deacon wrote:
> Hi guys,
>
> On Fri, Feb 22, 2013 at 08:08:05AM +, Stephen Boyd wrote:
>> From: Steve Muckle
>>
>> The subarchitecture field in the fpsid register is 7 bits wide.
>> The topmost bit is used to designate that the subarchitecture
>> designer is not
On 02/21/2013 02:51 PM, Thomas Gleixner wrote:
Use the shadow timekeeper to do the update_wall_time() adjustments and
then copy it over to the real timekeeper.
Keep the shadow timekeeper in sync when updating stuff outside of
update_wall_time().
This allows us to limit the timekeeper_seq hold
On Fri, Feb 22, 2013 at 08:12:52AM +, Tony Lu wrote:
> I encountered the following panic when using xfs partitions as rootfs, which
> is due to the truncated log data read by xlog_bread_noalign(). We should
> extend the buffer by one extra log sector to ensure there's enough space to
>
On Fri, Feb 22, 2013 at 05:23:04PM -0500, Dave Jones wrote:
> On Fri, Feb 22, 2013 at 10:51:58PM +0100, Fabio Baltieri wrote:
> > On Fri, Feb 22, 2013 at 03:59:54AM -0500, Dave Jones wrote:
> > > On Thu, Feb 21, 2013 at 10:40:10AM -0800, Greg KH wrote:
> > >
> > > It looks like every port on
On Friday, February 22, 2013 10:51:58 PM Fabio Baltieri wrote:
> On Fri, Feb 22, 2013 at 03:59:54AM -0500, Dave Jones wrote:
> > On Thu, Feb 21, 2013 at 10:40:10AM -0800, Greg KH wrote:
> >
> > > USB patches for 3.9-rc1
> > >
> > > Here's the big USB merge for 3.9-rc1
> > >
> > > Nothing
> That seems to me like an application problem - poking at what the
> kernel is doing via diagnostic interfaces so often that it gets in
> the way of the kernel actually doing stuff is not a problem the
> kernel can solve.
I agree with you that the application shouldn't be doing that, but
if
On Friday, February 22, 2013 05:23:04 PM Dave Jones wrote:
> On Fri, Feb 22, 2013 at 10:51:58PM +0100, Fabio Baltieri wrote:
> > On Fri, Feb 22, 2013 at 03:59:54AM -0500, Dave Jones wrote:
> > > On Thu, Feb 21, 2013 at 10:40:10AM -0800, Greg KH wrote:
> > >
> > > It looks like every port on
On Saturday, February 23, 2013 01:10:55 AM Fabio Baltieri wrote:
> On Fri, Feb 22, 2013 at 05:23:04PM -0500, Dave Jones wrote:
> > On Fri, Feb 22, 2013 at 10:51:58PM +0100, Fabio Baltieri wrote:
> > > On Fri, Feb 22, 2013 at 03:59:54AM -0500, Dave Jones wrote:
> > > > On Thu, Feb 21, 2013 at
On Fri, Feb 22, 2013 at 4:19 PM, Rafael J. Wysocki wrote:
>
> It won't revert, there's more stuff on top of it. And it is a fix, so
> reverting it is not really a good idea anyway.
Rafael, please don't *ever* write that crap again.
We revert stuff whether it "fixed" something else or not. The
"Myklebust, Trond" wrote:
> > -Original Message-
> > From: Zach Brown [mailto:z...@redhat.com]
> > Sent: Thursday, February 21, 2013 5:25 PM
> > To: Myklebust, Trond
> > Cc: Paolo Bonzini; Ric Wheeler; Linux FS Devel;
> > linux-kernel@vger.kernel.org;
> > Chris L. Mason; Christoph
With git commit 8170e6bed465b4b0c7687f93e9948aca4358a33b
"x86, 64bit: Use a #PF handler to materialize early mappings on demand"
we started hitting an early bootup crash where the Xen hypervisor
would inform us that:
(XEN) d7:v0: unhandled page fault (ec=)
(XEN) Pagetable walk from
"Markus F.X.J. Oberhumer" wrote:
>for performance reasons I'd strongly suggest that you explicitly align
>all
>buffers passed to the LZO compress and decompress functions.
>
>Below is a small (and completely untested!) patch, but I think you
>get the idea.
Do you know what kind of performance
On Friday, February 22, 2013 04:30:25 PM Linus Torvalds wrote:
> On Fri, Feb 22, 2013 at 4:19 PM, Rafael J. Wysocki wrote:
> >
> > It won't revert, there's more stuff on top of it. And it is a fix, so
> > reverting it is not really a good idea anyway.
>
> Rafael, please don't *ever* write that
On Friday, February 22, 2013 10:51:58 PM Fabio Baltieri wrote:
> On Fri, Feb 22, 2013 at 03:59:54AM -0500, Dave Jones wrote:
> > On Thu, Feb 21, 2013 at 10:40:10AM -0800, Greg KH wrote:
> >
> > > USB patches for 3.9-rc1
> > >
> > > Here's the big USB merge for 3.9-rc1
> > >
> > > Nothing
On Thu, Feb 21, 2013 at 05:56:35PM +0200, Samu Kallio wrote:
> On Thu, Feb 21, 2013 at 2:33 PM, Konrad Rzeszutek Wilk
> wrote:
> > On Sun, Feb 17, 2013 at 02:35:52AM -, Samu Kallio wrote:
> >> In paravirtualized x86_64 kernels, vmalloc_fault may cause an oops
> >> when lazy MMU updates are
> > [1.830762] IP: [] apei_hest_parse+0x2a/0x140
> > [1.830780] PGD 0
> > [1.830791] Oops: [#1] SMP
> > [1.830806] Modules linked in:
> > [1.830819] CPU 0
> > [1.830827] Pid: 1, comm: swapper/0 Not tainted
> > 3.8.0-rc2upstream-2-g92ef2a2 #1
> > [1.830838]
On Fri, Feb 22, 2013 at 4:48 PM, Rafael J. Wysocki wrote:
>
> The problem is, though, that even if bisection turns up something, it doesn't
> automatically mean that this particular commit is the one that caused the
> problem to happen in the first place.
No, I agree. I just react *very*
Hey Thomas,
I don't know if this is b/c the Xen code is missing something or
expects something that never happend. I hadn't looked at your
patch in any detail (was going to do that on Monday).
Either way, if I boot a HVM guest with PV extensions (aka PVHVM)
this is I what get:
Loading
Hello,
On Sat, Feb 23, 2013 at 09:30:11AM +0800, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> commit f5947173c082a04a9804bb42a91a0f5df5ee0527
> Author: Tejun Heo
> Date: Wed Feb 20 02:05:52 2013 +
>
> idr: implement lookup hint
Andy
On Fri, Feb 22, 2013 at 05:34:48PM -0800, Tejun Heo wrote:
> Hello,
>
> On Sat, Feb 23, 2013 at 09:30:11AM +0800, Fengguang Wu wrote:
> > Greetings,
> >
> > I got the below dmesg and the first bad commit is
> >
> > commit f5947173c082a04a9804bb42a91a0f5df5ee0527
> > Author: Tejun Heo
> > Date:
From: Konrad Rzeszutek Wilk
With git commit 8170e6bed465b4b0c7687f93e9948aca4358a33b
"x86, 64bit: Use a #PF handler to materialize early mappings on demand"
we started hitting an early bootup crash where the Xen hypervisor
would inform us that:
(XEN) d7:v0: unhandled page fault (ec=)
(XEN)
[ trim cc list]
On Fri, Feb 22, 2013 at 5:27 PM, Konrad Rzeszutek Wilk
wrote:
>> > static int xen_pgd_alloc(struct mm_struct *mm)
>> > {
>> > pgd_t *pgd = mm->pgd;
>> > @@ -2105,7 +2143,7 @@ static const struct pv_mmu_ops xen_mmu_ops
>> > __initconst = {
>> > #ifdef CONFIG_X86_32
>>
On Fri, Feb 22, 2013 at 05:35:54PM -0800, Tejun Heo wrote:
> On Fri, Feb 22, 2013 at 05:34:48PM -0800, Tejun Heo wrote:
> > Hello,
> >
> > On Sat, Feb 23, 2013 at 09:30:11AM +0800, Fengguang Wu wrote:
> > > Greetings,
> > >
> > > I got the below dmesg and the first bad commit is
> > >
> > >
On Thu, 21 Feb 2013 22:40:08 -0500
Nicolas Pitre wrote:
> On Thu, 21 Feb 2013, Kim Phillips wrote:
>
> > Here's the asm version I'm working on now, based on compiler
> > output of the C version. Haven't tested beyond defconfig builds,
> > which pass ok.
> >
> > Is there anything I have to do
On Sat, Feb 23, 2013 at 01:35:26AM +0100, Rafael J. Wysocki wrote:
> On Saturday, February 23, 2013 01:10:55 AM Fabio Baltieri wrote:
> > Well, this did the trick in my case:
> >
> > --- >8 ---
> > diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
> > index b820528..54175a0 100644
> > ---
On Fri, Feb 22, 2013 at 9:58 AM, Nick Dyer wrote:
> The bootloader state machine toggles the CHG/Interrupt line to indicate when
> it has transitioned between states. Waiting for this event improves bootloader
> reliability.
>
> Signed-off-by: Nick Dyer
> ---
>
On Friday, February 22, 2013 05:10:43 PM Linus Torvalds wrote:
> On Fri, Feb 22, 2013 at 4:48 PM, Rafael J. Wysocki wrote:
> >
> > The problem is, though, that even if bisection turns up something, it
> > doesn't
> > automatically mean that this particular commit is the one that caused the
> >
The following changes since commit 88b62b915b0b7e25870eb0604ed9a92ba4bfc9f7:
Linux 3.8-rc6 (2013-02-01 12:08:14 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/linux-leds.git for-next
for you to fetch changes up to
Hi Linus:
Here is the crypto update for 3.9:
* Added accelerated implementation of crc32 using pclmulqdq.
* Added test vector for fcrypt.
* Added support for OMAP4/AM33XX cipher and hash.
* Fixed loose crypto_user input checks.
* Misc fixes.
Please pull from
On Fri, 22 Feb 2013, Kim Phillips wrote:
> On Thu, 21 Feb 2013 22:40:08 -0500
> Nicolas Pitre wrote:
>
> > On Thu, 21 Feb 2013, Kim Phillips wrote:
> >
> > > Here's the asm version I'm working on now, based on compiler
> > > output of the C version. Haven't tested beyond defconfig builds,
> >
From: Min Zhang
A race condition can clear tty ldisc icanon bit unintentionally which
could stop n_tty from processing received characters. It can occur when
tty receiver buffer was full, e.g. 4096 chars received, 8250 serial driver
interrupt tried to flush_to_ldisc them, but other shell thread
Hi Nathan,
Sorry for pointing out this so late but i still feel we are missing something
really important.
On 22 February 2013 21:54, Nathan Zimmer wrote:
> - read_lock_irqsave(_driver_lock, flags);
> + rcu_read_lock();
> + freqs->flags =
Fixes the following checkpatch warning:
WARNING: Prefer netdev_err(netdev, ... then dev_err(dev, ... then pr_err(...
to printk(KERN_ERR ...
Signed-off-by: Thiago Farina
---
drivers/regulator/max8998.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
On 22 February 2013 21:54, Nathan Zimmer wrote:
> This eliminates the contention I am seeing in __cpufreq_cpu_get.
> It also nicely stages the lock to be replaced by the rcu.
>
> Cc: Viresh Kumar
> Cc: "Rafael J. Wysocki"
> Signed-off-by: Nathan Zimmer
Acked-by: Viresh Kumar
@Rafael: I am
On Saturday, February 23, 2013 02:44:27 AM Fabio Baltieri wrote:
> On Sat, Feb 23, 2013 at 01:35:26AM +0100, Rafael J. Wysocki wrote:
> > On Saturday, February 23, 2013 01:10:55 AM Fabio Baltieri wrote:
> > > Well, this did the trick in my case:
> > >
> > > --- >8 ---
> > > diff --git
ars in linux-next since next-20130220. It breaks mounting
a root filesystem on an SD card on the Raspberry Pi ARM platform, with
errors such as those shown below.
next-20130222 with just this patch reverted works fine.
> [0.708426] VFS: Mounted root (ext4 filesystem) on device 179:2.
Fixes the following checkpatch warning:
WARNING: Prefer netdev_err(netdev, ... then dev_err(dev, ... then pr_err(...
to printk(KERN_ERR ...
Signed-off-by: Thiago Farina
---
drivers/regulator/max8998.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git
The driver can be used in various subsystems and therefore should not
be unloaded when it is defined in the kernel configuration, so remove
support for unloading it.
Signed-off-by: Alexander Shiyan
---
drivers/mfd/syscon.c | 18 --
1 file changed, 18 deletions(-)
diff --git
Signed-off-by: Alexander Shiyan
---
drivers/mfd/syscon.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
index 55d7915..2c59ce6 100644
--- a/drivers/mfd/syscon.c
+++ b/drivers/mfd/syscon.c
@@ -25,17 +25,15 @@
static struct
On Fri, Feb 22, 2013 at 1:16 PM, Helge Deller wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
> parisc-3.9
In general, I'd love to also get a short human-readable explanation of
what the pull does for the merge message. As it is, I just made
something up.
> On Fri, Feb 22, 2013 at 04:29:55PM +0800, Dong Aisheng wrote:
> > On Fri, Feb 22, 2013 at 08:27:19AM +0100, Thierry Reding wrote:
> > ...
> > > > > > Otherwise, i'm also ok with this patch.
> > > > > > Acked-by: Dong Aisheng
> > > > > >
> > > > > > BTW, i did not see Samuel's tree having this
On 02/22/2013 10:15 PM, Alexander Shiyan wrote:
> The driver can be used in various subsystems and therefore should not
> be unloaded when it is defined in the kernel configuration, so remove
> support for unloading it.
Why not fix the clients to module_get() at the appropriate times; then
you
This patch allow using syscon driver from the platform data, i.e.
possibility using driver on systems without oftree support.
For search syscon device from the client drivers,
"syscon_regmap_lookup_by_pdevname" function was added.
Signed-off-by: Alexander Shiyan
---
drivers/mfd/Kconfig|
> On 02/22/2013 10:15 PM, Alexander Shiyan wrote:
> > The driver can be used in various subsystems and therefore should not
> > be unloaded when it is defined in the kernel configuration, so remove
> > support for unloading it.
>
> Why not fix the clients to module_get() at the appropriate times;
On 02/20/2013 02:29 AM, Peter Zijlstra wrote:
On Tue, 2013-02-19 at 10:25 -0800, John Stultz wrote:
So describe how the perf time domain is different then
CLOCK_MONOTONIC_RAW.
The primary difference is that the trace/sched/perf time domain is not
strictly monotonic, it is only locally
Hi Joseph,
Thank you for testing!
I will submit this patch to the linux-watchdog community after adding
commit log to patch.
2013/2/22 Joseph Salisbury :
> The I/O data can be seen at:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116835/+attachment/3540738/+files/iomem.txt
In the
On 02/22/2013 06:21 PM, Linus Walleij wrote:
> On Fri, Feb 22, 2013 at 4:44 PM, Daniel Lezcano
> wrote:
>
>> This patch fix the clock device irq field which is not initialized.
>>
>> Signed-off-by: Daniel Lezcano
>
> Makes perfect sense:
> Acked-by: Linus Walleij
>
> Sorry that I might have
I am using an ADI Pronghorn Metro board and noticed an issue with any
kernel >= 3.5-rc1 where the board would not boot (or at least no
console messages appear over the serial port), just giving
"Uncompressing Linux... done, booting the kernel." and stopping there.
I ran a git bisect between v3.4
Hello Naoya
[add Michal in cc list]
On Fri, Feb 22, 2013 at 3:41 AM, Naoya Horiguchi
wrote:
>
> +/* Returns true for head pages of in-use hugepages, otherwise returns false.
> */
> +int is_hugepage_movable(struct page *hpage)
s/int/bool/ can we?
> +{
> + struct page *page;
> +
>From: Dave Chinner [mailto:da...@fromorbit.com]
>On Fri, Feb 22, 2013 at 08:12:52AM +, Tony Lu wrote:
>> I encountered the following panic when using xfs partitions as rootfs, which
>> is due to the truncated log data read by xlog_bread_noalign(). We should
>> extend the buffer by one extra
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Signed-off-by: Kees Cook
Cc: Stephen Hemminger
Cc: David S. Miller
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Signed-off-by: Kees Cook
Cc: Stefano Stabellini
Cc: Mukesh Rathor
Cc: Konrad
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Signed-off-by: Kees Cook
Cc: David S. Miller
Cc: Asias He
Cc: Michael S.
Hello all
On Mon, Dec 17, 2012 at 7:19 AM, Linus Torvalds
wrote:
> On Wed, Dec 12, 2012 at 2:03 AM, Mel Gorman wrote:
>> This is a pull request for "Automatic NUMA Balancing V11". The list
>
> Ok, guys, I've pulled this and pushed out. There were some conflicts
> with both the VM changes and
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Signed-off-by: Kees Cook
Cc: Alex Williamson
---
drivers/vfio/pci/Kconfig |
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Signed-off-by: Kees Cook
Cc: Arjan van de Ven
Cc: Dan Williams
Cc: Alasdair G
Signed-off-by: Dmitry Torokhov
---
drivers/w1/masters/w1-gpio.c | 20
1 file changed, 8 insertions(+), 12 deletions(-)
diff --git a/drivers/w1/masters/w1-gpio.c b/drivers/w1/masters/w1-gpio.c
index 799dafd..c45b9ae 100644
--- a/drivers/w1/masters/w1-gpio.c
+++
This fixes the following warning:
CC drivers/w1/masters/w1-gpio.o
drivers/w1/masters/w1-gpio.c:50:28: warning: ‘w1_gpio_dt_ids’ defined but not
used [-Wunused-variable]
Also provide stub for w1_gpio_probe_dt() if device tree support is
disabled.
Signed-off-by: Dmitry Torokhov
---
This simplifies error unwinding and device teardown.
Signed-off-by: Dmitry Torokhov
---
drivers/w1/masters/w1-gpio.c | 31 ++-
1 file changed, 10 insertions(+), 21 deletions(-)
diff --git a/drivers/w1/masters/w1-gpio.c b/drivers/w1/masters/w1-gpio.c
index
The platform data in the dveice structure does not belong to the driver
and so it should not be trying to alter it, but instead use a local pointer
and populate it with a local copy in case we are dealing with device tree
setup.
Also allow mixed setups where platform data coexists with device
801 - 880 of 880 matches
Mail list logo
