All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	Rich Felker <dalias@libc.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] matroxfb: add Matrox MGA-G200eW board support
Date: Mon, 27 Jan 2020 10:40:24 +0000	[thread overview]
Message-ID: <CAMuHMdU32gF89zz86WH3AqkoPK7hdSjWMexJ1aLU9woe0qF0YA@mail.gmail.com> (raw)
In-Reply-To: <20200126071724.GA3520745@kroah.com>

Hi Greg,

On Sun, Jan 26, 2020 at 8:44 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Sat, Jan 25, 2020 at 02:55:06PM -0500, Rich Felker wrote:
> > Signed-off-by: Rich Felker <dalias@libc.org>
> > --
>
> I know I don't accept patches without any changelog text, don't know
> about other subsystem maintainers...

FTR, I do, iff the one-line summary says everything that needs to be said.

What's the point in writing a full paragraph like:

   Currently the foo driver does not support the bar device.
   As users may want to use the bar device, it makes perfect sense
   to add support for the bar device to the foo driver.
   Hence add support for the bar device to the foo driver.

if this doesn't add any value on top of the one-line summary?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	Rich Felker <dalias@libc.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] matroxfb: add Matrox MGA-G200eW board support
Date: Mon, 27 Jan 2020 11:40:24 +0100	[thread overview]
Message-ID: <CAMuHMdU32gF89zz86WH3AqkoPK7hdSjWMexJ1aLU9woe0qF0YA@mail.gmail.com> (raw)
In-Reply-To: <20200126071724.GA3520745@kroah.com>

Hi Greg,

On Sun, Jan 26, 2020 at 8:44 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Sat, Jan 25, 2020 at 02:55:06PM -0500, Rich Felker wrote:
> > Signed-off-by: Rich Felker <dalias@libc.org>
> > --
>
> I know I don't accept patches without any changelog text, don't know
> about other subsystem maintainers...

FTR, I do, iff the one-line summary says everything that needs to be said.

What's the point in writing a full paragraph like:

   Currently the foo driver does not support the bar device.
   As users may want to use the bar device, it makes perfect sense
   to add support for the bar device to the foo driver.
   Hence add support for the bar device to the foo driver.

if this doesn't add any value on top of the one-line summary?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-01-27 10:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200125195511eucas1p1d8326b54a4775038cb8b804078afcc19@eucas1p1.samsung.com>
2020-01-25 19:55 ` [PATCH] matroxfb: add Matrox MGA-G200eW board support Rich Felker
2020-01-25 19:55   ` Rich Felker
2020-01-26  7:17   ` Greg Kroah-Hartman
2020-01-26  7:17     ` Greg Kroah-Hartman
2020-01-27 10:40     ` Geert Uytterhoeven [this message]
2020-01-27 10:40       ` Geert Uytterhoeven
2020-01-27 11:59       ` Ville Syrjälä
2020-01-27 11:59         ` Ville Syrjälä
2020-01-27  7:36   ` Thomas Zimmermann
2020-01-27  7:36     ` Thomas Zimmermann
2020-01-28 18:58     ` Rich Felker
2020-01-28 18:58       ` Rich Felker
2020-01-29  7:20       ` Thomas Zimmermann
2020-01-29  7:20         ` Thomas Zimmermann
2020-03-02 15:42   ` Bartlomiej Zolnierkiewicz
2020-03-02 15:42     ` Bartlomiej Zolnierkiewicz

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=CAMuHMdU32gF89zz86WH3AqkoPK7hdSjWMexJ1aLU9woe0qF0YA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=dalias@libc.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.