From: "Jan Lübbe" <jlu@pengutronix.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Zubair Lutfullah <zubair.lutfullah@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH] typo fixes (coordiante -> coordinate) in am335x
Date: Tue, 05 Nov 2013 18:51:11 +0100 [thread overview]
Message-ID: <1383673871.6753.36.camel@polaris.local> (raw)
In-Reply-To: <20131105171553.GB30901@lee--X1>
On Tue, 2013-11-05 at 17:15 +0000, Lee Jones wrote:
> On Tue, 05 Nov 2013, Jan Lübbe wrote:
>
> > On Tue, 2013-10-22 at 10:05 +0100, Lee Jones wrote:
> > > This is the first time this patch has been sent to me.
> > >
> > > I need Dmitry's input (no pun intended) on how he's like to deal with
> > > this. At a bare minimum I'd like his Ack.
> >
> > Is there anything I can do to push this forward? The earlier we get the
> > typo fixed in the documentation, the less chance that someone will use
> > it that way.
>
> I think you should sent it again, but this time Cc the Device Tree
> list, Dmitry and myself when you submit.
The original patch was not from me. But sure, I can resend it.
Jan
WARNING: multiple messages have this Message-ID (diff)
From: jlu@pengutronix.de (Jan Lübbe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] typo fixes (coordiante -> coordinate) in am335x
Date: Tue, 05 Nov 2013 18:51:11 +0100 [thread overview]
Message-ID: <1383673871.6753.36.camel@polaris.local> (raw)
In-Reply-To: <20131105171553.GB30901@lee--X1>
On Tue, 2013-11-05 at 17:15 +0000, Lee Jones wrote:
> On Tue, 05 Nov 2013, Jan L?bbe wrote:
>
> > On Tue, 2013-10-22 at 10:05 +0100, Lee Jones wrote:
> > > This is the first time this patch has been sent to me.
> > >
> > > I need Dmitry's input (no pun intended) on how he's like to deal with
> > > this. At a bare minimum I'd like his Ack.
> >
> > Is there anything I can do to push this forward? The earlier we get the
> > typo fixed in the documentation, the less chance that someone will use
> > it that way.
>
> I think you should sent it again, but this time Cc the Device Tree
> list, Dmitry and myself when you submit.
The original patch was not from me. But sure, I can resend it.
Jan
next prev parent reply other threads:[~2013-11-05 17:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 15:25 [PATCH] typo fixes (coordiante -> coordinate) in am335x Zubair Lutfullah
2013-07-15 15:25 ` Zubair Lutfullah
2013-08-21 7:58 ` Tony Lindgren
2013-08-21 7:58 ` Tony Lindgren
2013-10-19 16:02 ` Jan Lübbe
2013-10-19 16:02 ` Jan Lübbe
2013-10-19 16:02 ` Jan Lübbe
2013-10-22 9:05 ` Lee Jones
2013-10-22 9:05 ` Lee Jones
2013-11-05 16:01 ` Jan Lübbe
2013-11-05 16:01 ` Jan Lübbe
2013-11-05 17:15 ` Lee Jones
2013-11-05 17:15 ` Lee Jones
2013-11-05 17:15 ` Lee Jones
2013-11-05 17:51 ` Jan Lübbe [this message]
2013-11-05 17:51 ` Jan Lübbe
2013-11-05 18:03 ` Lee Jones
2013-11-05 18:03 ` Lee Jones
2013-11-05 18:03 ` Lee Jones
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=1383673871.6753.36.camel@polaris.local \
--to=jlu@pengutronix.de \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.com \
--cc=zubair.lutfullah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.