public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Sachin Kamat <sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Naveen Krishna Chatradhi
	<ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH 1/1] i2c: exynos5: Use reinit_completion instead of INIT_COMPLETION
Date: Tue, 5 Nov 2013 12:24:09 +0100	[thread overview]
Message-ID: <20131105112409.GA2926@katana> (raw)
In-Reply-To: <CAK9yfHyf94oTyJRRYtAiaty=AYiPXf+RQTnqdW4-q=zbvwsdtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]


> > sed will find them all.
> 
> Yes, that would do. However, since I have already found and fixed
> this, wouldn't it save
> some time and effort for Andrew if he simply applies this?

Nope, running sed with git commit -a is the same effort regardless how
many hits it produces. And it is much cleaner to just have one patch.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-11-05 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  9:27 [PATCH 1/1] i2c: exynos5: Use reinit_completion instead of INIT_COMPLETION Sachin Kamat
     [not found] ` <1383643630-5036-1-git-send-email-sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-11-05  9:38   ` Naveen Krishna Ch
2013-11-05 10:10   ` Wolfram Sang
2013-11-05 10:21     ` Sachin Kamat
     [not found]       ` <CAK9yfHwv3T6OXO59b+VeFHLU6mxn1Gw+BotOBLUukHuArZ0qig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-05 10:56         ` Wolfram Sang
2013-11-05 11:09           ` Sachin Kamat
     [not found]             ` <CAK9yfHyf94oTyJRRYtAiaty=AYiPXf+RQTnqdW4-q=zbvwsdtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-05 11:24               ` Wolfram Sang [this message]
2013-11-05 11:27                 ` Sachin Kamat

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=20131105112409.GA2926@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@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