All of lore.kernel.org
 help / color / mirror / Atom feed
From: Debleena Sen <idebleenasen@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH v4] Staging: pi433: Fix line over 80 characters issue
Date: Tue, 5 Mar 2019 21:54:44 +0530	[thread overview]
Message-ID: <CACw+u4FnMCpiBiYPqaz3R054wm2q3Rx9q2R7S15_2+EPhJmkNA@mail.gmail.com> (raw)
In-Reply-To: <20190305074018.GA6158@kroah.com>

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

On Tue, Mar 5, 2019 at 1:10 PM Greg KH <gregkh@linuxfoundation.org> wrote:

> On Sun, Mar 03, 2019 at 02:01:36AM -0800, Debleena Sen wrote:
> > Break the line and match the indentation to remove the
> > checkpatch.pl warning:
> > WARNING: line over 80 characters
> >
> > Signed-off-by: Debleena Sen <idebleenasen@gmail.com>
> > ---
> >  drivers/staging/pi433/rf69.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
>
> What changed from the previous versions?  That information always goes
> below the --- line please.
>
> Please fix up and resend.
>
> thanks,
>
> greg k-h
>

I'm not able to find the commit.

I tried using "git reset --mixed e19b9ce" but it shows an error:

error: object e19b9ce794a8534f0ad19bfa1c60260fd74b9bb9 is a blob, not a
commit
fatal: could not parse object 'e19b9ce'

How can I recover it so that I can add the changes?

Thank you,
Debleena

[-- Attachment #2: Type: text/html, Size: 1593 bytes --]

  parent reply	other threads:[~2019-03-05 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03 10:01 [PATCH v4] Staging: pi433: Fix line over 80 characters issue Debleena Sen
2019-03-03 10:06 ` [Outreachy kernel] " Julia Lawall
2019-03-05  7:40 ` Greg KH
2019-03-05 14:00   ` Debleena Sen
2019-03-05 16:24   ` Debleena Sen [this message]
2019-03-06  9:15     ` Greg KH
2019-03-06  9:33       ` [Outreachy kernel] " Julia Lawall
     [not found]       ` <CACw+u4EWiZyqyYmuyK_5vMq+x5B-iB7-Z1JyeiT8_amOMyd3pQ@mail.gmail.com>
2019-03-06  9:46         ` Fwd: " Debleena Sen
2019-03-05 15:06 Debleena Sen

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=CACw+u4FnMCpiBiYPqaz3R054wm2q3Rx9q2R7S15_2+EPhJmkNA@mail.gmail.com \
    --to=idebleenasen@gmail.com \
    --cc=gregkh@linuxfoundation.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 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.