All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Zimmerman <joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Jarkko Sakkinen
	<jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH v4 2/2] Add "shutdown" to "struct class".
Date: Fri, 2 Jun 2017 15:00:22 -0700	[thread overview]
Message-ID: <CAHSjozDaMwGspg=hhTGR7CUa+tMV7qC8FAssMKin9h_bFcysaA@mail.gmail.com> (raw)
In-Reply-To: <20170601170721.uyjhkjtuey6p3gmt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Quite strange. Here's what I see.

$ git pull
Already up-to-date.
$ git branch
  master
* next
$ git am -3 /tmp/v6-0001-tpm-Issue-a-TPM2_Shutdown-for-TPM2-devices.patch
Applying: tpm: Issue a TPM2_Shutdown for TPM2 devices.
$ git am -3 /tmp/v6-0002-Add-shutdown-to-struct-class.patch  # This is
identical to v5
Applying: Add "shutdown" to "struct class".
$ git status
On branch next
Your branch is ahead of 'origin/next' by 2 commits.
  (use "git push" to publish your local commits)

nothing to commit, working tree clean
$ git log --oneline | head -n 4
58410b1fef64 Add "shutdown" to "struct class".
84e311a15e94 tpm: Issue a TPM2_Shutdown for TPM2 devices.
d68c51e0b377 Sync to mainline for security submaintainers to work against
08332893e37a Linux 4.12-rc2
$ git remote -v
origin  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
(fetch)
origin  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
(push)
Josh


On Thu, Jun 1, 2017 at 10:07 AM, Jarkko Sakkinen
<jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
> On Wed, May 31, 2017 at 03:01:13PM -0700, Josh Zimmerman wrote:
>> On Tue, May 30, 2017 at 12:54 AM, Jarkko Sakkinen
>> <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote:
>> > On Thu, May 25, 2017 at 04:20:30PM -0700, Josh Zimmerman wrote:
>> >> The TPM class has some common shutdown code that must be executed for
>> >> all drivers. This adds some needed functionality for that.
>> >>
>> >> Signed-off-by: Josh Zimmerman <joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
>> >> Acked-by: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
>> >> Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> >
>> > Does not apply yet to security-next (ancestor missing).
>>
>> Hm, it applied cleanly for me to the "next" branch of
>> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git.
>> Are you referring to something else with "security-next"?
>
> Hmm...
>
> I get
>
> $ git am -3 ~/Downloads/v5-2-2-Add-shutdown-to-struct-class-..patch
> Applying: Add "shutdown" to "struct class".
> error: patch fragment without header at line 7: @@ -407,6 +408,7 @@ struct class {
> error: could not build fake ancestor
> Patch failed at 0001 Add "shutdown" to "struct class".
> The copy of the patch that failed is found in: .git/rebase-apply/patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> My tree rebased to latest security/next
>
> /Jarkko

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  parent reply	other threads:[~2017-06-02 22:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 23:20 [PATCH v4 2/2] Add "shutdown" to "struct class" Josh Zimmerman
     [not found] ` <CAHSjozD_NjH0Ta=ELCOqG6ezX=qgteumKBnN2ceqE4ty2FaAZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-30  5:08   ` Jarkko Sakkinen
2017-05-30  7:54   ` Jarkko Sakkinen
     [not found]     ` <20170530075419.766mlyxomxrzbxz6-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-05-31 22:01       ` Josh Zimmerman
     [not found]         ` <CAHSjozBDNX-bEQGjUtjqJzG_kuSWgxmrjPmdA=nfYhr1DFGgYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-31 22:18           ` Jason Gunthorpe
2017-06-01 17:07           ` Jarkko Sakkinen
     [not found]             ` <20170601170721.uyjhkjtuey6p3gmt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-06-02 22:00               ` Josh Zimmerman [this message]
     [not found]                 ` <CAHSjozDaMwGspg=hhTGR7CUa+tMV7qC8FAssMKin9h_bFcysaA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-05 12:48                   ` Jarkko Sakkinen
     [not found]                     ` <20170605124834.e6myswydwvvscaao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-06-05 18:32                       ` Josh Zimmerman
     [not found]                         ` <CAHSjozAhiR0E5FvuZGgJ39hyd9oT3NYeHm=BCdouhCOXBdi+SA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-12 23:08                           ` Josh Zimmerman via tpmdd-devel
     [not found]                             ` <CAHSjozA4Jpq4JDgmfqMk6p_AHjjW4tpeAehFXBcWxe0WsY3psA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-13 19:11                               ` Jarkko Sakkinen
     [not found] <20170525230620.21656-1-joshz@google.com>
2017-05-25 23:06 ` Josh Zimmerman
2017-05-25 23:12   ` Josh Zimmerman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHSjozDaMwGspg=hhTGR7CUa+tMV7qC8FAssMKin9h_bFcysaA@mail.gmail.com' \
    --to=joshz-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
    --cc=jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
    --cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.