mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <ahmad@a3f.at>
Subject: [PATCH 1/2] Documentation: devel: project-ideas: update after DSA framework addition
Date: Fri,  5 Aug 2022 06:09:26 +0200	[thread overview]
Message-ID: <20220805040927.1658824-1-ahmad@a3f.at> (raw)

We have a proper abstraction for switches now, so drop this idea
from the list.

Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
---
 Documentation/devel/project-ideas.rst | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/Documentation/devel/project-ideas.rst b/Documentation/devel/project-ideas.rst
index a3643298ab08..e49bfa6ca4da 100644
--- a/Documentation/devel/project-ideas.rst
+++ b/Documentation/devel/project-ideas.rst
@@ -20,10 +20,8 @@ For GSoC, following barebox developers are mentoring:
   - Rouven Czerwinski (IRC: ``Emantor``)
 
 This list can be edited and extended by sending patches to the mailing list.
-Other interesting ideas: Support for new file systems (EROFS, extfat, btrfs).
-Switch device framework (currently scripts write into a ``/dev/switch`` file
-to configure passthrough), Improvements for barebox-efi (e.g. as a coreboot
-payload), ... etc.
+Other interesting ideas: Support for new file systems (EROFS, extfat, btrfs),
+Improvements for barebox-efi (e.g. as a coreboot payload), ... etc.
 
 Ideas listed below should contain a title, description, expected outcomes,
 skills (and HW if any) required and a difficulty rating.
-- 
2.34.1




             reply	other threads:[~2022-08-05  4:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  4:09 Ahmad Fatoum [this message]
2022-08-05  4:09 ` [PATCH 2/2] Documentation: devel: porting: bring up to date Ahmad Fatoum
2022-08-05  7:29   ` Ulrich Ölmann
2022-08-05  6:53 ` [PATCH 1/2] Documentation: devel: project-ideas: update after DSA framework addition Ulrich Ölmann
2022-08-08 13:07 ` Sascha Hauer

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=20220805040927.1658824-1-ahmad@a3f.at \
    --to=ahmad@a3f.at \
    --cc=barebox@lists.infradead.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