add Hisilicon BVT I2C controller driver support.
Signed-off-by: Pan Wen
---
change log
v4:
Modify the default frequency to 100KHz.
v3:
Add a SoC specific compatible string.
v2:
1)Fixed a compile error.
2)Dropped the clock-names property.
.../devicetree/bindings/i2c/i2c-hibvt.txt | 24 +
On Mon 26-09-16 18:55:25, Oleg Nesterov wrote:
> On 09/26, Jan Kara wrote:
> >
> > On Mon 26-09-16 18:08:06, Oleg Nesterov wrote:
> > > +/*
> > > + * Tell lockdep we are holding these locks before we call
> > > ->unfreeze_fs(sb).
> > > + */
> > > +static void sb_freeze_acquire(struct super_block *
Hello Stefan,
On Mon, Sep 26, 2016 at 05:18:58PM -0700, Stefan Agner wrote:
> Some SoC might load the GPIO driver after the I2C driver and
> using the I2C bus recovery mechanism via GPIOs. In this case
> it is crucial to defer probing if the GPIO request functions
> do so, otherwise the I2C driver
Hi all,
Changes since 20160923:
New tree: vfs-jk
The vfs-jk tree gained a conflict against the fuse tree.
The rdma tree gained a build failure so I used the version from
next-20160923.
The drm-exynos tree gained a conflict against the drm tree.
The kvm-arm tree lost its build failure but gain
The kernel oops is still reproducible on 4.8.0-rc8 on PowerPC bare metal
While running trinity system call fuzzer, I see these kernel oops messages:
Unable to handle kernel paging request for data at address
0xe45f7702
Faulting instruction address: 0xc0055380
Oops: Kernel acces
On 09/20/2016 09:21 PM, Robert Richter wrote:
On 20.09.16 19:32:34, Hanjun Guo wrote:
On 09/20/2016 06:43 PM, Robert Richter wrote:
Unfortunately either your nor my code does fix the BUG_ON() I see with
the numa kernel:
kernel BUG at mm/page_alloc.c:1848!
See below for the core dump. It l
On Tue, Sep 27, 2016 at 1:32 AM, Andrew Morton
wrote:
> On Fri, 23 Sep 2016 16:51:13 +0200 Andrey Konovalov
> wrote:
>
>> in_interrupt() returns a nonzero value when we are either in an
>> interrupt or have bh disabled via local_bh_disable(). Since we are
>> interested in only ignoring coverage
This replaces uses of __attribute__((packed)) with __packed, which is
recommended to be used over the direct __attribute__. This patch then
includes as necessary to use __packed.
Signed-off-by: Matthew Kilgore
---
drivers/staging/ks7010/eap_packet.h | 10 ++--
drivers/staging/ks7010/ks_hostif.h
On 09/22/2016 07:15 AM, David Rientjes wrote:
> On Thu, 22 Sep 2016, zijun_hu wrote:
>
>>> We don't support inserting when va->va_start == tmp_va->va_end, plain and
>>> simple. There's no reason to do so. NACK to the patch.
>>>
>> i am sorry i disagree with you because
>> 1) in almost all conte
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/arm/Kconfig
between commit:
1d8f51d41fc7 ("arm/arm64: arch_timer: Use archdata to indicate vdso
suitability")
from the arm64 tree and commit:
7b4d24d8c01d ("atomic64: no need for
CONFIG_ARCH_HAS_ATOMI
On Tue, Sep 20, 2016 at 05:53:55PM +0300, Roger Quadros wrote:
> Driver can now work with both ID and VBUS pins or either one of
> them.
>
> There can be the following 3 cases
>
> 1) Both ID and VBUS GPIOs are available:
>
> ID = LOW -> USB_HOST active, USB inactive
> ID = HIGH -> USB_HOST inact
Hi Christoph,
On Tue, 27 Sep 2016 07:04:15 +0200 Christoph Hellwig wrote:
>
> On Tue, Sep 27, 2016 at 11:23:34AM +1000, Stephen Rothwell wrote:
> > Hi Doug,
> >
> > After merging the rdma tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
>
> Please just disable broken
On Tue, Sep 27, 2016 at 7:12AM -0500, Scott Wood wrote:
> -Original Message-
> From: Scott Wood [mailto:o...@buserror.net]
> Sent: Tuesday, September 27, 2016 7:12 AM
> To: Qiang Zhao
> Cc: linuxppc-...@lists.ozlabs.org; pku@gmail.com; X.B. Xie
> ; linux-kernel@vger.kernel.org
> Subje
> When you need to make changes to patches that are part of a series,
> you must resubmit the entire series,
I imagine that will happen when the patch review time passed by a bit
more as Paul Bolle requested it yesterday.
> not just the things that are changes.
Thanks for your reminder.
Regard
Andrey Utkin writes:
>> Does (only) adding the
>>
>> pci_read_config_word(solo_dev->pdev, PCI_STATUS, &val);
>>
>> in solo_reg_write() help?
>
> Yes.
> I have posted a patch with this change few days ago, I thought you have
> noticed it.
Well, I think you haven't sent me a copy. Anyway, i
These patches configure
* the EEPROM
* the LEDs (with some default triggers)
* the USR1 gpio button
for the OMAP5 UEVM board.
H. Nikolaus Schaller (3):
DT: EVM: add EEPROM
DT: EVM: add LEDs
DT: EVM: add USR1 button
arch/arm/boot/dts/omap5-uevm.dts | 92 +
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap5-uevm.dts | 25 +
1 file changed, 25 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index 19f5f0a..1b919f5 100644
--- a/arch/arm/boot/dts/omap5-uevm.dts
+++ b/ar
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap5-uevm.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index 36ff7c3..be659e8 100644
--- a/arch/arm/boot/dts/omap5-uevm.dts
+++ b/arch/arm/boot/dts/omap
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap5-uevm.dts | 60
1 file changed, 60 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index be659e8..19f5f0a 100644
--- a/arch/arm/boot/dts/omap5-ue
>> Memory was not released (as it would be expected) when one call
>> of further resource reservations failed.
>
> This was the only thing in this series that triggered more than a,
> very uninspired, "meh" on first read.
Will it matter here if the function "kfree" will be called for the
data str
>> Use kmalloc_array() in two functions
>> Improve another size determination in gigaset_initcs()
>> Delete an error message for a failed memory allocation
>> Release memory in gigaset_initcs() after an allocation failure
>
> Which "static source code analysis" was used for that discovery?
-Original Message-
From: Thomas Gleixner [mailto:t...@linutronix.de]
Sent: Tuesday, September 27, 2016 3:01 AM
To: Liav Rehana
Cc: john.stu...@linaro.org; linux-kernel@vger.kernel.org; Elad Kanfi
; Noam Camus
Subject: Re: [PATCH] timekeeping: Change type of nsec variable to unsigned i
Hi Linus,
Today's linux-next merge of the gpio tree got a conflict in:
arch/arm/mach-omap2/board-rx51-peripherals.c
between commit:
9b7141d01a76 ("ARM: OMAP2+: Drop legacy board file for n900")
from the arm-soc tree and commit:
9132ce450bd1 ("ARM: omap2: fix missing include")
from the
fix Touchpad cursor does not work after touching Touchpad
by 3 or more fingers.
Issue reproduction procedure
1.Three or more fingers put on Touchpad.
2.release fingers from Touchpad.
3.move the cursor by one finger.
4.the cursor does not move.
Cause
This code does not notify multi fingers state
On Tue, Sep 27, 2016 at 11:23:34AM +1000, Stephen Rothwell wrote:
> Hi Doug,
>
> After merging the rdma tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
Please just disable broken staging code like lustre for the linux-next
builds. We had that discussion before, didn't we?
Hi Linus,
Today's linux-next merge of the gpio tree got a conflict in:
drivers/gpio/gpio-pca953x.c
between commit:
6212e1d6ed40 ("gpio: pca953x: variable 'id' was used twice")
from the i2c tree and commit:
e23efa30 ("gpio: pca954x: Add vcc regulator and enable it")
from the gpio tr
Hi Babu.
On Mon, Sep 26, 2016 at 03:31:37PM -0700, Babu Moger wrote:
> Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc.
>
> This feature limits the space used for "Lock debugging: prove locking
> correctness" by about 4MB. The current sparc systms have the limitation of
> 32M
On Mon, Sep 26, 2016 at 11:44:50AM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-09-25 20:29:27)
> > On Thu, Sep 22, 2016 at 11:51:02AM -0700, Stephen Boyd wrote:
> > > Quoting Peter Chen (2016-09-16 18:16:05)
> > > > On Wed, Sep 14, 2016 at 01:55:02AM -0700, Stephen Boyd wrote:
> > > > > Q
On Mon, Sep 26, 2016 at 01:14:18PM +0200, Fabien Lahoudere wrote:
> Changes in V2:
> - Patches sent to early with bad contents
> Changes in V3:
> - Change subject
> - Split "configure imx for ULPI phy" for disable-oc code
> Changes in V4:
> - Fix "Change switch order" commit
Hi Ulf,
On 9/23/2016 3:37 PM, Ulf Hansson wrote:
[...]
Is there anything else needed in msm sdhci driver so that the auto
tuning is taken care of?
I am not familiar with any other than sdhci-esdhc-imx which supports
the SDHCI_TUNING_MODE_3. I may be wrong though.
In the sdhci-esdhc-imx ca
Hello,
Ping?
- Sanchayan.
On 16-09-19 10:41:51, Sanchayan Maity wrote:
> Remove the use of DDC I2C bus bitbang to support reading of EDID
> and rely on support from internal HDMI I2C master controller instead.
> As a result remove the device tree property ddc-i2c-bus.
>
> Signed-off-by: Sanchay
Hello,
Ping?
- Sanchayan.
On 16-09-21 16:54:38, Sanchayan Maity wrote:
> Add support for Toradex Colibri iMX6 module.
>
> Signed-off-by: Sanchayan Maity
> ---
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts | 253
> arch/arm/boot
Emilio López writes:
> El 22/09/16 a las 06:43, Michael Ellerman escribió:
>> Emilio López writes:
>>
>> Please don't include the *kernel* headers, they're really not meant to
>> be used in userspace programs :)
>>
>>> +CFLAGS += -I../../../../usr/include/
>>
>> That is the correct place to get t
> -Original Message-
> From: Baoyou Xie [mailto:baoyou@linaro.org]
> Sent: Monday, September 26, 2016 5:31 PM
> To: subbu.seethara...@broadcom.com; ketan.muka...@broadcom.com;
> jitendra.bhiv...@broadcom.com; j...@linux.vnet.ibm.com;
> martin.peter...@oracle.com
> Cc: linux-s...@vger.ke
Mike Galbraith wrote:
>Whew, no mythical creature infestation. Thanks, next encounter with
>such an artifact should provide markedly less entertainment.
Oh, no worries. Next time it'll be something else.
There's no dull day with this this kernel thing ;-)
--
Sent from a small device: formattin
On Wed, Sep 14, 2016 at 10:37:05AM +0200, Miklos Szeredi wrote:
> This contains assorted cleanups in the splice area:
>
> - add helpers for pipe buf ops instead of directly calling them
>
> - page cache buf doesn't seem to need confirming (since ages)
>
> - generic_file_splice_read() and gene
Hi all,
Today's linux-next merge of the percpu tree got a conflict in:
include/asm-generic/percpu.h
between commit:
acbdf0e98066 ("percpu: make this_cpu_generic_read notrace")
from the asm-generic tree and commit:
1b5ca1212742 ("percpu: improve generic percpu modify-return implementatio
On 2016-09-26 04:07, Nikolay Borisov wrote:
Not sure if that's expected behaviour or not.
Why don't you sample the stacks of some of those kworker processes to
see if they are all executing a parituclar piece of work. That might
help you narrow down where they originate from. Cat multiple
/pr
Statements should start on tabstops.
Use a single statement and test instead of multiple tests.
Signed-off-by: Joe Perches
---
drivers/net/ethernet/intel/igb/e1000_mac.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/net/ethernet/intel/igb/e1000_mac.
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
arch/arm/include/asm/arch_gicv3.h
between commit:
91ef84428a86 ("irqchip/gic-v3: Reset BPR during initialization")
from the tip tree and commit:
3d9cd95f90b2 ("ARM: gic-v3: Work around definition of gic_write_bpr1")
On Wed, Sep 14, 2016 at 10:37:14AM +0200, Miklos Szeredi wrote:
> What __generic_file_splice_read() does is get a series of uptodate pages
> and put them into the pipe buffer.
>
> The get_page_for_read() helper can now be used to get the pages,
> simplifying the code and making sure the splice(2)
On Wed, Sep 14, 2016 at 10:37:13AM +0200, Miklos Szeredi wrote:
> Getting the page for reading is pretty complicated. This functionality is
> also duplicated between generic_file_read() generic_file_splice_read().
>
> So first extract the common code from do_generic_file_read() into a
> separate
On 2016년 09월 23일 01:53, bseg...@google.com wrote:
> Jeehong Kim writes:
>
>>> Peter Zijlstra writes:
>>>
You forgot to Cc Ben, who gave you feedback on v1, which is rather poor
style. Also, I don't see how kernel-janitors is relevant to this patch.
This is very much not a janitor
On Wed, Sep 14, 2016 at 10:37:11AM +0200, Miklos Szeredi wrote:
> Things could happen to that page that make it not uptodate while sitting in
> the pipe, but it's questionable whether we should care about that.
> Checking for being uptodate in the face of such page state change is always
> going t
On Tuesday, September 27, 2016 12:20 AM Vlastimil Babka wrote
>
> When increasing the compaction priority, also reset retries. Otherwise we can
> consume all retries on the lower priorities. Also pull the retries increment
> into should_compact_retry() so it counts only the rounds where we actual
Move some data to text
$ size drivers/net/ethernet/intel/i40e/i40e_ethtool.o*
textdata bss dec hex filename
25012 0 32 2504461d4
drivers/net/ethernet/intel/i40e/i40e_ethtool.o.new
228682120 32 2502061bc
drivers/net/ethernet/intel/i40e/i40e_e
v1-v2: Fix memory allocation issue in interrupt context.
Yijing Wang (2):
libsas: Alloc dynamic work to avoid missing sas events
libsas: Fix hotplug issue in libsas
drivers/scsi/libsas/sas_ata.c | 34 ++---
drivers/scsi/libsas/sas_discover.c | 245 ++--
Now libsas hotplug work is static, LLDD driver queue
the hotplug work into shost->work_q. If LLDD driver
burst post lots hotplug event to libsas, the hotplug
events may pending in the workqueue like
shost->workq
tail | PHYE_LOSS_OF_SIGNAL | PORTE_BYTES_DMAED | head
In this case, if a new PORTE_B
Hold off on this one. Currently reworking a patch series that won't
need this change after all.
On Thu, Sep 22, 2016 at 8:32 PM, Matt Ranostay wrote:
> bq24190_register_reset() function needs to reset the bdi->first_time
> condition every time to avoid spurious interrupts in suspend/resume.
>
> S
Now the libsas hotplug has some issues, Dan Williams report
a similar bug here:
https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html
The root cause of the issues is we use one workqueue(shost->work_q) to
process libsas event, and we divide a hot-on or hot-remove flow to several
ev
On Mon, 2016-09-26 at 15:35 -0400, Thomas Gleixner wrote:
> On Mon, 26 Sep 2016, Thomas Gleixner wrote:
> > Can you please provide your .config and the dmesg of a bad and a good run?
>
> Don't bother. I found it.
>
> It's a merge artifact. So git bisect pointing at the merge commit is
> entirely
On 2016.09.26 18:31 Srinivas Pandruvada wrote:
> On Mon, 2016-09-26 at 19:48 -0500, Larry Finger wrote:
>> On 09/26/2016 07:21 PM, Rafael J. Wysocki wrote:
>>> On Tue, Sep 27, 2016 at 1:53 AM, Larry Finger wrote:
>>> But for both we need a reproducer anyway.
>> I do not have a reliable reproducer.
On Mon, Sep 12, 2016 at 09:29:02PM +0200, Miklos Szeredi wrote:
> The first patch is actually a bug fix, but I put it into this bunch for
> simplicity...
>
> The rest are really cleanups as well as minor bugfixes that are byproducts
> of the cleanups.
>
> This series builds on the fact that i_op.
On Mon, Sep 26, 2016 at 02:43:17PM -0300, Marcelo Cerri wrote:
>
> Wouldn't be enough to provide a pair of import/export functions as the
> padlock-sha driver does?
I don't think that will help as ultimately you need to call the
export function on the fallback and that's what requires the extra
m
On Mon, Sep 26, 2016 at 10:30:56AM +0800, Johnny.Chuang wrote:
> There is only one different which is adding a new empty line for coding
> style.
>
> > if (!error)
> > - error = elants_i2c_query_fw_id(ts);
> > + error = error2;
> > +
> > if (!error)
> > erro
On 09/26/2016 08:30 PM, Srinivas Pandruvada wrote:
On Mon, 2016-09-26 at 19:48 -0500, Larry Finger wrote:
On 09/26/2016 07:21 PM, Rafael J. Wysocki wrote:
On Tue, Sep 27, 2016 at 1:53 AM, Larry Finger wrote:
On 09/26/2016 05:16 PM, Rafael J. Wysocki wrote:
On Tue, Sep 27, 2016 at 12:09 A
On 09/26/2016 11:57 AM, Brian Boylston wrote:
iLO5 will offer the same watchdog timer as previous generations, but the
PCI subsystem vendor ID will be PCI_VENDOR_ID_HP_3PAR (0x1590) instead of
PCI_VENDOR_ID_HP (0x103c). Add 0x1590 to the whitelist and be more
specific when ignoring the 103c,1979
On 2016/9/27 9:39, Jaegeuk Kim wrote:
> On Tue, Sep 27, 2016 at 08:57:41AM +0800, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2016/9/27 2:33, Jaegeuk Kim wrote:
>>> Hi Chao,
>>>
>>> On Tue, Sep 27, 2016 at 12:09:52AM +0800, Chao Yu wrote:
From: Chao Yu
In sync_node_pages, we won't check
Hi tglx,
I'm sorry for the late reply.
Awfully sorry that I could not do anything help.
In fact, it's my fault.
I should re-base my patches after the commit c291b0151585 in time.
I learned a lot from it.
Thank a lot, and once again my apologies.
Thanks,
Dou
At 09/27/2016 01:36 AM, Thomas Gle
There exists almost same codes when get the value of pre_version
and cur_version in function validate_checkpoint, this patch adds
get_checkpoint_version to clean up redundant codes.
Signed-off-by: Tiezhu Yang
---
fs/f2fs/checkpoint.c | 63 ++--
1 f
On 9/26/16 4:38 PM, Cyrill Gorcunov wrote:
> Something like
>
> Index: linux-ml.git/include/uapi/linux/inet_diag.h
> ===
> --- linux-ml.git.orig/include/uapi/linux/inet_diag.h2016-09-11
> 20:56:18.191584145 +0300
> +++ linux-ml.g
On 09/20/16 at 02:53pm, Joerg Roedel wrote:
> Hmm, have you tried hooking this into the set_dma_mask call-back? Every
> driver should call it for its device, so that should be a better
> indicator to now map a new domain.
Hi Joerg,
I tried hooking this into set_dma_mask call-back, but on my local
On Mon, 2016-09-26 at 11:05 -0500, Eric W. Biederman wrote:
> Ian Kent writes:
>
> > On Fri, 2016-09-23 at 14:15 -0500, Eric W. Biederman wrote:
> > > Ian Kent writes:
> > >
> > > 2> On Thu, 2016-09-22 at 20:37 -0500, Eric W. Biederman wrote:
> > > > > Ian Kent writes:
> > > > >
> > > > > > O
On 2016/9/27 7:58, Arnaldo Carvalho de Melo wrote:
Le 26 sept. 2016 8:47 PM, "Alexei Starovoitov"
mailto:alexei.starovoi...@gmail.com>> a
écrit :
>
> On Mon, Sep 26, 2016 at 09:49:30AM +0800, Wangnan (F) wrote:
> >
> >
> > On 2016/9/24 23:16, Alexei Starovoitov wrote:
> > >On Fri, Sep 23, 2
On 一, 2016-09-19 at 10:18 +0900, Inhyuk Kang wrote:
> It is necessary to be added governor at each thermal_zone.
> Because some governors should be operated in the during the kernel
> booting
> in order to avoid heating problem.
>
> Default governor cannot be covered all thermal zones policy becau
Hi Inki,
Today's linux-next merge of the drm-exynos tree got a conflict in:
drivers/gpu/drm/exynos/exynos_drm_drv.c
between commit:
2b58e98d42af ("drm/atomic-helper: Add NO_DISABLE_AFTER_MODESET flag support
for plane commit")
from the drm tree and commit:
3a87f9383457 ("drm/exynos: fi
On Tue, Sep 27, 2016 at 08:50:02AM +0800, Huang, Ying wrote:
> Jaegeuk Kim writes:
>
> > On Mon, Sep 26, 2016 at 02:26:06PM +0800, Huang, Ying wrote:
> >> Hi, Jaegeuk,
> >>
> >> "Huang, Ying" writes:
> >>
> >> > Jaegeuk Kim writes:
> >> >
> >> >> Hello,
> >> >>
> >> >> On Sat, Aug 27, 2016 at
On Tue, Sep 27, 2016 at 08:57:41AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/9/27 2:33, Jaegeuk Kim wrote:
> > Hi Chao,
> >
> > On Tue, Sep 27, 2016 at 12:09:52AM +0800, Chao Yu wrote:
> >> From: Chao Yu
> >>
> >> In sync_node_pages, we won't check and commit last merged pages in private
>
On Mon, 2016-09-26 at 17:01 -0700, Andrew Morton wrote:
> I don't share Eric's concerns about performance here. If the vmalloc()
> is called, we're about to write to that quite large amount of memory
> which we just allocated, and the vmalloc() overhead will be relatively
> low.
I did not care o
On Mon, 2016-09-26 at 19:48 -0500, Larry Finger wrote:
> On 09/26/2016 07:21 PM, Rafael J. Wysocki wrote:
> >
> > On Tue, Sep 27, 2016 at 1:53 AM, Larry Finger > r.net> wrote:
> > >
> > > On 09/26/2016 05:16 PM, Rafael J. Wysocki wrote:
> > > >
> > > >
> > > > On Tue, Sep 27, 2016 at 12:09 AM,
> "Lee" == Lee Duncan writes:
Lee,
Lee> Chris Leech and I are taking over as open-iscsi maintainers.
Do you want me to queue the MAINTAINER update?
Lee> * Removed git repository, since code in tree
Is it your plan to go through the SCSI tree?
--
Martin K. Petersen Oracle Linux Eng
Hi Doug,
After merging the rdma tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c: In function
'kiblnd_hdev_setup_mrs':
drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c:2317:7: error: implicit
declaration of function 'i
Hi.
If you want to declare some things for user interface,
is it be better to put those thing include/uapi/linux/ than include/linux?
Agreed with Mr. Pinto's opinion with respect to implementing additional ioctls.
Regards.
> -Original Message-
> From: linux-scsi-ow...@vger.kernel.org [m
The Kconfig currently controlling compilation of this code is:
drivers/bus/Kconfig:config QCOM_EBI2
drivers/bus/Kconfig:bool "Qualcomm External Bus Interface 2 (EBI2)"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructu
In commit 30e92153b4e6 ("padata: Convert to hotplug state machine")
this file started using module.h and got module_init and module_exit
added to it.
However the Kconfig for it is:
init/Kconfig:config PADATA
init/Kconfig: depends on SMP
init/Kconfig: bool
...and so it currently is n
> "Baoyou" == Baoyou Xie writes:
Baoyou> We get a few warnings when building kernel with W=1:
Baoyou> drivers/scsi/megaraid/megaraid_sas_fp.c:94:5: warning: no
Baoyou> previous prototype for 'mega_mod64' [-Wmissing-prototypes]
Baoyou> drivers/scsi/megaraid/megaraid_sas_fp.c:112:5: warning: no
On Mon, Sep 26, 2016 at 03:25:30PM -0700, Lee Duncan wrote:
> Chris Leech and I are taking over as open-iscsi maintainers.
Can we get rid of the horribly unusable googlegroups list and just
move everything to linux-scsi while we're at it?
> "Baoyou" == Baoyou Xie writes:
Baoyou> We get a few warnings when building kernel with W=1:
Baoyou> drivers/scsi/mvsas/mv_sas.c:77:18: warning: no previous
Baoyou> prototype for 'mvs_find_dev_mvi' [-Wmissing-prototypes]
Baoyou> drivers/scsi/mvsas/mv_sas.c:105:5: warning: no previous
Baoyou>
> "Baoyou" == Baoyou Xie writes:
Baoyou> We get 2 warnings when building kernel with W=1:
Baoyou> drivers/scsi/pm8001/pm8001_sas.c:530:23: warning: no previous
Baoyou> prototype for 'pm8001_alloc_dev' [-Wmissing-prototypes]
Baoyou> drivers/scsi/pm8001/pm8001_hwi.c:4495:5: warning: no previous
Hi Jaegeuk,
On 2016/9/27 2:33, Jaegeuk Kim wrote:
> Hi Chao,
>
> On Tue, Sep 27, 2016 at 12:09:52AM +0800, Chao Yu wrote:
>> From: Chao Yu
>>
>> In sync_node_pages, we won't check and commit last merged pages in private
>> bio cache of f2fs, as these pages were taged as writeback, someone who is
Christoph Hellwig writes:
> Hi Ying,
>
>> Any update to this regression?
>
> Not really. We've optimized everything we could in XFS without
> dropping the architecture that we really want to move to. Now we're
> waiting for some MM behavior to be fixed that this unconvered. But
> in the end wi
Jaegeuk Kim writes:
> On Mon, Sep 26, 2016 at 02:26:06PM +0800, Huang, Ying wrote:
>> Hi, Jaegeuk,
>>
>> "Huang, Ying" writes:
>>
>> > Jaegeuk Kim writes:
>> >
>> >> Hello,
>> >>
>> >> On Sat, Aug 27, 2016 at 10:13:34AM +0800, Fengguang Wu wrote:
>> >>> Hi Jaegeuk,
>> >>>
>> >>> > > >> > - [
On 09/26/2016 07:21 PM, Rafael J. Wysocki wrote:
On Tue, Sep 27, 2016 at 1:53 AM, Larry Finger wrote:
On 09/26/2016 05:16 PM, Rafael J. Wysocki wrote:
On Tue, Sep 27, 2016 at 12:09 AM, Larry Finger
wrote:
Maybe it's better to try diagnose the problem instead of spending more
time on bis
Hello.
I'm hitting below bug when a process $pid terminates while somebody else is
reading
/proc/$pid/stat . According to https://lkml.org/lkml/2016/8/21/10 , it was
already
fixed. But it seems to me that this bug is still in linux-next-20160923.
Is this a different bug?
[ 191.915694] BUG: una
Fri, Sep 23, 2016 at 04:31:56PM -0300, Marcelo Cerri wrote:
> The driver does not handle endianness properly when loading the input
> data.
Indeed. I tested in both endianesses and it's working fine. Thanks!
Herbert, can we go ahead with this fix?
>
> Signed-off-by: Marcelo Cerri
> ---
> arch
On Mon, Sep 26, 2016 at 07:55:13PM -0400, Thomas Gleixner wrote:
> On Mon, 26 Sep 2016, Rich Felker wrote:
> > On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote:
> > Based on use of ftrace, I was able to see situations where a second
> > timer hardirq happened immediately after one occ
On Sun, 2016-09-25 at 09:14 -0700, James Smart wrote:
> add u64 number parser
>
> Reverted back to version 2 of the patch. This adds the interface
> using existing logic. Comments from the prior reviewers to move to
> kasprintf were rejected by Linus.
>
> Signed-off-by: James Smart
Acked-by: J
> "Baoyou" == Baoyou Xie writes:
Baoyou> In fact, these functions are only used in the file in which they
Baoyou> are declared and don't need a declaration, but can be made
Baoyou> static. so this patch marks these functions with 'static'.
Applied to 4.9/scsi-queue.
--
Martin K. Petersen
Add support to run sched-pipe benchmark test on pipe with packet I/O mode.
Signed-off-by: Shuah Khan
---
tools/perf/bench/sched-pipe.c | 20
1 file changed, 20 insertions(+)
diff --git a/tools/perf/bench/sched-pipe.c b/tools/perf/bench/sched-pipe.c
index 1dc2d13..c6e1b7a 10
If a GPIO gets freed after selecting a new pinctrl configuration
the driver should not change pinctrl anymore. Otherwise this will
likely lead to a unusable pin configuration for the newly selected
pinctrl.
Signed-off-by: Stefan Agner
---
This turned out to be problematic when using the I2C GPIO
On Tue, Sep 27, 2016 at 1:53 AM, Larry Finger wrote:
> On 09/26/2016 05:16 PM, Rafael J. Wysocki wrote:
>>
>> On Tue, Sep 27, 2016 at 12:09 AM, Larry Finger
>
> wrote:
>>
>>
>> Maybe it's better to try diagnose the problem instead of spending more
>> time on bisection.
>
>
> In my original post,
Some SoC might load the GPIO driver after the I2C driver and
using the I2C bus recovery mechanism via GPIOs. In this case
it is crucial to defer probing if the GPIO request functions
do so, otherwise the I2C driver gets loaded without recovery
mechanisms enabled.
Signed-off-by: Stefan Agner
---
T
On Tue, Sep 27, 2016 at 07:15:41AM +1000, Benjamin Herrenschmidt wrote:
What is that business with a command line argument ? Do that mean that
we'll need some magic command line argument to properly handle LPC memory
on CAPI devices or GPUs ? If yes that's bad ... kernel arguments should
be a las
From: Philippe Reynes
Date: Sun, 25 Sep 2016 23:31:24 +0200
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> Signed-off-by: Philippe Reynes
Applied, thanks.
On Tue, Sep 27, 2016 at 07:12:31AM +1000, Benjamin Herrenschmidt wrote:
In any case, if the memory hasn't been hotplug, this shouldn't be
necessary as we shouldn't be considering it for allocation.
Right. To be clear, the background info I put in the commit log refers
to x86, where the SRAT ca
On Thu, Mar 31, 2016 at 1:34 AM, Jens Axboe wrote:
> On 03/30/2016 05:31 PM, Alexey Klimov wrote:
>>
>> Hi all,
>>
>> On Wed, Jan 27, 2016 at 9:01 PM, Jeff Moyer wrote:
>>>
>>> Alexey Klimov writes:
>>>
Last user of elevator_init() with non-NULL name as second argument
that supposed to
Hi Jan,
Today's linux-next merge of the vfs-jk tree got a conflict in:
fs/fuse/dir.c
between commits:
3b3fb74935ce ("fuse: invalidate dir dentry after chmod")
5f69e628df75 ("fuse: fix killing s[ug]id in setattr")
from the fuse tree and commit:
62490330769c ("fuse: Propagate dentry dow
When you need to make changes to patches that are part of a series,
you must resubmit the entire series, not just the things that
are changes.
On Mon, 26 Sep 2016, Liav Rehana wrote:
> During the calculation of the nsec variable in the inline function
> timekeeping_delta_to_ns, it may undergo a sign extension if its msb
> is set just before the shift. The sign extension may, in some cases,
> gain it a value near the maximum value of the 6
On Thu, 22 Sep 2016 18:43:59 +0200 Vlastimil Babka wrote:
> The select(2) syscall performs a kmalloc(size, GFP_KERNEL) where size grows
> with the number of fds passed. We had a customer report page allocation
> failures of order-4 for this allocation. This is a costly order, so it might
> easily
1 - 100 of 623 matches
Mail list logo
