public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Mera <dev@michaelmera.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: William Hubbs <w.d.hubbs@gmail.com>,
	Chris Brannon <chris@the-brannons.com>,
	Kirk Reiser <kirk@reisers.ca>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	linux-kernel@vger.kernel.org, Michael Mera <dev@michaelmera.com>
Subject: Re: [PATCH v3] staging: speakup: fix wrong code indent
Date: Sat, 29 Apr 2017 10:24:13 +0900	[thread overview]
Message-ID: <87h918hupu.fsf@michaelmera.com> (raw)
In-Reply-To: <20170428155225.GA18808@kroah.com>

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> This patch doesn't apply to my tree at all, what tree/branch did you
> make it against?

>From the 'T:' line in MAINTAINER at STAGING SUBSYSTEM,  I thought that I
should base changes on:
  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git

Since there was no branch indication unlike some other lines, I worked
on master.

Now, given your remark I found your blog post where you ask to base the
changes on linux-next. Sorry.

Part of the patch is still relevant, so I intend to submit a v4. If that
is ok with you.

Thank you,
Michael Mera

  reply	other threads:[~2017-04-29  1:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  6:20 [PATCH] staging: speakup: fix wrong code indent Michael Mera
2017-04-28  7:11 ` Greg Kroah-Hartman
2017-04-28  8:46   ` [PATCH v2] " Michael Mera
2017-04-28  9:00     ` Greg Kroah-Hartman
2017-04-28  9:11       ` Michael Mera
2017-04-28  9:36         ` Greg Kroah-Hartman
2017-04-28 14:43           ` [PATCH v3] " Michael Mera
2017-04-28 15:52             ` Greg Kroah-Hartman
2017-04-29  1:24               ` Michael Mera [this message]
2017-05-09 23:48                 ` [PATCH v4] staging: speakup: fix unnecessary long line Michael Mera

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=87h918hupu.fsf@michaelmera.com \
    --to=dev@michaelmera.com \
    --cc=chris@the-brannons.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=w.d.hubbs@gmail.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