From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: lots of repeated patches in the tpmdd tree
Date: Mon, 27 Jun 2016 15:29:00 +0300 [thread overview]
Message-ID: <20160627122859.GA8685@intel.com> (raw)
In-Reply-To: <20160627093646.58390c59@canb.auug.org.au>
On Mon, Jun 27, 2016 at 09:36:46AM +1000, Stephen Rothwell wrote:
> Hi Jarkko,
>
> I noticed that a large number of the patches in the tpmdd tree appear
> twice (and some three times). They appear to have been rebased on top
> of the security tree before being remerged. Please clean this all up.
Cleaned up. Thanks (and sorry).
> --
> Cheers,
> Stephen Rothwell
/Jarkko
prev parent reply other threads:[~2016-06-27 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 23:36 linux-next: lots of repeated patches in the tpmdd tree Stephen Rothwell
2016-06-27 12:29 ` Jarkko Sakkinen [this message]
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=20160627122859.GA8685@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).