From: Dan Carpenter <dan.carpenter@oracle.com>
To: Anders Fridlund <anders.fridlund@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-fbdev@vger.kernel.org, teddy.wang@siliconmotion.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: sm750fb: ddk750_dvi.h: Fix brace coding style issue
Date: Fri, 10 Jul 2015 07:03:29 +0000 [thread overview]
Message-ID: <20150710070329.GT4341@mwanda> (raw)
In-Reply-To: <CAOcrEa6gTQCwovGEGw-pF-LECfr-nFaWJ=A42+qKA6e+yr=0UA@mail.gmail.com>
On Fri, Jul 10, 2015 at 08:56:05AM +0200, Anders Fridlund wrote:
> Sorry, for that. Do I need to re-submit the patch(es), or should I
> only change it for future patches?
For future patches.
regards,
dan carpenter
prev parent reply other threads:[~2015-07-10 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 12:45 [PATCH] Staging: sm750fb: ddk750_dvi.h: Fix brace coding style issue anders.fridlund
2015-07-10 5:45 ` Sudip Mukherjee
2015-07-10 6:56 ` Anders Fridlund
2015-07-10 7:03 ` Dan Carpenter [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=20150710070329.GT4341@mwanda \
--to=dan.carpenter@oracle.com \
--cc=anders.fridlund@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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 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).