From: Sutharsan <srmt@cypress.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-usb@vger.kernel.org, david.cross@cypress.com
Subject: Re: Staging: Westbridge: fix EXPORT_SYMBOL errors reported by checkpatch.pl
Date: Mon, 31 Jan 2011 14:07:33 -0800 [thread overview]
Message-ID: <1296511653.1772.30.camel@sutharsan-laptop> (raw)
In-Reply-To: <20110131213140.GA1671@kroah.com>
On Mon, 2011-01-31 at 13:31 -0800, Greg KH wrote:
> On Tue, Jan 25, 2011 at 09:03:22PM -0800, Sutharsan wrote:
> > From: Sutharsan Ramamoorthy <srmt@cypress.com>
> >
> > This patch fixes errors reported by checkpatch.pl
> > in westbridge device controller driver in the staging tree.
> > File containing EXPORT_SYMBOL() macros for all the APIs exported
> > by the westbridge software has been removed. EXPORT_SYMBOL()
> > macros are added after the corresponding function definitions.
> >
> > Signed-off-by: Sutharsan Ramamoorthy <srmt@cypress.com>
>
> I've already applied this patch, and you should have gotten the "this
> patch has been applied" email, right?
>
> So why was it resent?
I resent adding '[PATCH]' tag which was missing in my first submission.
Please ignore this.
>
> confused,
>
> greg k-h
>
---------------------------------------------------------------
This message and any attachments may contain Cypress (or its
subsidiaries) confidential information. If it has been received
in error, please advise the sender and immediately delete this
message.
---------------------------------------------------------------
next prev parent reply other threads:[~2011-01-31 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 5:03 Sutharsan
2011-01-31 21:31 ` Greg KH
2011-01-31 22:07 ` Sutharsan [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-20 1:31 [PATCH] Westbridge software module, fixes " Sutharsan Ramamoorthy
2011-01-21 20:40 ` Staging: Westbridge: fix EXPORT_SYMBOL " Greg KH
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=1296511653.1772.30.camel@sutharsan-laptop \
--to=srmt@cypress.com \
--cc=david.cross@cypress.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®