From: Marek Vasut <marex@denx.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: sdhci: Fix strings broken across multiple lines
Date: Thu, 19 Nov 2015 12:58:45 +0100 [thread overview]
Message-ID: <201511191258.45847.marex@denx.de> (raw)
In-Reply-To: <CAPDyKFq6XcKczr+QrJ_-XodxLZZxLiyG+EMpGBzDyR3pe5=oBw@mail.gmail.com>
On Thursday, November 19, 2015 at 12:52:06 PM, Ulf Hansson wrote:
> On 18 November 2015 at 10:47, Marek Vasut <marex@denx.de> wrote:
> > This is a trivial patch which fixes printed strings split across two
> > or more lines in the source. I tried to grep for some error output*,
> > but I couldn't find it easily because it was broken across multiple
> > lines. This patch makes my life easier.
> >
> > * in particular "Timeout waiting for hardware interrupt."
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Ulf Hansson <ulf.hansson@linaro.org>
Hi!
> Future wise, no need to add a Cc tag here. You should send the patch
> to me anyway.
Are CC tags now frowned upon? In case I have multiple distinct patches
(which go to distinct lists/recipients) in a queue, I use these CC tags
to track who to keep in a loop. Is there some better way to do this?
> Thanks, applied for next!
Thanks.
> FYI: There were some check patch warnings, but I decided to ignore
> them as those are related to the use of the DBG macro.
Oh yeah, the DBG() macro struck me as slightly odd. We should probably
use dev_err() or pr_err() where applicable.
> Kind regards
> Uffe
[..]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-11-19 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 9:47 [PATCH] mmc: sdhci: Fix strings broken across multiple lines Marek Vasut
2015-11-19 11:52 ` Ulf Hansson
2015-11-19 11:58 ` Marek Vasut [this message]
2015-11-19 12:05 ` Ulf Hansson
2015-11-19 15:16 ` Marek Vasut
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=201511191258.45847.marex@denx.de \
--to=marex@denx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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 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.