From: Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v1] spi: dw: amend warning message
Date: Wed, 07 Jan 2015 16:58:33 +0200 [thread overview]
Message-ID: <1420642713.12456.22.camel@linux.intel.com> (raw)
In-Reply-To: <20150105202106.GO2634-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Mon, 2015-01-05 at 20:21 +0000, Mark Brown wrote:
> On Fri, Jan 02, 2015 at 04:11:08PM +0200, Andy Shevchenko wrote:
> > On Fri, 2015-01-02 at 16:06 +0200, Andy Shevchenko wrote:
>
> > > + dev_warn(dev, "DMA init failed\n");
>
> > Oops, based on some WIP patches, though still applies smoothly on top of
> > recent linux-next.
>
> Not with git am it doesn't (I suspect mostly because it's easily
> confused by not having the required SHA1s but still).
git am -C1 -s helps, but anyway I submitted v2 with one additional patch
(the add-on I suggested to Alex Lin to print FIFO size when
autodetection happened).
--
Andy Shevchenko <andriy.shevchenko-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-01-07 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 14:06 [PATCH v1] spi: dw: amend warning message Andy Shevchenko
[not found] ` <1420207565-14712-1-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-02 14:11 ` Andy Shevchenko
[not found] ` <1420207868.12456.16.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-01-05 20:21 ` Mark Brown
[not found] ` <20150105202106.GO2634-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-01-07 14:58 ` Andy Shevchenko [this message]
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=1420642713.12456.22.camel@linux.intel.com \
--to=andriy.shevchenko-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).