mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Todd Poynor <toddpoynor@gmail.com>
Cc: Rob Springer <rspringer@google.com>,
	John Joseph <jnjoseph@google.com>,
	Ben Chan <benchan@chromium.org>,
	devel@driverdev.osuosl.org, Zhongze Hu <frankhu@chromium.org>,
	linux-kernel@vger.kernel.org, Simon Que <sque@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	Todd Poynor <toddpoynor@google.com>,
	Dmitry Torokhov <dtor@chromium.org>
Subject: Re: [PATCH resend] staging: gasket: remove X86 Kconfig restriction
Date: Sun, 15 Jul 2018 21:40:58 +0200	[thread overview]
Message-ID: <20180715194058.GB2288@kroah.com> (raw)
In-Reply-To: <20180715182545.187942-1-toddpoynor@gmail.com>

On Sun, Jul 15, 2018 at 11:25:45AM -0700, Todd Poynor wrote:
> From: Todd Poynor <toddpoynor@google.com>
> 
> The gasket and apex drivers are to be used on other architectures
> besides X86.
> 
> Signed-off-by: Todd Poynor <toddpoynor@gmail.com>
> ---
>  drivers/staging/gasket/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Why are these all a "resend"?  They need to be in a v2 series, based on
the changes requested, right?  "resend" implies I somehow did not see
them...

And always properly version your patch series, and number them in order,
otherwise I have no idea what order to apply them in, and if I have
missed any or not.

Remember, you need to make it as simple as possible for me not to mess
things up :)

thanks,

greg k-h

  reply	other threads:[~2018-07-15 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15 18:25 Todd Poynor
2018-07-15 19:40 ` Greg Kroah-Hartman [this message]
2018-07-19  1:18 ` kbuild test robot
2018-07-19  3:07   ` Todd Poynor

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=20180715194058.GB2288@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=benchan@chromium.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dtor@chromium.org \
    --cc=frankhu@chromium.org \
    --cc=groeck@chromium.org \
    --cc=jnjoseph@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rspringer@google.com \
    --cc=sque@chromium.org \
    --cc=toddpoynor@gmail.com \
    --cc=toddpoynor@google.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
all inboxes | Powered by JetHome®