All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: bankarsandhya512@gmail.com
Cc: outreachy-kernel@googlegroups.com
Subject: claiming tasks, upstream & endianess work "OutreachyTasks" by sandhyabankar]
Date: Fri, 23 Sep 2016 09:23:47 -0700	[thread overview]
Message-ID: <20160923162346.GA6861@d830.WORKGROUP> (raw)

----- Forwarded message from wiki@kernelnewbies.org -----

Date: Fri, 23 Sep 2016 15:53:25 -0000
From: wiki@kernelnewbies.org
To: wiki@kernelnewbies.org
Subject: [Linux Kernel Newbies] Update of "OutreachyTasks" by sandhyabankar

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Linux Kernel Newbies" for change notification.

The following page has been changed by sandhyabankar:
http://kernelnewbies.org/OutreachyTasks

The comment on the change is:
updating tasks.

  == Ongoing Tasks from round 13 =+  * Task name: Fix endianness warnings in drivers/iio/accel/mma7660 code
+
+  * Claimed by: Sandhya Bankar
+
+  * Date claimed: 23 Sep 2016
+
+
+  * Links to patch submissions: http://marc.info/?l=linux-iio&m\x147457709326372&w=2
+  * Current status:WIP
+  * Task name: Fix endianness warnings in drivers/iio/adc/max1027 code
+
+  * Claimed by: Sandhya Bankar
+
+  * Date claimed: 23 Sep 2016
+
+
+  * Links to patch submissions: http://marc.info/?l=linux-iio&m\x147464417710596&w=2
+

Hi Sandhya,

'cc-ing outreachy group...

I see that you got your kernelnewbies access working.  Great!

The sparse warnings in these drivers were not related to Endianess,
so they don't need to be claimed here.  The IIO claims here will only be
for Coding Task 2 - IIO Endianess work.

I do see that you've submitted the patches upstream already, so you'll
need to follow up on those as needed with the IIO maintainer.

Gentle reminder - try to stick to drivers/staging/ patches. 

The exception is for IIO Coding Task 2 Endianess issues. We are not
intending to go upstream in general.  That is, we won't go looking
for sparse and checkpatch fixes to do upstream now.

Let me know if this isn't clear.  You are out front on some of this, so
if it's not clear to you, it probably won't be clear to others, and I
want to fix that.

Thanks,
alisons



                 reply	other threads:[~2016-09-23 16:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160923162346.GA6861@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=bankarsandhya512@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 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.