linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: b.zolnierkie@samsung.com, linux-fbdev@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	corbet@lwn.net, rdunlap@infradead.org, daniel@ffwll.ch,
	yuanmingbuaa@gmail.com, w@1wt.eu, nopitydays@gmail.com,
	zhangyunhai@nsfocus.com, luto@amacapital.net,
	torvalds@linux-foundation.org
Subject: Re: [PATCH] docs: fb:  Remove scrollback option
Date: Tue, 15 Sep 2020 19:21:57 +0530	[thread overview]
Message-ID: <20200915135157.GB30746@Gentoo> (raw)
In-Reply-To: <20200915134127.GA873393@kroah.com>

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

On 15:41 Tue 15 Sep 2020, Greg KH wrote:
>On Tue, Sep 15, 2020 at 06:57:36PM +0530, Bhaskar Chowdhury wrote:
>> 
>> This patch remove the scrollback option under boot option.
>> Plus readjust the numbers for the options in that section.
>> 
>> This is the effect of these commits:
>> 
>> 973c096(vgacon: remove software scrollback support)
>> 5014547(fbcon: remove soft scrollback code)
>
>The kernel documentation file:
>	https://www.kernel.org/doc/html/latest/process/submitting-patches.html

>in section 2, describes how to show git ids within changelog text
>properly (the number of characters and the rest.)

Okay, I have only included 7 instead of 12 ... :( 
>
>Can you fix this up and resend?

Certain.
>
>And this is a v2 patch, right?  Always document what changed from
>previous patches below the --- line, as the above link asks for.

No ...no Greg ..  I shall be sending afresh ...kindly ignore all the previous and
this one too.. 

>
>thanks,
>
>greg k-h

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-09-15 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 13:27 [PATCH] docs: fb: Remove scrollback option Bhaskar Chowdhury
2020-09-15 13:41 ` Greg KH
2020-09-15 13:51   ` Bhaskar Chowdhury [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=20200915135157.GB30746@Gentoo \
    --to=unixbhaskar@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=corbet@lwn.net \
    --cc=daniel@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=nopitydays@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    --cc=yuanmingbuaa@gmail.com \
    --cc=zhangyunhai@nsfocus.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).