linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
	Dejin Zheng <zhengdejin5@gmail.com>,
	linux-i2c <linux-i2c@vger.kernel.org>,
	lkp@lists.01.org
Subject: Re: [PATCH v1] i2c: busses: convert to devm_platform_get_and_ioremap_resource
Date: Mon, 20 Apr 2020 11:57:15 +0200	[thread overview]
Message-ID: <20200420095715.GB2094@ninjato> (raw)
In-Reply-To: <CAHp75VeGNV-Jsyu1ev843GzBuJqwojfDcbC5H9MJokurrQLjjg@mail.gmail.com>

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


> > > 6. Fix ioremap(..., 0) [size = 0] across architectures, now some return NULL,
> > >    some return address, some may even have leaks
> >
> > This sounds more useful to me. Would be great if you have interest.
> 
> But it much more advanced :-) Complete dive into the kernel guts.

Well, learning by doing :) Dejin seems interested...


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

  reply	other threads:[~2020-04-20  9:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 13:48 [PATCH v1] i2c: busses: convert to devm_platform_get_and_ioremap_resource Dejin Zheng
2020-04-15 10:21 ` Wolfram Sang
2020-04-15 16:07   ` Dejin Zheng
2020-04-17 20:46     ` Andy Shevchenko
2020-04-18  4:06       ` Dejin Zheng
2020-04-18 13:00         ` Andy Shevchenko
2020-04-18 17:05           ` Dejin Zheng
2020-04-19 16:36           ` Dejin Zheng
2020-04-20  9:43             ` Wolfram Sang
2020-04-20  9:47               ` Andy Shevchenko
2020-04-20  9:57                 ` Wolfram Sang [this message]
2020-04-20 14:36                   ` Dejin Zheng
2020-04-21  1:24                 ` [LKP] " Philip Li
  -- strict thread matches above, loose matches on Subject: below --
2020-04-17 20:36 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=20200420095715.GB2094@ninjato \
    --to=wsa@the-dreams.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=zhengdejin5@gmail.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).