linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: omapfb: dss: Do not duplicate features data
Date: Wed, 29 Nov 2017 16:18:58 +0000	[thread overview]
Message-ID: <20171129161858.GB30740@lenoch> (raw)
In-Reply-To: <14688566-4b07-6167-914c-545948ace611@users.sourceforge.net>

On Wed, Nov 29, 2017 at 03:38:46PM +0100, SF Markus Elfring wrote:
> > As features data are read only, there is no need to allocate their
> > copy on the heap.
> …
> >  Note2: Marcus, I hope it is okay to add your Suggested-by tag.
> 
> Maybe.
> 
> >         Please let me know, if I'm wrong.
> 
> I am unsure about the view on how much I suggested such a source code adjustment.

Well, it is up to you completely. I didn't find any more relevant tag, which
neccessarily doesn't mean it is appropriate.

> A development discussion for my update suggestion “omapfb/dss: Delete an error message
> for a failed memory allocation in three functions” triggered the contribution of your idea.

I would never look at that code without looking to said patch.

> https://lkml.org/lkml/2017/11/27/919
> 
> Did you omit the general Linux kernel mailing list from your proposal intentionally?

I've never sent single mail to the general Linux kernel mailing list other than
it already was in Cc. It was write-only list decade ago and now it is not any
better :)

Best regards,
	ladis

  reply	other threads:[~2017-11-29 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 14:38 omapfb: dss: Do not duplicate features data SF Markus Elfring
2017-11-29 16:18 ` Ladislav Michl [this message]
2017-11-29 17:30 ` SF Markus Elfring

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=20171129161858.GB30740@lenoch \
    --to=ladis@linux-mips.org \
    --cc=linux-fbdev@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 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).