On Tue, Sep 29, 2015 at 06:30:25PM +0100, Matthew Garrett wrote:
> On Tue, Sep 29, 2015 at 08:07:10PM +0300, Jarkko Sakkinen wrote:
> > Migrate to struct acpi_driver in order to get out of 7 character
> > limitation for the HID.
>
> Are we guaranteed that there are no old systems reporting these
On Tue, Sep 29, 2015 at 11:26:53AM -0600, Jason Gunthorpe wrote:
> On Tue, Sep 29, 2015 at 08:07:10PM +0300, Jarkko Sakkinen wrote:
>
> > -static struct pnp_device_id tpm_pnp_tbl[] = {
> > +static struct acpi_device_id tpm_acpi_tbl[] = {
> > {"PNP0C31", 0}, /* TPM */
> >
Hello Shawn,
The driver has landed in your tree. Can you queue this DT change for the same?
Thanks.
- Sanchayan.
On 15-09-01 18:06:53, Sanchayan Maity wrote:
> Add device tree node for touchscreen support on Colibri VF50. The
> touchscreen functionality on VF50 uses the ADC channels of Vybrid
On 29 September 2015 at 21:09, Jason Baron wrote:
> However, if we call connect on socket 's', to connect to a new socket 'o2', we
> drop the reference on the original socket 'o'. Thus, we can now close socket
> 'o' without unregistering from epoll. Then, when we either close the ep
> or
On Tue, Sep 29, 2015 at 05:17:52PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.54 release.
> There are 84 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
Commit-ID: 1e034743e918d195d339af340ae933727c072bce
Gitweb: http://git.kernel.org/tip/1e034743e918d195d339af340ae933727c072bce
Author: Vitaly Kuznetsov
AuthorDate: Wed, 23 Sep 2015 12:02:57 +0200
Committer: Ingo Molnar
CommitDate: Wed, 30 Sep 2015 07:44:15 +0200
x86/hyperv: Fix the
On Tue, Sep 29, 2015 at 03:46:48PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.90 release.
> There are 56 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
* Vitaly Kuznetsov wrote:
> tip-bot for Vitaly Kuznetsov writes:
>
> > Commit-ID: 7d381b749a010ccd48d5649c843cac0d14d1c229
> > Gitweb:
> > http://git.kernel.org/tip/7d381b749a010ccd48d5649c843cac0d14d1c229
> > Author: Vitaly Kuznetsov
> > AuthorDate: Wed, 23 Sep 2015 12:02:57 +0200
Hello Suresh,
> * Add Device Tree support for the Dyna Image AP3223 ambient light sensor and
> * proximity driver,
> * Document the binding and
> * Add a vendor prefix for Dyna Image
the mail's subject line should read something like
iio: light: Add AP3223 DT support
tsl2563 is a different
On Thu, Aug 27, 2015 at 02:13:46PM +0800, Jianwei Wang wrote:
> Add DCU node, DCU is a display controller of Freescale
> named 2D-ACE.
>
> Signed-off-by: Alison Wang
> Signed-off-by: Xiubo Li
> Signed-off-by: Jianwei Wang
When you resend, please use "ARM: dts: ls1021a: ..." as subject prefix.
Contact us as we offer our finance service at a low and affordable interest
rate for long and short cash term. Interested applicant should contact us for
further acquisition procedures. Thanks as we remain obliged to render service
to you; worldtrading1...@gmail.com
--
To unsubscribe from this
On Thu, Aug 27, 2015 at 02:13:46PM +0800, Jianwei Wang wrote:
> Add DCU node, DCU is a display controller of Freescale
> named 2D-ACE.
>
> Signed-off-by: Alison Wang
> Signed-off-by: Xiubo Li
> Signed-off-by: Jianwei Wang
MAINTAINERS file has been updated for a couple of release cycles.
On 22.09.2015 16:43, Yakir Yang wrote:
> After exynos_dp have been split the common IP code into analogix_dp driver,
> the analogix_dp driver have deprecated some Samsung platform properties which
> could be dynamically parsed from EDID/MODE/DPCD message, so this is an update
> for Exynos DTS file
On Tue, Sep 29, 2015 at 10:28:57PM -0700, Andrew Morton wrote:
> On Wed, 30 Sep 2015 08:10:04 +0300 Alexandru Moise
> <00moses.alexande...@gmail.com> wrote:
>
> > > > --- a/mm/vmscan.c
> > > > +++ b/mm/vmscan.c
> > > > @@ -194,7 +194,7 @@ static bool sane_reclaim(struct scan_control *sc)
> > > >
Linus,
Please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
# HEAD: 7c4f1c694bf84eac538bee3e411aed10ae617d46 Merge branch 'for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
Hi Andrew,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: arm64-allmodconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
On Monday, September 28, 2015 10:52:33 PM Luis de Bethencourt wrote:
> The while() loop will only exit in a return or a goto ask_for_joinbss,
> which means it will never break and execute the return after it.
> Removing return _FAIL since it is dead code.
>
> Signed-off-by: Luis de Bethencourt
>
This patch fixes error handling case when buffer->pages allocation
fails. Also, it removes unreachable code of checking ret variable
although it is not updated.
Signed-off-by: Rohit kumar
---
drivers/staging/android/ion/ion.c | 14 +-
1 file changed, 5 insertions(+), 9
> Am 28.09.2015 um 09:02 schrieb Bean Huo 霍斌斌 (beanhuo):
> > Hello,
> >
> > This series aims at adding a bakvol module for MLC NAND paired page
> > Power loss protection.
> > MLC NAND paired page power loss is a known issue so far, MLC NAND
> > pages are coupled in a sense that if you cut power
On 22.09.2015 16:37, Yakir Yang wrote:
> Both hsync/vsync polarity and interlace mode can be parsed from
> drm display mode, and dynamic_range and ycbcr_coeff can be judge
> by the video code.
>
> But presumably Exynos still relies on the DT properties, so take
> good use of mode_fixup() in to
On Wed, 30 Sep 2015 08:10:04 +0300 Alexandru Moise
<00moses.alexande...@gmail.com> wrote:
> > > --- a/mm/vmscan.c
> > > +++ b/mm/vmscan.c
> > > @@ -194,7 +194,7 @@ static bool sane_reclaim(struct scan_control *sc)
> > >
> > > static unsigned long zone_reclaimable_pages(struct zone *zone)
> >
On 22.09.2015 16:34, Yakir Yang wrote:
> Fix some obvious alignment problems, like alignment and line
> over 80 characters problems, make this easy to be maintained
> later.
>
> Signed-off-by: Yakir Yang
> ---
> Changes in v5:
> - Resequence this patch after analogix_dp driver have been split
>
On 22.09.2015 16:29, Yakir Yang wrote:
> Split the dp core driver from exynos directory to bridge directory,
> and rename the core driver to analogix_dp_*, rename the platform
> code to exynos_dp.
>
> Beside the new analogix_dp driver would export four hooks.
> "analogix_dp_bind()" and
Hi Brian,
After merging the l2-mtd tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mtd/nand/vf610_nfc.c: In function 'vf610_nfc_resume':
drivers/mtd/nand/vf610_nfc.c:859:2: error: implicit declaration of function
'pinctrl_pm_select_default_state'
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -194,7 +194,7 @@ static bool sane_reclaim(struct scan_control *sc)
> >
> > static unsigned long zone_reclaimable_pages(struct zone *zone)
> > {
> > - int nr;
> > + unsigned long nr;
> >
> > nr = zone_page_state(zone, NR_ACTIVE_FILE)
On Mon, Sep 21, 2015 at 03:03:41PM +0200, Petr Mladek wrote:
> My intention is to make it easier to manipulate kthreads. This RFC tries
> to use the kthread worker API. It is based on comments from the
> first attempt. See https://lkml.org/lkml/2015/7/28/648 and
> the list of changes below.
>
>
The SND_PCM_RATE_KNOT covers all the rate settings, even though some that
we don't support, while we also list all the rate we support. Simply remove
it.
Signed-off-by: Maxime Ripard
---
sound/soc/sunxi/sun4i-codec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
The current code, disregarding the clk_set_rate error code, was always
returning -EINVAL. Fix that and return the code in order to have more clue
about what's going on.
Signed-off-by: Maxime Ripard
---
sound/soc/sunxi/sun4i-codec.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
On Tue, Sep 22, 2015 at 04:30:04PM +0200, Hans de Goede wrote:
> Hi,
>
> On 22-09-15 16:04, Maxime Ripard wrote:
> >On Tue, Sep 22, 2015 at 03:01:58PM +0200, Hans de Goede wrote:
> >>>In short, this is not about "power supply" but VBUS detection. IIRC,
> >>>if no VBUS detection method is
This patch introduces new boot option named "efi_fake_mem".
By specifying this parameter, you can add arbitrary attribute
to specific memory range.
This is useful for debugging of Address Range Mirroring feature.
For example, if "efi_fake_mem=2G@4G:0x1,2G@0x10a000:0x1"
is specified,
From: Geliang Tang
Date: Tue, 29 Sep 2015 19:31:32 -0700
> Just fix two typos in code comments.
>
> Signed-off-by: Geliang Tang
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
pm_runtime_enable is called in probe to enable runtime PM
for wm8962 codec, but pm_runtime_disable isn't called in remove
callback, nor is called in error path if probe fails after runtime
PM is enabled, this causes unbalanced pm_runtime_enable.
This patch Adds pm_runtime_disable in remove
I've missed git-format-patch after rebasing.
I'll resend right one..
> -Original Message-
> From: kbuild test robot [mailto:l...@intel.com]
> Sent: Wednesday, September 30, 2015 10:37 AM
> To: Izumi, Taku/泉 拓
> Cc: kbuild-...@01.org; linux-kernel@vger.kernel.org;
>
The patch f9db0d0f1b2c ("perf callchain: Allow disabling call graphs
per event") added an ability to enable/disable callchain recording per
event. But it had a problem when the enablement setting is changed at
'perf report' time using -g/--call-graph option.
For example, the following scenario
From: Vivien Didelot
Date: Tue, 29 Sep 2015 14:17:54 -0400
> Because of the default 0 value of ret in dsa_slave_port_attr_set, a
> driver may return -EOPNOTSUPP from the commit phase of a STP state,
> which triggers a WARN() from switchdev.
>
> This happened on a 6185 switch which does not
From: Vivien Didelot
Date: Tue, 29 Sep 2015 12:38:36 -0400
> Because of the default 0 value of ret in dsa_slave_port_attr_set, a
> driver may return -EOPNOTSUPP from the commit phase of a STP state,
> which triggers a WARN() from switchdev.
>
> This happened on a 6185 switch which does not
From: Vivien Didelot
Date: Tue, 29 Sep 2015 12:07:12 -0400
> This patchset changes switchdev add, del, dump operations from this:
...
> to something similar to the notifier_call callback of a notifier_block:
...
> This allows the caller to pass and expect back a specific switchdev_obj_*
>
David Rientjes wrote:
> I think both of your illustrations show why it is not helpful to kill
> additional processes after a time period has elapsed and a victim has
> failed to exit. In both of your scenarios, it would require that KT1 be
> killed to allow forward progress and we know that's
On 30 September 2015 at 03:16, Andy Lutomirski wrote:
> On Tue, Sep 29, 2015 at 6:03 PM, H. Peter Anvin wrote:
>> On 09/27/2015 12:06 AM, Ingo Molnar wrote:
>>>
>>> * Ard Biesheuvel wrote:
>>>
> If we allocate the EFI runtime as a single virtual memory block then
> issues
> like
From: Weidong Wang
Date: Tue, 29 Sep 2015 11:18:18 +0800
> @@ -839,11 +828,12 @@ bnx2_free_mem(struct bnx2 *bp)
> }
>
> static int
> -bnx2_alloc_mem(struct bnx2 *bp)
> +bnx2_alloc_stats_blk(struct net_device *dev)
> {
> - int i, status_blk_size, err;
> + int i, status_blk_size;
>
On 09/29/2015 05:14 PM, Yury Norov wrote:
> From: Philipp Tomsich
>
> Adjusted to move the move data page before code pages in sync with
> commit 601255ae3c98fd3a8bb4696425e4f868b4f1
This commit message needs more information about how the ilp32 VDSO uses
the existing arm64 code. I had to
From: Arnd Bergmann
Date: Mon, 28 Sep 2015 22:21:27 +0200
> When trying to build a kernel with time_t commented out, I found that
> the ntp subsystem still relies on timespec for its pps handling.
>
> This series addresses this and converts all the code to use timespec64
> instead, step by
Hi Linus,
Please pull hwmon fixes for Linux v4.3-rc4 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v4.3-rc4
Thanks,
Guenter
--
The following changes since commit 1f93e4a96c9109378204c147b3eec0d0e8100fde:
Linux 4.3-rc2
This patch fix seperated word in printk message.
Signed-off-by: Masanari Iida
---
drivers/usb/host/u132-hcd.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/host/u132-hcd.c b/drivers/usb/host/u132-hcd.c
index a67bd50..0a94895 100644
---
Hi Andrew,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: arm64-allnoconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
> On Sep 30, 2015, at 11:36, Geliang Tang wrote:
>
> Just fix a typo in the code comment.
>
> Signed-off-by: Geliang Tang
> ---
> fs/ceph/cache.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ceph/cache.c b/fs/ceph/cache.c
> index 834f9f3..a4766de 100644
> ---
Just fix a typo in a function name in kerneldoc comments.
Signed-off-by: Geliang Tang
---
kernel/power/hibernate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c
index 690f78f..b7342a2 100644
--- a/kernel/power/hibernate.c
Just fix a typo in the code comment.
Signed-off-by: Geliang Tang
---
fs/ceph/cache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ceph/cache.c b/fs/ceph/cache.c
index 834f9f3..a4766de 100644
--- a/fs/ceph/cache.c
+++ b/fs/ceph/cache.c
@@ -88,7 +88,7 @@ static uint16_t
Hi Andrew,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: arm64-allnoconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
There are many ECDT quirks in drivers/acpi/ec.c.
I tracked the commit log back to learn what was happening on each ECDT related
commits.
My observation result is:
For ACPI 2.0+ compliant platforms, where ECDT may be introduced, the BIOSes that
contain the ECDT will make the named object's value
Suppose that we got a data crc error, and it triggers the mmc_reset.
mmc_reset will call mmc_send_status to see if HW reset was supported.
before issue CMD13, it will do retune, and if EMMC was in HS400 mode,
it will reduce frequency to 52Mhz firstly, that results in card init
was doing at 52Mhz,
On 2015.09.29 15:39:03 +0100, Robert Bragg wrote:
>
> - Logistically it might be more practical to contain this to the
> graphics stack.
>
> It seems fair to consider that if we can't see a very compelling
> benefit to building on perf, then containing this work to
>
On Tue, Sep 29, 2015 at 08:04:21PM -0600, Ross Zwisler wrote:
> On Tue, Sep 29, 2015 at 12:44:58PM +1000, Dave Chinner wrote:
> <>
> > Already testing a kernel with those reverted. My current DAX patch
> > stack is (bottom is first commit in stack):
> >
> > f672ae4 xfs: add ->pfn_mkwrite support
Hi,
perf cross-compile error dual to fixdep is not a host executable, first bad
commit
is 7c422f557266("tools build: Build fixdep helper from perf and basic libs")
Cross-compiling an aarch64 target on x86_64 host, error like this:
$ make ARCH=aarch64 O=xx/aarch64
On 09/29/15 at 08:58pm, Lee, Chun-Yi wrote:
> This patch modified the code in fill_up_crash_elf_data by using
> walk_system_ram_res instead of walk_system_ram_range to count the max
> number of crash memory ranges. That's because the walk_system_ram_range
> filters out small memory regions that
On 09/29/2015 12:37 AM, Eric W. Biederman wrote:
Oleg Nesterov writes:
On 09/25, Konstantin Khlebnikov wrote:
+struct ns_common *proc_ns_fdget(int fd, int nstype, struct fd *fd_ref)
{
- struct file *file;
+ struct ns_common *ns;
+ struct fd f;
- file = fget(fd);
-
Hi all,
On Thu, 17 Sep 2015 10:34:23 +1000 Stephen Rothwell
wrote:
>
> On Wed, 16 Sep 2015 08:16:52 +0200 Jiri Olsa wrote:
> >
> > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote:
> > >
> > > After merging the tip tree, today's linux-next build (perf) failed
> > > like this:
When function graph tracer is enabled, the following operation
will trigger panic:
mount -t debugfs nodev /sys/kernel
echo next_tgid > /sys/kernel/tracing/set_ftrace_filter
echo function_graph > /sys/kernel/tracing/current_tracer
ls /proc/
[ cut here ]
[ 198.501417]
On Tue, Sep 29, 2015 at 10:37:24PM +0530, Arjun Krishna Babu wrote:
> Two lines of code that were over 80 characters long is fixed by
> splitting them into multiple lines.
>
> This way, the lines of code are now easier to read.
>
> Issue found by checkpatch.
>
> Signed-off-by: Arjun Krishna
On Tue, Sep 29, 2015 at 8:36 PM, Suresh Rajashekara
wrote:
> * Add Device Tree support for the Dyna Image AP3223 ambient light sensor and
> * proximity driver,
> * Document the binding and
> * Add a vendor prefix for Dyna Image
>
> v3
> * Fixing typo in comment
> v2
> * Seperating the device tree
Just fix two typos in code comments.
Signed-off-by: Geliang Tang
---
drivers/net/ethernet/cadence/macb.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/cadence/macb.h
b/drivers/net/ethernet/cadence/macb.h
index 6e1faea..866b128 100644
---
No, it is a natural result of an implemention which treats setting the A bit as
an abnormal flow (e.g. in microcode as opposed to hardware).
On September 29, 2015 7:11:59 PM PDT, ebied...@xmission.com wrote:
>"H. Peter Anvin" writes:
>
>> On 09/29/2015 06:20 PM, Eric W. Biederman wrote:
>>>
Dear Kukjin,
DTS related changes for 4.4.
Description along with a tag.
You can find them also on the lists with my reviewed-by.
Best regards,
Krzysztof
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in
Dear Kukjin,
Few defconfig related changes for 4.4.
Description along with a tag.
You can find them also on the lists with my reviewed-by.
Best regards,
Krzysztof
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are
Dear Kukjin,
One ARMv8 DTS change for 4.4.
Best regards,
Krzysztof
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in the git repository at:
https://github.com/krzk/linux.git tags/samsung-dt64-4.4
for
Oleg Nesterov wrote:
> Both "child->mm == mm" and "p->mm != mm" checks in oom_kill_process()
> are wrong. ->mm can be if task is the exited group leader. This means
can be [missing word here?] if task
> +static bool process_has_mm(struct task_struct *p, struct mm_struct *mm)
> +{
> +
"H. Peter Anvin" writes:
> On 09/29/2015 06:20 PM, Eric W. Biederman wrote:
>> Linus Torvalds writes:
>>
>>> On Tue, Sep 29, 2015 at 1:35 PM, Andy Lutomirski
>>> wrote:
Does anyone know what happens if you stick a non-accessed segment in
the GDT, map the GDT RO, and access it?
On Tue, Sep 29, 2015 at 02:15:27PM -0700, Guenter Roeck wrote:
> On 09/29/2015 08:17 AM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.14.54 release.
> >There are 84 patches in this series, all will be posted as a response
> >to this one. If anyone has any
Add the arch-specific code to support jump label for TILE-Gx. This
code shares NOP instruction with ftrace, so we move it to a common
header file.
Reviewed-by: Chris Metcalf
Signed-off-by: Zhigang Lu
---
arch/tile/Kconfig | 1 +
arch/tile/include/asm/insn.h | 59
This patch set adds jump_label support for TILE-Gx architecture. As
jump_label shares some code with ftrace, kgdb and kprobes, we factor
this out into a helper routine as a prequel patch.
Zhigang Lu (2):
tile: define a macro ktext_writable_addr to get writable kernel text
address
On Tue, Sep 29, 2015 at 12:44:58PM +1000, Dave Chinner wrote:
<>
> Already testing a kernel with those reverted. My current DAX patch
> stack is (bottom is first commit in stack):
>
> f672ae4 xfs: add ->pfn_mkwrite support for DAX
> 6855c23 xfs: remove DAX complete_unwritten callback
> e074bdf
Signed-off-by: Heloise NH
---
tools/perf/util/scripting-engines/trace-event-python.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/scripting-engines/trace-event-python.c
b/tools/perf/util/scripting-engines/trace-event-python.c
index cff58ae..14d8e73 100644
It is used by kgdb, ftrace, kprobe and jump label, so we factor
this out into a helper routine.
Reviewed-by: Chris Metcalf
Signed-off-by: Zhigang Lu
---
arch/tile/include/asm/page.h | 10 ++
arch/tile/kernel/ftrace.c| 2 +-
arch/tile/kernel/kgdb.c | 2 +-
A previous patch added a synthesized comm event for forked child
process but it missed that the event should contain area for
sample_id_hdr at the end. It worked by accident since the perf_event
union contains bigger event structs like mmap_events.
This patch fixes it by dynamically allocating
The perf top didn't add the idle/swapper thread to the machine's
thread list and its comm was displayed as ':0'. Fix it.
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-top.c | 3 +++
tools/perf/util/session.c | 2 +-
tools/perf/util/session.h | 2 ++
3 files changed, 6 insertions(+), 1
On Tue, Sep 29, 2015 at 12:44:58PM +1000, Dave Chinner wrote:
> On Mon, Sep 28, 2015 at 04:40:01PM -0600, Ross Zwisler wrote:
> > > > 4) Test all changes with xfstests using both xfs & ext4, using lockep.
> > > >
> > > > Did I miss any issues, or does this path not solve one of them somehow?
> >
The perf top uses 'dso,symbol' sort keys by default so it overlooked a
problem in task's comm resolving. When the sort key contains 'comm',
some task's comm is not shown properly. This is because the
perf_top__mmap_read_idx() checks the cpumode value improperly.
The cpumode value of non-sample
David Rientjes wrote:
> On Tue, 29 Sep 2015, Oleg Nesterov wrote:
>
> > The fatal_signal_pending() was added to suppress unnecessary "sharing
> > same memory" message, but it can't 100% help anyway because it can be
> > false-negative; SIGKILL can be already dequeued.
> >
> > And worse, it can
Hi Taku,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: i386-allmodconfig (attached as .config)
reproduce:
git checkout afcc94d3f91a00ce97d735a563a8e5d595f45a03
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings
Hi Takashi,
Today's linux-next merge of the sound tree got a conflict in:
drivers/gpu/drm/i915/intel_audio.c
between commit:
3c85f5027595 ("drm/i915: s/mode/adjusted_mode/ in functions that really get
passed the adjusted_mode")
from the drm-intel tree and commit:
7e8275c2f2bb
Minimal implementation with support for raw light and proximity reading.
This is based on the driver provided by the vendor
(which was an input driver). Authors of the
driver from the vendor included
* John Huang
* Templeton Tsai
* Vic Lee
v3
* Resubmitting due to typo in accompanying patch
* Add Device Tree support for the Dyna Image AP3223 ambient light sensor and
* proximity driver,
* Document the binding and
* Add a vendor prefix for Dyna Image
v3
* Fixing typo in comment
v2
* Seperating the device tree changes from code
Signed-off-by: Suresh Rajashekara
---
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/intel_lrc.c
between commit:
dfc53c5e73f8 ("drm/i915: Consider HW CSB write pointer before resetting the
sw read pointer")
from the drm-intel-fixes tree and commit:
83843d84fcd3 ("drm/i915:
On 09/29/2015 06:20 PM, Eric W. Biederman wrote:
> Linus Torvalds writes:
>
>> On Tue, Sep 29, 2015 at 1:35 PM, Andy Lutomirski wrote:
>>>
>>> Does anyone know what happens if you stick a non-accessed segment in
>>> the GDT, map the GDT RO, and access it?
>>
>> You should get a #PF, as you
Linus Torvalds writes:
> On Tue, Sep 29, 2015 at 1:35 PM, Andy Lutomirski wrote:
>>
>> Does anyone know what happens if you stick a non-accessed segment in
>> the GDT, map the GDT RO, and access it?
>
> You should get a #PF, as you guess, but go ahead and test it if you
> want to make sure.
I
On Tuesday, September 29, 2015 05:32:53 PM Tomeu Vizoso wrote:
> If a suitable prepare callback cannot be found for a given device and
> its driver has no PM callbacks at all, assume that it can go direct to
> complete when the system goes to sleep.
>
> The reason for this is that there's lots of
On Thu, Sep 24, 2015 at 06:51:52PM +0900, Sergey Senozhatsky wrote:
> From: Sergey SENOZHATSKY
>
> `mem_used_max' is designed to store the max amount of memory zram
> consumed to store the data. However, it does not represent the actual
> 'overcommited' (max) value. The existing code goes to
* Add Device Tree support for the Dyna Image AP3223 ambient light sensor and
* proximity driver,
* Document the binding and
* Add a vendor prefix for Dyna Image
v2
* Seperating the device tree changes from code
Signed-off-by: Suresh Rajashekara
---
Minimal implementation with support for raw light and proximity reading.
This is based on the driver provided by the vendor
(which was an input driver). Authors of the
driver from the vendor included
* John Huang
* Templeton Tsai
* Vic Lee
v2
* Using regmap framework
* Error handling
* Code
On 09/29/2015 06:16 PM, Andy Lutomirski wrote:
>
> Can we at least do 1:1 without an offset on arm64? Given that Linux
> seems to be more of a reference on arm64 than Windows is, maybe that
> would give everyone something vaguely sane to work with.
>
I have no idea. That's a question for the
On Thu, Sep 24, 2015 at 06:56:41PM +0900, Sergey Senozhatsky wrote:
> From: Sergey SENOZHATSKY
>
> Several documentation changes.
>
> First, we never mentioned any errors and never required any
> error checks in documentation.
>
> Second, mention that there is another way to configure and
>
On Tue, Sep 29, 2015 at 6:03 PM, H. Peter Anvin wrote:
> On 09/27/2015 12:06 AM, Ingo Molnar wrote:
>>
>> * Ard Biesheuvel wrote:
>>
If we allocate the EFI runtime as a single virtual memory block then issues
like rounding between sections does not even come up as a problem: we map
This patch introduces new boot option named "efi_fake_mem".
By specifying this parameter, you can add arbitrary attribute
to specific memory range.
This is useful for debugging of Address Range Mirroring feature.
For example, if "efi_fake_mem=2G@4G:0x1,2G@0x10a000:0x1"
is specified,
UEFI spec 2.5 introduces new Memory Attribute Definition named
EFI_MEMORY_MORE_RELIABLE which indicates which memory ranges are
mirrored. Now linux kernel can recognize which memory ranges are mirrored
by handling EFI_MEMORY_MORE_RELIABLE attributes.
However testing this feature necesitates boxes
This patch renames print_efi_memmap() to efi_print_memmap() and
make it global function so that we can invoke it outside of
arch/x86/platform/efi/efi.c
Signed-off-by: Taku Izumi
---
arch/x86/include/asm/efi.h | 1 +
arch/x86/platform/efi/efi.c | 4 ++--
2 files changed, 3 insertions(+), 2
On 18.09.2015 09:54, Nicholas Krause wrote:
> This fixes the function s3c64xx_i2c_cfg_gpio
The problem is not described and you did not provide a fix so the
description is highly inaccurate and misleading.
> to cause a kernel oopes
Warn causes oops?
> if the call to either
On Thu, Sep 24, 2015 at 04:26:28PM +0300, Jani Nikula wrote:
> On Thu, 24 Sep 2015, "da...@codemonkey.org.uk"
> wrote:
> > On Wed, Sep 23, 2015 at 11:07:56AM +, Lankhorst, Maarten wrote:
> > > Hey,
> > >
> > > Dave Jones schreef op di 22-09-2015 om 21:49 [-0400]:
> > > > On Tue,
On 09/27/2015 12:06 AM, Ingo Molnar wrote:
>
> * Ard Biesheuvel wrote:
>
>>> If we allocate the EFI runtime as a single virtual memory block then issues
>>> like rounding between sections does not even come up as a problem: we map
>>> the
>>> original offsets and sizes byte by byte.
>>
>>
On 09/29/2015 07:36 AM, Matt Fleming wrote:
>
> That's a pretty good summary for x86. I think specifically the reason
> we map the EFI memmap entries "backwards" (entry N has higher VA than
> entry N+1) is because the code was easier to write that way, but
> you'll know better than me ;-)
>
On 09/27/2015 11:16 PM, Ingo Molnar wrote:
>
> So the question is, what does Windows do?
>
> PC firmware is a hostile environment for Linux, to be compatible the best we
> can
> do is to mimic the environment that the firmware is tested under - i.e. try
> to use
> the firmware in the way
1 - 100 of 2174 matches
Mail list logo
