Hi Jaegeuk,
> On Sep 24, 2015, at 5:08 AM, Jaegeuk Kim wrote:
>
> Hi Chao,
>
> On Wed, Sep 23, 2015 at 06:11:36PM +0800, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>>> -Original Message-
>>> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
>>> Sent: Wednesday, September 23, 2015 6:54 AM
>>> To:
Hi Rob,
Thank you for your comment!
And, I'm sorry for the delayed response.
> Sent: Monday, September 21, 2015 11:01 PM
>
> On 09/18/2015 01:08 AM, Kishon Vijay Abraham I wrote:
> > Hi,
> >
> > On Tuesday 25 August 2015 02:40 PM, Yoshihiro Shimoda wrote:
> >> This patch adds support for R-Car
Hi Kishon,
Thank you for the review!
And I'm sorry for the delayed response.
> Sent: Friday, September 18, 2015 3:08 PM
>
> Hi,
>
> On Tuesday 25 August 2015 02:40 PM, Yoshihiro Shimoda wrote:
> > This patch adds support for R-Car generation 3 USB2 PHY driver.
> > This SoC has 3 EHCI/OHCI
On Fri, 25 Sep 2015, Sedat Dilek wrote:
> >> $ egrep -nr 'save|restore|acquire|release'
> >> objdump-Dr_kernel-workqueue_o_CLANG-3-7.txt | egrep 'irq|map'
> >> 5718: 4601: R_X86_64_PC32
> >> _raw_spin_unlock_irqrestore-0x4
> >> 5766: 4699: R_X86_64_PC32
The driver handles wakeup irq correctly using irq_set_irq_wake. There's
no need to use IRQF_NO_SUSPEND while registering the interrupt.
This patch removes the use of IRQF_NO_SUSPEND flag.
Cc: Samuel Ortiz
Acked-by: Lee Jones
Signed-off-by: Sudeep Holla
---
drivers/mfd/qcom_rpm.c | 2 +-
1
On Fri, Sep 25, 2015 at 2:00 PM, Jiri Kosina wrote:
> On Thu, 24 Sep 2015, Sedat Dilek wrote:
>
>> >> >> > >> [ 24.705767] [] dump_stack+0x7d/0xa0
>> >> >> > >> [ 24.705774] [] ___might_sleep+0x28a/0x2a0
>> >> >> > >> [ 24.705779] [] __might_sleep+0x4f/0xc0
>> >> >> > >> [ 24.705784]
On Thu, 24 Sep 2015 12:50:59 +0300
"Michael S. Tsirkin" wrote:
> On Thu, Sep 24, 2015 at 09:25:45AM +0200, Greg Kurz wrote:
> > On Wed, 23 Sep 2015 19:45:08 +0100
> > David Woodhouse wrote:
> >
> > > Commit 7d82410950aa ("virtio: add explicit big-endian support to memory
> > > accessors")
rce)\
+ VM_BUG_ON_PAGE(PageCompound(page), page); \
Linux next-20150925 crashes here (at least in lkvm)
if CONFIG_DEFERRED_STRUCT_PAGE_INIT=y
[0.00] Policy zone: DMA32
[0.00] Kernel command line: noapic noacpi pci=conf1 reboot=k
panic=1 i8042.direc
On Fri, Sep 25, 2015 at 02:16:07PM +0300, Jani Nikula wrote:
> On Fri, 25 Sep 2015, Geliang Tang wrote:
> > Leak a task reference in i915_ppgtt_info(), add put_task_struct()
> > to fix it.
>
> Introduced by
>
> commit 1c60fef535d143860d5bf6593e24ab6417f5227c
> Author: Ben Widawsky
> Date:
Commit-ID: 3f2c5085ed99b6ad233cf77009c2f4f898b2f7c8
Gitweb: http://git.kernel.org/tip/3f2c5085ed99b6ad233cf77009c2f4f898b2f7c8
Author: Andy Lutomirski
AuthorDate: Tue, 1 Sep 2015 15:41:06 -0700
Committer: Ingo Molnar
CommitDate: Fri, 25 Sep 2015 09:29:17 +0200
x86/sched/64: Don't save
Commit-ID: 0b101e62afe626ecae60173f92f1e0ec72151653
Gitweb: http://git.kernel.org/tip/0b101e62afe626ecae60173f92f1e0ec72151653
Author: Denys Vlasenko
AuthorDate: Thu, 24 Sep 2015 14:02:29 +0200
Committer: Ingo Molnar
CommitDate: Fri, 25 Sep 2015 09:44:34 +0200
x86/asm: Force inlining
Commit-ID: 7e5560a5648ab2bce7199c73b9c2a51b846f5541
Gitweb: http://git.kernel.org/tip/7e5560a5648ab2bce7199c73b9c2a51b846f5541
Author: Geliang Tang
AuthorDate: Thu, 24 Sep 2015 04:48:53 -0700
Committer: Ingo Molnar
CommitDate: Fri, 25 Sep 2015 09:42:40 +0200
perf/x86: Change
Another regression for Jairo to track.
-Daniel
On Thu, Sep 24, 2015 at 05:22:09PM -0400, Nick Bowler wrote:
> Hi,
>
> Testing out 4.3-rc2, first thing I notice is that the VGA output is
> not working. Specifically, the display is continuously powering on
> and off -- at no point is any image
On Fri, Sep 25, 2015 at 09:16:06AM +0200, Philipp Zabel wrote:
> Hi Thierry,
>
> Am Donnerstag, den 24.09.2015, 19:02 +0200 schrieb Thierry Reding:
> > From: Thierry Reding
> >
> > There's no use building the individual drivers as separate modules
> > because they are all only useful if
On Fri, 25 Sep 2015, Sedat Dilek wrote:
> > This however:
> >
> > [ 24.824639] hardirqs last enabled at (7913): []
> > _raw_spin_unlock_irq+0x32/0x60
> > [ 24.824646] hardirqs last disabled at (7914): []
> > del_timer_sync+0x37/0x110
> >
> > combined with the stacktrace above, doesn't
Like dma_unmap_sg, dma_sync_sg* should be called with the original
number of entries passed to dma_map_sg, so do the same check in the sync
path as we do in the unmap path.
Signed-off-by: Robin Murphy
---
lib/dma-debug.c | 8
1 file changed, 8 insertions(+)
diff --git
Hi Andrew,
This is a miscellany of fixes and tweaks to the common DMA mapping code
which I've been collecting. They don't strictly depend on each other,
but I figure I may as well send them all together for the sake of
explaining them in one place:
#1 is a straightforward and hopefully obvious
Many DMA controllers and other devices set max_segment_size to
indicate their scatter-gather capability, but have no interest in
segment_boundary_mask. However, the existence of a dma_parms structure
precludes the use of any default value, leaving them as zeros (assuming
a properly kzalloc'ed
Since some dma_alloc_coherent implementations return a zeroed buffer
regardless of whether __GFP_ZERO is passed, there exist drivers which
are implicitly dependent on this and pass otherwise uninitialised
buffers to hardware. This can lead to subtle and awkward-to-debug issues
using those drivers
If a DMA pool lies at the very top of the dma_addr_t range (as may
happen with an IOMMU involved), the calculated end address of the pool
wraps around to zero, and page lookup always fails. Tweak the relevant
calculation to be overflow-proof.
Signed-off-by: Robin Murphy
---
mm/dmapool.c | 2 +-
On Fri, Sep 25, 2015 at 2:00 PM, Jiri Kosina wrote:
> On Thu, 24 Sep 2015, Sedat Dilek wrote:
>
>> >> >> > >> [ 24.705767] [] dump_stack+0x7d/0xa0
>> >> >> > >> [ 24.705774] [] ___might_sleep+0x28a/0x2a0
>> >> >> > >> [ 24.705779] [] __might_sleep+0x4f/0xc0
>> >> >> > >> [ 24.705784]
Peter saids -tip tree doesn't have panic_on_unrecovered_nmi in the
previoius discussion, but it still exists. So, I didn't change
anything about panic_on_unrecovered_nmi.
Thanks,
Hidehiro Kawai
Hitachi, Ltd. Research & Development Group
> From: Hidehiro Kawai
On Thu, Sep 24, 2015 at 9:17 PM, Ashish Samant wrote:
> We did some performance testing without these patches and with these patches
> (with -o clone_fd option specified). We did 2 types of tests:
>
> 1. Throughput test : We did some parallel dd tests to read/write to FUSE
> based database fs
On Thu, 24 Sep 2015, Fu, Zhonghui wrote:
> >> Enable hid device to suspend/resume asynchronously. This can improve
> >> system suspend/resume speed.
> > How well was this tested?
> >
> > Power management is notorious for not being really in excellent shape on
> > many HID devices.
> >
> > So I'd
If panic on NMI happens just after panic() on the same CPU, panic()
is recursively called. As the result, it stalls after failing to
acquire panic_lock.
To avoid this problem, don't call panic() in NMI context if
we've already entered panic().
V4:
- Improve comments in io_check_error() and
nmi_shootdown_cpus(), a subroutine of crash_kexec(), sends NMI IPI
to non-panic cpus to stop them while saving their register
information and doing some cleanups for crash dumping. So if a
non-panic cpus is infinitely looping in NMI context, we fail to
save its register information and lose the
Currently, panic() and crash_kexec() can be called at the same time.
For example (x86 case):
CPU 0:
oops_end()
crash_kexec()
mutex_trylock() // acquired
nmi_shootdown_cpus() // stop other cpus
CPU 1:
panic()
crash_kexec()
mutex_trylock() // failed to acquire
This patch introduces new boot option "noextnmi" which disables
external NMI. This option is useful for the dump capture kernel
so that an HA application or administrator wouldn't mistakenly
shoot down the kernel by NMI.
Currently, only x86 supports this option.
Signed-off-by: Hidehiro Kawai
When an HA clustering software or administrator detects unresponsivenes
of a host, they issue an NMI to the host to completely stop current
works and take a crash dump. If the kernel has already panicked
or is capturing a crash dump at that time, further NMI can cause
a crash dump failure.
Also,
On Fri, 25 Sep 2015, Felipe Tonello wrote:
> Maybe a better description on Kconfig and/or comments on source code
> it's enough.
I personally find the current Kconfig description:
===
config USB_KBD
tristate "USB HIDBP Keyboard (simple Boot) support"
depends on USB && INPUT
On Thu, 24 Sep 2015, Sedat Dilek wrote:
> >> >> > >> [ 24.705767] [] dump_stack+0x7d/0xa0
> >> >> > >> [ 24.705774] [] ___might_sleep+0x28a/0x2a0
> >> >> > >> [ 24.705779] [] __might_sleep+0x4f/0xc0
> >> >> > >> [ 24.705784] [] start_flush_work+0x2f/0x290
> >> >> > >> [ 24.705789]
在 2015/9/25 3:30, Marc Zyngier 写道:
> On Wed, 23 Sep 2015 15:24:50 +0800
> "majun (F)" wrote:
>
> [...]
>
+static int mbigen_device_init(struct mbigen_chip *chip,
+ struct device_node *node)
[...]
+
+core_initcall(mbigen_init);
>>>
>>> That's the wrong
On Fri 25-09-15 11:51:53, Dmitry Vyukov wrote:
> On Fri, Sep 25, 2015 at 11:36 AM, Dmitry Vyukov wrote:
> > Looking at __inode_add_bytes/ext4_inode_blocks_set I see much more
> > ways to screw things up.
> > For example, __inode_add_bytes:
> >
> > void __inode_add_bytes(struct inode *inode,
On Thu, Sep 24, 2015 at 02:02:29PM +0200, Denys Vlasenko wrote:
> On x86, cpu_relax() simply calls rep_nop(), which generates one
> instruction, PAUSE (aka REP NOP).
>
> With this config:
> http://busybox.net/~vda/kernel_config_OPTIMIZE_INLINING_and_Os
> gcc-4.7.2 does not always inline
On 2015-09-24 16:14, Theodore Ts'o wrote:
On Thu, Sep 24, 2015 at 03:11:23PM -0400, Austin S Hemmelgarn wrote:
That is a startling result. Please say what architecture, kernel
version, dieharder version and commandline arguments you are using to
get 10% WEAK or FAILED assessments from
On 08/24/2015 04:19 AM, Joonsoo Kim wrote:
> Purpose of compaction is to make high order page. To achive this purpose,
> it is the best strategy that compaction migrates contiguous used pages
> to fragmented unused freepages. Currently, freepage scanner don't
> distinguish whether freepage is
On Tuesday 04 August 2015 20:06:57 Pali Rohár wrote:
> On Monday 03 August 2015 05:02:15 Robert Hancock wrote:
> > On Sun, Aug 2, 2015 at 3:08 AM, Pali Rohár
> > wrote:
> > > On Sunday 02 August 2015 03:45:32 Robert Hancock wrote:
> > >> On Sat, Aug 1, 2015 at 2:09 PM, Pali Rohár
> > >>
> > >>
On Wed, Sep 16, 2015 at 03:21:05PM +0100, Suzuki K. Poulose wrote:
> From: "Suzuki K. Poulose"
>
> This patch adds an infrastructure to keep track of the CPU feature
> registers on the system. For each register, the infrastructure keeps
> track of the system wide safe value of the feature bits.
On Monday 07 September 2015 16:04:35 Dmitry Vyukov wrote:
> The data race happens on ps2dev->cmdcnt and ps2dev->cmdbuf contents.
> __ps2_command reads that data concurrently with the interrupt handler.
> As the result, for example, if a response arrives just after the
> timeout, __ps2_command can
[Sorry for a really long delay]
On Wed 05-08-15 15:01:22, Vlastimil Babka wrote:
> The documentation for /proc/pid/status does not mention that the value of
> VmSwap counts only swapped out anonymous private pages and not shmem. This is
> not obvious, so document this limitation.
This is
On Thursday 17 September 2015 07:16:44 Pavel Machek wrote:
>
> > > if (image->depth == 1) {
> > > if (p->fix.visual == FB_VISUAL_TRUECOLOR ||
> > > p->fix.visual == FB_VISUAL_DIRECTCOLOR) {
> > > fgcolor =
> > >
On Thu, Sep 24, 2015 at 05:03:18PM -0700, Dan Williams wrote:
> That makes sense to me, especially because drivers/nvdimm/blk.c is
> broken in the same way as drivers/nvdimm/pmem.c and it would be
> awkward to have it use blk_dax_get() / blk_dax_put(). The
> percpu_refcount should be valid for
On Fri, Sep 25, 2015 at 09:21:34AM +0200, Geert Uytterhoeven wrote:
> On Mon, Sep 14, 2015 at 11:40 AM, Alexander Kuleshov
> wrote:
> > The MMU base is 32 bits size - 0xfe00, seems that we missed
> > one zero in the definition of the clock and interrupt register
> > addresses.
>
> Thanks for
On Tue 2015-09-22 15:35:13, Tejun Heo wrote:
> On Mon, Sep 21, 2015 at 03:03:48PM +0200, Petr Mladek wrote:
> > /**
> > + * try_to_grab_pending_kthread_work - steal kthread work item from
> > worklist,
> > + * and disable irq
> > + * @work: work item to steal
> > + * @is_dwork: @work is a
Here is another minor improvement that produces deny aces with fewer
permissions in them and avoids creating unnecessary deny aces in some
cases.
Andreas
---
fs/richacl_compat.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/richacl_compat.c b/fs/richacl_compat.c
On 09/25/2015 11:54 AM, Martin Kepplinger wrote:
> This shouldn't change anything since the core calls the events folder
> "events" anyways.
>
> Signed-off-by: Martin Kepplinger
Acked-by: Lars-Peter Clausen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
From: Jiri Kosina
In many cases of hardlockup reports, it's actually not possible to know
why it triggered, because the CPU that got stuck is usually waiting on a
resource (with IRQs disabled) in posession of some other CPU is holding.
IOW, we are often looking at the stacktrace of the victim
On 25/09/2015 03:49, Wu, Feng wrote:
> Hi Paolo,
>
> Thanks for your review on this series! I'd like to confirm this series (plus
> the patch fixing the compilation error) is okay to you and I don't need to
> do extra things for it, right?
Yes, can you check if branch vtd-pi of
On Fri, 25 Sep 2015, Geliang Tang wrote:
> Leak a task reference in i915_ppgtt_info(), add put_task_struct()
> to fix it.
Introduced by
commit 1c60fef535d143860d5bf6593e24ab6417f5227c
Author: Ben Widawsky
Date: Fri Dec 6 14:11:30 2013 -0800
drm/i915: Dump all ppgtt
>
> Signed-off-by:
Prompt proper error message when wrong config terms is specificed for
hw/sw type perf events. This patch makes the original error prompt
function formats_error_string() more generic, which only outputs the
static config terms for hw/sw perf events, and prepends pmu formats
for pmu events.
Before
This patch enable config terms for tracepoint perf events. Valid terms
for tracepoint events are call-graph and stack-size, so we can use
different callgraph settings for each event and eliminate unnecessary
overhead.
Here is an example for using different call-graph config for each
tracepoint.
Adds rules for parsing tracepoint names. Change rules of tracepoint
which derives of PE_NAMEs into tracepoint names directly, so adding
more rules based on tracepoint names will be easier.
Signed-off-by: He Kuang
---
tools/perf/util/parse-events.y | 38 +++---
1
Currently, function config_term() is used for checking config terms of
all types of events, while unknown terms is not reported as an error
because pmu events have valid terms in sysfs. But this is wrong when
unknown terms are specificed to hw/sw events. This patch Adds the
config_term callback so
On 15/09/24, Paul Moore wrote:
> On Friday, September 18, 2015 03:59:58 AM Richard Guy Briggs wrote:
> > Nothing prevents a new auditd starting up and replacing a valid
> > audit_pid when an old auditd is still running, effectively starving out
> > the old auditd since audit_pid no longer points
Linus,
The following changes since commit 00cc1633816de8c95f337608a1ea64e228faf771:
sched: access local runqueue directly in single_task_running (2015-09-18
13:47:59 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to
Leak a task reference in i915_ppgtt_info(), add put_task_struct()
to fix it.
Signed-off-by: Geliang Tang
---
drivers/gpu/drm/i915/i915_debugfs.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_debugfs.c
b/drivers/gpu/drm/i915/i915_debugfs.c
On Friday 25 September 2015, Aaro Koskinen wrote:
> Hi,
>
> On Thu, Sep 24, 2015 at 03:27:01PM +0300, Tomi Valkeinen wrote:
> > fbdev is (more or less) maintained, but it's a deprecated framework. All
> > new Linux display drivers should be done on DRM.
> >
> > So let's not add any more new fbdev
On Fri, Sep 25, 2015 at 10:47 AM, Minchan Kim wrote:
> On Fri, Sep 25, 2015 at 10:17:54AM +0200, Vitaly Wool wrote:
>>
>> > I already said questions, opinion and concerns but anything is not clear
>> > until now. Only clear thing I could hear is just "compaction stats are
>> > better" which is
On Fri, 2015-09-25 at 09:49 +0300, Artem Bityutskiy wrote:
> On Thu, 2015-09-24 at 16:45 -0400, Tejun Heo wrote:
> > Hello, Artem.
> >
> > On Thu, Sep 24, 2015 at 11:09:46AM +0300, Artem Bityutskiy wrote:
> > > On Wed, 2015-09-23 at 17:07 -0400, Tejun Heo wrote:
> > > > So, this should make the
On Thu, Sep 24, 2015 at 08:13:33PM +0100, Luis de Bethencourt wrote:
> reada is using -1 instead of the -ENOMEM defined macro to specify that
> a buffer allocation failed. Since the error number is propagated, the
> caller will get a -EPERM which is the wrong error condition.
>
> Also, updating
Hi,
fbdev is (more or less) maintained, but it's a deprecated framework. All
new Linux display drivers should be done on DRM.
What about no-mmu platforms? DRM has a big fat MMU dependency in the
kconfig, is there a way to write DRM driver for such devices?
/Kamil
--
To unsubscribe from
On 08/24/2015 04:19 AM, Joonsoo Kim wrote:
[...]
>
> Because we just allow freepage scanner to scan non-movable pageblock
> in very limited situation, more scanning events happen. But, allowing
> in very limited situation results in a very important benefit that
> memory isn't fragmented more
--
Guten Tag,
Ich bin Mrs. Rose Butler, die vollziehende Mittel aus einem gut
erkannt legitimen Darlehensgeberin als YesGrowth Darlehen bekannt. Haben
Sie schlechte Kredit haben, oder Sie brauchen Geld, um Ihre Rechnungen
zu bezahlen sind? unser Zinssatz von 3%.
füllen Sie das
On Fri, Sep 25, 2015 at 10:02 AM, Peter Chen wrote:
> On Fri, Sep 25, 2015 at 09:27:49AM +0100, Felipe Tonello wrote:
>> On Thu, Sep 24, 2015 at 2:20 AM, Peter Chen wrote:
>> > On Wed, Sep 23, 2015 at 12:40:46PM +0100, Felipe Tonello wrote:
>> >> Hi Peter,
>> >>
>> >> On Wed, Sep 23, 2015 at
On Thu, 24 Sep 2015, Thierry Reding wrote:
> From: Thierry Reding
>
> Some modules register several sub-drivers. Provide a helper that makes
> it easy to register and unregister a list of sub-drivers, as well as
> unwind properly on error.
>
> Cc: Greg Kroah-Hartman
> Signed-off-by: Thierry
On 09/24/2015 05:51 PM, SF Markus Elfring wrote:
>> +@rs@
>> +position p;
>> +typedef bool, u8, u16, u32, u64, s8, s16, s32, s64;
>> +{char, short int, int, long, long long, s8, s16, s32, s64} vs;
> Can it matter to specify also the type modifier "signed" in this SmPL
> approach?
>
On Thu, Sep 24, 2015 at 9:51 PM, Alan Stern wrote:
> On Thu, 24 Sep 2015, Jiri Kosina wrote:
>
>> On Wed, 23 Sep 2015, Alan Stern wrote:
>>
>> > Your mistake was thinking that the driver for your keyboard is usbkbd.
>> > It isn't. It's usbhid, as you can see in the "lsusb -t" output above.
>>
>>
On Thu, Sep 24, 2015 at 03:47:26PM -0500, atull wrote:
> Interesting. The amount of code bloat here compiles down to about two
> machine instructions (in two places). Actually a little more since I should
> be using IS_ERR_OR_NULL. But the main question is whether I should do
> it at all.
>
Currently there is a number of issues preventing PVHVM Xen guests from
doing successful kexec/kdump:
- Bound event channels.
- Registered vcpu_info.
- PIRQ/emuirq mappings.
- shared_info frame after XENMAPSPACE_shared_info operation.
- Active grant mappings.
Basically, newly booted kernel stumbles
On (09/25/15 10:27), Vitaly Wool wrote:
> > Have you seen those symptoms before? How did you come up to a conclusion
> > that zram->zbud will do the trick?
>
> I have data from various tests (partially described here:
> https://lkml.org/lkml/2015/9/17/244) and once again, I'll post a reply
yeah,
This shouldn't change anything since the core calls the events folder
"events" anyways.
Signed-off-by: Martin Kepplinger
---
drivers/iio/adc/ad799x.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iio/adc/ad799x.c b/drivers/iio/adc/ad799x.c
index b99de00..01d7158 100644
---
Protecting recovery flow by using cp_rwsem is not needed, since we have
prevent triggering any checkpoint by locking cp_mutex previously.
Signed-off-by: Chao Yu
---
fs/f2fs/recovery.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/fs/f2fs/recovery.c
Hello Minchan,
the main use case where I see unacceptably long stalls in UI with
zsmalloc is switching between users in Android.
There is a way to automate user creation and switching between them so
the test I run both to get vmstat statistics and to profile stalls is
to create a user, switch to
This shouldn't actually change anything since the core calls the events
sysfs folder "events" anyways.
Signed-off-by: Martin Kepplinger
---
drivers/iio/adc/max1363.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iio/adc/max1363.c b/drivers/iio/adc/max1363.c
index 1b3b74b..929508e
This patch fixes to maintain the right section count freed in garbage
collecting when triggering a foreground gc.
Besides, when a foreground gc is running on current selected section, once
we fail to gc one segment, it's better to abandon gcing the left segments
in current section, because anyway
Re-sending with correct mailing list address.
On Fri, Sep 25, 2015 at 11:36 AM, Dmitry Vyukov wrote:
> Looking at __inode_add_bytes/ext4_inode_blocks_set I see much more
> ways to screw things up.
> For example, __inode_add_bytes:
>
> void __inode_add_bytes(struct inode *inode, loff_t bytes)
> {
On 09/25/2015 11:45 AM, Martin Kepplinger wrote:
> This shouldn't actually change anything since the core calls the events
> sysfs folder "events" anyways.
>
> Signed-off-by: Martin Kepplinger
Acked-by: Lars-Peter Clausen
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe
Am 2015-09-25 um 11:45 schrieb Martin Kepplinger:
> This shouldn't actually change anything since the core calls the events
> sysfs folder "events" anyways.
>
> Signed-off-by: Martin Kepplinger
> ---
> drivers/iio/dac/ad5504.c | 1 -
> 1 file changed, 1 deletion(-)
>
sorry, this is a single
This shouldn't actually change anything since the core calls the events
sysfs folder "events" anyways.
Signed-off-by: Martin Kepplinger
---
drivers/iio/dac/ad5504.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iio/dac/ad5504.c b/drivers/iio/dac/ad5504.c
index 581ec14..e6e9756
tps6105x driver provides two cells. One is for GPIO and another one is
for selected mode depending on platform data. When tps6105x is used in
GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell
.name == NULL. This value causes an oops in platform_device_register()
later.
The
> -Original Message-
> From: dept_hsg_linux_nic_dev-boun...@qlclistserver.qlogic.com
> [mailto:dept_hsg_linux_nic_dev-boun...@qlclistserver.qlogic.com] On Behalf
> Of Nicholas Krause
> Sent: Friday, September 25, 2015 3:55 AM
> To: Sony Chacko
> Cc: Dept-GE Linux NIC Dev; linux-kernel;
On Thu 24-09-15 14:15:34, David Rientjes wrote:
> On Wed, 23 Sep 2015, Michal Hocko wrote:
>
> > I am still not sure how you want to implement that kernel thread but I
> > am quite skeptical it would be very much useful because all the current
> > allocations which end up in the OOM killer path
On 25/09/15 07:32, Takashi Iwai wrote:
> On Thu, 24 Sep 2015 21:08:39 +0200,
> Luis de Bethencourt wrote:
>>
>> On 24/09/15 19:56, Takashi Iwai wrote:
>>> On Thu, 24 Sep 2015 19:58:30 +0200,
>>> Luis de Bethencourt wrote:
The driver is using -1 instead of the -ENOMEM defined macro to
On Fri, Sep 25, 2015 at 09:54:26AM +0900, Chanwoo Choi wrote:
> Hi Charles,
>
> I have one comment.
> I think current extcon-arizona.c has the many platform data
> so, extcon-arizona.c use the too much if statement to support each feature
> for different wolfsonmicro codec. I think it cause the
On 08/24/2015 04:19 AM, Joonsoo Kim wrote:
> Now, we have a way to determine compaction depleted state and compaction
> activity will be limited according this state and depletion depth so
> compaction overhead would be well controlled without compaction deferring.
> So, this patch remove
These will not be exported by the new linux/sg.h header, and scsi/sg.h will
not have any user API after linux/sg.h is created. Since they have no
user in the kernel, they can be zapped.
Cc: James Bottomley
Cc: Christoph Hellwig
Cc: linux-s...@vger.kernel.org
Reviewed-by: Bart Van Assche
Provide a UAPI version of the header in the kernel, making it easier
for interested projects to use an up-to-date version of the header.
The new headers are placed under uapi/linux/ so as not to conflict
with the glibc-provided headers in /usr/include/scsi.
/dev/sgN default values are
This is v3 of the series to provide an "official" sg.h header (and
scsi_ioctl.h too, though it's basically obsolete) together with the other
userspace API definitions. The change from v2 to v3 is that defaults
for sg.c are not exported in include/uapi/linux/sg.c.
Paolo
2.5.0
--
To unsubscribe
SCSI_REMOVAL_* goes together with other SCSI command constants in
include/scsi/scsi.h. It is also used outside the implementation
of the ioctls (and it is not part of the user API).
scsi_fctargaddress/Scsi_FCTargAddress has had no in-tree use since
commit ca61f10ab2b8 ("[SCSI] remove broken
Some are in scsi.h. Keep them together in preparation for exposing them
in UAPI headers.
Cc: James Bottomley
Cc: Christoph Hellwig
Cc: linux-s...@vger.kernel.org
Reviewed-by: Bart Van Assche
Signed-off-by: Paolo Bonzini
---
include/scsi/scsi.h | 20
Hi Peter,
On Thu, Sep 24, 2015 at 2:38 AM, Peter Chen wrote:
> On Wed, Sep 23, 2015 at 01:01:44PM +0100, Felipe F. Tonello wrote:
>> req->actual == req->length means that there is no data left to enqueue,
>> so free the request.
>>
>> Signed-off-by: Felipe F. Tonello
>> ---
>>
>> Changes in v2:
On Mon, Sep 21, 2015 at 10:40:08AM +0200, Thierry Reding wrote:
> On Thu, Sep 17, 2015 at 12:13:04PM +0200, Antoine Tenart wrote:
> > +
> > +#define BERLIN_PWM_EN 0x0
> > +#define BERLIN_PWM_CONTROL 0x4
> > +#define BERLIN_PWM_DUTY0x8
> > +#define
Allow GPIOs to be configured as wakeup sources. When going to suspend,
disable all GPIO irqs excepting the one configured as wakeup sources.
Signed-off-by: Ludovic Desroches
---
drivers/pinctrl/pinctrl-at91-pio4.c | 76 +
1 file changed, 76 insertions(+)
From: Byungchul Park
hello,
i have already sent this patch about 1 month ago.
(see https://lkml.org/lkml/2015/8/13/160)
now, i am resending the same patch with adding some additional commit
message.
thank you,
byungchul
->8-
>From 8ece9a0482e74a39cd2e9165bf8eec1d04665fa9 Mon Sep 17
Hi,
On i.MX6 we have the situation that the CPU is supplied by a SoC
internal linear regulator which in turn is supplied by an external
switching regulator:
---> Switching regulator ---> LDO ---> CPU
For energy efficiency reasons we want to minimize the dropout voltage on
the LDO.
Any idea how
On Fri, Sep 25, 2015 at 09:27:49AM +0100, Felipe Tonello wrote:
> On Thu, Sep 24, 2015 at 2:20 AM, Peter Chen wrote:
> > On Wed, Sep 23, 2015 at 12:40:46PM +0100, Felipe Tonello wrote:
> >> Hi Peter,
> >>
> >> On Wed, Sep 23, 2015 at 8:09 AM, Peter Chen
> >> wrote:
> >> > On Tue, Sep 22, 2015
On Fri, Sep 25, 2015 at 09:26:21AM +0100, Felipe Tonello wrote:
> Hi Peter,
>
> On Thu, Sep 24, 2015 at 2:17 AM, Peter Chen wrote:
> > On Wed, Sep 23, 2015 at 12:56:58PM +0100, Felipe F. Tonello wrote:
> >> If CONFIG_PM or CONFIG_PM_SLEEP is not set, driver will not compile
> >> properly.
> >>
>
2015-09-25 4:40 GMT+08:00 Jim Davis :
> On Fri, Sep 18, 2015 at 7:35 AM, 慕冬亮 wrote:
>> I git clone and git pull the latest linux kernel.
>> When I make pdfdocs, it reports the following error to me.
>> But I checked the filesystems.xml:14946, no error found.
>>
>>
On Thu, 24 Sep 2015 22:53:03 -0700 (PDT)
"David Miller" wrote:
> From: Ivan Mikhaylov
> Date: Fri, 25 Sep 2015 08:07:52 +0400
>
> > Ben proposed one, is it eligible?
> > Need I resubmit patch with sign and detailed description?
>
> If I genuinely need to answer that question, maybe you should
On Thu, Sep 24, 2015 at 11:35:00AM -0700, Kees Cook wrote:
> On Thu, Sep 24, 2015 at 11:33 AM, Luis Henriques
> wrote:
> > On Tue, Sep 08, 2015 at 11:30:43AM -0700, Kees Cook wrote:
> >> When seq_show_option (068acf2ee776) was merged, it did not correctly
> >> collide with cgroup's addition of
401 - 500 of 1180 matches
Mail list logo
