Linux-IIO Archive on
 help / color / Atom feed
From: Renato Lui Geh <>
To: Jonathan Cameron <>
Cc: Renato Lui Geh <>,,,,,,,
Subject: Re: IIO on KernelDevDay
Date: Fri, 17 May 2019 21:43:14 -0300
Message-ID: <20190518004313.xodfmsnpac33stco@renatolg> (raw)
In-Reply-To: <>

Hi Jonathan,

Sorry for taking so long to give you an update on things.
We've been quite busy with the organizational aspects of the
event. Anyways, we're all set for KDD. We're keeping touch
with all the great fellas at Analog, who've helped us a
great bunch. They've helped us set a battle plan for
tomorrow and we're ready to put things in motion!

Adding a tiny little comment inline below replying to one of
your comments. :)

Many thanks!
Renato and everyone at KDD

On 04/16, Jonathan Cameron wrote:
>On Mon, 15 Apr 2019 19:09:48 -0300
>Renato Lui Geh <> wrote:
>> Hi Jonathan,
>Hi Renato,
>> (CC-ing linux-iio in case others would like to comment. :)
>> So some history to begin with. Since late last year, we've
>> been attempting to build a tradition of kernel contribution
>> amongst students here at the computer science department of
>> the University of São Paulo (USP). We made it "official" and
>> created a student group made out of graduate and
>> undergraduate students: FLUSP [1].
>> We started small, but as you probably know, managed to get
>> almost three drivers moved out of staging! We've been quite
>> excited with what we've achieved so far and decided to open
>> up our small group to the whole University.
>It's been great to see your activities grow!
>> Since then we've managed to get some new people involved and
>> some of their patches sent out. Recently we have received
>> quite a big influx of students interested in contributing to
>> the kernel, and so we wanted to do something big. We came up
>> with this idea for a KernelDevDay [2], in which we get a
>> bunch of us in a room and spend the whole day sending out
>> patches to a specific subsystem.
>Sounds fun :)
>> We were thinking of going with the IIO for this debut
>> version, as that's the one we've most experience with. We
>> intend on working on 5 or more specific drivers (depending
>> on the number of attendees), and our objective is to move
>> them out of staging. This event would happen on May 18
>> (that's a Saturday), with several patches sent throughout
>> the day.
>> We know that your review window is on weekends, and that
>> this might mean a high volume of patches on that day, so we
>> wanted to let you know of all this beforehand and give you
>> the time to send any suggestions or comments on all this.
>> Like if maybe you'd want us to specifically tag our patches
>> for a later batch review, and not have to deal with them all
>> at once; or have us send large patchsets as opposed to small
>> or individual patches so as to not spam you.
>Don't worry about it, but thanks for the warning.  Just send
>the patches out when they are ready to post.  Given this
>whole day sounds like a great idea, I'll see if I can be available
>that afternoon / evening UK time to give some immediate feedback.
>No promises though!

You're too kind, Jonathan. We don't want to give you any
trouble. Especially because of the significant difference
in timezones. Besides, I'm assuming we're only going to be
sending in patches to IIO late in the day, and only after
passing an internal review, so please don't waste your
weekend on us. :)
>If we are lucky there may be a few others who can help out as
>well on the day.
>> We are also aware of several problems that might turn up.
>> Like that our patches might not be accepted or reviewed on
>> the same day, which might result in a bottleneck. We plan on
>> working on multiple drivers at the same time to solve this
>> issue. We also plan on having an internal review to avoid
>> wasting your time with minor reviews. We also know that
>> you're not the only one reviewing drivers (and we obviously
>> don't expect you to review everything on the same day!), and
>> that the event being on a Saturday might be troublesome, but
>> I think what we really want is to just help out the IIO any
>> way we can. :)
>> Anyway, we'd really love to have your opinion on this.
>> Sorry for the high content email.
>Great stuff in general so I'll look forward to the outputs.
>One thing I would suggest though is to discuss potential drivers
>to look at on the list before you get started. The reason being
>that the last thing you want to happen is to:
>a) Send big changes for a driver that clash with someone elses
>   ongoing work.
>b) Work hard on a driver for hardware that is unobtainable / obsolete.
>The number of IIO drivers left in staging has shrunk, partly
>of course because of your groups efforts, so the chances of running
>into these sorts of issues is increasing!
>Also given we have a month, you can probably get some reviews of
>current driver status if that is helpful to work out where to focus.
>Keep up the good work.
>> Looking forward to hearing from you,
>> Thanks,
>> Renato
>> [1] -
>> [2] -

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 22:09 Renato Lui Geh
2019-04-16 11:51 ` Jonathan Cameron
2019-05-18  0:43   ` Renato Lui Geh [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190518004313.xodfmsnpac33stco@renatolg \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-IIO Archive on

Archives are clonable:
	git clone --mirror linux-iio/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-iio linux-iio/ \
	public-inbox-index linux-iio

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox