From: Julia Lawall <julia.lawall@lip6.fr>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
arnaud.patard@rtp-net.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Re: [PATCH] staging: xgifb: function prototype argument should have an identifier name
Date: Fri, 24 Feb 2017 17:48:48 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702241748000.3089@hadrien> (raw)
In-Reply-To: <CA+XqjF_sihk6_UhgLzUH6FVSFMu02Vadp1tjatQft-UJ14SJeA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On Fri, 24 Feb 2017, Arushi Singhal wrote:
>
>
> On Fri, Feb 24, 2017 at 10:01 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> On Wed, Feb 22, 2017 at 04:49:19PM +0530, Arushi Singhal wrote:
> > function prototype arguments like 'struct vb_device_info
> *','unsigned
> > long' etc. should have an identifier name.
> >
> > Signed-off-by: Arushi Singhal
> <arushisinghal19971997@gmail.com>
> > ---
> > Changes in v3:
> > - By mistake one irrelevant line was added which is removed
> in this
> > patch.
> > - write the changes done in previous version in correct
> format.
> > - make the commit subject more relevant and accurate.
>
> This patch doesn't apply to my tree at all :(
>
> Why this is so?
Maybe someone else made a change on the same lines as yours. Check that
your tree is up to date.
julia
> thanks
> Arushi
> sorry,
>
> greg k-h
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visithttps://groups.google.com/d/msgid/outreachy-kernel/CA%2BXqjF_sihk6_UhgLzUH6
> FVSFMu02Vadp1tjatQft-UJ14SJeA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
next prev parent reply other threads:[~2017-02-24 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 11:19 Arushi Singhal
2017-02-24 16:31 ` Greg Kroah-Hartman
[not found] ` <CA+XqjF_sihk6_UhgLzUH6FVSFMu02Vadp1tjatQft-UJ14SJeA@mail.gmail.com>
2017-02-24 16:48 ` Julia Lawall [this message]
[not found] ` <CA+XqjF91bd_er+idvUBPZCTYFHaxF6Mgf1oQ6vTz9gmk6ggC6Q@mail.gmail.com>
2017-02-25 6:34 ` [Outreachy kernel] " Julia Lawall
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=alpine.DEB.2.20.1702241748000.3089@hadrien \
--to=julia.lawall@lip6.fr \
--cc=arnaud.patard@rtp-net.org \
--cc=arushisinghal19971997@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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
all inboxes | Powered by JetHome®