All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: commit reverted in staging/sm750fb
Date: Tue, 7 Apr 2015 19:38:33 +0530	[thread overview]
Message-ID: <20150407140833.GA30981@sudip-PC> (raw)
In-Reply-To: <CAOMZO5CAJLkJoq=Rrx6JJPJoR6hJscGc5gC09BgapoBNoKHKtQ@mail.gmail.com>

On Tue, Apr 07, 2015 at 11:01:57AM -0300, Fabio Estevam wrote:
> On Tue, Apr 7, 2015 at 10:56 AM, Sudip Mukherjee
> <sudipm.mukherjee@gmail.com> wrote:
> > Hi Greg,
> > I saw that you have reveretd one commit
> > <6ad6b5ed3e2472b399b567a2f036006bf25df467>
> > "Staging: sm750fb: Fix C99 Comments" in staging/sm750fb.
> > I was trying to search for that patch, but it seems I am not able to
> > find that in my personal mails nor in lkml. can you please let me know
> > when it was sent..
> 
> Just run 'git show 6ad6b5ed3e247' in linux-next and you can see such commit.
I have already seen the patch. But being the maintainer of that driver
i hold myself responsible for missing a new file creation in a patch.
So i was trying to search for that patch in my mails and also in lkml,
but i could not find it, so thought of mailing and asking. :(

regards
sudip

> 
> Regards,
> 
> Fabio Estevam

  reply	other threads:[~2015-04-07 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 13:56 commit reverted in staging/sm750fb Sudip Mukherjee
2015-04-07 14:01 ` Fabio Estevam
2015-04-07 14:08   ` Sudip Mukherjee [this message]
2015-04-07 14:24     ` Fabio Estevam
2015-04-07 14:31       ` Sudip Mukherjee
2015-04-07 14:34 ` Greg KH
2015-04-07 15:01   ` Sudip Mukherjee
2015-04-07 15:07     ` 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=20150407140833.GA30981@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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 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.