From: Antoine Tenart <antoine.tenart@bootlin.com>
To: Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>
Cc: Antoine Tenart <antoine.tenart@bootlin.com>,
Pascal van Leeuwen <pascalvanl@gmail.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH] crypto: inside-secure - remove unused struct entry
Date: Fri, 5 Jul 2019 16:39:40 +0200 [thread overview]
Message-ID: <20190705143940.GG3926@kwain> (raw)
In-Reply-To: <MN2PR20MB297394029C591248FA258760CAF50@MN2PR20MB2973.namprd20.prod.outlook.com>
On Fri, Jul 05, 2019 at 02:32:46PM +0000, Pascal Van Leeuwen wrote:
> > From: Antoine Tenart <antoine.tenart@bootlin.com>
> >
> > You should wait for either those patches to be merged (or directly
> > integrate this change in a newer version of those patches), or send this
> > patch in the same series. Otherwise it's problematic as you do not know
> > which patches will be applied first.
>
> This patch indeed depends on earlier patches. I was just assuming
> people to be smart enough to apply the patches in the correct order :-)
It's actually very difficult for a maintainer to remember this,
especially when he has to deal with plenty of patches from many
contributors. And some series can take time to be merged while others
can be accepted easily, so it's hard to keep track of dependencies :)
> So please ignore, I'll either resend or incorporate it in an update of the
> earlier series later. It's nothing important (i.e. functional) anyway.
Thank you!
Antoine
--
Antoine Ténart, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-05 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 8:17 [PATCH] crypto: inside-secure - remove unused struct entry Pascal van Leeuwen
2019-07-05 14:18 ` Antoine Tenart
2019-07-05 14:32 ` Pascal Van Leeuwen
2019-07-05 14:39 ` Antoine Tenart [this message]
2019-07-05 14:54 ` Pascal Van Leeuwen
2019-07-05 15:57 ` Antoine Tenart
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=20190705143940.GG3926@kwain \
--to=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pascalvanl@gmail.com \
--cc=pvanleeuwen@verimatrix.com \
/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).