On Fri, 26 Oct 2018 18:14:36 +
Carlos Iglesias wrote:
> Add device tree bindings for the HSC pressure sensors.
>
> Signed-off-by: Carlos Iglesias
> ---
> .../bindings/iio/pressure/hsc_spi.txt | 85 +++
> 1 file changed, 85 insertions(+)
> create mode 100644
On Thu, Oct 25, 2018 at 9:38 PM Andy Gross wrote:
>
> On Thu, Oct 25, 2018 at 10:55:32AM +0530, Amit Kucheria wrote:
>
>
>
> > Andy,
> >
> > While you acked the tsens thermal DT patches[1] so they could go
> > through the thermal tree[2] to avoid a dependency, Eduardo would
> > prefer the DT
On Sun, 28 Oct 2018 11:33:35 -0600
Shuah Khan wrote:
> Hi Steve,
>
> Are there any dependencies on my pull request I sent to Linus? It hasn't
> been pulled in yet. If there is one, could please you mention that in your
> pull request for this.
There's no dependency on the patches you took. But
On Sun, 28 Oct 2018 13:52:32 -0300
Renato Lui Geh wrote:
> Hi Jonathan,
>
> Thank you for the review.
>
> >> + voltage_uv = regulator_get_voltage(st->reg);
> >> + if (voltage_uv)
> >> + st->int_vref_mv = voltage_uv/1000;
> >>*val = st->int_vref_mv
On Wed, Oct 24, 2018 at 9:17 AM Adam Ford wrote:
>
> On Wed, Oct 24, 2018 at 9:08 AM jacopo mondi wrote:
> >
> > Hi Adam,
> >
> > On Wed, Oct 24, 2018 at 08:53:41AM -0500, Adam Ford wrote:
> > > On Tue, Oct 23, 2018 at 6:03 PM jacopo mondi wrote:
> > > >
> > > > Hi Adam,
> > > >
> > > > On Tue,
On Sun, Oct 28, 2018 at 12:13 PM Matthew Wilcox wrote:
>
> On Sun, Oct 28, 2018 at 11:50:19AM -0700, Linus Torvalds wrote:
>
> > NOTE! I did get some conflicts with other stuff, and while the
> > conflict resolution all looked pretty straightforward, this does want
> > looking at.
> >
> >
This satifies a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index f64da16dbec9..bad2ee26cd4e 100644
--- a/drivers/w1/w1.c
This fixes a warning raised by the checkpatch tool
Signed-off-by: Steffen Vogel
---
drivers/w1/w1_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/w1/w1_io.c b/drivers/w1/w1_io.c
index 283c89708c7c..b18d82cde71e 100644
--- a/drivers/w1/w1_io.c
+++
These changes fix several warnings emitted by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 20 +---
drivers/w1/w1_family.c | 2 +-
drivers/w1/w1_io.c | 17 +
drivers/w1/w1_netlink.c | 2 +-
4 files changed, 20
This fixes a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 3 ++-
drivers/w1/w1_int.c | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index e8ce97e066ec..c790c79352a0 100644
---
This satisfies a checkpatch warning and is the preferred
method for notating the license.
The SPDX identifier is a legally binding shorthand, which
can be used instead of the full boiler plate text.
Signed-off-by: Steffen Vogel
---
drivers/w1/masters/ds1wm.c | 5 +
This satisfies a checkpatch warning
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 56 +
drivers/w1/w1_int.c | 3 ++-
drivers/w1/w1_io.c | 29 +++--
drivers/w1/w1_netlink.c | 16 +-
4 files
This fixes a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1_netlink.h | 28 +---
1 file changed, 13 insertions(+), 15 deletions(-)
diff --git a/drivers/w1/w1_netlink.h b/drivers/w1/w1_netlink.h
index 08cbf08f3649..7873eb54352e
Hi,
memory-barriers.txt says:
[on "store tearing"]
"In fact, a recent bug (since fixed) caused GCC to incorrectly use
this optimization in a volatile store.".
I was wondering if you could help me retrieve some reference/discussions
about this?
Thanks,
Andrea
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in:
include/linux/platform_data/gpio-omap.h
between commit:
b764a5863fd8 ("gpio: omap: Remove custom PM calls and use cpu_pm instead")
from Linus' tree and commit:
26683316c92a ("ARM: OMAP1: ams-delta-fiq: Use
")
On 2018년 10월 27일 14:47, Julia Lawall wrote:
> The clk_ops structure is only stored in the ops fields of
> clk_init_data structures. This field is const, so the clk_ops
> structure can be const as well.
>
> Identified and transformed using Coccinelle.
>
> Signed-off-by: Julia Lawall
>
> ---
>
On Sun, Oct 28, 2018 at 10:21:42AM -0700, Paul E. McKenney wrote:
> On Sat, Oct 27, 2018 at 07:16:53PM -0700, Joel Fernandes (Google) wrote:
> > The RCU example for 'rejecting stale data' on system-call auditting
> > stops iterating through the rules if a deleted one is found. It makes
> > more
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
fs/ceph/file.c
between commit:
fce7a9744bdf ("ceph: refactor ceph_sync_read()")
from the ceph tree and commit:
00e23707442a ("iov_iter: Use accessor function")
from the vfs tree.
I fixed it up (see below) and can
Replace platform data with device tree support.
Signed-off-by: Nishad Kamdar
---
drivers/staging/iio/resolver/Kconfig| 1 +
drivers/staging/iio/resolver/ad2s1210.c | 17 -
drivers/staging/iio/resolver/ad2s1210.h | 17 -
3 files changed, 9 insertions(+), 26
Hi Sasha,
On Fri, Oct 26, 2018 at 04:42:25PM -0400, Sasha Levin wrote:
> On Fri, Oct 26, 2018 at 04:04:45PM -0300, Shayenne da Luz Moura wrote:
> > This change was suggested by checkpath.pl. Use unsigned int with bitfield
> > allocate only one bit to the boolean variable.
> >
> > CHECK: Avoid
Add device tree table for matching vendor ID.
Signed-off-by: Nishad Kamdar
---
drivers/staging/iio/resolver/ad2s1210.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/staging/iio/resolver/ad2s1210.c
b/drivers/staging/iio/resolver/ad2s1210.c
index 93c3c70ce62e..0234869e9d74
On 27/10/18 12:16, Dmitry Vyukov wrote:
> On Wed, Oct 24, 2018 at 1:03 PM, Juri Lelli wrote:
> >
> > On 19/10/18 22:50, luca abeni wrote:
> > > On Fri, 19 Oct 2018 13:39:42 +0200
> > > Peter Zijlstra wrote:
> > >
> > > > On Thu, Oct 18, 2018 at 01:08:11PM +0200, luca abeni wrote:
> > > > > Ok, I
Hi Dave,
> Dave Stevenson hat am 26. Oktober 2018 um
> 19:15 geschrieben:
>
>
> Thanks Stefan.
> I've picked up your latest patches which mean I can get the driver
> loaded via the (almost) approved method.
> I do seem to still have issues with not getting the expected address
> ranges, so
Hi Linus,
On 27-10-18 18:08, Linus Torvalds wrote:
Julian, Jiri,
On my laptop I'm getting a kernel page fault with the current git
tree, and I'm tentatively blaming commit
9ee3e06610fd ("HID: i2c-hid: override HID descriptors for certain devices")
but that's simply because it's the only
* Jordan Borgner wrote:
> Added missing parentheses to sizeof() function in detect_memory_e820().
>
> Removed unnecessary braces in detect_memory_e801().
>
> Replaced three if-statements with a ternary if-statement and
> removed an unnecessary integer variable in detect_memory().
>
> This
On Sun, 28 Oct 2018, Himanshu Jha wrote:
> On Sun, Oct 28, 2018 at 09:47:15AM +0100, Julia Lawall wrote:
> > > The "possible alignement issues" in CHECK report is difficult to figure
> > > out by just doing a glance analysis. :)
> > >
> > > Linus also suggested to use bool as the base type
Hi Lokesh,
On Fri, 26 Oct 2018 21:19:41 +0100,
Lokesh Vutla wrote:
>
> Hi Marc,
>
> [..snip..]
> >> [...]
> >>
> > +/**
> > + * ti_sci_inta_register_event() - Register a event to an interrupt
> > aggregator
> > + * @dev: Device pointer to source generating the event
>
On Tue, Oct 23, 2018 at 10:11 AM Leonardo Brás wrote:
>
> Creates DEF_FIELD_ADDR_VAR as a more generic version of the DEF_FIELD_ADD
> macro, allowing usage of a variable name other than the struct element name.
> Also, sets DEF_FIELD_ADDR as a specific usage of DEF_FILD_ADDR_VAR in which
> the
Thu, 25 Oct 2018 09:49:03 +0200 tarihinde
Pavel Machek yazdı:
> Hi!
>
> Here's problem bisected down to:
>
> commit 9d659ae14b545c4296e812c70493bfdc999b5c1c
> Author: Peter Zijlstra
> Date: Tue Aug 23 14:40:16 2016 +0200
>
> locking/mutex: Add lock handoff to avoid starvation
>
>
On Thu, Oct 25, 2018 at 11:36 AM Shuah Khan wrote:
>
> Please pull the following kselftest update for Linux 4.20-rc1
Pulled,
Linus
On Sat, Oct 27 2018, Josh Triplett wrote:
> On Fri, Oct 26, 2018 at 08:14:51AM +1100, NeilBrown wrote:
>> On Wed, Oct 24 2018, Josh Triplett wrote:
>>
>> > On Tue, Oct 23, 2018 at 07:26:06AM +1100, NeilBrown wrote:
>> >> On Sun, Oct 21 2018, Josh Triplett wrote:
>> >>
>> >> > On Mon, Oct 22,
Attn: My Dear
I am glad to inform you that i have successfully concluded the
transaction which i seek for your family help before, Now the fund has
been transferred to Hong Kong through the assistant of Mr.Wong Lee,
who is a business man base in Hong Kong.Once again, I have mapped out
a
Hi,
This is my first series of patches for the Linux kernel.
I started by familiarizing myself with coding style and
satisfying my inner OCD by cleaning the 1-wire subsystem.
Steffen
This fixes a warning raised by the checkpatch tool.
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 7 +--
drivers/w1/w1_int.c | 6 +-
2 files changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index bad2ee26cd4e..e8ce97e066ec 100644
---
This satisfies a checkpatch warning
Signed-off-by: Steffen Vogel
---
drivers/w1/w1.c | 23 +++
drivers/w1/w1_netlink.c | 7 +++
2 files changed, 30 insertions(+)
diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
index bd95dfe4041d..812186ce35d6 100644
---
On Sat, Oct 20, 2018 at 01:23:40PM +0530, Vignesh R wrote:
>
>
> On 28-Sep-18 10:55 AM, Vignesh R wrote:
> > Couple of patches to enable i2c-omap driver to be used with TI's new
> > AM654 platforms.
> >
> >
> > Vignesh R (2):
> > dt-bindings: i2c-omap: Add new compatible for AM654 SoCs
> >
Hi Linus,
After merging the origin tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
net/bridge/br_multicast.c: In function 'br_multicast_query_received':
net/bridge/br_multicast.c:1432:32: error: 'union ' has no member
named 'ip6'; did you mean 'ip4'?
On Sun, Oct 28, 2018 at 3:35 PM Stephen Rothwell wrote:
>
> After merging the origin tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
linux-next is back! Wheee..
> 5a2de63fd1a5 ("bridge: do not add port to router list when receives query
> with source 0.0.0.0")
Hi Linus,
After merging the origin tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/net/ethernet/mellanox/mlx4/en_rx.c:582:18: warning: 'struct iphdr'
declared inside parameter list will not be visible outside of this definition
or declaration
On Sun, 2018-10-28 at 23:09 +0100, Steffen Vogel wrote:
> This satisfies a checkpatch warning
Perhaps run your patches through checkpatch with --strict
> diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
[]
> @@ -85,7 +85,8 @@ static void w1_slave_release(struct device *dev)
>
Hi Andreas,
On Thu, Oct 25, 2018 at 08:44:06AM +, Andreas Puhm wrote:
> >My experience with cvp is with Arria10 and Stratix 10. The PCIe Hard IP
> >gets configured when the IOring gets configured at power on. The idea is
> >that the load of the IOring is very fast, much before the infamous
On 10/28/2018 02:01 AM, Steven Rostedt wrote:
> On Mon, 22 Oct 2018 00:07:50 +0900
> Masami Hiramatsu wrote:
>
>> Hi,
>>
>> I found another bug in synthetic event. This is a small fix, but
>> confusingly, there is also a bug in a test case.
>>
>> Steve, since the testcase bugfix ([2/2]) breaks
On Sun, Oct 28, 2018 at 12:13 PM Linus Torvalds
wrote:
>
> So the recent change to enable the high-res scrolling really seems a
> bit *too* extreme.
>
> Is there some middle ground that turns the mouse from "look at it
> sideways and it starts scrolling" to something slightly more
> reasonable?
On Sun, Oct 28 2018, Jiri Kosina wrote:
> On Sat, 27 Oct 2018, tim.b...@sony.com wrote:
>
>> Al,
>>
>> Can you please, even in the face of comments you find irritating, keep
>> your responses more civil? Calling someone a "wankstain" is
>> unprofessional
>
> Tim,
>
> to be completely honest,
Hello,
When mounting a broken XFS image, the kernel hangs and floods dmesg
with stack traces.
How to reproduce with kvm-xfstests:
1) Checkout v4.19, copy x86_64-config-4.14 to .config, `make
olddefconfig` and compile
2) Unpack the attached image (128 Mb uncompressed) to /tmp/kvm-xfstests-$USER
On Fri, 26 Oct 2018 18:14:37 +
Carlos Iglesias wrote:
> Add device driver for the HSC pressure sensors with SPI interface.
> In addition to the main measurement -pressure- these sensors also
> provide temperature measurement.
>
> Signed-off-by: Carlos Iglesias
Hi Carlos,
A few minor
On Sun, 28 Oct 2018 12:10:17 -0600
Shuah Khan wrote:
> Here it is
>
> Acked-by: Shuah Khan
>
Thanks a lot Shuah!
-- Steve
So I use a Logitech MX Anywhere 2S mouse, and really like it. I have
the scroll-wheel unlocked, because I like flicking once to scroll a
lot.
However, the new high-res scroll code means that the scroll wheel
action is now much too sensitive. It's not even stable - it will
scroll back-and-forth a
On Sun, Oct 28, 2018 at 11:50:19AM -0700, Linus Torvalds wrote:
> On Tue, Oct 23, 2018 at 1:08 PM Matthew Wilcox wrote:
> <
> > Please consider pulling the XArray patch set.
>
> Pulled.
Thanks!
> I took the more recent version of yours, because by the time I
> actually had time to review this
make[1]: Entering directory '/usr/src/linux-4.19'
CC [M] /tmp/rtl8812AU_8821AU_linux/os_dep/linux/os_intfs.o
/tmp/rtl8812AU_8821AU_linux/os_dep/linux/os_intfs.c:816:22: error:
initialization of ‘u16 (*)(struct net_device *, struct sk_buff *,
struct net_device *, u16 (*)(struct net_device *,
On Sun, Oct 28, 2018 at 02:51:08PM +, Jonathan Cameron wrote:
> On Sun, 28 Oct 2018 13:23:23 +0530
> Nishad Kamdar wrote:
>
> > Replace platform data with device tree support.
> >
> > Signed-off-by: Nishad Kamdar
> The whole gpio in or out thing makes less and less sense to
> me and seems
We offer all types of loans at 2% interest rate contact us at
gylesloan...@gmail.com
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
> Nicolas Saenz Julienne hat am 26. Oktober 2018 um
> 15:48 geschrieben:
>
>
> Some operations performed in the probe function should have been
> implemented in the init function. Namely class and dev region creations.
>
Please explain the why in the commit log
On Fri, Oct 26 2018, Jeff Layton wrote:
> On Wed, 2018-10-24 at 09:43 +1100, NeilBrown wrote:
>> This took longer that I had wanted, due to various reasons - sorry.
>> And I'm now posting it in a merge window, which is not ideal. I don't
>> expect it to be included in this merge window and I
On Tue, Oct 23, 2018 at 1:08 PM Matthew Wilcox wrote:
<
> Please consider pulling the XArray patch set.
Pulled.
I took the more recent version of yours, because by the time I
actually had time to review this thing for pulling, even the recent
version had been in linux-next for a week.
Of
Hi Nicolas,
> Nicolas Saenz Julienne hat am 26. Oktober 2018 um
> 15:48 geschrieben:
>
>
> vchiq_init_state() initialises a series of semaphores to then call
> remote_event_create() on the same semaphores, which initializes them
> again.
i would prefer to have all init stuff at one place in
> Nicolas Saenz Julienne hat am 26. Oktober 2018 um
> 15:48 geschrieben:
>
>
> We update sync to reflect that the firmware version is compatible with
> that option. We don't need to check both of them again further down the
> code.
please fix the typo in the subject s/stagning/staging/ for
Arnd,
I was kind of hoping/expecting to get an explicit ack for this from
you, since it's a new architecture.
Good to merge?
Linus
On Fri, Oct 26, 2018 at 9:08 PM Guo Ren wrote:
>
> This tag contains the Linux port for C-SKY(csky) based on linux-4.19
> Release, which has been
> Nicolas Saenz Julienne hat am 26. Oktober 2018 um
> 15:48 geschrieben:
>
>
> The more the better.
Please try to find a better commit log ;-)
>
> Signed-off-by: Nicolas Saenz Julienne
> ---
> .../staging/vc04_services/interface/vchi/TODO | 46 ++-
> 1 file changed, 44
UBIFS's recovery code strictly assumes that a deleted inode will never
come back, therefore it removes all data which belongs to that inode
as soon it faces an inode with link count 0 in the replay list.
Before O_TMPFILE this assumption was perfectly fine. With O_TMPFILE
it can lead to data loss
On Mon, 22 Oct 2018, Zi Yan wrote:
> Hi David,
>
Hi!
> On 22 Oct 2018, at 17:04, David Rientjes wrote:
>
> > On Tue, 16 Oct 2018, Mel Gorman wrote:
> >
> > > I consider this to be an unfortunate outcome. On the one hand, we have a
> > > problem that three people can trivially reproduce with
On Fri, Oct 19, 2018 at 09:59:57AM +0100, Charles Keepax wrote:
> irq_create_mapping calls irq_find_mapping internally and will use the
> found mapping if one exists, so there is no need to manually call this
> from i2c_smbus_host_notify_to_irq.
>
> Signed-off-by: Charles Keepax
Adding Benjamin
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in:
drivers/soc/qcom/Kconfig
between commit:
a978a5b8d83f ("net/kconfig: Make QCOM_QMI_HELPERS available when
COMPILE_TEST")
from Linus' tree and commit:
ccfb464cd106 ("soc: qcom: Allow COMPILE_TEST of qcom SoC
Hopefully, with Paul's proper email address this time,
Andrea
On Mon, Oct 29, 2018 at 12:06:27AM +0100, Andrea Parri wrote:
> Hi,
>
> memory-barriers.txt says:
>
> [on "store tearing"]
>
> "In fact, a recent bug (since fixed) caused GCC to incorrectly use
>this optimization in a
Hi Linus,
Thanks! Its hopefully fixed now.
For those who are interested. Rspamd, by default, includes the sender
address into the list of signed headers:
https://www.rspamd.com/doc/modules/dkim_signing.html#default-sign_headers-after-173
> End result: the DKIM signature is guaranteed to fail
On Sat, Oct 27, 2018 at 09:44:31PM -0700, Joel Fernandes wrote:
> On Sat, Oct 27, 2018 at 7:16 PM, Joel Fernandes (Google)
> wrote:
> > The RCU example for 'rejecting stale data' on system-call auditting
> > stops iterating through the rules if a deleted one is found. It makes
> > more sense to
On Sun, Oct 28, 2018 at 12:21:19PM -0700, Linus Torvalds wrote:
> On Sun, Oct 28, 2018 at 12:13 PM Matthew Wilcox wrote:
> >
> > On Sun, Oct 28, 2018 at 11:50:19AM -0700, Linus Torvalds wrote:
> >
> > > NOTE! I did get some conflicts with other stuff, and while the
> > > conflict resolution all
On 10/28/18 3:13 PM, Greg Kroah-Hartman wrote:
On Sun, Oct 28, 2018 at 02:22:40PM +0100, Michael Straube wrote:
On 10/28/18 12:27 PM, Greg Kroah-Hartman wrote:
On Sun, Oct 28, 2018 at 11:04:06AM +0100, Michael Straube wrote:
Hi,
which GPL version should be used in SPDX Identifiers for files
We offer all types of loans at 2% interest rate contact us at
gylesloan...@gmail.com
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
> Nicolas Saenz Julienne hat am 26. Oktober 2018 um
> 15:48 geschrieben:
>
>
> It is preferred in the kernel to avoid using semaphores to wait for
> events, as they are optimised for the opposite situation; where the
> common case is that they are available and may block only occasionally.
>
Are you searching for a Genuine Loan? At an affordable interest rate? Get back
to us with your Name and Phone Number
Best Regards,
Emrah Global Loan
On Tue, Oct 16, 2018 at 12:01:49PM +0900, Masahiro Yamada wrote:
> The current IRQ handler clears all the IRQ status bits when it bails
> out. This is dangerous because it might clear away the status bits
> that have just been set while processing the current handler. If this
> happens, the IRQ
On Tue, Oct 16, 2018 at 12:01:48PM +0900, Masahiro Yamada wrote:
> Currently, a timeout error could happen at a repeated START condition.
>
> For a (non-repeated) START condition, the controller starts sending
> data when the UNIPHIER_FI2C_CR_STA bit is set. However, for a repeated
> START
On Tue, Oct 16, 2018 at 12:01:47PM +0900, Masahiro Yamada wrote:
> This is unlikely to happen, but it is possible for a CPU to enter
> the interrupt handler just after wait_for_completion_timeout() has
> expired. If this happens, the hardware is accessed from multiple
> contexts concurrently.
>
>
On Fri, Oct 19, 2018 at 09:59:58AM +0100, Charles Keepax wrote:
> The IRQ will be mapped in i2c_device_probe only if client->irq is zero and
> i2c_device_remove does not clear this. When rebinding an I2C device,
> whos IRQ provider has also been rebound this means that an IRQ mapping
> will never
On 10/28/2018 02:09 AM, Steven Rostedt wrote:
> On Sun, 28 Oct 2018 04:01:35 -0400
> Steven Rostedt wrote:
>
>> I'll add them on top of my linux-next code, and include them in the
>> pull request I'm hoping to do on Tuesday.
>
> Bah, I think this is on a different branch, and that will make it
On Sun, 28 Oct 2018 13:09:42 +
Changbin Du wrote:
> The level4_kernel_pgt is only defined when X86_5LEVEL is enabled.
> So declare check_la57_support() as inline to make sure the code
> referring to level4_kernel_pgt is optimized out. This is a preparation
> for
On Thu, 2018-10-25 at 22:58 +0200, Martin Blumenstingl wrote:
> Hi Jerome,
>
> On Thu, Oct 25, 2018 at 2:54 PM Jerome Brunet wrote:
> [snip]
> > > > > +static void clk_regmap_div_init(struct clk_hw *hw)
> > > > > +{
> > > > > + struct clk_regmap *clk = to_clk_regmap(hw);
> > > > > + struct
On Sun, Oct 28, 2018 at 4:16 AM Adam Borowski wrote:
>
> Amen to that. But, perhaps you could encourage people to do enable drivers
> once they become very popular? For example, I just (72a9c673636) got hit by
> USB 3.0 being off in defconfigs, and not having keyboard is not that cool.
Yes,
On Sun, Oct 28, 2018 at 10:12 AM Masahiro Yamada
wrote:
>
> Please pull Kbuild updates for v4.20
Pulled,
Linus
On Sun, Oct 28, 2018 at 02:36:07PM +, Jonathan Cameron wrote:
> On Sun, 28 Oct 2018 13:21:25 +0530
> Nishad Kamdar wrote:
>
> > Use the gpiod interface instead of the deprecated old non-descriptor
> > interface.
> >
> > Signed-off-by: Nishad Kamdar
> Hi Nishad,
>
> Sorry it took me most
On Sat, Oct 27, 2018 at 01:09:44PM -0700, Vinicius Costa Gomes wrote:
> Hi Jirka,
>
> Jiri Olsa writes:
>
> > On Fri, Oct 26, 2018 at 04:19:52PM -0700, Vinicius Costa Gomes wrote:
> >> Hi,
> >>
> >> Adrian Hunter writes:
> >>
> >> > On 18/10/18 1:55 AM, Arnaldo Carvalho de Melo wrote:
> >>
[ This is not about your patch series per se, only about your email settings ]
On Sun, Oct 28, 2018 at 3:20 PM Steffen Vogel wrote:
>
> This is my first series of patches for the Linux kernel.
> I started by familiarizing myself with coding style and
> satisfying my inner OCD by cleaning the
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
net/sunrpc/svcsock.c
between commit:
64dbf4dc5496 ("SUNRPC: Simplify TCP receive code")
from the nfsd tree and commit:
aa563d7bca6e ("iov_iter: Separate type from direction and use accessor
functions")
from the vfs
On Mon, Oct 29, 2018 at 12:10:03AM +0100, Andrea Parri wrote:
> Hopefully, with Paul's proper email address this time,
>
> Andrea
>
> On Mon, Oct 29, 2018 at 12:06:27AM +0100, Andrea Parri wrote:
> > Hi,
> >
> > memory-barriers.txt says:
> >
> > [on "store tearing"]
> >
> > "In fact, a
> The "possible alignement issues" in CHECK report is difficult to figure
> out by just doing a glance analysis. :)
>
> Linus also suggested to use bool as the base type i.e., `bool x:1` but
> again sizeof(_Bool) is implementation defined ranging from 1-4 bytes.
If bool x:1 has the size of bool,
Hi,
which GPL version should be used in SPDX Identifiers for files that
are GPL licensed but do not mention any version? It is not clear to
me after reading license-rules.rst.
For example:
/**
* Copyright(c) 2008 -
On Sun, Oct 28, 2018 at 02:13:26PM +0800, Gao Xiang wrote:
> It's a trivial simplification for get_next_ra_size and
> clear enough for humans to understand.
>
> It also fixes potential overflow if ra->size(< ra_pages) is too large.
>
> Cc: Fengguang Wu
> Signed-off-by: Gao Xiang
Reviewed-by:
Hi,
On 28-10-18 05:13, Diego Viola wrote:
On Fri, Oct 26, 2018 at 5:36 PM Diego Viola wrote:
On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe wrote:
On 10/26/18 7:45 AM, Diego Viola wrote:
med_power_with_dipm causes my T450 to freeze with a SAMSUNG
MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
On Sun, Oct 28, 2018 at 11:04:06AM +0100, Michael Straube wrote:
> Hi,
>
> which GPL version should be used in SPDX Identifiers for files that
> are GPL licensed but do not mention any version? It is not clear to
> me after reading license-rules.rst.
>
> For example:
>
>
On Sat, 27 Oct 2018 22:44:28 +0530
Himanshu Jha wrote:
> Hi Dan,
>
> On Thu, Oct 25, 2018 at 04:35:41PM +0100, Dan O'Donovan wrote:
> > From: Nicola Lunghi
> >
> > ACPI _HID AANT1280 matches an ADC124S101 present on E3940 SKUs of the UP
> > Squared board.
> >
> > Add it to the driver.
> >
>
On 10/26/18 6:37 PM, Lucas Stach wrote:
> Am Freitag, den 26.10.2018, 15:03 +0300 schrieb Dmitry Osipenko:
> [...]
>>> On the other hand, the tegra20 cpufreq driver is common across a lot of
>>> boards.
>>> What will happen if the DT for some of the boards isn't correct and missed
>>> the
>>>
> On 25 Oct 2018, at 08:37, Takashi Iwai wrote:
>
> On Thu, 25 Oct 2018 00:02:34 +0200,
> Kirill Marinushkin wrote:
>>
When you play sound - the pointer increments.
>>>
>>> Unfortunately, when you play sound, the pointer does not actually
>>> increment, for up to about 10
Hi Kirill. Thanks for the post.
Mike
> On 25 Oct 2018, at 18:20, Kirill Marinushkin wrote:
>
> Hello Takashi, Mike,
>
> @Takashi
>
> On 10/25/18 09:37, Takashi Iwai wrote:
>> Well, in the API POV, it's nothing wrong to keep hwptr sticking while
>> updating only delay value. It implies that
On Sun, 28 Oct 2018 13:23:23 +0530
Nishad Kamdar wrote:
> Replace platform data with device tree support.
>
> Signed-off-by: Nishad Kamdar
The whole gpio in or out thing makes less and less sense to
me and seems to contradict the datasheet.
If I'm not missing something I would just get rid of
On Sat, Oct 27, 2018 at 2:08 PM, Peng15 Wang 王鹏 wrote:
> When initialing prz with invalid data in buffer(no PERSISTENT_RAM_SIG),
> function call path is like this:
>
> ramoops_init_prz ->
> |
> |-> persistent_ram_new -> persistent_ram_post_init -> persistent_ram_zap
> |
> |-> persistent_ram_zap
>
Below is the list of build error/warning regressions/improvements in
v4.19[1] compared to v4.18[2].
Summarized:
- build errors: +5/-3
- build warnings: +14715/-247
JFYI, when comparing v4.19[1] to v4.19-rc8[3], the summaries are:
- build errors: +0/-0
- build warnings: +158/-166
Note
Use the gpiod interface instead of the deprecated old non-descriptor
Changes in v6:
- Split device tree table addition and device tree support
addition in two patches.
- Replace platform data with device tree support.
- Rename boolean property.
Changes in v5:
- Add device tree support.
-
Use the gpiod interface instead of the deprecated old non-descriptor
interface.
Signed-off-by: Nishad Kamdar
---
drivers/staging/iio/resolver/ad2s1210.c | 92 ++---
drivers/staging/iio/resolver/ad2s1210.h | 3 -
2 files changed, 50 insertions(+), 45 deletions(-)
diff --git
On Sun, Oct 28, 2018 at 09:47:15AM +0100, Julia Lawall wrote:
> > The "possible alignement issues" in CHECK report is difficult to figure
> > out by just doing a glance analysis. :)
> >
> > Linus also suggested to use bool as the base type i.e., `bool x:1` but
> > again sizeof(_Bool) is
1 - 100 of 520 matches
Mail list logo
