lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 20 Sep 2021 14:32:21 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     "Fabio M. De Francesco" <fmdefrancesco@...il.com>
Cc:     Saurav Girepunje <saurav.girepunje@...il.com>,
        Greg KH <gregkh@...uxfoundation.org>,
        saurav.girepunje@...mail.com, Larry.Finger@...inger.net,
        phil@...lpotter.co.uk, straube.linux@...il.com,
        linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: r8188eu: core: remove the function
 power_saving_wk_hdl

On Mon, Sep 20, 2021 at 01:13:54PM +0200, Fabio M. De Francesco wrote:
> On Monday, September 20, 2021 12:36:06 PM CEST Greg KH wrote:
> > On Sat, Sep 18, 2021 at 10:52:50PM +0530, Saurav Girepunje wrote:
> > > 
> > > 
> > > On 13/09/21 9:48 pm, Greg KH wrote:
> > > > On Fri, Sep 10, 2021 at 11:24:39PM +0530, Saurav Girepunje wrote:
> > > > > Remove the function power_saving_wk_hdl() as it just calling
> > > > > the rtw_ps_processor().Instead of power_saving_wk_hdl() call directly
> > > > > rtw_ps_processor().
> > > > > 
> > > > > Signed-off-by: Saurav Girepunje <saurav.girepunje@...il.com>
> > > >
> > > > []
> > > > 
> > > > Also does not apply to my tree.  Please rebase against my staging-next
> > > > branch and resend.
> > > > 
> > > > thanks,
> > > > 
> > > > greg k-h
> > > > 
> > > 
> > > Hi Greg,
> > > 
> > > I always do rebase against your staging-testing branch. Can you help me 
> to
> > > understand.When we need to rebase on staging-next. Do we always need to
> > > rebase against staging-next..!
> > 
> > Yes, you should.  When you are working on code that lots of other people
> > are working on, there will be conflicts like this, and you just need to
> > stay on top of it.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> Sorry, Greg. I'm confused... :(
> 
> As far as I know, everyone here make patches for staging-testing.

Nope.  It's only you.

The staging-testing branch can be rebased so maybe you will write a
patch against something that never makes it to staging-next and everyone
will be puzzled.

That's unlikely to happen and we won't be puzzled for long because we
try not to invest too much time wondering why patches don't apply.

regards,
dan carpenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ