From: Deepak R Varma <mh12gx2825@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Sumera Priyadarsini <sylphrenadin@gmail.com>,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [Outreachy][PATCH 0/3] staging: Replace snprintf() with scnprintf()
Date: Mon, 19 Oct 2020 11:55:47 +0530 [thread overview]
Message-ID: <20201019062547.GA6451@ubuntu204> (raw)
In-Reply-To: <20201019060925.GB691366@kroah.com>
On Mon, Oct 19, 2020 at 08:09:25AM +0200, Greg KH wrote:
> On Mon, Oct 19, 2020 at 11:32:40AM +0530, Deepak R Varma wrote:
> > On Sun, Oct 18, 2020 at 07:38:57AM +0200, Greg KH wrote:
> > > On Sun, Oct 18, 2020 at 11:02:43AM +0530, Deepak R Varma wrote:
> > > > On Thu, Oct 15, 2020 at 08:21:57PM +0100, Matthew Wilcox wrote:
> > > > > On Fri, Oct 16, 2020 at 12:41:42AM +0530, Sumera Priyadarsini wrote:
> > > > > > The show() methods in device attributes should return the number of
> > > > > > bytes printed into the buffer which is the return value of scnprintf().
> > > > > > snprintf() returns the potential number of bytes that could be written
> > > > > > which may be greater than the actual length to be written.
> > > > >
> > > > > There's a big patchset just gone into 5.10 yesterday which adds a new
> > > > > sysfs_emit() for show methods. You probably want to use that instead
> > > > > of scnprintf().
> > > > >
> > > > Hello Matthew,
> > > > I am able to build my staging branch into 5.9.0-rc8 release. Can you
> > > > please suggest how can I get 5.10?
> > >
> > > Pull from Linus's tree right now, or pull from linux-next.
> >
> > Thank you Greg. I assume you are fine with patches sent from that tree
> > base.
>
> For the time up to 5.10-rc1, no, you need to work off of my
> staging-testing branch as there is no way for me to merge new stuff into
> linux-next until 5.10-rc1 comes out, sorry.
>
> The middle of the merge window is a rough time to try to get new work
> done, maintainers are not allowed to really take it. I'm trying to be
> nice and stage stuff for the outreachy developers, so please, work off
> of staging-testing for now.
Thank you Greg. I understand.
In that case, the three patches I sent yesterday were from the linux-next tree.
Will you reject those or hold back?
Deepak.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2020-10-19 6:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 19:11 [Outreachy][PATCH 0/3] staging: Replace snprintf() with scnprintf() Sumera Priyadarsini
2020-10-15 19:14 ` [Outreachy][PATCH 1/3] staging: fbtft: " Sumera Priyadarsini
2020-10-15 19:16 ` [Outreachy][PATCH 2/3] staging: fieldbus: " Sumera Priyadarsini
2020-10-23 13:03 ` Sven Van Asbroeck
2020-10-23 13:39 ` Sumera Priyadarsini
2020-10-15 19:18 ` [Outreachy][PATCH 3/3] staging: comedi: " Sumera Priyadarsini
2020-10-16 9:14 ` Ian Abbott
2020-10-16 9:36 ` Sumera Priyadarsini
2020-10-18 19:51 ` [Outreachy kernel] " Deepak R Varma
2020-10-18 20:35 ` Helen Koike
2020-10-18 21:31 ` Julia Lawall
2020-10-15 19:21 ` [Outreachy kernel] [Outreachy][PATCH 0/3] staging: " Matthew Wilcox
2020-10-16 8:24 ` Greg KH
2020-10-16 8:44 ` Sumera Priyadarsini
2020-10-18 5:32 ` Deepak R Varma
2020-10-18 5:38 ` Greg KH
2020-10-19 6:02 ` Deepak R Varma
2020-10-19 6:09 ` Greg KH
2020-10-19 6:25 ` Deepak R Varma [this message]
2020-10-19 6:59 ` Greg KH
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=20201019062547.GA6451@ubuntu204 \
--to=mh12gx2825@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sylphrenadin@gmail.com \
--cc=willy@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 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.