On Sat, Jun 25, 2016 at 06:47:45PM +0300, Jarkko Sakkinen wrote:
> My repositories are ready for next pull request. The master has been
> rebased to James' tree and merged to next.
This seems fine..
Generally you shouldn't rebase to create pull requests, but this
seemed needed..
Organize your g
On Sat, Jun 25, 2016 at 06:24:30PM +0300, Jarkko Sakkinen wrote:
> On Fri, Jun 24, 2016 at 02:26:15PM -0600, Jason Gunthorpe wrote:
> > On Fri, Jun 24, 2016 at 11:21:31PM +0300, Jarkko Sakkinen wrote:
> > > Hmm... Do you mean by 4 month old stuff the stuff that is in mainline
> > > and not in my ma
On Fri, Jun 24, 2016 at 02:26:15PM -0600, Jason Gunthorpe wrote:
> On Fri, Jun 24, 2016 at 11:21:31PM +0300, Jarkko Sakkinen wrote:
> > Hmm... Do you mean by 4 month old stuff the stuff that is in mainline
> > and not in my master branch?
>
> I mean the stuff that is in your branch but not in main
On Fri, Jun 24, 2016 at 11:21:31PM +0300, Jarkko Sakkinen wrote:
> Hmm... Do you mean by 4 month old stuff the stuff that is in mainline
> and not in my master branch?
I mean the stuff that is in your branch but not in mainline.
$ git log --pretty=oneline jarkko/master ^v4.7-rc3 | wc -l
73
> I'm
On Fri, Jun 24, 2016 at 11:21:31PM +0300, Jarkko Sakkinen wrote:
> Hi Jason,
>
> On Fri, Jun 24, 2016 at 12:25:15PM -0600, Jason Gunthorpe wrote:
> > > expected = be32_to_cpu(*(__be32 *) (buf + 2));
> > > if (expected > count) {
> > > + dev_err(chip->pdev, "Response too long (wanted %z
Hi Jason,
On Fri, Jun 24, 2016 at 12:25:15PM -0600, Jason Gunthorpe wrote:
> > expected = be32_to_cpu(*(__be32 *) (buf + 2));
> > if (expected > count) {
> > + dev_err(chip->pdev, "Response too long (wanted %zd, got %d)\n",
> > + count, expected);
>
> This all
> expected = be32_to_cpu(*(__be32 *) (buf + 2));
> if (expected > count) {
> + dev_err(chip->pdev, "Response too long (wanted %zd, got %d)\n",
> + count, expected);
This all needs to be rebased on Jarkko's tree I guess, chip->pdev is
gone now.
http://gi
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
---
drive
8 matches
Mail list logo