From: Vinod Koul <vinod.koul@intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 1/3] DMA: shdma: Fix warnings due to improper casts and printk formats
Date: Thu, 06 Mar 2014 06:20:05 +0000 [thread overview]
Message-ID: <20140306060805.GA1976@intel.com> (raw)
In-Reply-To: <1386765786-1926-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Tue, Mar 04, 2014 at 06:07:55PM +0100, Laurent Pinchart wrote:
> Hi Vinod,
>
> On Tuesday 04 March 2014 16:50:29 Koul, Vinod wrote:
> > On 4 Mar 2014 17:11, Laurent Pinchart wrote:
> > > On Tuesday 21 January 2014 13:10:30 Laurent Pinchart wrote:
> > > > On Tuesday 07 January 2014 16:08:37 Laurent Pinchart wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > Ping ? Could this patch series (with patches v3.1 1/3, v3 2/3 and v3
> > > > > 3/3) be applied for v3.14 ? Same question for "DMA: shdma: Enable
> > > > > driver compilation with COMPILE_TEST".
> > > >
> > > > PING ?
> > >
> > > HELLO ? ANYONE THERE ? This is v3.14 material.
> >
> > Sorry looks like I missed out earlier... Am just back from vacation, give me
> > few days to go thru this and do the needful...
>
> No worries, and thanks for handling this. I'm glad to know you're still alive
> :-)
Well i shouldnt have missed this earlier!
Anyway I have applied these. Since these are fixing warning I am going to push
them to 3.15. Sending warnings fixes to Linus after rc4 isn't a good idea. Sorry
bad timing :(
--
~Vinod
next prev parent reply other threads:[~2014-03-06 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 12:43 [PATCH v3 1/3] DMA: shdma: Fix warnings due to improper casts and printk formats Laurent Pinchart
2013-12-11 12:59 ` Shevchenko, Andriy
2013-12-11 14:27 ` Laurent Pinchart
2014-01-07 15:08 ` Laurent Pinchart
2014-01-21 12:10 ` Laurent Pinchart
2014-03-04 11:42 ` Laurent Pinchart
2014-03-04 16:50 ` Koul, Vinod
2014-03-04 17:07 ` Laurent Pinchart
2014-03-06 6:20 ` Vinod Koul [this message]
2014-03-06 11:24 ` Laurent Pinchart
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=20140306060805.GA1976@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-sh@vger.kernel.org \
/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).