> It's not as efficient as glimpse because the query language is simpler.
Interesting, what is missing compared to glimpse?
> So more filtering has to be done at the ocaml level. But it's probably
> fine in most cases.
For me, it has two advantages over glimpse:
a) it is in the debian
> It's not as efficient as glimpse because the query language is simpler.
Interesting, what is missing compared to glimpse?
> So more filtering has to be done at the ocaml level. But it's probably
> fine in most cases.
For me, it has two advantages over glimpse:
a) it is in the debian
This patch introduces a separate GPIO driver for Intel WhiskeyCove PMIC.
This driver is based on gpio-crystalcove.c.
Signed-off-by: Ajay Thomas
Signed-off-by: Bin Gao
---
drivers/gpio/Kconfig | 13 ++
drivers/gpio/Makefile
This patch introduces a separate GPIO driver for Intel WhiskeyCove PMIC.
This driver is based on gpio-crystalcove.c.
Signed-off-by: Ajay Thomas
Signed-off-by: Bin Gao
---
drivers/gpio/Kconfig | 13 ++
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-wcove.c | 402
On Sat, 11 Jun 2016, SF Markus Elfring wrote:
> > Also enable the load balancing to be dynamic, so that
> > if a thread finishes early we keep feeding it.
>
> Is this functionality influenced by the parameter "chunksize"?
Yes, without chunksize the distribution of work to processes is static.
On Sat, 11 Jun 2016, SF Markus Elfring wrote:
> > Also enable the load balancing to be dynamic, so that
> > if a thread finishes early we keep feeding it.
>
> Is this functionality influenced by the parameter "chunksize"?
Yes, without chunksize the distribution of work to processes is static.
> in practice though this seems to not perform better than
> regular grep however its expected to help with some use cases
> so we use that if you have no other indexing options in place
> available.
Would you like to fix a typo in this paragraph?
Regards,
Markus
> in practice though this seems to not perform better than
> regular grep however its expected to help with some use cases
> so we use that if you have no other indexing options in place
> available.
Would you like to fix a typo in this paragraph?
Regards,
Markus
On Sat, 11 Jun 2016, Wolfram Sang wrote:
>
> > real16m11.692s
> > user127m50.388s
> > sys 0m2.168s
>
> That's better but not a magnitude, I wonder.
I think that it is because the filtering that Coccinelle does already
works pretty well, and there are quite a lot of files (7514)
On Sat, 11 Jun 2016, Wolfram Sang wrote:
>
> > real16m11.692s
> > user127m50.388s
> > sys 0m2.168s
>
> That's better but not a magnitude, I wonder.
I think that it is because the filtering that Coccinelle does already
works pretty well, and there are quite a lot of files (7514)
From: Bhaktipriya Shridhar
Date: Wed, 8 Jun 2016 01:03:45 +0530
> alloc_workqueue replaces deprecated create_workqueue().
>
> Since the driver is infiniband which can be used as block device and the
> workqueue seems involved in regular operation of the device, so a
>
> Also enable the load balancing to be dynamic, so that
> if a thread finishes early we keep feeding it.
Is this functionality influenced by the parameter "chunksize"?
Regards,
Markus
From: Bhaktipriya Shridhar
Date: Wed, 8 Jun 2016 01:03:45 +0530
> alloc_workqueue replaces deprecated create_workqueue().
>
> Since the driver is infiniband which can be used as block device and the
> workqueue seems involved in regular operation of the device, so a
> dedicated workqueue has
> Also enable the load balancing to be dynamic, so that
> if a thread finishes early we keep feeding it.
Is this functionality influenced by the parameter "chunksize"?
Regards,
Markus
From: Mario Limonciello
Date: Tue, 7 Jun 2016 13:22:37 -0500
> The RTL8153-AD supports a persistent system specific MAC address.
> This means a device plugged into two different systems with host side
> support will show different (but persistent) MAC addresses.
>
>
From: Mario Limonciello
Date: Tue, 7 Jun 2016 13:22:37 -0500
> The RTL8153-AD supports a persistent system specific MAC address.
> This means a device plugged into two different systems with host side
> support will show different (but persistent) MAC addresses.
>
> This information for the
From: Ivan Khoronzhuk
Date: Tue, 7 Jun 2016 16:59:35 +0300
> if (!cpsw_common_res_usage_state(priv)) {
> + int buf_num;
> struct cpsw_priv *priv_sl0 = cpsw_get_slave_priv(priv, 0);
>
Please always order local variable declarations
From: Ivan Khoronzhuk
Date: Tue, 7 Jun 2016 16:59:35 +0300
> if (!cpsw_common_res_usage_state(priv)) {
> + int buf_num;
> struct cpsw_priv *priv_sl0 = cpsw_get_slave_priv(priv, 0);
>
Please always order local variable declarations from longest to shortest
From: "Naveen N. Rao"
Date: Tue, 7 Jun 2016 19:02:17 +0530
> Please note that patch [2] is a pre-requisite for this patchset, and is
> not yet upstream.
...
> [1] http://thread.gmane.org/gmane.linux.kernel/2188694
> [2]
From: "Naveen N. Rao"
Date: Tue, 7 Jun 2016 19:02:17 +0530
> Please note that patch [2] is a pre-requisite for this patchset, and is
> not yet upstream.
...
> [1] http://thread.gmane.org/gmane.linux.kernel/2188694
> [2] http://thread.gmane.org/gmane.linux.ports.ppc.embedded/96514
Because of
> real16m11.692s
> user127m50.388s
> sys 0m2.168s
That's better but not a magnitude, I wonder.
signature.asc
Description: PGP signature
> real16m11.692s
> user127m50.388s
> sys 0m2.168s
That's better but not a magnitude, I wonder.
signature.asc
Description: PGP signature
> we should be able to also take advantage of with coccicheck,
> the most important one is paramap support.
Do OCaml developers prefer to refer to the software "Parmap" here?
https://rdicosmo.github.io/parmap/
Regards,
Markus
> we should be able to also take advantage of with coccicheck,
> the most important one is paramap support.
Do OCaml developers prefer to refer to the software "Parmap" here?
https://rdicosmo.github.io/parmap/
Regards,
Markus
From: Bjorn Andersson
Support the two supplies - vdd and vio - to make it possible to control
power to the Synaptics chip.
Signed-off-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
---
On Fri, 10 Jun 2016, Wolfram Sang wrote:
> > AFAICT coccinelle does not have integration support for id-utils though.
>
> I used it just today ;) -- "--use-idutils ./ID"
>
> ID was generated with simple 'mkid -s'.
Coccinelle includes a script scripts/idutils_index.sh
This does mkid -i C
On Fri, 10 Jun 2016, Wolfram Sang wrote:
> > AFAICT coccinelle does not have integration support for id-utils though.
>
> I used it just today ;) -- "--use-idutils ./ID"
>
> ID was generated with simple 'mkid -s'.
Coccinelle includes a script scripts/idutils_index.sh
This does mkid -i C
From: Bjorn Andersson
Support the two supplies - vdd and vio - to make it possible to control
power to the Synaptics chip.
Signed-off-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
---
.../devicetree/bindings/input/rmi4/rmi_i2c.txt | 9 +
drivers/input/rmi4/rmi_i2c.c
Do you need a personal loan or a business loan? our offer is the best and
reliable offer for you. duration period: 1 to 25 years get your loan approved
within 3 days contact us now for more information:
internationalloan...@gmail.com
---
This email has been checked for viruses by Avast
Do you need a personal loan or a business loan? our offer is the best and
reliable offer for you. duration period: 1 to 25 years get your loan approved
within 3 days contact us now for more information:
internationalloan...@gmail.com
---
This email has been checked for viruses by Avast
On Sat, 11 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:51:26PM +0200, Wolfram Sang wrote:
> > > AFAICT coccinelle does not have integration support for id-utils though.
> >
> > I used it just today ;) -- "--use-idutils ./ID"
> >
> > ID was generated with simple 'mkid -s'.
On Sat, 11 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:51:26PM +0200, Wolfram Sang wrote:
> > > AFAICT coccinelle does not have integration support for id-utils though.
> >
> > I used it just today ;) -- "--use-idutils ./ID"
> >
> > ID was generated with simple 'mkid -s'.
On Fri, 10 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:43:57PM +0200, Wolfram Sang wrote:
> > > > Well, slightly better.
> > >
> > > No, it should be much better. You would have to look at the standard
> >
> > I use id-utils regularly and it is indeed at least a
On Fri, 10 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 10, 2016 at 11:43:57PM +0200, Wolfram Sang wrote:
> > > > Well, slightly better.
> > >
> > > No, it should be much better. You would have to look at the standard
> >
> > I use id-utils regularly and it is indeed at least a
From: Manfred Schlaegl
Date: Mon, 6 Jun 2016 10:47:47 +0200
> We detected some problems using the smsc lan8720a in combination with
> i.MX28 and tracked this down to commit 21009686662f ("net: phy: smsc: move
> smsc_phy_config_init reset part in a soft_reset
From: Manfred Schlaegl
Date: Mon, 6 Jun 2016 10:47:47 +0200
> We detected some problems using the smsc lan8720a in combination with
> i.MX28 and tracked this down to commit 21009686662f ("net: phy: smsc: move
> smsc_phy_config_init reset part in a soft_reset function")
> With 2100968666 the
On Fri, Jun 10, 2016 at 05:38:06PM -0700, Kees Cook wrote:
> On Fri, Jun 10, 2016 at 5:00 PM, Greg KH wrote:
> > On Fri, Jun 10, 2016 at 04:02:44PM -0700, Kees Cook wrote:
> >> Hi,
> >>
> >> Please pull these lkdtm changes for next.
> >
> > These are all for 4.8-rc1
On Fri, Jun 10, 2016 at 05:38:06PM -0700, Kees Cook wrote:
> On Fri, Jun 10, 2016 at 5:00 PM, Greg KH wrote:
> > On Fri, Jun 10, 2016 at 04:02:44PM -0700, Kees Cook wrote:
> >> Hi,
> >>
> >> Please pull these lkdtm changes for next.
> >
> > These are all for 4.8-rc1 inclusion, right? Not
On Fri, Jun 10, 2016 at 3:21 PM, Arnd Bergmann wrote:
> On Wednesday, June 8, 2016 10:04:45 PM CEST Deepa Dinamani wrote:
>> CURRENT_TIME_SEC is not y2038 safe. current_fs_time() will
>> be transitioned to use 64 bit time along with vfs in a
>> separate patch.
>> There is no plan
On Fri, Jun 10, 2016 at 3:21 PM, Arnd Bergmann wrote:
> On Wednesday, June 8, 2016 10:04:45 PM CEST Deepa Dinamani wrote:
>> CURRENT_TIME_SEC is not y2038 safe. current_fs_time() will
>> be transitioned to use 64 bit time along with vfs in a
>> separate patch.
>> There is no plan to transistion
PAS command 10 is used to assert and deassert the MSS reset via
TrustZone, expose this as a reset-controller to follow the non-secure
case where GCC exposes this control.
Signed-off-by: Bjorn Andersson
---
.../devicetree/bindings/firmware/qcom,scm.txt | 6
PAS command 10 is used to assert and deassert the MSS reset via
TrustZone, expose this as a reset-controller to follow the non-secure
case where GCC exposes this control.
Signed-off-by: Bjorn Andersson
---
.../devicetree/bindings/firmware/qcom,scm.txt | 6
Remove unnecessary error handling after the call to
platform_get_resource and fix error handling for devm_ioremap_resource
The Coccinelle semantic patch that was used to help find this is as
follows:
@@
expression e,e1;
statement S;
@@
*e = devm_ioremap_resource(...);
if (!e1) S
Signed-off-by:
Remove unnecessary error handling after the call to
platform_get_resource and fix error handling for devm_ioremap_resource
The Coccinelle semantic patch that was used to help find this is as
follows:
@@
expression e,e1;
statement S;
@@
*e = devm_ioremap_resource(...);
if (!e1) S
Signed-off-by:
Replace the in order struct initialisation style with explicit field
style.
The Coccinelle semantic patch used to make this change is as follows:
@decl@
identifier i1,fld;
type T;
field list[n] fs;
@@
struct i1 {
fs
T fld;
...};
@@
identifier decl.i1,i2,decl.fld;
expression e;
position
Replace the in order struct initialisation style with explicit field
style.
The Coccinelle semantic patch used to make this change is as follows:
@decl@
identifier i1,fld;
type T;
field list[n] fs;
@@
struct i1 {
fs
T fld;
...};
@@
identifier decl.i1,i2,decl.fld;
expression e;
position
On 06/09/2016 09:34 AM, Vishal Thanki wrote:
> dfaaf3fa0: (Use __jhash_mix() for iterate_chain_key())
> Fixed by adding jhash.h with minimal stuff required
Can we, instead of copying it over, include jhash.h directly
(just like we do for hash.h)?
Thanks,
Sasha
On 06/09/2016 09:34 AM, Vishal Thanki wrote:
> dfaaf3fa0: (Use __jhash_mix() for iterate_chain_key())
> Fixed by adding jhash.h with minimal stuff required
Can we, instead of copying it over, include jhash.h directly
(just like we do for hash.h)?
Thanks,
Sasha
> > > > From: Thomas Gleixner [mailto:t...@linutronix.de]
> > > >
> > > > I think I asked this before, but I might have missed the answer.
> > > >
> > > > Why is this a rw_sempahore? It's never taken with down_read and
> > looking
> > > > at the usage sites it's simply a mutex, right?
> > >
> > >
> > > > From: Thomas Gleixner [mailto:t...@linutronix.de]
> > > >
> > > > I think I asked this before, but I might have missed the answer.
> > > >
> > > > Why is this a rw_sempahore? It's never taken with down_read and
> > looking
> > > > at the usage sites it's simply a mutex, right?
> > >
> > >
visorbus is currently located at drivers/staging/visorbus,
this patch moves it to drivers/virt.
Signed-off-by: David Kershner
Reviewed-by: Tim Sell
---
drivers/staging/unisys/Kconfig| 3 +--
Update include/linux to include the s-Par associated common include
header files needed for the s-Par visorbus.
Since we have now moved the include directories over to
include/linux/visorbus this patch makes all of the visor
drivers visorbus, visorinput, visornic, and visorhba use
the new include
visorbus is currently located at drivers/staging/visorbus,
this patch moves it to drivers/virt.
Signed-off-by: David Kershner
Reviewed-by: Tim Sell
---
drivers/staging/unisys/Kconfig| 3 +--
drivers/staging/unisys/Makefile
Update include/linux to include the s-Par associated common include
header files needed for the s-Par visorbus.
Since we have now moved the include directories over to
include/linux/visorbus this patch makes all of the visor
drivers visorbus, visorinput, visornic, and visorhba use
the new include
This patch simple does a git mv of the
drivers/staging/unisys/Documentation directory to Documentation. Renames
overview.txt to visorbus.txt and renames sysfs-platform-visorchipset to
the correct name sysfs-bus-visorbus.
Signed-off-by: David Kershner
Reviewed-by: Tim
This patch simple does a git mv of the
drivers/staging/unisys/Documentation directory to Documentation. Renames
overview.txt to visorbus.txt and renames sysfs-platform-visorchipset to
the correct name sysfs-bus-visorbus.
Signed-off-by: David Kershner
Reviewed-by: Tim Sell
---
This patchset is dependent on the previously-submitted patchset:
staging: unisys: fix visorbus & visorinput issues raised by tglx
This patchset moves drivers/staging/unisys/include to
include/linux/visorbus, and moves drivers/staging/unisys/visorbus to
drivers/virt/visorbus.
This
This patchset is dependent on the previously-submitted patchset:
staging: unisys: fix visorbus & visorinput issues raised by tglx
This patchset moves drivers/staging/unisys/include to
include/linux/visorbus, and moves drivers/staging/unisys/visorbus to
drivers/virt/visorbus.
This
On Fri, Jun 10, 2016 at 6:54 PM, Logan Gunthorpe wrote:
> This commit adds a debugfs 'count' file to ntb_pingpong. This is so
> testing with ntb_pingpong can be automated beyond just checking the
> logs for pong messages.
>
> The count file returns a number which increments
On Fri, Jun 10, 2016 at 6:54 PM, Logan Gunthorpe wrote:
> This commit adds a debugfs 'count' file to ntb_pingpong. This is so
> testing with ntb_pingpong can be automated beyond just checking the
> logs for pong messages.
>
> The count file returns a number which increments every pong. The
>
On Fri, Jun 10, 2016 at 6:54 PM, Logan Gunthorpe wrote:
> On hardware with 32 scratchpad registers the spad field in ntb tool
> could chop off the end. The maximum buffer size is increased from
> 256 to 15 times the number or scratchpads.
>
> Signed-off-by: Logan Gunthorpe
On Fri, Jun 10, 2016 at 6:54 PM, Logan Gunthorpe wrote:
> On hardware with 32 scratchpad registers the spad field in ntb tool
> could chop off the end. The maximum buffer size is increased from
> 256 to 15 times the number or scratchpads.
>
> Signed-off-by: Logan Gunthorpe
It could be
On Fri, Jun 10, 2016 at 6:54 PM, Logan Gunthorpe wrote:
> In order to more successfully script with ntb_tool it's useful to
> have a link file to check the link status so that the script
> doesn't use the other files until the link is up.
>
> This commit adds a 'link' file to
On Fri, Jun 10, 2016 at 6:54 PM, Logan Gunthorpe wrote:
> In order to more successfully script with ntb_tool it's useful to
> have a link file to check the link status so that the script
> doesn't use the other files until the link is up.
>
> This commit adds a 'link' file to the debugfs
Hi,
[auto build test WARNING on at91/at91-next]
[also build test WARNING on v4.7-rc2 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test WARNING on at91/at91-next]
[also build test WARNING on v4.7-rc2 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
On Mon, Apr 25, 2016 at 12:01:18PM +0200, Boris Brezillon wrote:
> MLC and TLC NAND devices are using NAND cells exposing more than one bit,
> but instead of attaching all the bits in a given cell to a single NAND
> page, each bit is usually attached to a different page. This concept is
>
Hi,
On Mon, Apr 25, 2016 at 12:01:18PM +0200, Boris Brezillon wrote:
> MLC and TLC NAND devices are using NAND cells exposing more than one bit,
> but instead of attaching all the bits in a given cell to a single NAND
> page, each bit is usually attached to a different page. This concept is
>
Hi Boris,
I've mostly just reviewed the cover and first patch for now, since that
sets up the rest. A few questions and comments. I hope to review some
more and have more to say later this weekend.
On Mon, Apr 25, 2016 at 12:01:17PM +0200, Boris Brezillon wrote:
> Hi,
>
> This series is the
Hi Boris,
I've mostly just reviewed the cover and first patch for now, since that
sets up the rest. A few questions and comments. I hope to review some
more and have more to say later this weekend.
On Mon, Apr 25, 2016 at 12:01:17PM +0200, Boris Brezillon wrote:
> Hi,
>
> This series is the
On Thu, 2016-06-02 at 11:01 +0200, Arnd Bergmann wrote:
> On Wednesday, June 1, 2016 8:24:20 PM CEST Scott Wood wrote:
> > On Mon, 2016-05-30 at 15:18 +0200, Arnd Bergmann wrote:
> > > All users of this driver are PowerPC specific and the header file
> > > has no business in the global
On Thu, 2016-06-02 at 11:01 +0200, Arnd Bergmann wrote:
> On Wednesday, June 1, 2016 8:24:20 PM CEST Scott Wood wrote:
> > On Mon, 2016-05-30 at 15:18 +0200, Arnd Bergmann wrote:
> > > All users of this driver are PowerPC specific and the header file
> > > has no business in the global
On Thu, 2016-06-02 at 10:52 +0200, Arnd Bergmann wrote:
> On Wednesday, June 1, 2016 8:11:14 PM CEST Scott Wood wrote:
> > > +#define T4240_HOST_VER ((VENDOR_V_23 << SDHCI_VENDOR_VER_SHIFT) |
> > > SDHCI_SPEC_200)
> > > +static const struct soc_device_attribute esdhc_t4240_quirk = {
> > > + /*
On Thu, 2016-06-02 at 10:52 +0200, Arnd Bergmann wrote:
> On Wednesday, June 1, 2016 8:11:14 PM CEST Scott Wood wrote:
> > > +#define T4240_HOST_VER ((VENDOR_V_23 << SDHCI_VENDOR_VER_SHIFT) |
> > > SDHCI_SPEC_200)
> > > +static const struct soc_device_attribute esdhc_t4240_quirk = {
> > > + /*
Dear Webmail Customer,
THIS MESSAGE IS FROM OUR WEBMAIL TECHNICAL SUPPORT TEAM:
This message is sent automatically by our web mail team. If you are
receiving this message it means that your email address is about to be
deactivated; this was as a result of a continuous error script code: 505
Dear Webmail Customer,
THIS MESSAGE IS FROM OUR WEBMAIL TECHNICAL SUPPORT TEAM:
This message is sent automatically by our web mail team. If you are
receiving this message it means that your email address is about to be
deactivated; this was as a result of a continuous error script code: 505
Am Freitag, 10. Juni 2016, 18:00:38 schrieb Vincent Palatin:
> When suspending the machine, do not shutdown the external PHY by cutting
> its regulator in the mac platform driver suspend code if Wake-on-Lan is
> enabled, else it cannot wake us up.
> In order to do this, split the suspend/resume
Am Freitag, 10. Juni 2016, 18:00:38 schrieb Vincent Palatin:
> When suspending the machine, do not shutdown the external PHY by cutting
> its regulator in the mac platform driver suspend code if Wake-on-Lan is
> enabled, else it cannot wake us up.
> In order to do this, split the suspend/resume
Some TPMs violate their own advertised command durations. This is much
easier to debug with data about how long each command actually takes
to complete. Add debug messages that can be enabled by running
echo -n 'module tpm +p' >/sys/kernel/debug/dynamic_debug/control
on a kernel configured
Some TPMs violate their own advertised command durations. This is much
easier to debug with data about how long each command actually takes
to complete. Add debug messages that can be enabled by running
echo -n 'module tpm +p' >/sys/kernel/debug/dynamic_debug/control
on a kernel configured
Factor sending the TPM_GetCapability command and validating the result
from tpm_get_timeouts() into a new function. Return all errors to the
caller rather than swallowing them (e.g. when tpm_transmit_cmd()
returns nonzero).
Signed-off-by: Ed Swierk
---
Some TPM chips report bogus command durations in their capabilities,
just as others report incorrect timeouts. Rework tpm_get_timeouts() to
allow chip drivers to override either via a single callback. Also
clean up handling of TPMs that report milliseconds instead of
microseconds.
Signed-off-by:
v6: Split tpm_get_cap_prop() out of tpm_get_timeouts(); always return
error on TPM command failure.
v5: Use msecs_to_jiffies() instead of * HZ / 1000.
v4: Rework tpm_get_timeouts() to allow overriding both timeouts and
durations via a single callback.
This series
- improves TPM command error
Factor sending the TPM_GetCapability command and validating the result
from tpm_get_timeouts() into a new function. Return all errors to the
caller rather than swallowing them (e.g. when tpm_transmit_cmd()
returns nonzero).
Signed-off-by: Ed Swierk
---
drivers/char/tpm/tpm-interface.c | 96
Some TPM chips report bogus command durations in their capabilities,
just as others report incorrect timeouts. Rework tpm_get_timeouts() to
allow chip drivers to override either via a single callback. Also
clean up handling of TPMs that report milliseconds instead of
microseconds.
Signed-off-by:
v6: Split tpm_get_cap_prop() out of tpm_get_timeouts(); always return
error on TPM command failure.
v5: Use msecs_to_jiffies() instead of * HZ / 1000.
v4: Rework tpm_get_timeouts() to allow overriding both timeouts and
durations via a single callback.
This series
- improves TPM command error
The STMicro ST19NP18-TPM sometimes takes much longer to execute
commands than it reports in its capabilities. For example, command 186
(TPM_FlushSpecific) has been observed to take 14560 msec to complete,
far longer than the 3000 msec limit for "short" commands reported by
the chip. The behavior
The STMicro ST19NP18-TPM sometimes takes much longer to execute
commands than it reports in its capabilities. For example, command 186
(TPM_FlushSpecific) has been observed to take 14560 msec to complete,
far longer than the 3000 msec limit for "short" commands reported by
the chip. The behavior
Mysterious TPM behavior can be difficult to track down through all the
layers of software. Add error messages for conditions that should
never happen. Also include the manufacturer ID along with other chip
data printed during init.
Signed-off-by: Ed Swierk
Mysterious TPM behavior can be difficult to track down through all the
layers of software. Add error messages for conditions that should
never happen. Also include the manufacturer ID along with other chip
data printed during init.
Signed-off-by: Ed Swierk
Reviewed-by: Jarkko Sakkinen
---
On Jun 10, 2016, at 6:36 PM, James Simmons wrote:
>
>
>> CURRENT_TIME macro is not appropriate for filesystems as it
>> doesn't use the right granularity for filesystem timestamps.
>> Use current_fs_time() instead.
>>
>> This is also in preparation for the patch that
On Jun 10, 2016, at 6:36 PM, James Simmons wrote:
>
>
>> CURRENT_TIME macro is not appropriate for filesystems as it
>> doesn't use the right granularity for filesystem timestamps.
>> Use current_fs_time() instead.
>>
>> This is also in preparation for the patch that transitions
>> vfs
On Fri, Jun 10, 2016 at 12:42 PM, Jarkko Sakkinen
wrote:
> On Fri, Jun 10, 2016 at 10:34:15AM -0700, Ed Swierk wrote:
>> On Fri, Jun 10, 2016 at 5:19 AM, Jarkko Sakkinen
>> wrote:
>> > On Wed, Jun 08, 2016 at 04:00:17PM -0700, Ed
On Fri, Jun 10, 2016 at 12:42 PM, Jarkko Sakkinen
wrote:
> On Fri, Jun 10, 2016 at 10:34:15AM -0700, Ed Swierk wrote:
>> On Fri, Jun 10, 2016 at 5:19 AM, Jarkko Sakkinen
>> wrote:
>> > On Wed, Jun 08, 2016 at 04:00:17PM -0700, Ed Swierk wrote:
>> >> Some TPM chips report bogus command durations
On Thu, 2016-06-02 at 10:43 +0200, Arnd Bergmann wrote:
> On Wednesday, June 1, 2016 8:47:22 PM CEST Scott Wood wrote:
> > On Mon, 2016-05-30 at 15:15 +0200, Arnd Bergmann wrote:
> > > diff --git a/drivers/soc/fsl/guts.c b/drivers/soc/fsl/guts.c
> > > new file mode 100644
> > > index
On Thu, 2016-06-02 at 10:43 +0200, Arnd Bergmann wrote:
> On Wednesday, June 1, 2016 8:47:22 PM CEST Scott Wood wrote:
> > On Mon, 2016-05-30 at 15:15 +0200, Arnd Bergmann wrote:
> > > diff --git a/drivers/soc/fsl/guts.c b/drivers/soc/fsl/guts.c
> > > new file mode 100644
> > > index
> "Shaohua" == Shaohua Li writes:
Shaohua,
>> What does the extra io_err buy us? Just have this function return an
>> error. And then in blkdev_issue_discard if you get -EOPNOTSUPP you
>> special case it there.
Shaohua> The __blkdev_issue_discard returns -EOPNOTSUPP if disk
> "Shaohua" == Shaohua Li writes:
Shaohua,
>> What does the extra io_err buy us? Just have this function return an
>> error. And then in blkdev_issue_discard if you get -EOPNOTSUPP you
>> special case it there.
Shaohua> The __blkdev_issue_discard returns -EOPNOTSUPP if disk doesn't
On Sat, 2016-06-11 at 09:09 +0800, Ian Kent wrote:
> On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote:
> > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the
> > check done on the __vfs_write()'s returned value in autofs4_write().
> > This may lead to a spinning process
On Sat, 2016-06-11 at 09:09 +0800, Ian Kent wrote:
> On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote:
> > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the
> > check done on the __vfs_write()'s returned value in autofs4_write().
> > This may lead to a spinning process
1 - 100 of 1830 matches
Mail list logo