Hi,
I was looking through tip Git tree...
Why didn't you use...
+ IS_ENABLED(CONFIG_DEBUG_PAGEALLOC) ? " DEBUG_PAGEALLOC" : "",
...instead of...
+ debug_pagealloc_enabled() ? " DEBUG_PAGEALLOC" : "",
...for consistency reasons?
Regards,
- Sedat -
[1]
Hi,
I was looking through tip Git tree...
Why didn't you use...
+ IS_ENABLED(CONFIG_DEBUG_PAGEALLOC) ? " DEBUG_PAGEALLOC" : "",
...instead of...
+ debug_pagealloc_enabled() ? " DEBUG_PAGEALLOC" : "",
...for consistency reasons?
Regards,
- Sedat -
[1]
On Sat, 02 Apr 2016 00:28:31 +0200,
Luis R. Rodriguez wrote:
>
> On Fri, Apr 01, 2016 at 07:34:10AM +0200, Takashi Iwai wrote:
> > On Fri, 01 Apr 2016 00:26:18 +0200,
> > Luis R. Rodriguez wrote:
> > >
> > > On Wed, Mar 30, 2016 at 08:07:04AM +0200, Takashi Iwai wrote:
> > > > On Tue, 29 Mar
On Sat, 02 Apr 2016 00:28:31 +0200,
Luis R. Rodriguez wrote:
>
> On Fri, Apr 01, 2016 at 07:34:10AM +0200, Takashi Iwai wrote:
> > On Fri, 01 Apr 2016 00:26:18 +0200,
> > Luis R. Rodriguez wrote:
> > >
> > > On Wed, Mar 30, 2016 at 08:07:04AM +0200, Takashi Iwai wrote:
> > > > On Tue, 29 Mar
Thanks for the comments.
Re: is this a useful semantic?
Yes, average MHz over an interval is significantly more useful than
a snapshot of the recent instantaneous frequency.
It is possible to convert the former into the later,
but it is not possible to reliably and efficiently convert the later
Thanks for the comments.
Re: is this a useful semantic?
Yes, average MHz over an interval is significantly more useful than
a snapshot of the recent instantaneous frequency.
It is possible to convert the former into the later,
but it is not possible to reliably and efficiently convert the later
2016-03-29 11:33 GMT+09:00 Masahiro Yamada :
> Commit 271707b1d817 ("mtd: nand: denali: max_banks calculation
> changed in revision 5.1") supported the new encoding of the "n_banks"
> bits of the "features" register, but there is an unfortunate case
> not covered by
2016-03-29 11:33 GMT+09:00 Masahiro Yamada :
> Commit 271707b1d817 ("mtd: nand: denali: max_banks calculation
> changed in revision 5.1") supported the new encoding of the "n_banks"
> bits of the "features" register, but there is an unfortunate case
> not covered by that commit.
>
> Panasonic (its
Hi Boris,
2016-03-29 16:53 GMT+09:00 Boris Brezillon :
> Hi,
>
> I'm answering to this one, but I already saw your v2.
>
> On Sat, 26 Mar 2016 13:27:50 +0900
> Masahiro Yamada wrote:
>
>> 2016-03-25 23:45 GMT+09:00 Boris
Hi Boris,
2016-03-29 16:53 GMT+09:00 Boris Brezillon :
> Hi,
>
> I'm answering to this one, but I already saw your v2.
>
> On Sat, 26 Mar 2016 13:27:50 +0900
> Masahiro Yamada wrote:
>
>> 2016-03-25 23:45 GMT+09:00 Boris Brezillon
>> :
>> > On Thu, 24 Mar 2016 21:24:37 +0900
>> > Masahiro
We should be testing for -ENOMEM but the minus sign is missing.
Fixes: c9af28fdd449 ('ext4 crypto: don't let data integrity writebacks fail
with ENOMEM')
Signed-off-by: Dan Carpenter
diff --git a/fs/ext4/page-io.c b/fs/ext4/page-io.c
index 51b3492..b39d9c7 100644
---
We should be testing for -ENOMEM but the minus sign is missing.
Fixes: c9af28fdd449 ('ext4 crypto: don't let data integrity writebacks fail
with ENOMEM')
Signed-off-by: Dan Carpenter
diff --git a/fs/ext4/page-io.c b/fs/ext4/page-io.c
index 51b3492..b39d9c7 100644
--- a/fs/ext4/page-io.c
+++
On Fri, 01 Apr 2016, Michal Hocko wrote:
From: Michal Hocko
Introduce a generic implementation necessary for down_write_killable.
This is a trivial extension of the already existing down_write call
which can be interrupted by SIGKILL. This patch doesn't provide
On Fri, 01 Apr 2016, Michal Hocko wrote:
From: Michal Hocko
Introduce a generic implementation necessary for down_write_killable.
This is a trivial extension of the already existing down_write call
which can be interrupted by SIGKILL. This patch doesn't provide
down_write_killable yet
Hi Emese,
Sorry for my late reply.
> Thanks for the patch. I tested it and there is a problem when I run a
> parallel make.
> The plugins are compiled later than needed (e.g., scripts/mod/empty.o). There
> is a lot of important
> code under scripts/mod which may need the plugins.
Ah, I
Hi Emese,
Sorry for my late reply.
> Thanks for the patch. I tested it and there is a problem when I run a
> parallel make.
> The plugins are compiled later than needed (e.g., scripts/mod/empty.o). There
> is a lot of important
> code under scripts/mod which may need the plugins.
Ah, I
Hi,
On Thu, Mar 31, 2016 at 10:42:31AM +0800, YH Huang wrote:
> On Wed, 2016-03-30 at 17:09 +0200, Sebastian Reichel wrote:
> > Hi,
> >
> > On Wed, Mar 30, 2016 at 04:58:30PM +0800, YH Huang wrote:
> > > If I revise the description in this way(using your clear explanation):
> > >
Hi,
On Thu, Mar 31, 2016 at 10:42:31AM +0800, YH Huang wrote:
> On Wed, 2016-03-30 at 17:09 +0200, Sebastian Reichel wrote:
> > Hi,
> >
> > On Wed, Mar 30, 2016 at 04:58:30PM +0800, YH Huang wrote:
> > > If I revise the description in this way(using your clear explanation):
> > >
On Thu, Mar 31, 2016 at 09:37:56AM +0300, Jarkko Sakkinen wrote:
> On Wed, Mar 30, 2016 at 11:46:23PM -0600, Jason Gunthorpe wrote:
> > On Wed, Mar 30, 2016 at 04:20:45PM +0300, Jarkko Sakkinen wrote:
> >
> > > - rc = be32_to_cpu(cmd.header.out.return_code);
> > > if (rc ==
On Thu, Mar 31, 2016 at 09:37:56AM +0300, Jarkko Sakkinen wrote:
> On Wed, Mar 30, 2016 at 11:46:23PM -0600, Jason Gunthorpe wrote:
> > On Wed, Mar 30, 2016 at 04:20:45PM +0300, Jarkko Sakkinen wrote:
> >
> > > - rc = be32_to_cpu(cmd.header.out.return_code);
> > > if (rc ==
On Fri, 2016-04-01 at 23:11 +0200, Sebastian Andrzej Siewior wrote:
> * Mike Galbraith | 2016-03-31 08:31:43 [+0200]:
>
> > 3. nuke irksome grab_lock: make everybody always try to get the hell
> > outta Dodge or hotplug can bloody well wait.
> >
> > I haven't yet flogged my 64 core box doing
On Fri, 2016-04-01 at 23:11 +0200, Sebastian Andrzej Siewior wrote:
> * Mike Galbraith | 2016-03-31 08:31:43 [+0200]:
>
> > 3. nuke irksome grab_lock: make everybody always try to get the hell
> > outta Dodge or hotplug can bloody well wait.
> >
> > I haven't yet flogged my 64 core box doing
When performing direct I/O, the current ext4 code does
not pass in the DIO_SKIP_DIO_COUNT flag to dax_do_io() or
__blockdev_direct_IO() when inode_dio_begin() has, in fact, been
called. This causes dax_do_io()/__blockdev_direct_IO() to invoke
inode_dio_begin()/inode_dio_end() internally. This
When performing direct I/O, the current ext4 code does
not pass in the DIO_SKIP_DIO_COUNT flag to dax_do_io() or
__blockdev_direct_IO() when inode_dio_begin() has, in fact, been
called. This causes dax_do_io()/__blockdev_direct_IO() to invoke
inode_dio_begin()/inode_dio_end() internally. This
This patchset aims to improve parallel I/O performance of the ext4
filesystem on fast storage devices like NVDIMM.
Patch 1 eliminates duplicated inode_dio_begin()/inode_dio_end() calls.
Patch 2 provides a set of simple percpu statistics count helper functions.
Patch 3 converts some ext4
This patchset aims to improve parallel I/O performance of the ext4
filesystem on fast storage devices like NVDIMM.
Patch 1 eliminates duplicated inode_dio_begin()/inode_dio_end() calls.
Patch 2 provides a set of simple percpu statistics count helper functions.
Patch 3 converts some ext4
This patch introduces a set of simple per-cpu statictics count helper
functions that can be used by other kernel subsystems for keeping
track of the number of events that happens. It is per-cpu based to
reduce overhead and improve accuracy of the counter. Using per-cpu
counter is usually overkill
This patch changes the es_stats_cache_hits and es_stats_cache_misses
statistics counts to per-cpu variables to reduce cacheline contention
issues whem multiple threads are trying to update those counts
simultaneously. It uses the new per-cpu stats APIs provided by the
percpu_stats.h header file.
This patch introduces a set of simple per-cpu statictics count helper
functions that can be used by other kernel subsystems for keeping
track of the number of events that happens. It is per-cpu based to
reduce overhead and improve accuracy of the counter. Using per-cpu
counter is usually overkill
This patch changes the es_stats_cache_hits and es_stats_cache_misses
statistics counts to per-cpu variables to reduce cacheline contention
issues whem multiple threads are trying to update those counts
simultaneously. It uses the new per-cpu stats APIs provided by the
percpu_stats.h header file.
Hi,
Sorry for digging up an old patch, but... ;-)
dev_disable_lro() is a leftover from ancient times. If you read commit
27660515a,
there is a hint where it should go. Please, read on if you'd like to
fix this properly.
2015-11-03 3:55 GMT+01:00 Jarod Wilson :
> There are some
Hi,
Sorry for digging up an old patch, but... ;-)
dev_disable_lro() is a leftover from ancient times. If you read commit
27660515a,
there is a hint where it should go. Please, read on if you'd like to
fix this properly.
2015-11-03 3:55 GMT+01:00 Jarod Wilson :
> There are some netdev features,
On Fri, Apr 01, 2016 at 05:21:31PM +0800, Lijun Ou wrote:
> The driver for HiSilicon RoCE is a platform driver.
> The driver will support multiple versions of hardware. Currently only "v1"
> for hip06 SoC is supported.
> The driver includes two parts: common driver and hardware-specific
>
On Fri, Apr 01, 2016 at 05:21:31PM +0800, Lijun Ou wrote:
> The driver for HiSilicon RoCE is a platform driver.
> The driver will support multiple versions of hardware. Currently only "v1"
> for hip06 SoC is supported.
> The driver includes two parts: common driver and hardware-specific
>
On 30/03/2016 1:14 AM, Boris Ostrovsky wrote:
> On 03/29/2016 04:56 AM, Steven Haigh wrote:
>>
>> Interestingly enough, this just happened again - but on a different
>> virtual machine. I'm starting to wonder if this may have something to do
>> with the uptime of the machine - as the system that
On 30/03/2016 1:14 AM, Boris Ostrovsky wrote:
> On 03/29/2016 04:56 AM, Steven Haigh wrote:
>>
>> Interestingly enough, this just happened again - but on a different
>> virtual machine. I'm starting to wonder if this may have something to do
>> with the uptime of the machine - as the system that
On Fri, Apr 01, 2016 at 11:34:10PM +0200, Johannes Berg wrote:
>
> I was thinking about that one - it's not obvious to me from the code
> how this "explicitly checking for dups" would be done or let's say how
> rhashtable differentiates. But since it seems to work for Ben until
> hitting a certain
On Fri, Apr 01, 2016 at 11:34:10PM +0200, Johannes Berg wrote:
>
> I was thinking about that one - it's not obvious to me from the code
> how this "explicitly checking for dups" would be done or let's say how
> rhashtable differentiates. But since it seems to work for Ben until
> hitting a certain
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit f1d84af1835846a5a2b827382c5848faf2bb0e75 upstream.
This patch removes the custom
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit f1d84af1835846a5a2b827382c5848faf2bb0e75 upstream.
This patch removes the custom release parent function as the
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit a0fa2d037129a9849918a92d91b79ed6c7bd2818 upstream.
This patch adds a compatibility path
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit a1383cd86a062fc798899ab20f0ec2116cce39cb upstream.
This patch adds a way for skcipher
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit a0fa2d037129a9849918a92d91b79ed6c7bd2818 upstream.
This patch adds a compatibility path to support old applications
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit a1383cd86a062fc798899ab20f0ec2116cce39cb upstream.
This patch adds a way for skcipher users to determine whether a
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit ad46d7e33219218605ea619e32553daf4f346b9f upstream.
We need to lock the child socket in
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit ad46d7e33219218605ea619e32553daf4f346b9f upstream.
We need to lock the child socket in hash_check_key as otherwise
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 6e8d8ecf438792ecf7a3207488fb4eebc4edb040 upstream.
This patch adds an exception to the
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 6de62f15b581f920ade22d758f4c338311c2f0d4 upstream.
Hash implementations that require a
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 6e8d8ecf438792ecf7a3207488fb4eebc4edb040 upstream.
This patch adds an exception to the key check so that cipher_null
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 6de62f15b581f920ade22d758f4c338311c2f0d4 upstream.
Hash implementations that require a key may crash if you use
them
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Josh Boyer
commit 4ec0ef3a82125efc36173062a50624550a900ae0 upstream.
The iowarrior driver expects at least
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Josh Boyer
commit 4ec0ef3a82125efc36173062a50624550a900ae0 upstream.
The iowarrior driver expects at least one valid endpoint. If
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit 0f886ca12765d20124bd06291c82951fd49a33be upstream.
create_fixed_stream_quirk() may cause a
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 1822793a523e5d5730b19cc21160ff1717421bc8 upstream.
We need to lock the child socket in
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit 0f886ca12765d20124bd06291c82951fd49a33be upstream.
create_fixed_stream_quirk() may cause a NULL-pointer
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 1822793a523e5d5730b19cc21160ff1717421bc8 upstream.
We need to lock the child socket in skcipher_check_key as
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oliver Neukum
commit 8835ba4a39cf53f705417b3b3a94eb067673f2c9 upstream.
An attack has become available which
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit 447d6275f0c21f6cc97a88b3a0c601436a4cdf2a upstream.
Add some sanity check codes before actually
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vasily Kulikov
commit 8a5e5e02fc83aaf67053ab53b359af08c6c49aaf upstream.
Poison pointer values should be small
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oliver Neukum
commit 8835ba4a39cf53f705417b3b3a94eb067673f2c9 upstream.
An attack has become available which pretends to be a quirky
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit 447d6275f0c21f6cc97a88b3a0c601436a4cdf2a upstream.
Add some sanity check codes before actually accessing the
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vasily Kulikov
commit 8a5e5e02fc83aaf67053ab53b359af08c6c49aaf upstream.
Poison pointer values should be small enough to find a room
On 03/31, Lars Persson wrote:
> diff --git a/drivers/clk/axis/Makefile b/drivers/clk/axis/Makefile
> new file mode 100644
> index 000..628c9d3
> --- /dev/null
> +++ b/drivers/clk/axis/Makefile
> @@ -0,0 +1 @@
> +obj-$(CONFIG_MACH_ARTPEC6) += clk-artpec6.o
> diff --git
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "Paul E. McKenney"
commit 00df35f991914db6b8bde8cf09808e19a9cffc3d upstream.
Currently,
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit d7b65aee1e7b4c87922b0232eaba56a8a143a4a0 upstream.
This patch removes the custom
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "Paul E. McKenney"
commit 00df35f991914db6b8bde8cf09808e19a9cffc3d upstream.
Currently, smpboot_unpark_threads() is invoked before the
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit d7b65aee1e7b4c87922b0232eaba56a8a143a4a0 upstream.
This patch removes the custom release parent function as the
On 03/31, Lars Persson wrote:
> diff --git a/drivers/clk/axis/Makefile b/drivers/clk/axis/Makefile
> new file mode 100644
> index 000..628c9d3
> --- /dev/null
> +++ b/drivers/clk/axis/Makefile
> @@ -0,0 +1 @@
> +obj-$(CONFIG_MACH_ARTPEC6) += clk-artpec6.o
> diff --git
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tom Lendacky
commit 952bce9792e6bf36fda09c2e5718abb5d9327369 upstream.
Commit 8996eafdcbad ("crypto: ahash -
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tom Lendacky
commit 952bce9792e6bf36fda09c2e5718abb5d9327369 upstream.
Commit 8996eafdcbad ("crypto: ahash - ensure statesize is
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Dan Carpenter
commit 6f3508f61c814ee852c199988a62bd954c50dfc1 upstream.
dct_sel_base_off is declared as a
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Hans de Goede
commit 7445e45d19a09e5269dc85f17f9635be29d2f76c upstream.
SPC 880NC PC camera discussions:
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tiffany Lin
commit 7df5ab8774aa383c6d2bff00688d004585d96dfd upstream.
In v4l2-compliance utility, test
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Peter Hurley
commit f33798deecbd59a2955f40ac0ae2bc7dff54c069 upstream.
commit 9ce119f318ba ("tty: Fix GPF in
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Dan Carpenter
commit 6f3508f61c814ee852c199988a62bd954c50dfc1 upstream.
dct_sel_base_off is declared as a u64 but we're only using the
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Hans de Goede
commit 7445e45d19a09e5269dc85f17f9635be29d2f76c upstream.
SPC 880NC PC camera discussions:
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tiffany Lin
commit 7df5ab8774aa383c6d2bff00688d004585d96dfd upstream.
In v4l2-compliance utility, test QUERYBUF required correct
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Peter Hurley
commit f33798deecbd59a2955f40ac0ae2bc7dff54c069 upstream.
commit 9ce119f318ba ("tty: Fix GPF in flush_to_ldisc()") fixed
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tom Lendacky
commit d1662165ae612ec8b5f94a6b07e65ea58b6dce34 upstream.
Since the exported information can be
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tom Lendacky
commit d1662165ae612ec8b5f94a6b07e65ea58b6dce34 upstream.
Since the exported information can be exposed to user-space,
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ingo Molnar
commit 590ee7dbd569a012df705a5204fc5f1066f52b8c upstream.
Now that we are using smpboot_thread_init() in
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "Spencer E. Olson"
commit 1fd24a4702d2af0ea4d5845126cf57d4d1796216 upstream.
This fixes a bug in function
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "Spencer E. Olson"
commit 1fd24a4702d2af0ea4d5845126cf57d4d1796216 upstream.
This fixes a bug in function ni_tio_input_inttrig(). The
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ingo Molnar
commit 590ee7dbd569a012df705a5204fc5f1066f52b8c upstream.
Now that we are using smpboot_thread_init() in init/main.c as
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Lior Amsalem
commit b3a7f31eb7375633cd6a742f19488fc5a4208b36 upstream.
The Armada 375 has the same SATA IP as
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tom Lendacky
commit b31dde2a5cb1bf764282abf934266b7193c2bc7c upstream.
Use a local variable for the exported
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Benjamin Tissoires
commit 4392bf88cabdad5afe5b152d7b9c318e upstream.
hid_ignore_special_drivers
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Peter Hurley
commit 401879c57f01cbf2da204ad2e8db910525c6dbea upstream.
The N_IRDA line discipline may access
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Sebastian Frias
commit 0b41ce991052022c030fd868e03877700220b090 upstream.
Some UART HW has a single register
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tom Lendacky
commit b31dde2a5cb1bf764282abf934266b7193c2bc7c upstream.
Use a local variable for the exported and imported state so
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Benjamin Tissoires
commit 4392bf88cabdad5afe5b152d7b9c318e upstream.
hid_ignore_special_drivers works fine until
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Peter Hurley
commit 401879c57f01cbf2da204ad2e8db910525c6dbea upstream.
The N_IRDA line discipline may access the previous line
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Sebastian Frias
commit 0b41ce991052022c030fd868e03877700220b090 upstream.
Some UART HW has a single register combining
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Lior Amsalem
commit b3a7f31eb7375633cd6a742f19488fc5a4208b36 upstream.
The Armada 375 has the same SATA IP as Armada 370 and Armada
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oliver Neukum
commit 264904ccc33c604d4b3141bbd33808152dfac45b upstream.
Some devices I got show an inability to
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kamal Mostafa
commit 50fe6dd10069e7c062e27f29606f6e91ea979399 upstream.
Use the local uapi headers to keep in
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oliver Neukum
commit 264904ccc33c604d4b3141bbd33808152dfac45b upstream.
Some devices I got show an inability to operate right after
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kamal Mostafa
commit 50fe6dd10069e7c062e27f29606f6e91ea979399 upstream.
Use the local uapi headers to keep in sync with "recently"
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andi Kleen
commit 940db6dcd3f4659303fdf6befe7416adc4d24118 upstream.
When an error happens during alias parsing
3.19.8-ckt18 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Hans de Goede
commit 3e71da19f9dc22e39a755d6ae9678661abb66adc upstream.
bytesperline should be the bytesperline
1 - 100 of 1798 matches
Mail list logo