From: Dan Carpenter <dan.carpenter@oracle.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: devel@driverdev.osuosl.org, Kirk Reiser <kirk@reisers.ca>,
Raphael S Carvalho <raphael.scarv@gmail.com>,
speakup@braille.uwo.ca,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 1/1] staging/speakup/kobjects.c: Code improvement.
Date: Wed, 11 Sep 2013 10:59:44 +0300 [thread overview]
Message-ID: <20130911075944.GA25896@mwanda> (raw)
In-Reply-To: <878uz4du2k.fsf@mushroom.PK5001Z>
On Tue, Sep 10, 2013 at 06:29:39PM -0700, Chris Brannon wrote:
> Ok. I just sent up a patch to the driverdev list. I missed a few
> of the Cc's that were on this thread, though.
> Also, it will conflict with Raphael's cleanup.
You're missing Raphael's CC in particular...
Really, Raphael's patch arrived first. No one seems to have any
objections to his patch. Normally apply it first and then apply this
one. If we decide to push this one to -stable then we would redo it (in
other words push the one you just sent).
Of course, the merge window is open right now so nothing is going to be
applied for a couple weeks.
regards,
dan carpenter
next prev parent reply other threads:[~2013-09-11 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 22:20 [PATCH 1/1] staging/speakup/kobjects.c: Code improvement Raphael S.Carvalho
2013-09-09 3:56 ` Chris Brannon
[not found] ` <CACz=WeeE+jxdaxpR_amF60deDcEy8nChYYfY3UA3CNfhmOB8Gw@mail.gmail.com>
2013-09-09 4:16 ` Fwd: " Raphael S Carvalho
2013-09-09 6:02 ` Chris Brannon
2013-09-10 23:12 ` Dan Carpenter
2013-09-11 1:29 ` Chris Brannon
2013-09-11 7:59 ` Dan Carpenter [this message]
2013-09-11 21:01 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2013-06-22 1:54 Raphael S. Carvalho
2013-06-30 8:11 ` Samuel Thibault
2013-07-23 21:39 ` Greg Kroah-Hartman
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=20130911075944.GA25896@mwanda \
--to=dan.carpenter@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=raphael.scarv@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@braille.uwo.ca \
/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